Related
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
nmyshkin said:
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
Click to expand...
Click to collapse
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
Does this work on 16GB only or does this include 8GB version?
It should work on both, they run the same ROMs, only requirement is Lollipop+.
Edit: I'm making the assumption users know which ROMs accommodate the 512mb models. Obviously, the ROM needs to be functional for Magisk to work.
fddm said:
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
Click to expand...
Click to collapse
OK, no joy here. After waiting for a couple of hours to download a ROM (!) I finally put it all together. The system hangs at the "N" screen, never getting to the Cyanoboot screen. I tried this on an 8 GB tablet because I didn't want to mess majorly with my 16 GB one, but as you say, the result should be the same
BTW, there were no error messages I detected as the Magisk zip installed.
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
fddm said:
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
Click to expand...
Click to collapse
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
nmyshkin said:
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
Click to expand...
Click to collapse
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
fddm said:
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
Click to expand...
Click to collapse
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Your right, sorry, after testing again I can reproduce this error. Going to have a closer look, see if I can correct it. Thank you!
Edit: problem found, fix incoming
nmyshkin said:
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Click to expand...
Click to collapse
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
fddm said:
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
Click to expand...
Click to collapse
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
Anyway, I now have questions as I'm no magiskan I read about Magisk before and even tried it on a similar ROM (to no avail, of course), but there are many things I don't fully understand.
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
2. I need to install an SU manager, yes? MM seems to indicate that it can't find any. Seems like I recall it was based on the phh su so can I just install the manager app for that? Is that what I need to effect "root" or do I already have it?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
nmyshkin said:
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
Click to expand...
Click to collapse
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
fddm said:
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
Click to expand...
Click to collapse
Things are looking up I searched the AdAway issue and see there is a newer version that seems to solve the problem for people using Nougat ROMs (including someone running Magisk!). Worked like a charm. ES File Explorer seemed to have root access issues but I went into MM to see what the issue was and managed to manually turn on root access. Seems OK now.
As you say, part of this is getting used to it. I'm not seriously thinking this ROM is going to be good for the 8 GB tablet (for one thing I cannot tolerate the shutdown bug) but it's fun to see what's going on and try out this approach. Who knows? Someday there may be an Unlegacy AOSP 8.1 "mini-me" that will run (and maybe even shut down...) and I'll have the know-how to deal with it.
Thanks for your efforts. Sorry to have been a bit of a pain.
nmyshkin said:
Thanks for your efforts. Sorry to have been a bit of a pain.
Click to expand...
Click to collapse
No, you were perfect. You provided essential information and kept trying when you hit a wall, and we got working Magisk in the end. Couldn't be happier, thank you!
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
https://developers.google.com/android/ota
Ota is live too...
Where I found the changelog?
Thanks
shark147 said:
Where I found the changelog?
Thanks
Click to expand...
Click to collapse
Same place as always: https://source.android.com/security/bulletin/pixel/2019-05-01.html
There doesn't seem to be much though:
This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices.
Click to expand...
Click to collapse
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
CSX321 said:
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
Click to expand...
Click to collapse
1) flash-all (minus -w). Phone reboots to system automatically.
2) shut down and boot to BL
3) fastboot boot twrp-3.3.0-0-blueline.img (be sure to have a copy of the .img file on your phone)
4) install twrp using Advanced > Install Recovery Ramdisk > twrp-3.3.0-0-blueline.img
5) boot to system
6) shut down and boot to BL>recovery (TWRP loads)
7) install Magisk-v19.1 (I did already have 19.1 installed on this phone via Magisk Manager update/Magisk update from before the May image came out in case it matters, so if necessary install 18.1 and then update to 19.1 with Magisk Manager)
8) reboot to system
9) confirm root and install kernel (for me that was ElementalX automated install using EX Kernel Manager app but installing the kernel by going back to TWRP and flashing should do the same)
The two things I might be doing different than others are not using ADB to get back to BL or recovery (I always use the key combo) and booting to system before next step (I don't stack my TWRP/Magisk/kernel installs). Hope this helps.
Whew! Back in business. Thanks!
CSX321 said:
Whew! Back in business. Thanks!
Click to expand...
Click to collapse
That's cool. Which part was the culprit?
sliding_billy said:
That's cool. Which part was the culprit?
Click to expand...
Click to collapse
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
CSX321 said:
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
Click to expand...
Click to collapse
I'd just be spit balling at this point like you are, but at least you are up and running. I do think there is possibly something going on with Magisk going from 18.1 to 19.1 without Manager doing the back end work (even if it happened previously) since Magisk still does retain some data even if root is lost during the upgrade. There are certainly some changes that occured between 18.1 and 19.0 beta since coming from 18.1 you would need to redo your Magisk hide check marks. Either that or using MM to patch boot may have completely changed.
sliding_billy said:
There are certainly some changes that occured between 18.1 and 19.0 beta
Click to expand...
Click to collapse
I probably just had something in some weird state, because I ran 18.1, 19.something beta, 19.something canary, then back to 19.1 stable when it came out. I forgot, I also ran the uninstaller at some point in my previous attempts.
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Same question
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I was coming to ask the same question, only I am in WA and have T-mobile. Stock, not rooted. Not had an issue before.
Same here. New P3 during April, so awaiting first security update for my new device. Carrier is AT&T, but why would that matter, right? Just seems strange having to wait. I got the impression that monthly updates for Pixels would come out the same day they were announced as being available. Live and learn I guess.
Finally popped this evening (5/16/2019). No clue why the delay.
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I have a Pixel 3 on Google Fi and still haven't gotten the update. Contacted support yesterday and they couldn't find anything wrong. They "promised" I'd get it. Always gotten them within a day or two before.
I guess I just never looked into this before since I'm a new Pixel user or I'm just naive but I assumed when I got a Pixel phones updates would not have to be pushed through my carrier anymore? No May update here on my stock Pixel 3 on T-Mobile.
Always get OTA on the day of release, stock phone, T-Mobile, the Netherlands.
(Pixel didn't launch in the Netherlands, I got it from Germany)
Just installed the may update OTA.
Anyone else having issues with apps accessing the gallery. Both WhatsApp and stock messenger now taking ages to display the thumbnails of the images and videos in my gallery when I add them to a message.
ok could I get some hints here on how to update?
I have rooted and I have magisk.
hi there
i have unlocked bootloader and i can root my phone with magisk completely
but when i try to root with supersu , it flash completely in twrp but nothing appear in the app drawer and when i install apk it says phone is not rooted !
any one rooted mi a3 or any android one device with supersu ?
up up uppp
Why do you want to install root app which hasn't been updated for more than 2 years and pretty much no one uses it (at least with recent devices/Android versions)?
_mysiak_ said:
Why do you want to install root app which hasn't been updated for more than 2 years and pretty much no one uses it (at least with recent devices/Android versions)?
Click to expand...
Click to collapse
becauae when i flash magisk my phone start lagging and other problems ...
#MmdRza said:
becauae when i flash magisk my phone start lagging and other problems ...
Click to expand...
Click to collapse
Not sure how could be that related to Magisk, there are probably thousands of Magisk users with A3 phone and so far no one reported such issue. Personally I see no lagging or "other" problems while using Magisk. In each case, it would be better to invest your time to troubleshooting Magisk, where you have a high chance of finding a solution and possibly receiving a fix from developer (if your issue is valid). With SuperSU you're on your own.
SuperSU is very outdate
It´s a Crazy idea to install SuperSU in 2020, Magisk is more, more, and more better.
Hi.
Well, I have faced the same problem: flash magisk and... soft brick ?. I followed this tutorial https://magisk.me/root-xiaomi-mi-a3/ and
I tried 2 times and doesn't work, so I went back to stock room.
Please somebody could help to solve. Thanks and sorry my bad english, I speak Portuguese...
the tutorial posted in the link above uses a specific boot.img (V10.3.5.0.PFQEUXM) are you sure you are using the correct rom to match the tutorial ?
instead why not use TWRP and root from there by flashing Magisk.zip over a clean Flash of the rom of your choice..?
i have used Magisk on my A3 with many different roms , no lagging issues atall , so i cannot suggest supersu as im not even sure it possible with the A3...
_mysiak_ said:
Not sure how could be that related to Magisk, there are probably thousands of Magisk users with A3 phone and so far no one reported such issue. Personally I see no lagging or "other" problems while using Magisk. In each case, it would be better to invest your time to troubleshooting Magisk, where you have a high chance of finding a solution and possibly receiving a fix from developer (if your issue is valid). With SuperSU you're on your own.
Click to expand...
Click to collapse
I recently installed magisk and my battery drain increases too much. I had to uninstall and flash stock rom
krishna.telgave said:
I recently installed magisk and my battery drain increases too much. I had to uninstall and flash stock rom
Click to expand...
Click to collapse
Can't confirm this, I have Magisk on all my phones and it doesn't cause any "battery drain". What was your screen off battery consumption with and without Magisk? I see no difference if I have Magisk installed or not.
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