Related
FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Edit: see following post by @zippy411. Appears a rollback to FireOS 5.3.1 (rootable) is viable.
Davey126 said:
FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Click to expand...
Click to collapse
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!
great news that we can downgrade without issue.
P.S: Maybe my HD 10 5.3.1.0 will never see the light of getting root as Fire 7" as Amazon is pushing another update already
Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).
Orbiting234 said:
Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).
Click to expand...
Click to collapse
Quite likely you can retain 5.0.1 bootloader while 'upgrading' to FireOS 5.4.x (when released) using the time proven procedure in this thread yielding the best of both worlds. Backup your existing CM install in TWRP so you can revert back after grabbing the Alexa components. You could do the same with the FireOS build and toggle between the two (awkwardly) via TWRP backup/restore. Can do the same thing with recent FlashFire builds although I would always retain a true nandroid (ie: twrp backup) of CM as a fallback.
zippy411 said:
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!
Click to expand...
Click to collapse
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!
ManWithCamera said:
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!
Click to expand...
Click to collapse
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.
Apart of the NEW Alexa, does anyone here has noticed something NEW or any improvements with the latest FireOS 5.3.2 update?
Can we root it after the update with dirty cow?
just4u32 said:
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.
Click to expand...
Click to collapse
Hi - this forum is for 5th gen Fire (released fall 2015); you'll want to ask you question here. While 5th and 6th gen devices often run similar builds of FireOS there are some differences attributable to hardware variations and software release cycles. What works on one type of device may or may not on others. Rollbacks can be especially dangerous as bootloaders/kernels generally differ across device types. A failed rollback attempt typically yields a bricked device with no recovery options. In short, I would not generalize across device types.
Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
To my knowledge there is no indication Dirty Cow has any meaningful relevance on this device. Although the underlying vulnerability may exist there is no evidence it has been successfully exploited on FireOS.
OK I thanks
Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
5.3.2 > 5.3.1 downgrade IS possible
Good Afternoon,
I recent purchased a Kindle Fire 7 (11/11/16) and it was upgraded to 5.3.2. I was able to downgrade the OS to 5.3.1 using the ADB sideload method and then root using Kingroot (11/18/16). Be sure to block OTA updates once completed. Have not seen any issues yet and will report if i do.
Good Luck everyone.
ManWithCamera said:
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
Click to expand...
Click to collapse
Thanks
Tried to disable lockscreen ads using adb (com.amazon.kindle.kso), but when I touch the special offers icon on lockscreen, I get a window that says Selected Offers. Is there another package that I should be disabling? I'm on Fire OS 5.3.2.
Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Onlye root, not recovery modded or other rom.
Thanks
p.s.: not use slang with me, thanks
Palux said:
Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Click to expand...
Click to collapse
Yes - 5.3.1 can be reloaded again if pure stock is desired. However, this is not generally required for warranty exchanges (the only type of hardware assistance Amazon provides) as they do not perform a detailed inspection of returned devices.
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
br
Arret said:
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
Click to expand...
Click to collapse
Something went wrong; the Amazon Logo should display for <30 sec. You will need to reload FireOS 5.3.1 from the stock recovery menu and start over. Guidance here, here. Once recovered post back for further assistance loading CM 12.1.
Hello forum,
Is it truly possible to root the xt1563 running 6.0.1? I've followed multiple sties with instrutions and when I can easily get past unlocking the bootloader, installing twrp but when I go to install the supersu from twrp, I go into a boot loop.
Can someone here say that they've successfully rooted their xt1563 running 6.0.1? If so, where did you get your files?
Thanks!
I rooted my XT1603 on 6.0.1 successfully. I used twrp-lux-3.0.2-r3.img and flashed supersu 2.46, got a bootloop. I reflashed supersu 2.62-3, still got a bootloop. Then I reflashed supersu 2.65 and it worked. Thanks to this post:
http://forum.xda-developers.com/mot...oto-x-play-t3211941/post68057600#post68057600
chinhodado said:
I rooted my XT1603 on 6.0.1 successfully. I used twrp-lux-3.0.2-r3.img and flashed supersu 2.46, got a bootloop. I reflashed supersu 2.62-3, still got a bootloop. Then I reflashed supersu 2.65 and it worked. Thanks to this post:
http://forum.xda-developers.com/mot...oto-x-play-t3211941/post68057600#post68057600
Click to expand...
Click to collapse
thanks chinhodado. I will try to flash with 2.65. Do you know where I can find the same file you used?
Here: https://download.chainfire.eu/921/SuperSU
Didn't work. I first tried 2.65 then it froze on load-up. I left it for about 3 minutes, then rebooted in recovery. Tried 2.62 same thing. I left it load this time for 7 minutes. Stuck on motorola planet picture.
I honestly don't know what it takes to root this device. oneclickroot.com offer rooting for 39.95 which I think is silly. Somehow they seem confident that they are able to sell a "root" package.
I remain confused and frustrated.
thanks for trying to help chinhodado
Did you try wiping the cache? I think I had to do that several times too.
chinhodado said:
Did you try wiping the cache? I think I had to do that several times too.
Click to expand...
Click to collapse
yeah that and davlik
only systemless method work on moto x play whether its XT1562 / 1563
Go to terminal in TWRP - Advanced-Terminal type command in your phone
Code: echo SYSTEMLESS=true>>/data/.supersu
http://forum.xda-developers.com/moto-x-play/general/how-to-root-moto-x-play-xt1562-running-t3509344
I did not have to enter any command when I rooted my phone and it still succeeded in the end. I think 2.62-3 uses systemless root by default. It doesn't hurt to try though.
I am getting the same problem on XT1562, it stucks on Bootloader warning, tried everything above and available elsewhere. Help!
Hey, today Supersu wanted to update from the play store so i updated it, and once it was done it asked to restart the phone like usual, i restarted and when it was done booting supersu said the phone was no longer rooted. Not exactly sure what to do to fix this, i am on the unlocked V20 (US996) i am not running any rom, just stock and root. Hopefully you guys can help me get root back on my phone, thank you.
If you have TWRP installed , try to flash a supersu zip file for the update or one from a rom in the development thread . I just updated myself but didn't reboot yet.
I think the Playstore update screws it up.
You need to search the update .zip and flash it in recovery.
SuperSU 2.80 and 2.81 are both broken. Flash 2.79 SR3 in TWRP and root will be back. Worked for me anyway.
P.S. Don't re-update through the Play Store until they fix the issue, just stay with 2.79 SR3 for now.
Bubba Fett said:
If you have TWRP installed , try to flash a supersu zip file for the update or one from a rom in the development thread . I just updated myself but didn't reboot yet.
Click to expand...
Click to collapse
I downloaded the supersu zip from chainfire's site supersu 2.46. Flashed it and then rebooted, however the boot never ended, it doesn't seem to be bootlooping it just gets to the final boot animation and sits on that, waited 10 minutes and it still never made it to the home screen, trying to figure out how to get into twrp from here.
Okay, i found this thread https://forum.xda-developers.com/v20/how-to/booting-recovery-t3488099/page2 which states that pressing the power and volume down button in a certain way will take me to a white screen asking me to reset my phone and that if i have twrp installed (Which i do) it will take me to twrp saying yes, should i do this to get to twrp and then flash Supersu 2.79 as jeston suggested? And should i wipe dalvik/cache after flashing?
Okay i fixed it, entered the bootloader by doing the power and volume button factory reset thing i found and then flashed supersu 2.79, then wiped the dalvik/cache and rebooted, it bootlooped once but it started after that and is working perfectly! Thank you all for your help!
Good to see you're sorted now.
meccano300 said:
Hey, today Supersu wanted to update from the play store so i updated it, and once it was done it asked to restart the phone like usual, i restarted and when it was done booting supersu said the phone was no longer rooted. Not exactly sure what to do to fix this, i am on the unlocked V20 (US996) i am not running any rom, just stock and root. Hopefully you guys can help me get root back on my phone, thank you.
Click to expand...
Click to collapse
I had the same problem. Lost root after allowing supersu to update from playstore.
Just flashed supersu2.79.zip in twrp and was rooted again.
I lost root after updating SuperSU. I don't think it was from the Play Store, it was a SuperSU notification that kept bugging so I let it do it's thing and then lost root after rebooting. I do not have TWRP because I have a locked bootloader (Samsung on Verizon). How do I get it back?
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
DirtyHennessy said:
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
Click to expand...
Click to collapse
Thanks! I will try that.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Have you made sure to update your radio, bootloader and vendor to the most recent version? Make sure to also try flashing twrp again but do everything through fastboot flash commands on your pc.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Flash root in TWRP before your first boot into the stock rom. On Nougat 7.0+, stock recovery replaces TWRP on boot if you do not. This solves both of your problems. When you clean flash and install a custom rom, with or without root, TWRP will remain. If you just use stock unrooted, then you should flash root before first boot each month when you update.
Sent from my Nexus 5X using Tapatalk
SuperSu 2.80 & 2.81 broke root for most phones - including mine. I had to flash 2.79 SR3 to get root again. Chainfire released 2.82 this morning but I haven't tried it yet.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you boot to twrp first time mount system and use the filemanager to delete recovery-from-boot.p under system. Use magisk instead of supersu for root.
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
treysky54 said:
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
Click to expand...
Click to collapse
Why can't you just flash SuperSu or Magisk via twrp?
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
gwardsc65 said:
Why can't you just flash SuperSu or Magisk via twrp?
Click to expand...
Click to collapse
gwardsc65 said:
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
Click to expand...
Click to collapse
Sorry mate, not the way it works on this device (3rd gen HDX). Bootloader must be unlocked to obtain root on any custom ROM based on Android 5+. There are no (reasonable) workarounds or exceptions.
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
Expected symptom when attempting to secure root on a bootloader locked HDX.
Ahhh... so it somehow got locked back and need to redo the procedure?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
No need to restore stock. Use MTP in TWRP to transfer (push) a KitKat based custom ROM zip to device, install and then go through bootloader unlock procedure. Suggest using Fire Nexus as the interim ROM as it is self contained with GApps and SuperSU built in.
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
treysky54 said:
Ahhh... so it somehow got locked back and need to redo the procedure?
Click to expand...
Click to collapse
That's what the symptoms suggest. What makes you believe the device was properly unlocked sometime in the past?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
Can I do it without TWRP????