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?
Related
I have a 16gb wifi 7" HDX (Thor).
I was on 13.3.2.4 forever rooted with ota blocked. I saw TWRP was available and the latest SW too. I enjoy it on the HD7 we have, so I figured I"d flash TWRP, then install the latest rom 14.4.5.2.
I had to downgrade in order to flash TWRP, so I used safestrap and flashed the roll back images provided by @ggow and followed the instructions listed here - http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 - with no problems at this point. I then booted up into the 13.3.1.0 with a factory wiped system.
I then installed towelroot, rooted, installed flashify and installed TWRP recovery 2.8.5.0 from here - http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Once that was done, I flashed the 14.4.5.2 TWRP file provided by @Cpasjuste - http://forum.xda-developers.com/showpost.php?p=57988207&postcount=19
Booted up and followed the guide provided here - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - to install gapps and stop OTA. The only thing I think I did different was, when I was prompted to overwrite certain system files when copying gapps folders over, I declined. Unfortunately the tablet is at home and I can't get to it until tonight.
My problem - Amazon Instant Video and my Kindle Library won't load properly. I can install apps, listen to Amazon music, and shop the store, but I cannot get video or books to work.
I will try to re-copy the gapps packages over and let everything overwrite, but I'm not sure if that is the issue.
Has anyone experienced this before?
Thanks.
riggsandroid said:
I have a 16gb wifi 7" HDX (Thor).
I was on 13.3.2.4 forever rooted with ota blocked. I saw TWRP was available and the latest SW too. I enjoy it on the HD7 we have, so I figured I"d flash TWRP, then install the latest rom 14.4.5.2.
I had to downgrade in order to flash TWRP, so I used safestrap and flashed the roll back images provided by @ggow and followed the instructions listed here - http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 - with no problems at this point. I then booted up into the 13.3.1.0 with a factory wiped system.
I then installed towelroot, rooted, installed flashify and installed TWRP recovery 2.8.5.0 from here - http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Once that was done, I flashed the 14.4.5.2 TWRP file provided by @Cpasjuste - http://forum.xda-developers.com/showpost.php?p=57988207&postcount=19
Booted up and followed the guide provided here - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - to install gapps and stop OTA. The only thing I think I did different was, when I was prompted to overwrite certain system files when copying gapps folders over, I declined. Unfortunately the tablet is at home and I can't get to it until tonight.
My problem - Amazon Instant Video and my Kindle Library won't load properly. I can install apps, listen to Amazon music, and shop the store, but I cannot get video or books to work.
I will try to re-copy the gapps packages over and let everything overwrite, but I'm not sure if that is the issue.
Has anyone experienced this before?
Thanks.
Click to expand...
Click to collapse
You have to upgrade to OS 3.2.3.2.3, it doesn't work with 3.1.0
kulturschock said:
You have to upgrade to OS 3.2.3.2.3, it doesn't work with 3.1.0
Click to expand...
Click to collapse
i'm currently on 13.4.5.2 - not 13.3.1.0.
Can you clarify what you mean?
Thanks.
riggsandroid said:
i'm currently on 13.4.5.2 - not 13.3.1.0.
Can you clarify what you mean?
Thanks.
Click to expand...
Click to collapse
You have flashed the 13.4.5.2 over the 13.3.1.0 not over the 13.3.2.3, this is the problem. I had the same problem.
You can find infos in the nexus 2.0.5 thread, I think, the problem has the same reason. I think, you need the bootloaader or the kernel of the 13.3.2.3 OS.
There is a thread with the kernel of the 13.3.2.3 to flash, perhaps this works. Otherwise
You have to flash the whole bin-file, then root, then flash twrp and then flash the higher 13.4.5.2 OS. This worked for me.
---------- Post added at 07:49 PM ---------- Previous post was at 06:54 PM ----------
Here is the link to the thread of the bootloader you need:
http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
kulturschock said:
You have flashed the 13.4.5.2 over the 13.3.1.0 not over the 13.3.2.3, this is the problem. I had the same problem.
You can find infos in the nexus 2.0.5 thread, I think, the problem has the same reason. I think, you need the bootloaader or the kernel of the 13.3.2.3 OS.
There is a thread with the kernel of the 13.3.2.3 to flash, perhaps this works. Otherwise
You have to flash the whole bin-file, then root, then flash twrp and then flash the higher 13.4.5.2 OS. This worked for me.
Click to expand...
Click to collapse
i'm going to try flashing the updated bootloader in TWRP first provided here - http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
Did you have the SAME issues that I've listed or just similar?
Looks like you updated your post as I was making mine. Will let you know how it goes tonight.
I had the same problem, I got messages with license error in prime video, many others things worked normally but not all. For example, l couldn't flash other OS like my backup of the 3.2.6 made by safestrap, this worked well, too.
kulturschock said:
I had the same problem, I got messages with license error in prime video, many others things worked normally but not all. For example, l couldn't flash other OS like my backup of the 3.2.6 made by safestrap, this worked well, too.
Click to expand...
Click to collapse
Yea that didn't fix it. Next I'm going to deregister and reflash the 13.4.5.2 and see if that fixes it.
Can I just flash the 3.2.3.2 bin with twrp?
Edit
So I deregistered, wiped and reflashed 13.4.5.2 and have working video and books again. Haven't touched gapps yet but glad to see its semi sorted.
Since there seems to be no way of installing current (and future) patches from stock recovery when the device is rooted, it'd be good to know if someone has information about whether it's possible or not to develop a custom recovery. The old method using 5.02 droidboot won't work because the updates mess up the whole system if you use them. So since we have unlockable bootloaders in 5.1, could there be the possibility of compiling a permanent CWM?
since there seems no one to be working on it at the moment, i'll start a few tries myself and document the progress in this thread. Feel free to help or comment.
For now, i', stuck at unlocking the bootloader and still don't know why. "OEM unlock" was set in the developer options, rebooted to fastboot and tried "fastboot oem unlock". Results as attached. :\
I'll google a bit around and see if i can get it working....
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
He's asking about a recovery that can be installed to the recovery partition, not just tethered.
It's possible, but we'd need somebody to build one. I tried one a while back from the Zenfone 2, but it didn't want to boot.
jumpup said:
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
Click to expand...
Click to collapse
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
toxic_garden said:
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
Click to expand...
Click to collapse
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
@xBIGREDDx made some instructions on this. Let me find it.
http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
This is not straightforward, but you *can* get to tethered CWM and root your 5.1 system. I did exactly this.
jumpup said:
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
Click to expand...
Click to collapse
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
toxic_garden said:
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
Click to expand...
Click to collapse
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
jumpup said:
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
However, I have always used a multi-tiered backup system:
* Titanium Backup (FULL on Sunday, INCREMENTAL every other day)
* Online NAndroid Backup (One per week using CWM format)
Each app's backup data syncs to the home NAS and Dropbox once a week.
I thought I had the Stagefright fix already in place. That's why I wanted to compare build/version details with a device that has the fix installed.
jumpup said:
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
Click to expand...
Click to collapse
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
toxic_garden said:
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
Click to expand...
Click to collapse
D'oh. I should have remembered about the data encryption. Need more caffeine
If you need anything tested or confirmed in the field, I'd be glad to help.
Sent from my Venue 8 7840 using Tapatalk
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
jumpup said:
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
Click to expand...
Click to collapse
oops you're right. Didn't even notice.
First steps forward: it seems like it's not possible to unlock the bootloader with installed sf-patch. No matter which version of fastboot i tried, i always got "FAILED: (some text i can't remember)". After downgrading to 5.1 stock firmware, unlock was possible. So as i now at least have the possibility to boot another recovery, i'll try setting up the build env. The Recovery Builder from CWM seems to be out of order at the moment.
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
I now have the Stagefright patch installed. Used the 5.02 droidboot temporarily to engage tethered CWM and install SuperSU. Reflashed 5.10 droidboot and firmware before proceeding. All is well. As you mentioned, it makes for a mixed 5.1 boot system, but I simply cannot live without root.
Here are the new build/version details:
After taking your advice and flashing the sg droidboot, my IWFI version is in line. I'll see if any system issues occur.
Is anyone still working on the 7840? Would be nice to have TWRP or CWM
I've been poking around on my 7840 on and off for a few weeks now. I seem to have verified that, after unlocking the bootloader, you can modify the boot and recovery partitions to your heart's content. However, any time I rebuild the kernel myself, I end up back at the "Dell" screen, frozen. Any other files are free game.
Assuming that the kernel needs to be signed using some tool I haven't figured out yet, I'm going to see if I can get a version of CWM working w/ the stock kernel. I tried dumping the version from the tethered recovery onto the recovery.img, but running it results in a black screen. I'll keep poking around though.
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.
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
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!