Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Special THANK YOU to @NFound, @raystef66, @DrakenFX, @Oki, @WesTD and to everyone else who has helped with the development of the Axon 7 and with this thread
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlocked bootloader message removal:
Have not found a working method yet.
Always backup your intSD before flashing ROMs and other TWRPs (Recoveries)
Stock user, need to install TWRP?
Flash TWRP 3.2.1-0 https://androidfilehost.com/?fid=673791459329066789 by @raystef66
If you already have TWRP installed, any version will do since the ROM will replace it with TWRP 3.2.1-6 after installation.
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Do a full backup!
Wipe to perform a clean install. Recommended.
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which modem you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM.
Flash the safetynet fix linked below.
Wipe Cache and Dalvik
Reboot
Edit: Changing partitions to ext4 might be necessary for some non-stock users on f2fs.. Still updating
What's not working and how to fix it:
Magisk doesn't pass Safetynet? (ctsProfile: False). Download and flash https://androidfilehost.com/?fid=674106145207489292 Thank you @raystef66
Google play store shows as uncertified? The .ZIP above from @raystef66 fixes this as well. Your device is now certified.
How do I disable force encryption? Go to post #63 by @DrakenFX
Bad battery life? Flash Jojoc V2.1 or V3.1 module within Magisk or via TWRP V3.2 : https://androidfilehost.com/?fid=962187416754476535 V2.1 : https://androidfilehost.com/?fid=673956719939820457 by @raystef66
AdAway cannot install hosts file: Open Magisk -> Settings and select Systemless hosts.
Daydream is not working? Check post #23 B12 Thread by @kountry83 Download: Daydream.zip
How do I enable or disable the Navigation bar?: Check thread [A2017G][TWRP-ZIP]NAVIGATION BAR Enabler/Disabler by @raystef66 or Direct Link download for aroma installer
How do I remove the carrier label and center the clock on the status bar? Check thread [PATCH][A2017X V1.3.0B01] Remove Carrier & Center Clock by @raystef66 Download: A2017X_V1.3.0B01_carrier&clock
Remove carrier label only: Check post #342 by @raystef66 Download: A2017X_V1.3.0B01_carrierremover
Need modems, boot or bootstack? Download below by @raystef66
Modems:
ZTE_A2017X_Oreo_V1.30B01_Gmodem
ZTE_A2017X_Oreo_V1.30B01_Umodem
ZTE_A2017X_Oreo_V1.30B01_CNmodem
Boot:
A2017X-O_beta-B01-boot
Bootstack: twrp 3.2.1.6 included
ZTE_A2017X_V1.3.0B01_OREO_BootStack_twrp3216
What's working:
Pretty much everything other than what I wrote above it seems. The ROM is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. Fixed by Jojoc V3.2 by @raystef66. Link above.
Testing Camera...
Working HDR+ Patch by @NFound: : HDR+ for v1.3.0 B01
GCAM: GCAM
Flashed an older version of that HDR+ Patch by @NFound and does your Magisk not pass the safetynet anymore? Flash this safetynet fix by @raystef66: A2017X-V1.30B01_safetynet_fix_HDR
Dual Sims: Fully working
I'll continue updating the thread according to your feedback and my testing.
Victor13f said:
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Thank you @NFound once again for your hard work!
Thank you @Oki for having written https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693 If you need a better guide visit this thread and follow this guide simply using different files and not installing the bootstack separately.
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlock boot message removal:
If you want to remove the unlocked bootloader message at boot, you just need TWRP Exclusive. Just boot to recovery and go to the Advanced Menu -> More -> Del Inscription. You must to do this every time you update the bootloader. Thank you @Oki
Need to install TWRP?
Flash TWRP exclusive by @NFound https://androidfilehost.com/?fid=673956719939822011
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP or ADB: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which bootstack you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM or with TWRP Exclusive go to Advanced -> More -> Root -> Magisk
Wipe Cache and Dalvik
Reboot
What's not working?:
Magisk root doesn't pass Safetynet (ctsProfile: False). Tested with V16.4, V16.0 and V15.3. None of them passes the safetyNet. Have also tried installing the props module to no avail.
Google play store shows as uncertified (yet all the apps are available and install with no restrictions).
Battery charging light turns off when I turn the screen on and turns back on when the screen is off (Maybe it's intended to be like that, not sure)
What's working:
Pretty much everything other than what I wrote above it seems. The rom is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. I haven't tested the dualsims yet but I will soon and I'll post the result here.
Testing Camera...
I'll continue updating the thread according to your feedback and my testing.
Click to expand...
Click to collapse
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Cool, an easy guide to get you started.
Thanks man.
GabbaGandalf42 said:
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Click to expand...
Click to collapse
I belive the link is allowed. A Forum mod said so on NFounds AEX thread.
I didn't snatch anything. I used guides that exist because they work and I gave props to every single person I could think of. I never claimed this was all my work. Just trying to help other people who want to try the ROM or are interested in how it performs.
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Can /system be mounted as RW in this rom?
blackpac said:
Can /system be mounted as RW in this rom?
Click to expand...
Click to collapse
You can edit system just from TWRP.
mickey36736 said:
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Click to expand...
Click to collapse
Didn't work unfortunately. Edited the ro.build.fingerprint and it still failed safetynet check.
SAFETYNET-FIX
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4 and 16.0
raystef66 said:
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4
Click to expand...
Click to collapse
Thank you, it works
all set up and running
Predatorhaze said:
all set up and running
Click to expand...
Click to collapse
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
battery dont know yet,but i dont use any sound mods on stock rom.Didnt try substratum.....i can try,but not gonna use it
GabbaGandalf42 said:
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
Click to expand...
Click to collapse
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Victor13f said:
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Click to expand...
Click to collapse
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Two questions please:
1. would flashing no-verity-opt-encrypt do anything for this ROM? as in, making encryption optional?
2. would it be a good idea to flash FASTBOOT_UNLOCK_EDL_N if I want to change my recovery now that I am no longer on N?
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Substratum works, used swift black theme 8.0 pixel or nexus
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Batterywise, I flashed the jojoc battery module and it's looking a lot better already
Here is working fine but how do I remove the operator name from the status bar?
Battery is absolutely horrible, coming from a beta tester. If you experience terrible battery it isn't a problem on your side, it's the beta rom. At best, I get barely 3 hours of screen on time only browsing Facebook
Related
(All credit goes to wanam for providing Xposed for TouchWiz roms)
I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017.
Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages.
I mostly followed the steps in this thread but i'll write the steps here as well.
This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables
A recovery like CWM or TWRP (guide) is required.
Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system
Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings)
Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on
Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64).
Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes
Enjoy the flexibility of Xposed
If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you.
Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery.
You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker).
Known bugs on the A3 2017:
- none (will add from comments or if i find any)
Sources:
https://github.com/wanam/Xposed
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Hello,
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
SinusStudios said:
(All credit goes to wanam for providing Xposed for TouchWiz roms)
I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017.
Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages.
I mostly followed the steps in this thread but i'll write the steps here as well.
This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables
A recovery like CWM or TWRP (guide) is required.
Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system
Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings)
Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on
Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64).
Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes
Enjoy the flexibility of Xposed
If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you.
Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery.
You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker).
Known bugs on the A3 2017:
- none (will add from comments or if i find any)
Sources:
https://github.com/wanam/Xposed
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Click to expand...
Click to collapse
knzsys said:
Hello,
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
Click to expand...
Click to collapse
To be honest i flashed 32 bit xposed because i searched for the phones architecture and found 32 bit but that must be a misinformation.
I'm surprised now that it's working on my phone!
Thanks for mentioning this, if you have time feel free to safely try out both versions and report back what's working and what's not.
knzsys said:
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
Click to expand...
Click to collapse
Can't find a reason why our 64-bit phone is not recognized bit the 64-bit Xposed
I you want to install the 64-bit Xposed: got through Magisk
Don't know if it has a direct link: had lotz of reboot with 32-bit Xposed; nearly no reboot with 64-bit Xposed.
PS: Don't get too addict to Xposed has it will stop running when we'll get Nougat
The 64bit version will not work because Samsung shipped the SM-A320F with 32bit Android, even though it has a 64bit-capable SoC.
Im Wondering something here ... 32 bit os on our phone, no custom roms .. etc ... but the J7 2016 has the same CPU, same ram, storage, screen res ... you get the point .. i just wonder if a rom from that would ... and its 64 bit ... i mean, its the same damm SoC
are there any news for android 7 to get xposed without magisk. I have supersu root
y2kadir said:
are there any news for android 7 to get xposed without magisk. I have supersu root
Click to expand...
Click to collapse
Yes, you just have to search the Xposed thread and read.
Pat750 said:
Yes, you just have to search the Xposed thread and read.
Click to expand...
Click to collapse
ok but I just did it and coulnd`t find anything. can you tell me where to find?
y2kadir said:
ok but I just did it and coulnd`t find anything. can you tell me where to find?
Click to expand...
Click to collapse
Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry.
Pat750 said:
Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry.
Click to expand...
Click to collapse
why are you talking foolish ****. if you don't wanna help other people go home.
y2kadir said:
why are you talking foolish ****. if you don't wanna help other people go home.
Click to expand...
Click to collapse
OK here's something to start with.
https://forum.xda-developers.com/showthread.php?t=3034811
but please read the threads there are some good advice's.
Pat750 said:
OK here's something to start with.
https://forum.xda-developers.com/showthread.php?t=3034811
but please read the threads there are some good advice's.
Click to expand...
Click to collapse
I only found this in the thread "The first fixes have found their way into version 88.1, only available for Nougat. That includes especially some fixes for Samsung ROMs, but might also fix bootloops and slowdowns on other devices. Besides that, I think I fixed a MIUI incompatibility, not sure if it works now (and to be honest, I don't give much priority to MIUI). There are still unfixed issues on the queue, and again, please keep reporting whatever you find." but this information is not confirming me that its working.
INTRODUCTION
I posted my configuration before inside a couple of threads. After that, I have received a lot of questions about the same issues. I have also been asked to create a thread so newbies could have an easy way of having an Oreo system up and running in the Axon 7. So I am doing it. Newbies will have an easy entry point to the world of custom Oreo ROMs and a single point to clarify any question. We have a healthy and active Axon 7 scene here at XDA. This guide provides a path to have a custom Oreo system with the latest features available for this device requiring a minimum effort. It applies to any of the 3 Axon 7 flavors: A2017 (China), A2017G (Europe) and A2017U (Americas) with any memory and storage capacity. At this time there are 3 groups of ROMs depending on the Bootstack and GSI support:
1. B32+B10 ROMs use the reliable Nougat bootstack. They are very stable and battery efficient. On the other hand, none of them support dual SIM or HDR+ camera. However they support HDR and Camera2 API.
2. B12 without GSI support ROMs use the Oreo beta B12 bootstack. Full support for Camera2 API and HDR+ but very poor battery performance and stability issues.
3. B12 with GSI support ROMs also use the same Oreo beta B12 bootstack. They also require a separated vendor partition. They share the same benefits and limitations of the previous group. So far they are experimental and the Treble ROMs don't support yet all the Axon 7 Hardware when using them along with a GSI image. They are examples of a Work-In-Progress that is yet to be finished.
WHAT THE HECK IS TREBLE AND GSI?
Since Oreo, all the new devices must have a separated vendor partition to fulfill Google's Treble project requirements. This way the OS is structured in two parts:
1. Treble ROM: includes all the device drivers and vendor related files in the vendor and boot partitions. The Treble ROM is owned and updated by the device vendor or a custom ROM developer.
2. Generic System Image (GSI): Includes the Android OS, it is controlled by Google and allow generic and frequent security and system feature updates directly from Google. It uses the system partition.
So far, custom Android distributions such as LineageOS, Resurrection Remix, AOKP, Dirty Unicorns, AEX, etc... had to create specific ROMs for each supported device. This was painful and it all was depending on the willingness of a developer to maintain a version for each device. Thanks to Treble project, now Android distributions just release a single GSI able to be installed in any device using a Treble ROM. This way they can properly maintain all the devices with a single GSI image by focusing on frequent updates of a single GSI. These custom distributions will also deliver the security and feature updates by Google. So a fully Treble ROM for the Axon 7 will open the door to virtually all the Android distribution out there.
@NFound in the AEX ROM thread) is the only one working in developing a Treble ROM for our device. He has released some incomplete Treble ROMs coupled with non-generic system images. Others like @Kranoner in the Hellsgate Kernel thread or @OrdenKrieger in the LineageOS 15.1 are building and kindly sharing unofficial releases of several custom Oreo 8.1 ROMs that are used in the EDL packages below.
@Victor13f has also created guides on how to install the leaked Stock Oreo 8.0 Beta B12 ROM. I really advise to upgrade to any of the current Oreo ROMs since the current unofficial releases work way better than the previous Nougat versions. The custom AOSP Oreo 8.1 ROMs offer a wider spectrum for tweaking for better performance and battery. Custom kernels are adding full featured and optimized drivers for custom ROMs. They support almost everything, including backported drivers from the latest Linux 4.xx official kernel sources.
BACKUP:
Please note that a dirty flash won't work when coming from any non Treblerized Axon 7 (Axon 7 without the vendor partition). So, if you want to keep your information, then you should do a backup of your data before continuing with this guide. You can use the file manager to move your Documents, Downloads, Music, Pictures, Videos, etc... from your internal storage to an external SD card. You can upload them to a cloud service such as Google Drive, One Drive, MEGA, DropBox, etc. Or use the USB connection to move your information to your PC.
DEVICE UNLOCK:
Unlocking your bootloader will trigger a factory reset, and will delete the internal storage along with all the information in your phone. If your Axon 7 bootloader is still locked, you have to follow this guide before proceeding to the rest of this guide. It works for Marshmallow and Nougat stock phones. Please use that thread to ask any question related to unlocking your device.
INSTALLATION INSTRUCTIONS:
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES YOUR DEVICE TO BE UNLOCKED, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
In case you get stuck at any point in this guide, do not panic! There is a straightforward way to go back to stock. Just follow this Unbrick/Restore guide. I've tried to make things as easier as possible for everyone, specially newbies not used to deal with the Axon 7. So, I have created stable custom EDL packages. In order to reduce the risk and complexity, this one Stop ROM Shop performs all the following actions in a single flash:
- installs TWRP custom recovery
- installs my customized Bootstack
- removes unlocked bootloader annoying warning message.
- installs custom Oreo ROM.
- installs google apps.
- installs custom kernel.
- installs magisk root
- creates vendor partition to treblerize your phone, this way it will be futureproof.
- formats vendor partition as ext4 filesystem to complete the previous task.
- And the guide also helps you to format data and cache as f2fs in case you haven't done it already. It provides better battery, performance and extends the lifespan of the internal flash.
I provide here 2 basic EDL package options. Both of them include the vendor partition so you won't have to perform any additional formatting and backup when upgrading to treble roms. Both options are this way future proof, just choose one of them:
OPTION 1: B32+B10 based EDL Package if you prefer stability. It includes:
- N+O custom Bootstack (B32+B10)
- TWRP 3.2.1-7 recovery by NFound
- Resurrection Remix Oreo 6.0.0 2018.05.11 ROM By Kranoner
- Google apps (ARM64, 8.1, micro)
- HellsGate v3.0 Kernel by Kranoner
- Magisk root 16.7
OPTION 2: B12 based EDL Package If you require dual SIM or full support for HDR+ camera apps. It includes:
- O custom Bootstack (B12)
- TWRP 3.2.2 recovery
- AEX 5.7 20180711 ROM by NFound
- Google apps (ARM64, 8.1, micro)
- HellsGate X12 GClang Kernel by Kranoner
- Magisk root 16.7
Once you had chosen your preferred option then proceed with these steps:
Download and Un7zip the chosen package to a folder in your computer, ensuring there are no errors. I have an A2017U, so the American modem is the package default. If you have an A2017 or A2017G just copy your modem firmware, from the corresponding provided modem subfolder, to the main folder. Just overwrite the default American modem file.
Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest Qualcomm drivers.
Enter EDL mode using one of the following options:
by pressing VolUp+VolDn+Power until the power led flashes briefly
Installing a terminal app and typing reboot edl at the app prompt.
connecting your phone to your PC and typing adb reboot edl at your computer's command prompt.
While your phone is completely off, press VolUp+VolDn while connecting your phone to your PC.
If you haven't done yet, it's time to connect your phone to your computer.
Open MiFlash in your computer.
Click Browse button and select the folder you created with the firmware files.
Click Refresh button and your device will appear listed as virtual COM port.
Click Flash button and wait for a few minutes until it finishes. Note the bottom options are not applicable.
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery. Go to Advanced > Terminal and now type: reboot "dm-verity enforcing"
Press VolUp+Power until the phone vibrates to enter into recovery, then release both buttons. Go to Advanced > Terminal and type: reboot disemmcwp
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery for a 3rd time. To ensure everything is clean you should format the DATA partition, including internal storage. Go to settings and ensure "Use rm -rf instead of formatting" option is not selected. Then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Select F2FS and confirm action. Do the same to apply F2FS to the Cache Partition. Now, from the main menu > Wipe, select and clean dalvik.
NOTE: If you receive an error while formatting data, then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Format DATA as EXT4 first and, without leaving TWRP do it again as F2FS. That will fix the issue.
Go to main menu and reboot system.
Complete the setup process so you can continue with the rest of the customizations not included in the basic package:
SOUND EXPERIENCE:
The following steps will provide you with Dolby ATMOS and Viper4Audio pre-processors along with the HiFi DAC output. Please note that the activation of these features will drain your battery faster since both will use your CPU. Nonetheless the benefits are evident. if you want to fully enjoy the audio capabilities of the Axon 7 you should go ahead and use them. The steps are:
Download Mixer_AK4490.zip and Dolby-Oreo.zip to your phone.
Open Magisk Manager app, go to the Download section and Download (do not install yet) Ainur Sauron, Viper4Android FX and Audio Modification Library.
Reboot to recovery the same way you did during System installation, press install, navigate to /sdcard/MagiskManager folder and install Ainur Sauron, Viper4Android (I prefer 2.5.0.5 and traditional interface, however it is all up your personal preference) and Audio Modification Library zip files in that order. Do not reboot after flashing these files, just navigate now to the /sdcard/Download folder and flash Dolby-Oreo.zip and Mixer_AK4490.zip
SCREEN COLOR ENHANCEMENT:
Download and install KCAL Color Calibration/enhancement app. I only modify the Saturation to 62 to get amazing vibrant colors from this AMOLED screen, nonetheless this is a very personal configuration. At the end this has to please your own eyes. . This app optional since Kernel Adiutor and EX Kernel Manager apps can also configure Qualcomm SoC Color Control.
AVOID BATTERY DEGRADATION:
Install Battery charge Limit [ROOT] app. Open it and set Limit charge to 85% and recharge below 79%. Do you want to avoid your battery to wear as the time go by? do not miss this guide to understand why this step is so important for the health of your device.
BETTER CAMERA:
+ Snap Camera App
I am using, and heavily recommend the paid version of Snap Camera HDR. It supports Camera2 API with full manual and HDR support. Find recommended settings here.
Testing now GCAM v4.0. Nonetheless so far I am just starting testing.
Bacon Camera is another Camera I am now actively testing.
The next level of this guide will provide with instructions on how to change recovery, ROM, kernels and all the details and options you have. It is late today so I'll finish it later.
Hope it helps. I will be updating this guide in the future as soon my configuration changes or I find new technologies, apps or patches. If you know about a better option just post your suggestions!
Thanks and credits go to @NFound, @Kranoner, @Infy_AsiX, @roisuke, @Skrem339, @djkuz and you too for bringing up issues and valuable solutions.
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
kitcostantino said:
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
Click to expand...
Click to collapse
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
This was actually why:
NFound said:
TWRP Exclusive™
For "U" models pacth cleaning inscriptions bootloader NO BET!
Warning! "Del Inscription" - only for A2017 and A2017G !!!
Click to expand...
Click to collapse
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
kitcostantino said:
This was actually why:
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
Click to expand...
Click to collapse
Well NFound just tried to say that his solution was not tested at that time in an A2017U. Actually the 2017U is unbrickable thanks to the hardware EDL mode of the Qualcomm SOC.
By the way, I have updated the OP. Now it matches my current configuration. I have also mentioned my current testing efforts in the battery and camera areas.
Regards
Hi. Any fix for Dual Sim? I read through XDA and it seems dual sim is still not fixed. I am getting tired with nougat ROMs but without dual sim I have to stick with it...
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Dave_XDA said:
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Click to expand...
Click to collapse
Yes, the guide is valid for any Axon 7 flavor: Chinese, Euro and Americas.
marcdw said:
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Dave_XDA said:
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Click to expand...
Click to collapse
There is no problem as long you have an Oreo Bootloader. Since you are already running a custom Oreo ROM it means you already have a valid bootloader. Thus, you only need to flash the RR-O ROM. Should you find any problem you can just flash the latest bootloader I link in the OP or go back to AEX. It is important to do a clean install when switching Oreo flavors, as you plan, otherwise you will face problems.
Thanks for this. Been running stock since I got the phone, but missing the old phone days where I used to flash something new like once a week. Gonna try this out tonight I think. Really appreciate the concise directions
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
amphi66 said:
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
Click to expand...
Click to collapse
No issues, you can always go back to B35.
Oki said:
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Click to expand...
Click to collapse
Thanks for the info.
Never used/explored TWRP Exclusive's extras really. In my environment I might break something [emoji39] but cool that everything is there.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
How long does the first boot after flashing the bootloader take? I don't seem to get past the ZTE powered by android screen.
Never mind. Just hold Power + Volume Up at boot.
Thanks !! Oreo AND RR together !!
I will flash it tomorrow on my A2017G !!
(maybe you should write the A2017G compatibility on the first page because this :
RR-O-v6.0.0-20180422-axon7-Unofficial.zip
for the ZTE Axon 7(2017U), by Kranoner
on androidfilehost almost made me missed it )
EDIT : Does this ROM+kernel have the dualsim problem ?
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
ashishv said:
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
Click to expand...
Click to collapse
What have you really done my friend? This guide requires a complete cleanup so it is impossible that you had any locksettings after a clean install. If you follow all the steps and follow the guide then you shouldn't have any problem.
The lock settings get corrupted after migrating to f2fs, and you can also find that problem when dirty flashing some roms or kernels. For that reason, to take care of that step, in the f2fs migration link, there is a link to a very detailed way to cleanup the lock settings. You can find that guide here: https://forum.xda-developers.com/axon-7/how-to/guide-access-locked-axon-7-how-to-t3525403 but, it shouldn't happen when following the steps of this guide. By the way, this guide requires RR Oreo ROM, and you mention you are using AEX Oreo...
Updated OP since this thread became useful to track if magisk works with our stock ROM.
The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.
I suggest that you change the update channel to custom and set the address to 127.0.0.1
For the most recent Magisk version:
mickey36736 said:
I tested 19.3 on B01 oreo and it still bootloop.
Click to expand...
Click to collapse
Thanks for checking @mickey36736
rzarectha said:
It bootloops
Click to expand...
Click to collapse
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
raystef66 said:
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
Click to expand...
Click to collapse
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
rzarectha said:
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
Click to expand...
Click to collapse
You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
Not only on stock...
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Prophet 5 said:
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Click to expand...
Click to collapse
use the uninstaller zip first
Try 17.1. supposedly solves the bootloops.
bootloops are easily fixed by using the uninstaller first.
koftheworld said:
Try 17.1. supposedly solves the bootloops.
Click to expand...
Click to collapse
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
KwesiJnr said:
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
Click to expand...
Click to collapse
You have to use the uninstaller first and then flash 17.1.
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
pnin said:
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
Click to expand...
Click to collapse
Did you use the magisk uninstaller? If not, just reflash your bootloader
koftheworld said:
Did you use the magisk uninstaller? If not, just reflash your bootloader
Click to expand...
Click to collapse
Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?
I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.
That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]
Dark ROM. FTW. [emoji41]
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image).
Click to expand...
Click to collapse
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
Using stock anything above and v17.0 will bootloop using stock,
Just my 2cents, if that your issue just do the following:
-Download v16.7 first in case you don't have it yet, and move it to the SDCard.
* Head back to TWRP
* Flash v16.7 or your preferred release.
* You're good to go.
pnin said:
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
Click to expand...
Click to collapse
Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...
/data/magisk
/data/magisk.img
and files in /data/adb/
Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.
Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
pnin said:
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
Click to expand...
Click to collapse
I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
New beta version released. Still bootloop
Dear All , this method maybe already here somewhere ,
i have tried to root this specific device and i ran into many issues !
but successfully i have done it .
i'll upload the patched file here and i'll mention what method i have done ! ..
unlock boot loader is a must . ( Please read about it in google , All Samsung devices is the same method )
u might repeat the process to times until it successfully unlocked and greyed-out !
Next download this firmware only to be able to run the patched AP .
un-tick Auto-reboot before flashing .
once flash done , power + Volume down to restart , then volume up with power until u boot into the recovery
wipe data . restart . done
to make sure u have done every thing correctly u'll see RED massage once u boot you're device
Firmware ( This is UAE Firmware " T725XXS1ATC5_T725OJM1ASJ3_XSG " ) All Languages included . Link
Patched AP File Link
Please Note that i'm not responsible if u break your Tablet ! .
Proof ( IMG )
GD day :angel:
after rooting is it possible to update firmware to a new one?
moresat said:
after rooting is it possible to update firmware to a new one?
Click to expand...
Click to collapse
No ! ..
Hi
Do I just need to use odin to flash the Firmware you mentioned then use ODIN again to flash the patched ap
I can just add that with this specific fw version and patched ap everything worked on LTE version but I might add my little deviations ...
1st original firmware flash (BL,AP,CP,CSC-non-home one) instantly followed by wipe data in recovery mode.
2nd After the initial setup + wifi connection I installed and updated magisk.
3rd "adb restart bootloader" (here i am not sure if it mattered but anyway) and flush again with the provided Patched AP File (BL,the_patched_AP,CSC - the home one this time ... using CP failed with modem err with me so I just skipped it here)
4th get trough the init setup again with wifi on and open magisk which will install more stuff.
The prerequisites still apply oem unlocked bootloader before you start and keep your battery at least 60-70% since the process drained mine a lot.
You know you are on the right track when you have warning with tablet bootloader is unlocked (at startup yellow) and tablet not running Samsung's official software (red after the first one)
Ive just bought this SM-T725 model android 11. There is no sign of OEM Unlock Bootloader under development. Does anyone know how I can unlock this.
chadandchew said:
Ive just bought this SM-T725 model android 11. There is no sign of OEM Unlock Bootloader under development. Does anyone know how I can unlock this.
Click to expand...
Click to collapse
The option only shows up when you are connected to the internet.
Thanks for reply mate, I got it figured. I also manage to get root and twrp recovery but not both at the same time. After flashing and using twrp recovery I then lose root after reboot and have to flash a patched magisk bundle over odin again. Bit inconvenient but I only intend using twrp now and then for backup/recovery.
Can you recommend a stable rom for this device - far too much google bloat on it for my liking. I tried latest lineage but found it unstable.
chadandchew said:
Thanks for reply mate, I got it figured. I also manage to get root and twrp recovery but not both at the same time. After flashing and using twrp recovery I then lose root after reboot and have to flash a patched magisk bundle over odin again. Bit inconvenient but I only intend using twrp now and then for backup/recovery.
Can you recommend a stable rom for this device - far too much google bloat on it for my liking. I tried latest lineage but found it unstable.
Click to expand...
Click to collapse
Just install LineageOS. Clean, no Bloat, everything smooth and you can have TWRP and Root/Magisk at the same time.
Depending on how much Google you want to have on your device, you might rather choose LOS+MG ( https://lineage.microg.org/) I can highly recommend it. You get rid of Google which debloats it even more and is a plus for your privacy but almost everything works (at leat for me. But migh depend on your needs)
If you like Google, just use normal LineageOS (https://lineageos.org) + GAPPS
Thanks for reply. Will try the LOS ROM later. Wish Google crap would disappear totally. I hate it enormously.
By the way which folder am I looking for on that LOS ROM download page
Ah gts4lv I presume
chadandchew said:
Wish Google crap would disappear totally. I hate it enormously.
Click to expand...
Click to collapse
then go for LOS+MG: https://download.lineage.microg.org/gts4lv/
topaza said:
then go for LOS+MG: https://download.lineage.microg.org/gts4lv/
Click to expand...
Click to collapse
Recently switched to using MicroG Lineage. Timely enough, MicroG passes the SafetyNet now as per the instructions mentioned below and indicated in the attached screenshot. For the fingerprint, I had selected the T720 from the list.
https://www.reddit.com/r/MicroG/comments/shmpng
Along with Aurora store installed as a service, I think you don't need Google anymore.
topaza said:
Just install LineageOS. Clean, no Bloat, everything smooth and you can have TWRP and Root/Magisk at the same time.
Depending on how much Google you want to have on your device, you might rather choose LOS+MG ( https://lineage.microg.org/) I can highly recommend it. You get rid of Google which debloats it even more and is a plus for your privacy but almost everything works (at leat for me. But migh depend on your needs)
If you like Google, just use normal LineageOS (https://lineageos.org) + GAPPS
Click to expand...
Click to collapse
I'm having some problem here:
I can install LineageOS, I can root/Magisk, I can have TWRP, but not all together at once.
Can you help me on how to do this?
Working on a SM-T725 of course, actually rooted, lineage and TWRP installed, but my Magisk can't install modules, it seems it doens't have root privileges.
Thanks in advance for your answer
anybody have an updated one, the file has been archived on the said link... thanks in advance
Only should work on Android 10 based ROMs
External wifi adapters need custom kernel compiling
I've suffered to get the Kali Nethunter working on custom ROMs
U need free storage available (not sure cuz I've formated data then installed and it's been a while but ig not less than 15 gbytes)
Here are the steps :
1.download the file from offensive security website
(Not sure if external links are allowed but here it is ) : https://www.offensive-security.com/kali-linux-nethunter-download/
(Just look for miui davinci file)
2.Download it and extract on whatever device u want the copy the extracted folder to the roo of the storage (of course not the "/" folder the "storage/emulated/0" one
3. Go into extractedFolder/data/app/
And make sure every app there is installed especially the nethunter.apk
4.copy the "kalifs-arm64-full.tar.xz" file to the root
"storage/emulated/0"
5.Open the Nethunter app and go into chroot manager and install chroot
5.Browse for the file location which you copied into the root "storage/emulated/0" and it will start installing it will take up too 10 to 15 minutes
6.You are done now but HID attacks aren't working
7.Go to USB arsenal and change "reset" into anything that has " hid" untill you see a successful toast message then save config to database
Done.
If it helped you hit the thanks button (your choice)
I'll be available asap if anyone has a question
how about monitor mode on wifi dongle? have you tested it?
yaro666 said:
how about monitor mode on wifi dongle? have you tested it?
Click to expand...
Click to collapse
Monitor mode works by default using the internal card
For external I don't have one to test it now
But I am sure it will work as long as it has a supported chip
batman957 said:
I've suffered to get the Kali Nethunter working on custom ROMs
U need free storage available (not sure cuz I've formated data then installed and it's been a while but ig not less than 15 gbytes)
Here are the steps :
1.download the file from offensive security website
(Not sure if external links are allowed but here it is ) :
(Just look for miui davinci file)
2.Download it and extract on whatever device u want the copy the extracted folder to the roo of the storage (of course not the "/" folder the "storage/emulated/0" one
3. Go into extractedFolder/data/app/
And make sure every app there is installed especially the nethunter.apk
4.copy the "kalifs-arm64-full.tar.xz" file to the root
"storage/emulated/0"
5.Open the Nethunter app and go into chroot manager and install chroot
5.Browse for the file location which you copied into the root "storage/emulated/0" and it will start installing it will take up too 10 to 15 minutes
6.You are done now but HID attacks aren't working
7.Go to USB arsenal and change "reset" into anything that has " hid" untill you see a successful toast message then save config to database
Done.
If it helped you hit the thanks button (your choice)
I'll be available asap if anyone has a question
Click to expand...
Click to collapse
i have a mi 9t with unlocked bootloader twrp also rooted using magisk, i flashed my nethunter kernel, but it gets stuck at the nethunter boot logo, how do i fix this, do i need a specific force encryption or something? ive restored the system couple times using mi flash, ive been trying for a couple days now, if you have any solutions please lmk a step by step guide, also is there a way i can do this without flashing it, but also get all the tools working?
Niksa2 said:
i have a mi 9t with unlocked bootloader twrp also rooted using magisk, i flashed my nethunter kernel, but it gets stuck at the nethunter boot logo, how do i fix this, do i need a specific force encryption or something? ive restored the system couple times using mi flash, ive been trying for a couple days now, if you have any solutions please lmk a step by step guide, also is there a way i can do this without flashing it, but also get all the tools working?
Click to expand...
Click to collapse
Sorry I wish I was able to help
But the tag says [CUSTOM ROM]
SO I HAVE No Idea
Maybe try this
Don't flash any thing just follow the procedure listed above and It may work
Just don't flash anything
It won't work, cuz you need kernel for monitoring for example wifi - stock kernels can't put wlan1 (internal or external) wifi to monitor mode, so you won't be able to pentest routers
batman957 said:
Sorry I wish I was able to help
But the tag says [CUSTOM ROM]
SO I HAVE No Idea
Maybe try this
Don't flash any thing just follow the procedure listed above and It may work
Just don't flash anything
Click to expand...
Click to collapse
Which custom ROM? Is it possible with AOSP based (I am on havoc 3.6 now)
hruaiapunte said:
Which custom ROM? Is it possible with AOSP based (I am on havoc 3.6 now)
Click to expand...
Click to collapse
Any whatever you want
I tested on evoX and titanium os
Niksa2 said:
i have a mi 9t with unlocked bootloader twrp also rooted using magisk, i flashed my nethunter kernel, but it gets stuck at the nethunter boot logo, how do i fix this, do i need a specific force encryption or something? ive restored the system couple times using mi flash, ive been trying for a couple days now, if you have any solutions please lmk a step by step guide, also is there a way i can do this without flashing it, but also get all the tools working?
Click to expand...
Click to collapse
Are you trying to install Nethunter onto stock miui rom?
If so, take a look at
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
This worked for me
I'm running full Nethunter on Mi9t stock MiUi Global 11.0.4 rooted with Magisk.zip (via TWRP) and everything just works like a charm. No problems capturing packets, injection support is doing fine and HID seems to work (never tested it but NH App shows its working)
All i had to do was root the Mi9t with Magisk (flashed the zip via TWRP), after checking that everything went well ive booted back into TWRP and flashed the nethunter-2020.2-pre3-davinci-miui-ten-kalifs-full.zip downloaded at https://www.offensive-security.com/kali-linux-nethunter-download/
After that i had to reflash Magisk.zip again (directly after flashing the nethunter.zip without rebooting the device!) and thats it.
As the pre-build images you get at offensive-security allready come with the tweaked kernel u need for injection and monitor mode, theres no need to flash a 'nethunter kernel' afterwards...it works 'out of the box'
Flashing another nethunter kernel afterwards will most probably result in a bootloop... (tried myself a few times with hasty nethunter kernel)
Ive only tried this with the officiall pre-built images on a stock MiUi ROM.
If you want to flash NH on a Costum ROM, you should probably go with the Guide from OP
Happy Hunting
hello, after so many tests they managed like this:
1. twrp orange fox
2.format and wipe
3.flash: fw "miui_DAVINCIGlobal_V11.0.5.0.QFJMIXM_aaab5b40c7_1 0.0.zip" flash "AOSiP-10-Quiche-davinci-20200526-gapps.zip" flash "Magisk-v19.3.zip" flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip"
4.reboot
5.inizializza and upgrade Magisk (download update Magisk to phone)
6.download Busybox module (Magisk)
7.poweroff
8.twrp flash "nethunter-2020.2-davinci-miui-ten-kalifs-full.zip" flash (Magisk downloaded to phone) flash "Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
9.reboot
HardcodedString said:
Are you trying to install Nethunter onto stock miui rom?
If so, take a look at
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
This worked for me
I'm running full Nethunter on Mi9t stock MiUi Global 11.0.4 rooted with Magisk.zip (via TWRP) and everything just works like a charm. No problems capturing packets, injection support is doing fine and HID seems to work (never tested it but NH App shows its working)
All i had to do was root the Mi9t with Magisk (flashed the zip via TWRP), after checking that everything went well ive booted back into TWRP and flashed the nethunter-2020.2-pre3-davinci-miui-ten-kalifs-full.zip downloaded at https://www.offensive-security.com/kali-linux-nethunter-download/
After that i had to reflash Magisk.zip again (directly after flashing the nethunter.zip without rebooting the device!) and thats it.
As the pre-build images you get at offensive-security allready come with the tweaked kernel u need for injection and monitor mode, theres no need to flash a 'nethunter kernel' afterwards...it works 'out of the box'
Flashing another nethunter kernel afterwards will most probably result in a bootloop... (tried myself a few times with hasty nethunter kernel)
Ive only tried this with the officiall pre-built images on a stock MiUi ROM.
If you want to flash NH on a Costum ROM, you should probably go with the Guide from OP
Happy Hunting
Click to expand...
Click to collapse
henghst69 said:
1. twrp orange fox
2.format and wipe
3.flash: fw "miui_DAVINCIGlobal_V11.0.5.0.QFJMIXM_aaab5b40c7_1 0.0.zip" flash "AOSiP-10-Quiche-davinci-20200526-gapps.zip" flash "Magisk-v19.3.zip" flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip"
4.reboot
5.inizializza and upgrade Magisk (download update Magisk to phone)
6.download Busybox module (Magisk)
7.poweroff
8.twrp flash "nethunter-2020.2-davinci-miui-ten-kalifs-full.zip" flash (Magisk downloaded to phone) flash "Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
9.reboot
Click to expand...
Click to collapse
Does Kali work with QFJEUXM 11.0.5?
By following the cited guide
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
I don't see anything about:
- Format Data and wipe
Is it necessary?
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Is it necessary to flash, maybe Kali breaks the stock built-in GApps?
-"Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
Is it also necessary to flash, Magisk cannot make it pass SafetyNet without?
Also, does installing Kali affect:
- Widevine L1 (dropping to L3)
- 4G/4G+ (by disabling some bands or carrier aggregation)?
One more question, what would be a procedure to go back to stock?
Manually updating to the stock Recovery/ZIP firmware from System update/Choose update package would be enough or flashing Fastboot/TGZ firmware by Mi Flash Tool will be needed?
zgfg said:
Does Kali work with QFJEUXM 11.0.5?
By following the cited guide
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
I don't see anything about:
- Format Data and wipe
Is it necessary?
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Is it necessary to flash, maybe Kali breaks the stock built-in GApps?
-"Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
Is it also necessary to flash, Magisk cannot make it pass SafetyNet without?
Also, does installing Kali affect:
- Widevine L1 (dropping to L3)
- 4G/4G+ (by disabling some bands or carrier aggregation)?
One more question, what would be a procedure to go back to stock?
Manually updating to the stock Recovery/ZIP firmware from System update/Choose update package would be enough or flashing Fastboot/TGZ firmware by Mi Flash Tool will be needed?
Click to expand...
Click to collapse
-Does Kali work with QFJEUXM 11.0.5?
Well, somewhere i've read that it should work with 11.0.5 too but dont remember where...would have to search for it again to provide a link to you...
- Format Data and wipe
Not sure if its necessary, but i did so. Its always a good thing to do before flashing any ROM.
Just try it without that step and you'll see...you can always reflash to stock if you get any errors, so just give it a shot mate
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Nope, thats not necessary for sure. I'm using it with the stock built gapps and its working fine
-Disable_Dm-rity_ForceEncrypt_03.04.2020.zip
Thats pretty strange with that ForceEncrypt step, some say they had to others not. I did not flash it to be honest and everythings okay so far. But theres a Chance that you will have to! Maybe it belongs to which ROM you are using (global,eu,chinese) but cant tell for sure...
So this one you will have to figure out yourself, sry.
-4G and LTE is working good for me, so i'd say kali isnt affecting it
-About Widefine, well i dont know to be honest...im watching Prime and Sky Go on the Phone sometimes but for the Quality Prime just says 'optimal' and Sky Go 'HD'...it looks great for sure but i cant tell the exact Quality....if theres a way to check that, let me know and i'll be happy to do that for you
-One more question, what would be a procedure to go back to stock?
I would just do a wipe/format and flash the stock MiUI image or better, your backup via TWRP (or any other custom Recovery)
For me, Fastboot by MiFlashTool is always the last option. If nothing else works, Fastboot is a Livesaver but thats just 'my way' of doing it, there are probably many others who say otherwise!
Sometimes it needs a lot of testing to figure out the best way for your specific device, so always do a backup and flash a custom recovery before flashing Nethunter. That way, its always posible to get back to Stock if you encounter any bootloops/problems after the installation.
Its like always while playing around with any OS...if it wont work, you just have to "Try Harder"
Im happy to help anyway, if you got any more Questions just shout out mate
HardcodedString said:
-Does Kali work with QFJEUXM 11.0.5?
Well, somewhere i've read that it should work with 11.0.5 too but dont remember where...would have to search for it again to provide a link to you...
- Format Data and wipe
Not sure if its necessary, but i did so. Its always a good thing to do before flashing any ROM.
Just try it without that step and you'll see...you can always reflash to stock if you get any errors, so just give it a shot mate
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Nope, thats not necessary for sure. I'm using it with the stock built gapps and its working fine
-Disable_Dm-rity_ForceEncrypt_03.04.2020.zip
Thats pretty strange with that ForceEncrypt step, some say they had to others not. I did not flash it to be honest and everythings okay so far. But theres a Chance that you will have to! Maybe it belongs to which ROM you are using (global,eu,chinese) but cant tell for sure...
So this one you will have to figure out yourself, sry.
-4G and LTE is working good for me, so i'd say kali isnt affecting it
-About Widefine, well i dont know to be honest...im watching Prime and Sky Go on the Phone sometimes but for the Quality Prime just says 'optimal' and Sky Go 'HD'...it looks great for sure but i cant tell the exact Quality....if theres a way to check that, let me know and i'll be happy to do that for you
-One more question, what would be a procedure to go back to stock?
I would just do a wipe/format and flash the stock MiUI image or better, your backup via TWRP (or any other custom Recovery)
For me, Fastboot by MiFlashTool is always the last option. If nothing else works, Fastboot is a Livesaver but thats just 'my way' of doing it, there are probably many others who say otherwise!
Sometimes it needs a lot of testing to figure out the best way for your specific device, so always do a backup and flash a custom recovery before flashing Nethunter. That way, its always posible to get back to Stock if you encounter any bootloops/problems after the installation.
Its like always while playing around with any OS...if it wont work, you just have to "Try Harder"
Im happy to help anyway, if you got any more Questions just shout out mate
Click to expand...
Click to collapse
Thank you a lot for your answer.
Btw, few days ago I upgraded to QFJEUXM v11.0.6 (so no more 11.0.5), which is newer than the Kali pre-built image, but according to v11.0.6 Changelog only Security patch was updated
I'm still tempting to try Kali (currently having new official TWRP v3.4.0, Magisk Canary 20416 and Hasty kernel)...
You can check your Widevine Security level (still interested if you have L1) by
https://play.google.com/store/apps/details?id=flar2.devcheck
https://play.google.com/store/apps/details?id=com.androidfung.drminfo
By going back to stock you said flashing MIUI. - so you mean flashing ZIP/Recovery firmware through TWRP?
zgfg said:
Thank you a lot for your answer.
Btw, few days ago I upgraded to QFJEUXM v11.0.6 (so no more 11.0.5), which is newer than the Kali pre-built image, but according to v11.0.6 Changelog only Security patch was updated
I'm still tempting to try Kali (currently having new official TWRP v3.4.0, Magisk Canary 20416 and Hasty kernel)...
You can check your Widevine Security level (still interested if you have L1) by
https://play.google.com/store/apps/details?id=flar2.devcheck
https://play.google.com/store/apps/details?id=com.androidfung.drminfo
By going back to stock you said flashing MIUI. - so you mean flashing ZIP/Recovery firmware through TWRP?
Click to expand...
Click to collapse
No problem, i'm happy to help wherever i can :good:
-Btw, few days ago I upgraded to QFJEUXM v11.0.6...
Yeah, im not surprised bout that...sorry for the late answer :/
Thank you for pointing out these two Apps mate!
I've checked my Widevine Security Level and both Apps showing Widefine L1 (Screenshots attached) so no downgrade after flashing Nethunter
Yes thats correct, to get back to stock you would have to flash the ZIP/Recovery firmware through TWRP.Only if that doesnt work you'd have to do it through Fastboot.
If you did a full backup (i.e. through TWRP) of your system before flashing Nethunter, you would be able to restore it by flashing the recovery,dtbo,boot and system images one by one through TWRP/Fastboot (not sure but i think it should be enough to just reflash the system.img, boot.img and dtbo.img to get your pre-Nethunter Setup/Specs back (English isnt my native Language so in case you dont get what im trying to explain...that means your stock 11.0.6 with TWRP v3.4.0, Magisk Canary 20416 and the Hasty kernel including all your Settings and Stuff)
You wouldnt have to flash a 'naked stock rom' if Nethunter doesnt work
If you're still not comfortable enough to install Nethunter onto your Device, just wait a few more Days.
I will try to get Nethunter running on the 11.0.6 ROM myself as soon as i have some more time!Will also try it with your Specs/Setup by then
Hi, i cant install chroot.
image transparente png
sinanlenfom said:
Hi, i cant install chroot.
image transparente png
Click to expand...
Click to collapse
Obviously you set the wrong Folder Name...just choose one of the three options from Screenshot 1!?
But to be honest, and i really dont want to offend you, if you couldnt figure that one out yourself you shouldnt install Nethunter at all...
@zgfg
Sorry mate, wasnt able to try it so far.....very busy at work atm! Will do the next few Days
HardcodedString said:
@zgfg
Sorry mate, wasnt able to try it so far.....very busy at work atm! Will do the next few Days
Click to expand...
Click to collapse
Thanks
HardcodedString said:
Sorry mate, wasnt able to try it so far.....very busy at work atm! Will do the next few Days
Click to expand...
Click to collapse
Ok, I installed NetHunter zip image for Davinci over QFJEUXM v11.0.6.0 and re-rooted with Magisk Canary v20419.
Ran NetHunter app and chroot.
I think it looks ok - screenshots attached
Btw, tried yesterday Wifite to 'break' three WPA WLANs (Private, not Enterprise) for whom I actually know passwords - their passwords are weak like vesna1970 or 136923457
Wifite was running for two or three hours, trying Pixie-Dust, NULL PIN, PIN Attack, Handshake capture but eventually failed for all three connections
I will set up a WEP AP at home next week to test again, but who nowadays still uses WEP. Almost everybody would be using WPA, and with stronger passwords than above
If so, I doubt it is of big (educational) use and I am suspect about YT movies where they successfully break WPA in 30 minutes (or more)
Receiving a notification to update NetHunter from Installed 2020.2 to 2020.2?!
But the Update fails with Error -110 - on screenshots
Btw, I have successfully updated (couple of times) packages from NetHunter app, currently there is nothing to update there
Edit:
Fixed the NH app update notification: open NetHunter Store, Settings, Expert mode and untick Privilege Extention.
Let it update the NetHunter app