Related
DO NOT USE ON FOF6 FIRMWARE. WILL "BREAK" YOUR CAMERA. CHECK YOUR FIRMWARE VERSION.
Root method for FOG6 / 5.1.1 for the G900t THIS WILL TRIP KNOX. If you don't want to trip knox don't use this. If you do use it and whine you tripped knox because you didn't read ,we will all point and laugh at you.
Named it TrapKernel because well its not my normal HispAsian Kernel and I listened to a crap ton of Trap Music while doing it.
Thanks to @g.lewarne and his root method with his Unibase and Unikernel for the s6 , we finally have root after I ported it over to us. So be sure to thank him for his work.
What's included:
Auto installation of root and busy box
SuperSu.apk
A stock build prop with secure storage set to false so wifi passwords and etc aren't forgotten after reboots.
Kernel set to permissive
Otherwise stock
So here's the deal. Stupid simple.
1. Download the kernel
2. Flash in recovery (if twrp asks if you want to install su say NO)
3. Reboot and profit.
If you need more detailed help go HERE
Download
TrapKernel G6 [TWRP ZIP]
TrapKernel G6 [ODIN TAR]
Do NOT mirror this link. That means you "Android Geeks".
Special thanks to:
@g.lewarne for the obvious reason of being awesome and his root method for the s6. I suggest donating to him here [emoji14]
@ashraf sharif for testing
@Chainfire for SuperSU
also mine
This is wonderful. Thank you, sir.
EDIT: Works perfectly.
i just flashed it and somehow it broke the fingerprint scanner. nvm after a reboot, it is working now.
Awesome... thanks man!
Thanks! Working good. This. Is the 5.1.1 we should have gotten.
So when I come BAck I have everything.... is this new update faster the older one. was so buggy like 4-5 random restarts and freezes
I tripped Knox thanks bro ahaha!!!!
edited. My questions seemed too dumb
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
dpluigi said:
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
Click to expand...
Click to collapse
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Just did mine. All seems good. Camera working.
Question. Lately, anytime I flash anything, when clicking on twrp reboot, it gets stuck on tmobile screen on reboot, and sometimes I long press power button and it's finishes boot and my homescreen loads. Other times, I gotta pull battery, and then boots fine and all further reboots are fine, no hang ups. What you think this is? Something in my twrp? I leave everything checkmarked in twrp restore, cache and everything. Wonder if that is causing it somehow. Should I wipe cache and dalvik in twrp reboot?
Thanks for the new trapkernel! I missed my root access those past two days and not having my adaway to block ads.
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Thanks, that was quick and easy. TWRP was updated to 2.8.7.0, and with TrapKernel both Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not letting TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. So under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks,
Donat
dpluigi said:
Thanks, that was quick and easy. Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not let TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. Under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks
Click to expand...
Click to collapse
Because hispasian kernel doesn't contain the auto root.
You should be able to update it. I've havent been prompted yet
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
CptCrackers said:
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
Click to expand...
Click to collapse
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
What dhould the wake and sleep be set at and what do they do ?
Thanks
Sent from my SM-G900T using XDA Free mobile app
ShinySide said:
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
Click to expand...
Click to collapse
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
CptCrackers said:
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
Click to expand...
Click to collapse
Yeah you can
what will happen if I try to do this with SM-G900V ?
Hello is there a way to root the stock mm rom?
If I flash the super su binaries manually will it work? i've already got my TWRP installed on my device.
thanks for your help (if you help me )
SuperSU version 2.65-3
Yes you can root it but it is BETA
So don't expect it to work perfectly like it does on Lollipop.
There was security changes in Android that made things different on MM.
I advise people be extra cautious when planning on Rooting with MM.
There is a bunch of topics created on how to do this (i made one for example)
What you HAVE to do is get a special version called SuperSU "systemless" installed
this is a new way to get root on that was made because of security changes on Marshmallow.
Don't just start flashing things on your phone with out researching first or you may brick your phone.
I know i did that myself LOL
Then realize because the new Root works different then you may have some app's now not work properly.
For example make sure you use the most current updates if you use Stericson's BusyBox (35 pro or 41 free or higher)
Research and read on it then make sure to only use the Flashable zip format's shared by chainfire.
Don't just install APK's.. he tells you this on his pages over & over.
xpmule said:
Yes you can root it but it is BETA
So don't expect it to work perfectly like it does on Lollipop.
There was security changes in Android that made things different on MM.
I advise people be extra cautious when planning on Rooting with MM.
There is a bunch of topics created on how to do this (i made one for example)
What you HAVE to do is get a special version called SuperSU "systemless" installed
this is a new way to get root on that was made because of security changes on Marshmallow.
Don't just start flashing things on your phone with out researching first or you may brick your phone.
I know i did that myself LOL
Then realize because the new Root works different then you may have some app's now not work properly.
For example make sure you use the most current updates if you use Stericson's BusyBox (35 pro or 41 free or higher)
Research and read on it then make sure to only use the Flashable zip format's shared by chainfire.
Don't just install APK's.. he tells you this on his pages over & over.
Click to expand...
Click to collapse
Thanks, i know just installing the APK won't do anything, actually after posting this i tried the latest version of the systemless root, and my phone bricked, it wouldn't even show me the boot logo, and in the bootloader I didn't have a baseband version, thank god I had a back up
I'm now following your post and i'm going to try and root my phone after i'm done backing it up, btw do you know if xposed works with this systemless root? I want to use gravity box so I can add a few tweaks to the stock rom... and I also want to unnintall system apps with titanium backup, but these aren't that important as the tweaks..
Not too sure never used Xposed but i was Google searching and found a fix from guys for the Moto-G
I had to use, BETA-SuperSU-v2.62-3-20151211162651.zip
Newer versions failed to patch the bootloader and do a systemless install.
Use a newer one and then look in the TWRP console (after flashing from TWRP)
You can see on newer versions it simply does a normal install.
So if it does NOT patch your Bootloader for you then your screed.. bricked !
Re-Install the firmware then..
SO far installing BETA-SuperSU-v2.62-3-20151211162651
worked to get the Bootloader patched and the systemless version installed.
Then before exiting TWRP i have flashed over-top (with out restarting) BETA-SuperSU-v2.67-20160121175247
Get them from here..
EXPERIMENT: Root without modifying /system #2: Automation
Supposedly updating to 2.71 Beta is suppose to work.
But i am sketchy about it and 2.67 is for sure working good.
I just tried tonight 2.71 beta updating over-top via TWRP
and i think it was ok i guess.. i have not tested it much though.
(not sure if it will auto-patch the bootloader on a fresh install on it's own with out needing an old version first)
Get 2.71 here.. Note, i am sure chainfire said he merged those older versions into 1 beta version now.
[BETA][2016.03.30] SuperSU v2.71
You have to make sure you have these versions downloaded and ready on your SD card before you start fiddling..
Because if you are on MM and you install and it does not tell you in the console log you got your bootloader patched
..you got a brick on your hands when you reboot LOL
NOTE:
2.65 stable (on Play Store) will NOT work for Marshmallow guys.. it's too old etc.
Okay so I have not seen anything new in regards to us unfortunate enough to have the Cricket variant of the grand prime, so I decided to put together a little step by step to get xposed installed and running on this device, I think it may work on others as well, but since I have not attempted it then do not just assume it will. This guide is as stated in the sub line of the post for the SM-G530AZ running 5.1.1 Lollipop. I am not responsible if you brick or bootloop etc etc your device. So long as you can follow directions you should be fine.
1. First of all you must already have root access on your device, mine is using SUPERSU to handle root requests. If you do not have root yet then check forums for way to do so it is there already, however you must root with kingroot or manually with the same exploit that kingroot is leveraging in order to obtain it before attempting the install of xposed, otherwise it will fail.
2. You need to download the zip file attached to this post to your desktop or device and unzip it into your device sdcard.
3. Once you have extracted the apk and zip files into the sdcard you need to install the xposed installer apk so make sure you have enabled Unknown Sources from your settings/Security menu and you may get a warning from the device as well that is okay just tap okay and finish the install.
4. Now you need to download flashfire from the play store and install it as well. Open flashfire and flash the xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip that you will have extracted Choose flash zip in flashfire and make sure you leave automount unchecked. You can open the xposed installer app to make sure it recognized it, which it should if you flashed it properly.
5. Now you can enjoy the Xposed Framework on your device.
I am currently attempting to learn as much as I can about the trust zone and smc as I can tell you that is the only way we are going to get custom recovery and roms on this thing sadly. I am also following someone who claims to be able to rollback android from 5.0+ to 4.0-4.4.4 via jtag which is something I too have pondered on if it was possible and honestly I think it would be, I would like to explore the possibility that their may have been more vulnerabilities within the device prior to the 5.1.1 update I currently have 5.1.1 installed which is what the device had at time of purchase for me, however some may still be running 4.4.4 if you happen to be using 4.4.4 still then I cannot say whether this guide will work or not for you I think it would but you would probably need to use a little older version of the xposed installer but I am not certain, I would probably just update to lollipop if you really want to be safe about it and the firmware has been posted on these forums as well. Please hit the thanks if this helped you out at all, and if you are confused or have an issue you can pm me and I will try my best to get back to you whenever possible. But this is how I got xposed working on my device by simply rooting with kingroot, then using the mrw script to remove kingroot and replace with supersu and enabling unknown sources. The root guide that exists for this device however stated to flash some other boot.img and I actually had issues when I did that step, so after i went back to stock again I did the root guide with kingroot and did not ever flash that other boot image and all worked fine for me.
Awesome thanks. I assume install King root then flashfire then SuperSU binary then uninstall king root. For SuperSU?
Sent from my DROID Turbo using XDA-Developers mobile app
THANK YOU THANK YOU THANK YOU! Thank you so much!!!!!! I have been trying to do this for 3 days now!!! I have soft bricked my device, restored it, got it going again, soft bricked again. Over and over. Until finally, today on my first day off all week I took the time to read your posts over again. I found this one and it finally got me there! I have the same exact phone, Cricket Samsung Galaxy Grand Prime Model SM-G530AZ. I have been struggling to find a TWRP or CWP recovery and I am pretty sure there isn't one available currently. So then I found this method and FINALLY SUCCESS!!!!! Anywhere I can donate to you?
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
lexluthor said:
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
Click to expand...
Click to collapse
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
iBolski said:
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
Click to expand...
Click to collapse
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
eagle132 said:
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
Click to expand...
Click to collapse
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
iBolski said:
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
Click to expand...
Click to collapse
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
eagle132 said:
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
Click to expand...
Click to collapse
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
eagle132 said:
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
Click to expand...
Click to collapse
Did you try Magisk at all? I am on Jasmine ROM (Android 5.1.1) and would love a way to still have Root & Xposed, but be able to pass SafetyNet for PokemonGO and Wallet
Question on XDABBEB's VS985 ROM
Considering that this phone will probably see no more OTA's, I'm ready to go back to root, but I don't want to break Android Pay. Also, I'm not going to use Kingroot. Don't trust it. So, I'll TOT back to 10B to flash XDABBEB VS985 ROM. But i have some questions regarding it (I haven't ran a custom ROM in almost a year).
Does anyone know if removing SuperSU from XDABBEB VS985 ROM will allow Android Pay to work? Curious if so, otherwise, I'll probably just stick with my stock 48A unrooted phone in order to keep Android Pay.
I also miss TiBu as my backup tool. Yes, LG Backup is nice and all, but TiBu is so much more flexible, including the scheduled backups that I like to do as well as pushing to my Google Drive for backing up the files. Also, TiBu doesn't store it in one giant backup file. I really wish LG Backup would store each app as a separate file, rather than one giant, humongous file. Also, if I do upgrade to a new phone that's not LG, LG Backup won't work for me, so I'll need TiBu (and of course, I have to make sure the new phone is rootable).
Thanks!
While I have not tried this (I plan to try magisk later this week) supposedly Reddit says we can use this bump script after applying magisk in order to make everything will boot. I'm reading mixed comments about if/which certain bootloader is needed to have this work (KitKat vs Lollipop vs Marshmallow) or which ROM to start with as a base (though I saw CM 13 mentioned). If anyone tries this, let me know. I'll post my results in the coming days.
Hi guys,
first of all I want to salut everybody here as I am completely new to the Android world and that's indeed the best resource online. Thanks for that.
Now my big problem. As from the title, I downgrade my Fire HD 6 (4th gen) to 4.5.3 with adb sideload to root it with kingroot and everything went fine. I have then installed TWRP and everything went fine. I have then used TWRP to go back to 5.3.1 and I lost root and recovery. I managed to gain my root privileges back but as for the recovery not a chance. I tried to install TWRP again with dd from adb shell (as I can su) but once again nothing. Checking with fastback getval all, I do have a locked bootload:
Is this the reason why TWRP doesn't run anymore?
If yes, how can I unlock it back?
Is this what's meant with boot loader loop?
Thank you all in advance!
Edit 1:
maybe cuber.py may help but I can't find this file.
Edit 2:
ok found the tools here https://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Edit 3:
I tried with cuber.py but the tool can't sign the img because it's not ANDROID. That's what it says. Now I am really stuck. Help please!
LM
I was in the exact same situation, so maybe I can offer some insight. I also have an HD 6 running 5.3.1 that I have downgraded to get root then upgraded a few times. Let me say that I am still learning too, and am by no means an expert but I can try to help.
As far as losing root, i'm not sure as that never happened to me. Did you flash the most up-to date SuperSu with TWRP or did you just answer yes when TWRP prompted you if you wanted root privileges? Flashing a SuperSu through TWRP will give you the SuperSu icon on your home screen once you upgrade back to 5.3.1, whereas just letting TWRP grant root access won't. You will still have root, but without the icon there's no direct control over it (at least not that I could find) so it's still there, just hidden.
My TWRP also replaced by the stock recovery upon updating back to 5.3.1. As far as I know, this is unavoidable. I believe it's as you suspect and is due to the 5.3.1 bootloader being locked. This would also explain why the process for rooting 5.3.1 is so involved as opposed to just using something like Kingroot. I also don't think there's anyone still doing active development on the HD 6 / HD 7.
If you really want to have both root and TWRP, you could try downgrading to an older OS that still has the feel of 5.3.1. I'm not sure about any other versions, but 5.1.1 is rootable via Kingroot (which should mean that it has an unlocked bootloader) and has the same exact UI as 5.3.1. So if you're feeling adventurous try downgrading to 4.5.3, installing TWRP, and upgrading to 5.1.1 instead of 5.3.1 (just be sure to block automatic updates!) and see if TWRP is still active. If so, root with Kingroot and you're good. If you still don't have TWRP, at least you're no worse off than you were.
If you do try this, please post your results here. I might try this myself. I am currently running stock. As I said, I went through the process a few times. For some reason SuperSu was causing erratic behavior in some of my apps and when I tried to switch my SU app to kingroot I lost root completely. I really didn't care about root enough to repeat the whole process again, but if I could keep TWRP it might be worth it. Anyway, good luck.
P.S. You may need to try rooting with Kingroot several times for it to work. I know for a fact that it can root 5.1.1 since I've done it on my own HD 6 when I was running 5.1.1. I'm not sure why it fails, but keep trying and eventually it will get root access. You may have to try 6 or 7 times but eventually it will work.
I went back and re-read this thread more carefully:https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and it turns out that TWRP doesn't play well with any 5.X.X bootloaders. Oh well, I was kind of hoping my idea would work. It turns out that you can use TWRP on your current rooted 5.3.1, but only on a temporary basis. Refer to the above thread post #2 for instructions. Basically, you put the correct 5.3.1 bootloader on your device then run AutoTWRP which will flash 4.5.3 bootloaders and TWRP for you. Reboot into recovery and you have your TWRP. You can then do whatever you want. The downside is that since you are running a 4.5.3 bootloader you can't get back into your OS, only TWRP. And once you flash your 5.3.1 bootloader to get back into your OS, TWRP no longer works. I know it's a pain in the arse having to connect to a PC and run a batch file every time you need to use TWRP, but at least it's a sort of workaround.