Flash Factory Image on Nexus 5X with TWRP Installed - Android Q&A, Help & Troubleshooting

I'm wanting to manually install the April 2016 update to my Nexus 5X (currently running February 2016) but due to being rooted (with SuperSU BETA 2.67) and having TWRP as my recovery. I've looked for ways of doing it and trying to be a cautious as I can (when I tried to root las time, I soft-bricked my phone for a few hours). So far the best way I've found is simply through the Google Developers page (link below) with instructions and all the files I need.
Before I go through with it however, I'm wanting to know whether TWRP will prevent the install, if there's a better method, and do I install the latest image, or the one currently installed on my device, then update? Let me know if you need more details too.
Google page:
developers.google.com/android/nexus/images#instructions

Just follow the directions on Google's page, then redo twrp and root all over again.

zelendel said:
Just follow the directions on Google's page, then redo twrp and root all over again.
Click to expand...
Click to collapse
So just to be clear, manually updating will get rid of TWRP too?

sebowow said:
I'm wanting to manually install the April 2016 update to my Nexus 5X (currently running February 2016) but due to being rooted (with SuperSU BETA 2.67) and having TWRP as my recovery. I've looked for ways of doing it and trying to be a cautious as I can (when I tried to root las time, I soft-bricked my phone for a few hours). So far the best way I've found is simply through the Google Developers page (link below) with instructions and all the files I need.
Before I go through with it however, I'm wanting to know whether TWRP will prevent the install, if there's a better method, and do I install the latest image, or the one currently installed on my device, then update? Let me know if you need more details too.
Google page:
developers.google.com/android/nexus/images#instructions
Click to expand...
Click to collapse
Look at this very good guide. It helped me very much.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Dont be afraid to brick it. As long as you are carefully flashing the bootloader, nothing really bad can happen. It is a Nexus.
Bad news is, March brought a new bootloader. So if you dont want to fool around with the bootloader, I would recommend flashing System, recovery and boot of Febraury and then update via OTA. Have fun

Related

[Q] how can i root nexus 9 without custom recovery?

Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Wrong forum. This is a dev forum, not Q&A. Rooting w/out custom recovery is possible with chainfire's autoroot flashable zips. But still you won't receive OTA updates b/c since Lollipop the validation process has changed and you need to be pure stock. This also includes the recovery iirc.
Moved to correct forum
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
giannisgt said:
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Click to expand...
Click to collapse
brownog1 said:
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
You will not receive OTA updates if you are rooted.
cam30era said:
You will not receive OTA updates if you are rooted.
Click to expand...
Click to collapse
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
HansiHusten said:
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
Click to expand...
Click to collapse
My bad. I should have said you will not be able to install OTA if you are rooted. The install script checks system files and if anything has been modified, it aborts installation. Your better option is to fastboot flash the Google factory image.
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
HansiHusten said:
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
Click to expand...
Click to collapse
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
cam30era said:
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Click to expand...
Click to collapse
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
HansiHusten said:
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
Click to expand...
Click to collapse
Stable should work for Lollipop. Beta necessary for M. And beta works fine on Lollipop, too, FWIW.

Can I even root my phone? Or at least install a rooted rom? (I545VRUGOC1 Build)

Ok.. so.. I keep seeing people saying there is a way to root still if you are on GOC1.. but I can't find anything that says what that way is. I also see 5.1 roms for this phone, but nothing that says how to install the bootloader it requires to install them. On my old phone, a Droid X2 you had to root before you could install a bootloader before you could install a rom. I am not seeing any straight up guides on here for working with this S4.
What I really want is just a basic root, so I can uninstall all the hardcoded crapware on this phone (NFL Mobile, Trip Advisor, etc..)
Short of that I want to install CM 12.1, which is probably a better route anyway, but the page for that says you must be on so and so bootloader without telling you how to INSTALL said bootloader. I'm totally lost here, things were a bit more straight forward on that old phone.
Edit: Yeah, I think what I really want to do is install CM 12.1, but I don't even know where to start.
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
skepticmisfit said:
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
Click to expand...
Click to collapse
Kingroot doesn't work. I don't know what its saying in the orange text after I run it since its not in english, but it doesn't work.
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Try getting KingRoot desktop version 3.0 I just used it on Version I545VRUGOC1 that I did the OTA update with and got it rooted I can use Titanium Backup to remove all samsung Knox and other bloat wear.
bangdosa said:
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
Click to expand...
Click to collapse
I gave kingroot another try since I had rebooted a couple of times since making this post, it worked this time! Huge thanks for that tip.
XxD34THxX said:
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Click to expand...
Click to collapse
Thank your for that. Flashfire is in the process of installing the rom. We'll see how it goes.
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
DallasDave said:
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
Click to expand...
Click to collapse
Just use the KingRoot app to root. It worked for me on first try.

[Help Needed] Flashed 4.5.2 cant update update failed

I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931

[Q] GT-P 7510, I can't get Root

I've looked at several guides here, but despite following the details, I can't seem to obtain Root on my Tab.
I have got TWRP installed (via Odin) and also this Android 7.1.1 Nougat ROM, I've flashed Samsung_Galaxy_Tab_10.1_root.zip (multiple times now), but still no Root.
I must have missed something?y
Edit: I had previously obtained root using the Kingroot tool, but then read that it might not be a trustworthy tool and I uninstalled it. Could that be stopping me from getting root this time?
I gave up in the end and installed a Lollipop ROM, I do have Root with that. That said, I'm wondering if there was some other setting within the Nougat ROM that I should have enabled?
UKseagull said:
I have got TWRP installed (via Odin) and also this Android 7.1.1 Nougat ROM, I've flashed Samsung_Galaxy_Tab_10.1_root.zip (multiple times now), but still no Root.
Click to expand...
Click to collapse
Why did you even try flashing that root package? It's sooo old... Did you actually follow the steps in the OP for the 7.1.1 ROM to install either phh SuperUser, ot SuperSU? It's an extra step, along with the gapps install.

[Fire HD 6] Downgrade to 4.5.3 to root, went back to 5.3.1 and lost TWRP

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.

Categories

Resources