{
"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:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
Intro:Hello everybody. My name is Fera. I want to share this project with you for free. I made it myself from scratches once again. Please hit "thanks" button, rate this thread 5-star, or consider donating me to support my work. (Thanks!)
What's in:FeraDroid Engine (simply FDE) - an All-in-One ultimate optimizer for all devices on Android OS. No settings/customization and rest 'headache' - all parameters are individual for EVERY device depending on it's hardware/software characteristics. All parameters are very balanced - you may gain performance without increase of power consumption AND reduce power consumption without losing performance. FDE is totally compatible with very wide range of devices and Android versions.
Installation requirements:Supported CPU arch's:
ARMv7 (armeabi-v7a) (32bit)
ARMv8 (arm64-v8a) (64bit)
x64bit (x86_64)
Supported Android OS versions:
4.1 and higher
Detailed tech description:FDE - very universal Android OS optimizer. Very wide-range settings of OS and Linux kernel are configured, still being cross-platform utility, maximally compatible with all devices. This means that it doesn't have any dirty hacks/hardcore and 3rd part binaries (except busybox) & config files. FDE applies configurations depending on It's hardware and software, so that in the end every device is configured individually.
New unique method of execution - all required FDE components are loaded directly to RAM and executed from there. System partitions are remounted RW only once while installation. This means high speed (the worst RAM will have at least ~500MB/s of I/O speed), no power consumption (no NAND memory I/O occurs) and security (system partitions are in read-only state). Also new-gen FDE is synced with OS boot process - so tweaks will be applied in correct time. All system partitions are trimmed and checked for errors after every OS boot with FDE onboard. Universal installer automatically detects what ROOT-method you use and how to auto-start. Finally, FDE is not only about optimization. It's also about security and feature-enabler.
See compacted list of most included features HERE.
Artificial Intelligence:
As you may notice from the name "FDE.AI" - can tell us that it has real AI inside. AI will learn how do you use your device, check out current usage scenario and adapt some system parameters real time to give you best usage experience. Details HERE.
Why to optimize?First of all to make you happy with your device, to make it live longer & be snappy. Another reason is garbage. WTF? Yes. There is a world problem of e-garbage utilization, especially electronic devices & their toxic stuff like batteries..etc.. I'm not against progress - I'm against the selling politics of corporations, which add features slowly, to make people buy them. I'd say OKAY if it wasn't harmful, but in fact Africa became a toxic garbage continent - they need somewhere to put retarded e-devices & that's sad. It costs them cheaper to move toxic garbage to another country, rather then properly utilize it. You may say, how FDE can help with that, are you mad bro? Well, I hope that if you install FDE on your device, you'd use it for longer time, because of all optimizations. So that it will make you happy & you won't change it too frequent, in fact possibly reducing the amount of e-garbage. Thanks.
Installation:
WARNING! Don't use any other All-in-One tweakers or things may get much worse! I warned you!
Make a backup just in case something goes wrong.
Download latest version of FDE and install it via custom recovery OR add zip in modules list if you are using Magisk systemless root.
After OS boot, you will get vibration and a log file /sdcard/Android/fde.txt will be created if FDE worked OK.
If you want to uninstall FDE simply remove module from Magisk Manager if you are on Magisk OR flash this zip in custom recovery.
Download:
FDE.AI-v7.3-20200127
About FDE APK
FAQ
Related Videos
Join my group in Telegram for 24/7 support.
Join my Facebook group.
Thread at 4PDA.
Fan-art
Thanks to all guys, who contributed, helped, tested my work.. You all are wonderful, amazing, smart, super cool, beautiful people!
Consider donating me to support my project if you like it. Thanks!
XDA:DevDB Information
FDE.AI - Ultimate Android Optimizer, Tool/Utility for all devices (see above for details)
Contributors
FeraVolt
Version Information
Status: Stable
Current Stable Version: v8.0
Created 2019-03-10
Last Updated 2020-01-27
FDE.AI FAQ
Will it work on this or that device?
It will work on any device which runs Android OS.
Will it work along with this or that tweak/optimizer?
NO. Don't use any other All-in-One tweakers or things may get much worse!
Can I use this on custom kernel?
Yes, why not? It will work even better on custom kernel.
Does FDE has any configuration/logs?
No configurations. This is "flash & forget" optimizer. It will configure your system depending on you hardware/software automatically & individually. Log is available in /sdcard/Android/fde.txt
Is it worth to try FDE if I have a powerful flagship?
Yes, sure. FDE not only gives performance, but also increases power-saving.
Is there any difference between zip from Magisk module repo and zip provided here?
The difference is only in installer - zip provided here is universal, while one in Magisk repo is for Magisk root only.
I have ROOT, but don't have recovery. Can I do something?
You may try to install FDE via Flashfire app.
I have ROOT - not Magisk, and not SuperSU, and I don't have init.d support. What to do?
Try to emulate init.d support with app like Universal_Init.d_Support or similar.
Installation was successful, but no vibration. What does this mean?
Try to reboot device. Wait for a minute or two more. Maybe it will work, but a little later than expected. Also check for /sdcard/Android/fde.txt file. If still no luck, try to update your ROOT method (Magisk preferred). If you do have log and it says "all good" - then don't worry at all. Some rare devices doesn't support vibrations triggered by script. If still not working, read THIS post.
Do I need busybox?
No, FDE has a built-in one already. But if you already have one - they will not conflict.
Are project treble ROMs supported?
YES.
Flashed fine, but can't find icon for FDE. Huh?
This is not an Android apk and it has no interface yet.
Can I flash FDE right after ROM installation?
NO. Boot ROM first, then install FDE.
AI says '...turbo' is not supported. What can i do to make it work?
You may try to install another custom kernel. Those features are kernel dependent.
It's running fine, but i got a problem...
FDE.AI is under active development. Please attach any useful information such as log/screenshot, name of your device, ROM/recovery version. I am developer of FDE and I will help you to figure out the problem.
Nice mod, please check your git
Where is the download link???
来自我的 SM-G920F 上的 Tapatalk
There is a 'downloads' tab over main post
FeraVolt said:
There is a 'downloads' tab over main post
Click to expand...
Click to collapse
Error executing update-binary
Here is zip with fixed recovery installation. Forgot ';' in script...
No log file for me
I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1
russia101 said:
No log file for me
Click to expand...
Click to collapse
kioshio said:
I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1
Click to expand...
Click to collapse
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..
FeraVolt said:
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..
Click to expand...
Click to collapse
I'm using a s3 LTE and I'm currently on marshmallow 6.0.1
No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?
Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk
ChavitoArg said:
Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk
Click to expand...
Click to collapse
Yes..it's working on your device fine. Do you notice any improvement? In case of high-end devices, most noticable should be a battery consumption decrease.
Will provide uninstaller asap.
hipocrazy said:
No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?
Click to expand...
Click to collapse
Yes..via terminal emulator type:
su
sh /system/engine/as.sh
sh /system/engine/feradroid.sh
Then recheck log file..
FeraDroid-Engine-v0.19-beta2
FeraDroid-Engine-v0.19-beta2
Changes captured:
https://github.com/feravolt/FeraDroid-Engine/commits/master
Manuall FDE run
Here is a little instruction in case you couldn't install FDE on your device. Recovery doesn't install it well..or..FDE doen't autostart or you just don't have a recovery for your device (as in my case with china noname phone).
So:
-> Download latest FDE zip and extract it.
-> With any root explorer copy engine folder to /system/
-> Set 777 (check all tabs) permissions to whole engine folder and what is in there and in every folder content
-> Then get 'Terminal Emulator' app from Google Play store, run it and type:
Code:
su
-> Grant root permission then type:
Code:
sh /engine/as.sh
-> After that reboot your device and in 2 minutes, check log file on path: /sdcard/Android/FDE.txt
-> If there is no FDE.txt log then open Terminal Emulator again and type:
Code:
su
sh /system/engine/feradroid.sh
-> Wait it's completion, then check log file again. If it exists, please send it to me to deal with autostart issue for your device. You should run theese two commands every time you reboot your device..
Hope this will help you and you will be happy to see your device runnign fast. :fingers-crossed:
Log file
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment FDE.txt
Click to expand...
Click to collapse
init.d start
russia101 said:
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment 3598637
Click to expand...
Click to collapse
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse
FeraVolt said:
russia101 said:
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse
Ok did what you said and it looks Like everything works
View attachment FDE.txt
Click to expand...
Click to collapse
Related
{
"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"
}
OMNIROMUNOFFICIAL
He guys. I managed to find the time to port Omni to the z5c. Since it compiled, booted and works well (except camera) I thought I would upload to share. My goal being that we would have greater choices available adding to Stock, CM and AOSP roms. Note: This is not a developer thread. I'm just sharing this because it worked and others might be interested.
About Omni:
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality. https://omnirom.org/
BIG THANKS to...
@humberos - for creating the first omni device tree (that I know of) for the kitakami family. (my suzuran dev tree is largely his work)
@CTXz - for all the work he and the kitakamy dev team have done/will do for CM that will find its way in to the omni flavour of aosp.
@superR - I used his kitchen to make the zip file with sparse dat .img
The Sonyxperiadev team for releasing their sources to the public
The good..
Compiled with latest camera and vendor blobs provided by Sonyxperiadev.
Full working omni features
- Comes with latest TWRP packed in the kernel
- Advanced reboot menu - boot directly in to twrp or boot-loader, or reboot and hold up when led turns purple)
- Omni switch
-Advanced power menu (like kernel auditor)
The not so good..
Camera is slow.
- Colours are inverted on screen for main camera but pictures are fine in photo viewer.
- Colours are fine on screen for front camera but inverted heavy blue tinge in photo viewer.
Security in settings F/C (there is no trustzone for CM yet, when they reverse sonys binary and include it in their code I will kang it )
No fingerprint detection/ firmware (yet - this will be reversed from sony at some point as well.)
-Bluetooth reported to have the same limited functionality as AOSP.
-Root: The ramdisk.img patcher within systemless SU installer is detecting that Omniboot.img is already patched/rooted when its not, so aborts, thus at this stage we cant get full root. (Im working on this)
If anyone is interested in building Omnirom for the z5c let me know and Ill push my device tree and provide a link.
Here is the twrp installable zip for omni. Do NOT install this on another device other then the E5823
Do a factory reset/full wipe in twrp before you install. Make sure wou have GAPS and the latest SU zips ready to go as neither are included.
https://mega.nz/#!kkZRTb5Z!i96cGUNUztTAATQ8mkkv0ivcQI9aOqErZNjgVqNFoAE
Enjoy.
Kernel source is:
https://github.com/omnirom/android_kernel_sony_msm.git
Device tree/s :
https://github.com/joeisgood99/TWRP_device_sony_Omni-suzuran_MM.git
https://github.com/omnirom/
Reserved
wow finally,gonna transfer from cm to it
EDIT:no way to dirty flash from cm,android.phone will crash,will do clean flash.Camera seems better than cm one,keep going!
Really thank you! Will try soon!
Not sent by me!
Best of luck for your project and thank you!
Sent from my E5803 using XDA-Developers mobile app
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Edit : deleted duplicate post.
mangusmeister said:
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Click to expand...
Click to collapse
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Awesome work mate! Always good to have another ROM to choose from
Joeisgood99 said:
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Click to expand...
Click to collapse
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
mangusmeister said:
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
Click to expand...
Click to collapse
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Joeisgood99 said:
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Click to expand...
Click to collapse
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
Click to expand...
Click to collapse
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Does Bluetooth work?
civicsr2cool said:
Does Bluetooth work?
Click to expand...
Click to collapse
Same errors as in cm13.
mangusmeister said:
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
Click to expand...
Click to collapse
LolaPalocz said:
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Click to expand...
Click to collapse
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Joeisgood99 said:
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Click to expand...
Click to collapse
Good luck!!!
Got time to do my own testing with SU.2.7.1
The error Im getting is that su installer detects that the stock omni boot.img is already su patched....
Stay tuned.
LightningROM for the SM-T713/SM-T719/SM-T813/T819 - v1.0
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Lightning ROM is for the SM-T713, SM-T719, SM-T813, and SM-T819 designed to make the device faster and last longer on a single charge, while also getting rid of toasters embedded within your tablet.
Screenshots
{
"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"
}
Features
AROMA Installer included, so you can choose what you want and what you don't
Based from Odexed 6.0.1 XAR firmware (wifi variants) and 6.0.1 BTU/AUT firmware (cellular variants)
Mildly debloated
Build.prop tweaks
Su.d support
Compatible with Xposed
Kernel without dm-verity or force-encrypt by @ashyx included
Prerequisites
Any galaxy tab s2 2016 variant - T713/T719/T813/T819
Install TWRP 3.0.2 from here
FRP MUST BE OFF by going to Settings>About Tablet and tapping "Build Number" 10 times, then going to Settings>Developer Options and turning ON OEM Unlock.
You should optimally have some experience flashing ROMs, and if not, follow the below instructions VERY carefully.
Installing
Follow in order:
1) Make a backup of your device in TWRP (Optional)
2) In TWRP, select "Wipe" and then select "Advanced Wipe" and wipe the following:
-System
-Cache
-Dalvik/ART cache
-Data
-Internal Storage (do not wipe internal storage if you put the ROM on your internal sd!)
3) In TWRP, go to "Install" and navigate to where you saved the ROM zip
NOTE: On some devices the touchscreen does not work in the AROMA installer. On these devices, it has been reported that using the volume/power buttons to control the installer is possible.
4) Flash the ZIP
5) Reboot system
6) Enjoy! (First boot WILL bootloop ONE time, do not freak out)
Bugs
Red = High Priority, Yellow = Medium Priority, Green = Low Priority
ADB doesn't work (kernel bug, as far as I know)
9.7inch Tab S2 AROMA touchscreen not working; volume and power buttons must be used on those devices
Downloads
LightningROM T713 v1.0
LightningROM T813 v1.0
LightningROM T819 v1.0 (fixed)
LightningROM T719 v1.0 (fixed)
Github: https://github.com/Lightn1ng/LightningROM
WiFi Fix
If you flash the ROM and WiFi isn't working, flash this ZIP:
T713 WIFI FIX
T813 WIFI FIX
T819 WIFI FIX
WiFi fix for T819 and T719 coming soon.
Thanks
@ashyx - Kernel and TWRP
@pvsgh - Some ROM kitchen help
@DeeXii - Stock firmware for base
@Tkkg1994 - update-binary and update-binary-installer
@Chainfire - SuperSU
@SuperR. - ROM kitchen
ROM STATUS: Stable
Changelog:
v1.0:
-> ROM is now fully stable! (I hope)
-> AROMA Installer allows you to choose things you want to install and things you don't - while installing the ROM!
07-19-16:
-First Build
RESERVED
Congrats! I haven't rooted my 713 yet, but now I have more motivation to get it done. Once I'm rooted, I'll try this baby.
Windsor1959 said:
Congrats! I haven't rooted my 713 yet, but now I have more motivation to get it done. Once I'm rooted, I'll try this baby.
Click to expand...
Click to collapse
You don't need to root just install TWRP and flash the ROM. let me know if you need more precise instructions.
be sure to disable oem unlocking first!
Thanks for sharing this rom. I know parts of it gave you fits. Downloading now and well flash later tonight
Sent from my SM-T713 using Tapatalk
ElAguila said:
Thanks for sharing this rom. I know parts of it gave you fits. Downloading now and well flash later tonight
Sent from my SM-T713 using Tapatalk
Click to expand...
Click to collapse
Let me know how it goes.
I have flashed TWRP and the boot.img as well. I'm now downloading your ROM. One question: does your ROM have adaptive storage enabled, or will I need to repeat the little process you told me about in another thread? Thanks for all your work!
Windsor1959 said:
I have flashed TWRP and the boot.img as well. I'm now downloading your ROM. One question: does your ROM have adaptive storage enabled, or will I need to repeat the little process you told me about in another thread? Thanks for all your work!
Click to expand...
Click to collapse
The process can be different for different SDs, so I couldn't include it. The link I gave you in the other thread will still work. Keep me posted! :highfive:
Lightn1ng said:
The process can be different for different SDs, so I couldn't include it. The link I gave you in the other thread will still work. Keep me posted! :highfive:
Click to expand...
Click to collapse
Okay. Your ROM is Installed! I have run into one glitch. I am trying to switch my SD card to adaptive storage, like I did before. This time, when I type "adb shell", I get: error. Device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try adb-kill-server if that seems wrong. " I tried that. No luck. Any suggestions? Thanks.
Windsor1959 said:
Okay. Your ROM is Installed! I have run into one glitch. I am trying to switch my SD card to adaptive storage, like I did before. This time, when I type "adb shell", I get: error. Device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try adb-kill-server if that seems wrong. " I tried that. No luck. Any suggestions? Thanks.
Click to expand...
Click to collapse
This is a bug with the kernel, that's not my kernel so I can't fix it. That said, you can get a terminal emulator on the tablet and execute the commands he did after adb shell from there.
Lightn1ng said:
This is a bug with the kernel, that's not my kernel so I can't fix it. That said, you can get a terminal emulator on the tablet and execute the commands he did after adb shell from there.
Click to expand...
Click to collapse
Tried this. What I got after the partition command was that this process didn't have the MOUNT FORMAT FILESYSTEMS permission . Did I miss a step?
Windsor1959 said:
Tried this. What I got after the partition command was that this process didn't have the MOUNT FORMAT FILESYSTEMS permission . Did I miss a step?
Click to expand...
Click to collapse
Type "su" into terminal emulator before doing the commands.
Lightn1ng said:
Type "su" into terminal emulator before doing the commands.
Click to expand...
Click to collapse
That did it. I should have remembered that!
Everything looks good so far. I'm installing some apps. Love the debloating that you did.
Windsor1959 said:
That did it. I should have remembered that!
Everything looks good so far. I'm installing some apps. Love the debloating that you did.
Click to expand...
Click to collapse
Now I wish I put an OTA updater into the ROM so I didn't have to upload updates here. Maybe I'll upload a "revised" version before too many people use it.
Would you mind bringing pitchforks to ashyx so we can get ADB? lol.
Lightn1ng said:
Now I wish I put an OTA updater into the ROM so I didn't have to upload updates here. Maybe I'll upload a "revised" version before too many people use it.
Would you mind bringing pitchforks to ashyx so we can get ADB? lol.
Click to expand...
Click to collapse
Maybe if we used the pitchforks to cook hot dogs or s'mores...?
Windsor1959 said:
Maybe if we used the pitchforks to cook hot dogs or s'mores...?
Click to expand...
Click to collapse
I was thinking T713 users in front of his house holding pitchforks and torches demanding ADB, but that works too...
Lightn1ng said:
I was thinking T713 users in front of his house holding pitchforks and torches demanding ADB, but that works too...
Click to expand...
Click to collapse
I thought that's what you were thinking, but sometimes a little bit of goodness can work wonders! If that doesn't work, then we'll go with your idea!
I've been installing and setting up apps. I haven't met a single bug yet. My AnTuTu score is around 74k, which is slightly less than stock. But, if your tweaks help out in battery life send other areas, that's a very small price to pay. I haven't been able to get a sense of battery life yet, as I've been downloading and setting up my stuff. Everything feels smooth. I look forward to anything else you plan to add. But, this is quite good as it is.
Hi,
first of all thanks for your work&time! Is it possible to use this ROM for my T813? Thanks in advance!
The other thing is. it possible for you to give us a list which Apps do you removed? It's nice to know for the updater-script by Blaz1nfor ( sry can't send you the link, because i'm new here ) Or better for us, can you make an update of this list and post this here? This will be awesome!
Changelog 4.2
For people using Nougat, all custom ROMs currently are not able to mount the SYSTEM in read/write mode. So you are advised to use latest version of debloater in TWRP mode only.
Note: For Gaming tools => Don't debloat it ... otherwise you will get a force close for BadgeProvider apk (which responsible about count badge of apks that receive notifications). Also choose option A or R during debloating...
Thanks,
Disclaimer: Please ask before use and give proper credits.
Introduction:
Have you ever want an interactive way to debloat your Samsung Galaxy S7 or Note 7? Are you looking for best speed, less battery consumption and more system space ?
Yes, with its backup strategy, this binary allows you to debloat your device and push the bloatwares to a backup folder under your internal storage and known as DebloatedFOLDER which will include all the categorized bloatwares. :highfive:
It runs on : Marshmallow 6.0.1 and tested on Galaxy S7 Flat/Edge and Note 7 whether normal or ported.
Environment : Terminal system mode or Terminal TWRP mode
Screenshots:
{
"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"
}
Features:
Better Battery life
Gain more SYSTEM space
Less CPU utilization
Better phone speed and more responsiveness
Categorised Backup Folder (check attachment)
Debloating Selection:
Q) Cancel debloating and exit now
A) Ask me what to debloat (excluding special apks)
B) Auto-Debloat Everything (excluding special apks)
R) Ask me what to debloat (including special apks)
K) Auto-Debloat Everything (including special apks)
How to proceed:
you need to have a rooted device and TWRP installed.
the downloaded zip file attached here.
one of the debloating options below. (check Note 2 below)
WARNING : IF YOU ARE COMING DIRECTLY FROM ROM' FLASHING, LET YOUR PHONE START AT LEAST ONE TIME AFTER ROM INSTALLATION. DON'T RUN THIS BINARY AFTER ROM INSTALLATION DIRECTLY.
RUN IT ON YOUR OWN RISK: I'm not responsible about anything that might happen during the use of this binary. A backup of the SYSTEM and Data partitions is highly recommended if you need to return back to original untouched device.
Debloater options:
Option 1: Steps to follow if you want to run from system mode
Make sure you have a backup of SYSTEM and Data partitions in TWRP
download debloater4.x.zip from the attachment below
Extract the content of the zip file, and put the 3 files in the following directory (using Root Browser or Solid Explorer) : /data/local
Give "debloater" and "decrypt_file" both rx,rx,rx permissions and give "debloater_db.enc" r,r,r permissions
if you know how to work with adb shell or SSHDroid, then fine. SSHDroid will allow you to connect to your phone wirelessly through secure connection port. if you don't know, follow coming step
from google play store, install any terminal emulator, or JuiceSSH.
Note about Terminal Emulator:if you face an issue with Terminal Emulator where the enter button is missing in the keyboard, I raised this bug to the developper. Workaround: navigate to telegram or whatsapp, and open any chat, then return back to the emulator, then enter button will appear.
start the Terminal and check if you have root by typing
Code:
[B]su[/B]
press enter. If you have root, you can continue, otherwise don't bother yourself.
after typing the "su" command and granting permissions to your terminal, type the following:
Code:
[B]cd /data/local[/B]
press enter.
I'll assume that you forgot to give file permissions above and let's give permissions by typing the following code:
Code:
[B]chmod +rx debloater ; chmod +rx decrypt_file ; chmod +r debloater_db.enc[/B]
press enter
now let's start the debloater by typing(don't forget the dot before the slash):
Code:
[B]./debloater[/B]
press enter
Once finished you can check the result in /sdcard/DebloatedFOLDER/<datetime of debloater>
Option 2: Steps to follow if you want to run from TWRP (changed in 4.x, double check and follow)
download debloater4.x.zip from the attachment below (extract the zip archive to get the files).
Put the 3 files in a folder for example , Download folder under /sdcard (internal storage)
Reboot your phone to recovery TWRP
Make sure you have a backup of SYSTEM and Data partitions in TWRP
In TWRP Home, click MOUNT and then mount SYSTEM and Data
In TWRP Home, click on Advanced -> Terminal
change your current directory to Download folder and type:
Code:
[B]cd /sdcard/Download[/B]
Hit Enter
change the mode of the binary to executable mode and type:
Code:
[B]chmod +rx debloater ; chmod +rx decrypt_file ; chmod +r debloater_db.enc[/B]
Hit Enter
now execute the binary (don't forget the dot before the /):
Code:
[B]./debloater[/B]
Hit Enter
Once finished you can check the result in /sdcard/DebloatedFOLDER/<datetime of debloater>
NOTE
DebloatedFOLDER: You can get back debloated folder' apks and put them in /system/app or /system/priv-app using Root Browser or Solid Explorer. Once you put back, don't forget to give necessary permissions for main folder (the one backed up) and subfolders: rwx,rx,rx and for files (apks, or odex in case of use): rw, r, r
If you see that some apps remains even after debloating, try the TWRP mode where no apps are running and you will be able to debloat completely what you couldn't in system mode.
Join us on Telegram:
If you need any help, kindly don't hesitate to contact me. Also you can join my group on telegram group: telegram.me/S7general
If you like my work, kindly hit the Thanks :good: button below.
XDA:DevDB Information
Debloater, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
Jowy007
Version Information
Status: Stable
Current Stable Version: 4.2
Stable Release Date: 2016-10-07
Created 2016-10-04
Last Updated 2016-10-10
Nougat 7.x
You can use this debloater on Nougat ROMs , but read the red note about nougat on top of the thread.
Cheers :highfive:
Changelog for debloater
Version 4.2 Changelog:
fixed rebloat old sms app
rebloated Download Provider
H20s category has been renamed to Hotspot
Version 4.1 Changelog:
added more 14 packages (thanks to @Agnadius)
rebloated old sms app
Version 4.0 Changelog:
code rewritten from scratch
binary name changed from "mydebloater" to "debloater"
new database file for handling the debloater
new terminal and colorful design interface
user no longer needs to press enter after choosing an option. The debloater will react immediately
now the debloater can be launched from system mode, TWRP recovery mode or from your Macbook/PC
new way intelligent way of detecting packages
new packages added, for a total of 454 packages for both s7 and n7
changes in option selection for debloating: A,B for Normal Users and R,K for Experienced Users
added an option for cleaning Dalvik-Cache at the end of the binary
auto-reboot option to avoid lock crashes (if any) in system mode only (no need for TWRP)
the debloated folder (DebloatedFOLDER) in /sdcard (internal storage) , has now categorized subfolders
[CTRL+C] option handled, so user can either continue or abort execution at any time
many other stuff that I might missed..
Great Job :good: thanks !!
Good job, bro! Thank you :good:
Sent from my SM-N930F using Tapatalk
Nice work mate, about to test this badboy, will post a report later.
Sent from my SM-G935F using XDA-Developers mobile app
Good Job Jowy !!
Dockyy said:
Great Job :good: thanks !!
Click to expand...
Click to collapse
you're welcome ! a new version coming soon !
sharingspider said:
Good Job Jowy !!
Click to expand...
Click to collapse
Thank you a new version is coming soon !
Jowy007 said:
Thank you a new version is coming soon !
Click to expand...
Click to collapse
Oh Wow - Waiting Eagerly !!
sharingspider said:
Good Job Jowy !!
Click to expand...
Click to collapse
Please learn that quoting the whole first post is against the rules. This is really impolite for those who seek answers in the comment too, who will have to scroll a lot.
Envoyé de mon SM-G935F en utilisant Tapatalk
fabulous69 said:
Please learn that quoting the whole first post is against the rules. This is really impolite for those who seek answers in the comment too, who will have to scroll a lot.
Envoyé de mon SM-G935F en utilisant Tapatalk
Click to expand...
Click to collapse
Oops might have quoted by mistake buddy. It's completely against the rules yeah.
Telegram Group - https://telegram.me/joinchat/C3LWqkA0hP6E-snnkh7OaQ
Thanks jowy. Superb work.
Sent from my SM-N930F using XDA-Developers mobile app
Works really well and the interactive binary is really great, phone feels faster and more battery
utkarsh_86 said:
Works really well and the interactive binary is really great, phone feels faster and more battery
Click to expand...
Click to collapse
Thank you dear .. hope you enjoy it.. as I said, a new version is coming soon as well, having additional apks..
Jowy007 said:
Thank you dear .. hope you enjoy it.. as I said, a new version is coming soon as well, having additional apks..
Click to expand...
Click to collapse
@Jowy007
Thanks for your good work and give us your precious time
ran it but there are no apps in the debloaded folder
dominicstg2 said:
ran it but there are no apps in the debloaded folder
Click to expand...
Click to collapse
it seems you forgot to MOUNT the partitions SYSTEM and DATA. What message did you get on screen ?
Jowy007 said:
it seems you forgot to MOUNT the partitions SYSTEM and DATA. What message did you get on screen ?
Click to expand...
Click to collapse
sd card not found or something along those lines i did it first go and said it was a success but 0 apps are in the folder i did the heavy option running it on effcient rom v 3.4
dominicstg2 said:
sd card not found or something along those lines i did it first go and said it was a success but 0 apps are in the folder i did the heavy option running it on effcient rom v 3.4
Click to expand...
Click to collapse
yeah , if you didn't see the folder DebloatedFOLDER under (/sdcard or My Device Storage), it does mean most probably that you missed to Mount partitions as requested in the steps
Try again ..
Soon, I'm releasing a new version v4.0 which can be run during normal mode, or in TWRP
DISCONTINUED SUPPORT
OKAY SO
I present to you: Kali NetHunter 3.15.4 for the ZTE Axon 7.
(yes, a custom kernel for the ZTE Axon 7 on MiFavor!)
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.4 (stable, 2017-01-22)
Please be careful to download the right version based on this table:
A2017U (North America): kernel-nethunter-ailsa_ii-*
A2017G (Europe / Hong Kong): kernel-nethunter-ailsa_ii-*
A2017 (China): kernel-nethunter-ailsa_ii-*
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 the official NetHunter build server: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: The Kali NetHunter installer 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.
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.
** If modifying the installer zip, you will have to disable ZIP signature verification as modifications will break it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
FULL INSTALLATION STEPS
Install Team Win Recovery Project (ailsa_ii) 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.
For new installations: Download the nethunter-generic-arm64-kalifs-full 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.
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.
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.
DEVICE RECOMMENDATIONS
The ZTE Axon 7 internal wireless does not support monitor mode. This means you'll need to use an OTG adapter and a wireless card that does.
I highly recommend these two items:
Alfa Networks AWUS036NEH: https://smile.amazon.com/802-11g-Wireless-Long-Rang-Network-Adapter/dp/B0035GWTKK/
iXCC USB Type-C to Type-A OTG adapter: https://smile.amazon.com/iXCC-Adapter-Charge-Supported-Devices/dp/B017TJN22C/
* I am not affiliated with these sellers
The AWUS036NEH is the most tested and stable adapter available, and also comes in a very convenient portable form factor allowing antenna swaps for greater scanning ranges.
The iXCC USB adapter is compliant with USB Type-C specifications and provides up to USB 3.1 Gen 2 compatibility. It's also well built.
I don't recommend using smaller OTG adapters - they can break your ports if you accidentally put too much pressure on them or your phone falls with them plugged in.
THE KERNEL
The NetHunter kernel for the ZTE Axon 7 is (somewhat) based on A2017U B27 kernel sources.
It has the following changes:
Carefully updated to Linux 3.18.47!
Merged with the latest CodeAurora tag for Android 6.0 msm8996: LA.HB.1.3.1.c1-20600-8x96.0
Many bug fixes and cleanups to ZTE's code, including disabling of debug tasks for battery life
SELinux Permissive (required for DriveDroid until I fix policy injection rules, it will pretend to be Enforcing)
Paragon UFSD drivers replaced with Samsung's latest open-source exFAT drivers
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
DriveDroid compatibility
USB HID Gadget keyboard & mouse support - temporarily disabled until issue solved
mac80211 packet injection support
savoca's KCAL color calibration driver built in (currently no invert support on msm8996)
Additional drivers built in for the full Kali NetHunter experience
Kernel module support, insert your own modules! (modprobe available in Kali chroot)
CIFS, NFS, USB Serial available through included kernel modules
VerifiedBoot=green status hack to pass SafetyNet (may not work with SuperSU, remove SuperSU from the installer if this is important!)
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.
Video Recording - The rear camera video encoder will corrupt the video on the first frame. Happens after restarting camera app.
HID attacks - There's an issue with USB descriptor breaking when HID gadget mode is enabled, so it is disabled for now.
DEVELOPMENT & CONTRIBUTIONS
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Kali NetHunter Official device updates: https://github.com/offensive-security/nethunter-devices/commits
ZTE NetHunter kernel source: https://github.com/jcadduono/android_kernel_zte_msm8996_old/tree/nethunter-6.0
If you wish to donate to the NetHunter project, you can donate directly to me through the Donate button under my name.
This will generally go towards supporting my next flagship device purchase, which will receive NetHunter and TWRP support from myself.
You can also use "Basenji Rescue and Transport" as your Amazon Smile charity and that will make me really happy!
(in my avatar, if you see a dog, that's a Basenji!)
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 ZTE Axon 7, Kernel for the ZTE Axon 7
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.4
Stable Release Date: 2017-01-22
Created 2016-12-16
Last Updated 2018-07-31
Work on a2017G too? I have open bootloader and on A2017G b29. And that Work perfekt
Kevinkuensken said:
Work on a2017G too? I have open bootloader and on A2017G b29. And that Work perfekt
Click to expand...
Click to collapse
you'll have to let me know if it works, i can't really understand if you're asking if it works or if it does work
IT Work for A2017G. I have installed IT but have no Hunter app
Guess I know what I'm doing tonight
Sent from my ZTE A2017U using XDA-Developers mobile app
https://www.kali.org/kali-linux-nethunter/
Seems like this is a "Hacker's" kernel with no real gain for the "regular" user.
KyJelly69 said:
https://www.kali.org/kali-linux-nethunter/
Seems like this is a "Hacker's" kernel with no real gain for the "regular" user.
Click to expand...
Click to collapse
Yea.... What are we supposed to do with this kernel if it doesn't improve anything over stock? We are not "Hackers"
Anyone He has flashed The kernel, have The Kali NetHunter App? For Me ist dont find the app
XblackdemonX said:
Yea.... What are we supposed to do with this kernel if it doesn't improve anything over stock? We are not "Hackers"
Click to expand...
Click to collapse
Don't use it. Not everything that is developed or posted here will be for everyone.
I'm sure there is more people here that find this useful, or you can try to use it useful and learn something new
jimbo77 said:
or you can try to use it useful and learn something new
Click to expand...
Click to collapse
I still don't need to hack WiFi networks lol
XblackdemonX said:
I still don't need to hack WiFi networks lol
Click to expand...
Click to collapse
That's one of its uses but there is more
Good work! Glad to see some more development for our device.
KyJelly69 said:
https://www.kali.org/kali-linux-nethunter/
Seems like this is a "Hacker's" kernel with no real gain for the "regular" user.
Click to expand...
Click to collapse
We don't care.
VinylJStar said:
We don't care.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=70122463&postcount=1356
Oh how very clever you are. And we still don't care...
Can I install update-nethunter-generic-arm64 zip instead of nethunter-generic-arm64-kalifs-full zip if I don't want to have all the apps? I basically just want this kernel to bypass SafetyNet.
Thanks
With this kernel, is it now possible to flash Substratum Themes, without causing a boot issue?
Or is that something that needs changed in the ROM itself?
XblackdemonX said:
Can I install update-nethunter-generic-arm64 zip instead of nethunter-generic-arm64-kalifs-full zip if I don't want to have all the apps? I basically just want this kernel to bypass SafetyNet.
Thanks
Click to expand...
Click to collapse
If you only want the kernel then just install the kernel lol update-nethunter is the apps, nethunter-generic is the apps + kali system
This is only my initial build for getting feedback on things that might be broken before I start merging in CAF/updates.
anyways, I'm not sure how safetynet will handle permissive since I had to use that for DriveDroid support. I haven't tested if exFAT works in enforcing (it probably doesn't), but here's an alternative kernel for you that is only safetynet+exfat+kcal (things typical xda users might care about):
https://build.nethunter.com/misc/axon7/ailsa_ii_xda_safetynet_kcal-1.0-20161216-1849.zip
Thank you very much i'll try it!
Loved it. Installed, used the Kcal app and it works great! I hope you keep bringing more and more features to a custom kernel!
Appreciate it!!
---------- Post added at 01:49 AM ---------- Previous post was at 01:29 AM ----------
@jcadduono do you have any idea why any of the apps that set options on boot work? I have tried with folder mount and Kcal and it seems boot commands are not executed. I need to get in the app after the phone has booted and apply the settings manually instead of then being applied on boot. Probably you can shred some light on this issue?
jimbo77 said:
@jcadduono do you have any idea why any of the apps that set options on boot work? I have tried with folder mount and Kcal and it seems boot commands are not executed. I need to get in the app after the phone has booted and apply the settings manually instead of then being applied on boot. Probably you can shred some light on this issue?
Click to expand...
Click to collapse
probably related to power management i guess, i know at least on my device any autostart apps don't start till like 20 seconds after the device is booted because the OS spreads out everything.
make sure your app policies allow auto start though, and that you hit the save button with start on boot and color service enabled:
{
"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"
}
DISCLAIMER!!I am just posting this here for Galaxy A71 users to be aware this custom ROM exists. I didn't develop anything nor i contributed with something. All the credit goes to Ancient developers and everyone who had been working on this GSI. I don't want this forum to be a ''copy-paste'' thread.. even if it looks like. Again,i don't take any credits!! If anyone wants to contribute on this to make it better for our device, please contact me.
Website of AncientOS
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
What is this?AncientOS - A Custom ROM based on AOSP (Android Open Source Project) CrafetedWithLove. With the Aim To Provide "Performance", "Security" and "Stability", with Multiple Customisation option. So that every User can customise thier phone as per their taste. While you get Best in class Customization options you also get a unique UI without any security Comprimises, Monthly Security patches are merged, Every Update has something new with bug fixes.
Generic System Images
'' A generic system image (GSI) is a system image with adjusted configurations for Android devices. It's considered a pure Android implementation with unmodified Android Open Source Project (AOSP) code that any Android device running Android 9 or higher can run successfully.
GSIs are used for running VTS and CTS-on-GSI tests. The system image of an Android device is replaced with a GSI then tested with the Vendor Test Suite (VTS) and the Compatibility Test Suite (CTS) to ensure that the device implements vendor interfaces correctly with the latest version of Android.) ''
BUGS- Fingerprint not working- No MTP inside system / *workaround* reboot to TWRP and transfer data there.- No Bluetooth Audio
- No audio in calls using SIM2 slot. ( you can't listen or be heard by the caller )[ USE SIM 1 INSTEAD ]YOU TELL ME
- How to -DownloadDownload the image from here.Install1.Have TWRP set up.2.In TWRP go to WIPE > Format Data > (type '' yes '') then enter.(2.5). If you don't have MicroSD then reboot to recovery and use ADB to move image to Internal Storage.ADB command should look like this : adb push AncientOS.img /sdcard/3.Copy/Move the .img file to MicroSD4.Install .img as SYSTEM.5.Flash NikGAPPS5.Install Magisk from this link only.6.Reboot7.Install Magisk APK ( Rename ''app-debug.zip'' to "app-debug.apk")DONE!
Some TIPS in order to fix some broken stuff and quality of life impovements:
Google Camera: https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/f/dl61/Apply this config. :https://www.celsoazevedo.com/files/android/p/f/2021/11/BSG-A71-GV1h.xmlAnd this LIB https://f.celsoazevedo.com/file/cfiles/gcm1/morgenmanlibv6.so
Get fast chargingBy default A71 on GSI charges really slow, this enables fast charging for the A71 on AncientOS and any GSITo install, download this from: https://drive.google.com/file/d/1KguCeLD-VHShm0MYzKhYrsAv-rZAuJeA/view?usp=sharingNow install the module it will ask you to use volume keys follow the instructions and choose 4500mah 27w. Once installed reboot!Note: this will not affect battery/ will barely affect battery
Increase performance without any battery impact or (by feravolt and gloeysik)
Step 1- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.- Go to the settings tab and use the AUTO settings for FDE AI.Install GMS Doze Magisk Module: https://github.com/gloeyisk/universal-gms-doze
Screenshoots
We have a telegram developer group for our Galaxy A71 device!! You can check what we are developing in real time or ask for help here.
~ About this GSI ~Maintainer Name : NazimRom Support Group :LinkDevice Support Group : LinkRom Changelog : LinkDate Updated :17-04-2022
CREDITS:AncientOS developers - for ROM@afaneh92 - for TWRPGoogle - for AOSP@bickbick - for testing the AOSP.
If you think i missed you DM me and i will credit you!
reserved1
reserved2
Can this rom work on m51 ?
I think it should work. Its a GSI after all.. but make sure you have a backup just in case.
1. Does it require Android 12 firmware?
2. What is GSI?
Looks interesting......an AOSP ROM for A71!
Cheers
bickbick said:
1. Does it require Android 12 firmware?
2. What is GSI?
Looks interesting......an AOSP ROM for A71!
Cheers
Click to expand...
Click to collapse
Hello! 1. Android 11 should be ok.
2). Generic System Images
A generic system image (GSI) is a system image with adjusted configurations for Android devices. It's considered a pure Android implementation with unmodified Android Open Source Project (AOSP) code that any Android device running Android 9 or higher can run successfully.
GSIs are used for running VTS and CTS-on-GSI tests. The system image of an Android device is replaced with a GSI then tested with the Vendor Test Suite (VTS) and the Compatibility Test Suite (CTS) to ensure that the device implements vendor interfaces correctly with the latest version of Android.)
Well guys you've done a brilliant job with this ROM.
It's fast, clean and not a Samsung app in sight!
Followed the 'How To' section and it was all installed, but didn't get Magisk...do I need to install the Magisk app?
With basic setup (I have not run the extra files in OP).
Observations:
1. It didn't like my 128GB SD card, not recognized after installing ROM (ok in TWRP). It suggests Formatting (I will back up and test).
2. Also SD card is not seen when connecting to a PC (driver needed?). I will test after formatting the SD card.
3. Does it need Magisk .APK? If so, will anyone do it? I did install the latest and it seemed ok until I updated Magisk ......it boot looped afterward and I had to start all over again!
4. Does it have Double Tap To Wake?
5. Also, in System it says an update is available, is it ok to update?
Otherwise a really good ROM. Highly recommended.
Bluetooth headset does not work, fix via magisk does not work on aosp
Still didn't recognize the 128GB SD card even after formatting it...
Tried 8GB, and that works fine.
bickbick said:
Well guys you've done a brilliant job with this ROM.
It's fast, clean and not a Samsung app in sight!
Followed the 'How To' section and it was all installed, but didn't get Magisk...do I need to install the Magisk app?
Click to expand...
Click to collapse
Thank You! Yes, after flashing Magisk in TWRP you need to install the same zip as an apk.
bickbick said:
With basic setup (I have not run the extra files in OP).
Observations:
1. It didn't like my 128GB SD card, not recognized after installing ROM (ok in TWRP). It suggests Formatting (I will back up and test).
2. Also SD card is not seen when connecting to a PC (driver needed?). I will test after formatting the SD card.
3. Does it need Magisk .APK? If so, will anyone do it? I did install the latest and it seemed ok until I updated Magisk ......it boot looped afterward and I had to start all over again!
4. Does it have Double Tap To Wake?
5. Also, in System it says an update is available, is it ok to update?
Otherwise a really good ROM. Highly recommended.
Click to expand...
Click to collapse
1.No drivers needed. Interesting tho'.. try formatting inside Android.
2.It's a kernel issue ,I cannot do anything.
3.Do not install another Magisk other than the one linked in the thread.
4.It should. I am not sure
5.I recommend you don't. You can try.
Thank you for your support!! I've listed you as a tester! Thank You @bickbick !!
Rawsion said:
Bluetooth headset does not work, fix via magisk does not work on aosp
Click to expand...
Click to collapse
try to disable a2dp offload in dev settings.. also you can try installing this apk .
No sound/mic in 2 sim card
AleksB.46 said:
try to disable a2dp offload in dev settings.. also you can try installing this apk .
Click to expand...
Click to collapse
Fix by the first point
Rawsion said:
No sound/mic in 2 sim card
Click to expand...
Click to collapse
this is common for AOSP.
Rawsion said:
Fix by the first point
Click to expand...
Click to collapse
what do you mean?
Couldn't get this ROM to see 128GB SD cards, so back to RayOS. Also Magisk was a bit iffy.
Maybe I'll take another look after some improvements. Really hoping this one is developed as AOSP on our A71 is very desirable.
Requests:
Fix SD card issues
DTtoWake gesture.
Volume Steps
Cheers.
bickbick said:
Couldn't get this ROM to see 128GB SD cards, so back to RayOS. Also Magisk was a bit iffy.
Maybe I'll take another look after some improvements. Really hoping this one is developed as AOSP on our A71 is very desirable.
Requests:
Fix SD card issues
DTtoWake gesture.
Volume Steps
Cheers.
Click to expand...
Click to collapse
I have noticed it will read an SD card if its formatted in NTFS