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
Related
This is for the Sprint SM-T587P "gtaxlqltespr" Galaxy Tab A 10.1 variant only.
As far as I can tell, the Nougat update came out for the Sprint Variant sometime around the 20th of September 2017. Update to the T587PVPU1BQI1 Nougat update if you have not already.
1. Read all instructions, there are no known issues. Be on 7.0.0 official. (QI1)
2 Enable Developer Options. Settings, About Device, Software info, tap on build number until it is enabled.
3. Enable OEM unlock and USB Debugging in the Developer Options menu.
There are a couple options here. You can do any combination of the following:
install TWRP
root via superuser (requires installing TWRP)
disable dm-verity (requires installing TWRP)
root by flashing magisk patched bootimage (does not require TWRP)
disable force-encryption (requires installing twrp)(required if you want TWRP to see /data/ files)(not required for flashing zips such as superuser through TWRP)
To install TWRP:
1. Boot into download mode
2. Launch ODIN, Uncheck "Auto Reboot" in the options tab. Flash included TWRP file in the AP section of ODIN.
To Disable Force-Encryption (if want to see /data/ in twrp)
1. Install TWRP recovery
2 Boot into TWRP recovery
3. Format Data
4. Reboot into TWRP from TWRP reboot menu, without rebooting into system.
5. Flash the included superuser.zip to disable force-encryption and dm-verity
To Root via superuser or disable dm-verity
1. Install TWRP recovery.
2. Boot into TWRP recovery
3. flash superuser.zip (this needs to be done with ADB if you have not disabled force-encryption and are unable to see /data/)
Superuser root provided as-is. Magisk is the recommended root. If you prefer the outdated, beta, un-updatable phh superuser binary which breaks safetynet that's all you. However it is the only way i have found to disable dm-verity.
Magisk v16 root:
Device is stock
If you have not installed twrp, disabled dm-verity, or disabled force encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-dm-patched_boot.img.tar"
Disabled dm-verity, but NOT force-encryption
If you did not format DATA in TWRP and have installed superuser.zip using ADB:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-patched_boot.img.tar"
Disabled Both
If you disabled dm-verity AND disabled force-encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "Magiskv16_patched_boot.img.tar"
WIFI IS NOW WORKING AFTER ROOT/BOOT PATCH
Recovery: twrp-3.1.1-0-gtaxlqltespr.tar
phh's Superuser.zip
fe-dm-patched_boot.img.tar
fe-patched_boot.img.tar
Magiskv16_patched_boot.img.tar
Magisk Manager 5.6.1(105)
XposedInstaller_3.1.4_Magisk.apk
Stock 7.0.0 boot image
Stock 7.0.0 Recovery
phh's Superuser
Nougat Firmware
AP
BP
CP
CSC
Gonna try it now!!! Been waiting for along time.... thanks
Sent from my Sprint Samsung Galaxy Note5 using XDA Labs
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
T587P need stock firmware and recovery
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Ok what i did being i just didnt have recovery and wifi , i restored the tablet in samsung smart switch now everything works again as it should..i will hold out until we have a safe root for our T587P devices. Thank you
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Any updates on WiFi fix?
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Rpartin04 said:
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
Click to expand...
Click to collapse
A stock kernel has to be built from source.
Rpartin04 said:
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
Click to expand...
Click to collapse
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
DavidBeckett.db said:
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Click to expand...
Click to collapse
I didnt realize the firmware was behind a paywall, the correct link has been posted.
This is a proper root via the magisk patched boot. There is no reason to flash the recovery at all.
Rpartin04 said:
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Click to expand...
Click to collapse
Anyone who doesnt read the first post closely enough to locate locate the stock firmware being made to pay for it seems like a form of natural selection. Edit: or that would be the case were this the case, however, i posted the wrong link in the OP ( i had visited a lot to find the firmware, i misremembered which one was correct.)
ashyx said:
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Click to expand...
Click to collapse
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
arlyn said:
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
Click to expand...
Click to collapse
This as well is not a free deal. It would help out a ton if you just link these files to your account via Google drive, mediafire, ect....
EDIT!!!!
I didn't scroll all the way down... ignore me
arlyn said:
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
Click to expand...
Click to collapse
Did you edit it? If not must be going blind.
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Rpartin04 said:
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Click to expand...
Click to collapse
Haha, I didn't realize you had to subscribe to your own threads, I didn't know people were even replying in here for weeks. Thank you for attempting to compile, i know there are some tutorials on xda, i'm pretty sure an flashing an SELinux permissive kernel will fix the wifi issue with the magisk root. I do not know that I'll ever have the time or motivation to compile it myself, but I can help to test.
Thanks arlyn! Will definitely be trying this out.
Says root is not properly installled.... any ideas? I followed directions to a T... even flashed back to stock nougat and tried a 2nd time...
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!
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
First, you must be unlocked. You can follow the instructions here for making that happen.
If you are first starting, you should first unlock, then install this ROM, and THEN install Magisk for root or any other addons. This rom uses addon.d to preserve Magisk and any other addons, but any system modifications like Magisk, gapps, etc, that you have installed prior to this ROM will NOT be preserved.
If you've already unlocked and installed Magisk, then after installing this ROM you need to reinstall Magisk in TWRP.
Starting with 6.2.6.6, Magisk is always installed.
Beyond that, Magisk and any other addons will be preserved as you flash newer roms. Consequently, if you would like to remove root, you will need to wipe /system in TWRP prior to installing this ROM. That will prevent it from being restored when installing the ROM.
Thanks to @k4y0z and @xyz` for the unlock.
NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE.
Changelog and Downloads:
October 24, 2021 - 6.2.8.1_r3 (md5sum: 3795edc2d640932a88da39da8a0811c5)
July 17, 2021 - 6.2.8.1_r2 (md5sum: e9e37a2d485a3397df041938818421e9)
This includes updated tz firmware to fix the device locking up when trying to play video.
April 3, 2021 - 6.2.8.0_r1 (md5sum: 2efdfc5728caba2953a351a082023a59)
December 26, 2020 - 6.2.7.7_r1 (md5sum: b835e29bb29458004063121a422c1bf7)
May 3, 2020 - 6.2.7.1_r1 (md5sum: 56ec885e5bd258682c90e8f08371301d)
November 10, 2019 - 6.2.6.8_r1 (md5sum: 8cdc16239df36c8640004232918c5477)
October 19, 2019 - 6.2.6.6_r1 (md5sum: df8f3d033fddf66a1b4aa3a6b228196b)
Starting with this version, Magisk will always be installed.
This includes updated tz firmware to fix LICENSE_ERROR with Prime video.
October 13, 2019 - 6.2.6.5_r1 (md5sum: bdde0303d8db5495ac6dc2aaf476d2f4)
Awesome!! Thanks!!
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
vasir13 said:
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
Click to expand...
Click to collapse
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
rbox said:
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
Click to expand...
Click to collapse
Yes .... I know ... called selective reading .... I got into TWRP and will try your image now ...
Happy to see the pre-rooted roms from you on mantis! It's starting to feel like the good old days again
Thank you, I feel safer already.
Any idea what version of gapps would work on this? Also, any idea if installing nanodroid, patched playstore & patching the ROM for signature spoofing be dangerous (as in bugger up the BL/TWRP)?
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Hi,
I successfully installed the hacked bootloader and TWRP a few days ago, but I did not do anything else. I was still on the original 6.2.5.8 version.
Today I wanted to flash the prerooted 6.2.6.5 and I can't manage to boot it (and since I did not expect problems, I did not make a backup of the old system). I cannot go past the "firetv" boot logo and in this stage "adb logcat" is not yet working, so I don't see any logs.
First boot was just installing the ROM. Second boot with previously wiping Cache / Dalvik. Finally I wiped also data (and Cache/Dalvik again). I cannot get past the boot logo.
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Thanks Tim
tehlers said:
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Click to expand...
Click to collapse
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Sus_i said:
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Click to expand...
Click to collapse
Yes, I have checked MD5 on my notebook after download, but not after pushing the file to the stick. I will do that now and post it here (with edit). But I doubt this being the issue.
EDIT: MD5 of the zip in the stick is also ok.
tehlers said:
EDIT: MD5 of the zip in the stick is also ok.
Click to expand...
Click to collapse
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Edit: Have you flashed the magisk.zip behind the ROM?
Sus_i said:
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Click to expand...
Click to collapse
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
EDIT: As I said in the first post, I did not do anything with the original ROM, except flashing the hacked BL and TWRP, no Magisk or whatever.
Best
Tim
tehlers said:
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
Best
Tim
Click to expand...
Click to collapse
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Sus_i said:
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
Click to expand...
Click to collapse
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
T1inkering said:
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Click to expand...
Click to collapse
for example with ADB / TWRP Commands, something like that...
Code:
adb push ~/Desktop/mantis-6.2.6.5-rooted_r1.zip /sdcard/
adb push ~/Desktop/Magisk-v19.3.zip /sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.5-rooted_r1.zip
twrp install /sdcard/Magisk-v19.3.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
tehlers said:
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
Click to expand...
Click to collapse
It is mentioned.. but not thats an issue without flashing magisk
Sus_i said:
It is mentioned.. but not thats an issue without flashing magisk
Click to expand...
Click to collapse
That's what I mean. It's not mentioned that you need Magisk in any case (to boot the image as such *and* probably also to get root [which is not prerooted then?]).
Thanks again!
puppinoo said:
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Click to expand...
Click to collapse
I reply to myself and happy to confirm I installed this "generic" image to my US Stick 4K and after I accept terms of use *Italian* Alexa and Prime video seem to wotk fine.
If I remember well my previous image was the 6.2.5.8 (basically the one I installed when the exploit for Fire TV Stick 2 (Tank) was released but can't be 100% sure.
Now I have to try it on my *Italian* Stick 4k (bought on amazon.it).
Amazing and thanks a lot again.
Puppinoo.
So great to see @rbox 'es prerooted roms for the Fire TV Stick 4k
There are some things that I am not familiar with:
1. What is magisk for and what if I don't install it?
2. Does root not work without magisk?
On the older Fire TV Devices we did never have to install magisk or so and it was prerooted with rboxes roms and root was working. Why is everybody talking about magisk? Can magisk break anything or be critical like xposed was on the Fire TV 2 box? I remember that xposed framework was a pretty messy issue for recent Fire TV 2 (Sloane) pre-rooted roms. Magisk seems to go deeply into the system, similar to xposed framework, isn't it?
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
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!