Related
[Solved] Manual install CM11 & Original Thread: How to install CM 11.1 on Fire HDX 7?
Hello,
as I just managed to install CM 11 on my Fire HDX 7 (3rd Gen) (thanks a lot to @Cl4ncy, @Davey126 and @EncryptedCurse) I want to share the information I got during the process.
Note: This manual might be outdated if you read it. So check if there is a newer manual You could break your device if you dont do everything correctly. I am not responsible for breaking your device! If you have a question just ask! It could be that i forgot something.
When I started my Fire HDX 7" had Fire OS 4.5.5.
Note: CM 12 is not available yet for Safestrap v4. If you want CM 12 you need an unlocked bootloader. You can't do it if your version is above Fire OS 3.2.3.2. And you are not able to downgrade below 3.2.8 due to rollback protection by Amazon.
Some preperations:
- connect your Fire HDX to your PC (if your PC doesnt recognize your Fire HDX then install the USB drivers. If that doesn't work deinstall the actual Fire HDX driver and try it again.)
- copy every folder from the Fire HDX storage to your PC (backup music, ....)
- install (Holo Backup and click on every Backup Button (in my version there were 5 buttons))
- install minimal adb + fastboot
Download these files and save them on your PC:
- ES Explorer
- KingRoot
- Safestrap v4
- a Safestrap v4 compatible ROM (CM11 or Nexus v4)
- SuperSU if you want root - Download the .zip file from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip //Check if there is a newer Version
- GApps if you want the Google Apps (the right things should be already selected. If not select: ARM, 4.4, nano) -> the name should be sth like: "arm 4.4 nano 30 September 2015"
Thanks to @Davey126 and @Cl4ncy:
- Turn Wifi Off and flightmode on (you might need to enable Wifi, when you root your device with KingRoot)
- rollback to FireOS 3.2.8
// you do that by copying the file into the 'Internal storage folder' of your Fire HDX (not in a subfolder, just copy it where the DCIM, Document, Download, kindle, ... folder are.). Now wait a few minutes and go to Settings -> Device -> System Updates -> Tap Update
- upgrade to FireOS 4.5.2
// do it as before
- install ES Explorer and KingRoot with minimal ADB + Fastboot
- make sure that only the Fire HDX 7" is connected
- run this Code to see the connected devices
Code:
adb devices
- install the ES Explorer and KingRoot by using minimal ADB + Fastboot
- replace "C:\users\p-4\es.apk" with your own path and do the same for KingRoot
Code:
adb install C:\users\p-4\es.apk
- root with KingRoot or another method (i didn't find another one) //if it doesn't work directly just try it again (I tried it 10 times). If it still doesn't work just try another Wlan (that nothing gets blocked) or wait a week.
- block OTA (over-the-air updates) - only step#1 //you don't have to install the GApps because you will flash them with the ROM
- install Safestrap v4
- Copy the installation files (ROM, SuperSU, Gapps) to your Fire HDX into the /sdcard folder. (There the files won't get deleted if you wipe). If there folder isn't available then create one. But normally there should be one. Make sure you have your Fire HDX rooted. Only then you can see the folder with ES Explorer. In my case the "/sdcard" folder was the normal one, where i stored my Music, Documents, ... so had didn't have to do sth.
- Reboot
- Make a backup of the 'Stock-Slot'
- Copy the backup to your PC
- flash a Safestrap v4 compatible ROM to the ROM-Slot-1 , 2, 3 or 4 (currently CM11 or Nexus v4)
Safestrap v4 Tutorials:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
Notes: If you use a secondary slot the biggest possible Data Size is 16GB and your battery won't last long. You have to charge the Fire HDX very often.. If you use the Stock Rom Slot you will have the whole storage of your device.
Congratulations you successfully installed CM11 if you did everything right.
But as I mentioned before the performance is not very good, because the ROM is installed on a secondary slot.
--------------------------------------------------------------------------------------------------------------------------------------
To get the best performance and a very good battery life you have to install the ROM on the 'stock-slot'.
Thanks to @Cl4ncy and @Davey126 :
For that just:
- Reboot and go to the Safestrap Menu
- check if the installation files (ROM, Gapps, SuperSU) are in the "/sdcard" folder press "..." in the installtion menu to go up the path. There should be the "/sdcard" folder.
- Delete the secondary ROM-Slots
- Go into the Wipe Menu and Swipe to perform a factory reset (only a simple one - no advanced wipe)
- Go to install and add the ROM File
- add Gapps
- add SuperSU if you want root
- perform the flash
- if it was successfull Reboot otherwise DON'T Reboot. Just wipe again and flash the files again.
Note: If something went wrong with the stock-ROM don't reboot directly. Just install a ROM on a secondary slot and reboot then.
// The Original Post:
Hello,
since it is possible to download prime videos on any android device i would like to install Cyanogenmod 12.1 on my fire hdx 7.
I found this Cm 12.1 Port.
Is there a step by step manual how to install such a rom, because i never did that before and i have heard that if you do something wrong your device is broken.
Because I neither know how to get an unlock bootloader or what a TWRP is. Furthermore i also dont know how to flash the ROM.
In some forum posts i read, that it is possible to go from Cyanogenmod back to FireOS (unbrick). For now i dont want to go back from Cyanogenmod to FireOS, but i think it would be good to have such a possibility.
Do I have to take precautions for that?
And how do I make backups?
Info:
Kindle Fire HDX 7" (3. Generation): Fire OS 4.5.5
Thanks a lot
p-4
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12. You can also NOT use TWRP recovery.
Reason: Rollback protection by Amazon, preventing downgrading to Fire OS versions below 3.2.8
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Thanks for this answer
Cl4ncy said:
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12.
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Click to expand...
Click to collapse
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
You can NOT use TWRP (see above), TWRP is available for Fire OS below 3.2.4 only. You must use Safestrap v4 (i.e. NOT Safestrap v3.72/3.75!).
I can't give you any recommendation, but you can try Nexus and CM11 after you installed Safestrap v4. You can even (depending on the size of your sdcard/storage) set up secondary slots and use dual boot with Safestrap installed.
But you should focus on downgrading to 3.2.8, then updating to 4.5.2, rooting, disabling OTA, and installing Safestrap first - that will be difficult and risky enough for the time being.
And note that CM12 is not an option for you. This could change in the future, but I wouldn't count on it.
And one other thing:
If you've Safestrap installed, NEVER use the factory reset in Amazon's stock recovery! You will most likely brick your HDX.
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
Nexus is basically an AOSP-based ROM (i.e. stock, just like Google intended).
CM11 should be self-explanatory.
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Or is it possible, after I installed CM 11, to upgrade to CM12? (Has Cyanogenmod an Over the Air update possibility?)
p-4 said:
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Click to expand...
Click to collapse
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Cl4ncy said:
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Click to expand...
Click to collapse
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
p-4 said:
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
Click to expand...
Click to collapse
Enable USB debugging, install Minimal ADB and fastboot, put the kingroot.apk into the adb directory, open a DOS box, change dir (cd) to your adb directory (e.g. enter cd\adb), then enter "adb install kingroot.apk" (without the quotes). This will install Kingroot on your HDX. Then do the same with ES Explorer.
The HDX must be connected to your PC by USB of course (should be obvious).
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
p-4 said:
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
Click to expand...
Click to collapse
As long as you're still on 4.5.2 you can try to root, just ensure 4.5.4 won't be installed. After successful root you can disable OTA, and delete the update file. Also ensure you have the latest Kingroot version - 4.50.902 I believe.
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
p-4 said:
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
Click to expand...
Click to collapse
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Cl4ncy said:
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Click to expand...
Click to collapse
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
p-4 said:
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
Click to expand...
Click to collapse
I'm afraid no.
Kingroot fails always between 53% and 55%. Once I got over 60%.
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
p-4 said:
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
Click to expand...
Click to collapse
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Cl4ncy said:
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Click to expand...
Click to collapse
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
p-4 said:
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
Click to expand...
Click to collapse
Ok, enable flightmode to avoid getting updated further to 4.5.5 then.
And good luck, I'm really not sure about this.
Does someone know if this root app works normally? (click)
After a few tries I can now locate to /system/priv-app/DeviceSoftwareOTA.apk but I am not able to rename this apk.
Can I also try these ways to root the Fire HDX 7" or will i brick my device then? (click)
//edit I just enabled wrong locations and it worked with kingroot
// edit now i got cm11 installed Can I also try other roms like CM12 and insert them in the Rom-slot 2? If it fails, my device isn't bricked, because i only have to restart and load rom-stock or rom slot 1, right?
The only big problem I noticed so far is the battery. After 8 hours in sleeping mode (only screen off) the battery status sank from 90% to 55%. How can I fix this problem?
Hello, I have a Fire HD6 Running Fire OS 5.0.0. I am trying to use the file for 5.2.2u2 to update. When I go to settings>>device options>>system updates>>check now, it says there are no updates. If I put the file at /sdcard using a computer and turn on airplane mode, I can hit the update button and it looks like it is going to update, but when it reboots, it says i am still on 5.0.0. ADB works, but adb reboot recovery just boots normally. I had TWRP until I updated to 5.0.0. I really need help. Thanks in advance.
See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."
DoLooper said:
See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."
Click to expand...
Click to collapse
Is there any way to get TWRP and Root at 5.2.2u2 and get play store, or am I doomed to have an unrooted device forever? Will update in a few minutes about things you said to try.
Update: adb push 5.2.2u2file /cache results in permission denied. Trying to enable packages via adb also results in permission denied. Debloater says no packages are blocked. I would really appreciate it if I could get root and playstore on this thing. Thanks in advance.
Well, since you're unrooted without recovery you may have to go the replacement route. But first see if @bibikalka has an alternative.
I'm trying to restore my HDX 7" (Thor) to stock (or at least as close as possible). I was able to restore from an old backup to get back to an old amazon firmware from 2014 but i cannot install updates through the OS (this is after a factory reset in the amazon fire OS)...i then attempt to load the newest update via ADB in TWRP but i get the message that "this package is for thor products this is cm_thor."
Any ideas?
Thanks!
edit: went into the "updater-script" and changed all instances of Thor to cm_thor to see if that would help...instead i just got "this package is for cm_thor products this is a thor."
xamievilx said:
I'm trying to restore my HDX 7" (Thor) to stock (or at least as close as possible). I was able to restore from an old backup to get back to an old amazon firmware from 2014 but i cannot install updates through the OS (this is after a factory reset in the amazon fire OS)...i then attempt to load the newest update via ADB in TWRP but i get the message that "this package is for thor products this is cm_thor."
Any ideas?
Thanks!
edit: went into the "updater-script" and changed all instances of Thor to cm_thor to see if that would help...instead i just got "this package is for cm_thor products this is a thor."
Click to expand...
Click to collapse
Wrong procedure; lucky you didn't brick it. Details please:
- native TWRP or Safestrap?
- what ROM is current installed (including version)
- reason for restoring? Are you trying to resolve a problem?
TWRP - 2.8.7.0
Amazon firmware: 13.3.2.1
i have an old backup that i can restore from at anytime from right after i initially rooted and blocked OTA updates back in 2014...
i just decided i wanted everything back to stock...didn't realize it was going to be such a pain...
xamievilx said:
TWRP - 2.8.7.0
Amazon firmware: 13.3.2.1
i have an old backup that i can restore from at anytime from right after i initially rooted and blocked OTA updates back in 2014...
i just decided i wanted everything back to stock...didn't realize it was going to be such a pain...
Click to expand...
Click to collapse
Given you have TWRP (nice!) and no interest in a custom ROM you could simply flash FireOS v4.5.5 from this thread. You won't be able to restore stock recovery...nor is their any benefit in doing so.
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.
I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
doobius said:
I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
Click to expand...
Click to collapse
If you are on 4.5.3 bootloader you can easily boot to unsigned recovery images. So install flashify and download the twrp for ariel and flash it:
https://forum.xda-developers.com/fire-hd/development/recovery-twrp-3-0-2-0-t3488768
So here you can install any zip, but when you finish, restore the correct recovery.img. For example: If you update to 5.3.6 with TWRP, then flash the 5.3.6 recovery.
But be careful of what you do, you can brick the tablet by flashing wrong bootloaders.
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
doobius said:
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
Click to expand...
Click to collapse
Wow very nice. You can use this toolbox in the next version since the dev will add support for ariel for debloat and do more things without root:
https://forum.xda-developers.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
doobius said:
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
Click to expand...
Click to collapse
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Rortiz2 said:
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Click to expand...
Click to collapse
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
doobius said:
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
Click to expand...
Click to collapse
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Rortiz2 said:
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Click to expand...
Click to collapse
PS \ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb shell
[email protected]:/ $ su
1|[email protected]:/ $
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
doobius said:
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
Click to expand...
Click to collapse
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Rortiz2 said:
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Click to expand...
Click to collapse
good idea. but that failed too.
doobius said:
good idea. but that failed too.
Click to expand...
Click to collapse
So then try installing google play as in Fire 7 2015/2017.
You have two methods:
- Manual: https://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603
- Automated tool: https://forum.xda-developers.com/amazon-fire/general/tool-amazon-fire-7-7gen-fire-os-5-6-x-t3815112
(Use install google play option).
When you logged in and setup it correctly, proceed to update supersu installer tought Play Store.
ok sir, you are on to something...
i downloaded the playstore stuff via that link you sent.
i logged in to playstore and went back to the supersu installer i already had.
i clicked play.
it took me to the same playstore suspersu program and it says it is currently unavailable.
i searched supersu and found the main updated download.
i hit open and it took me back to the installer i already have.
i went back and noticed the update option in the playstore and selected that.
it updated and is now saying that the su binary needs to be updated and is asking me to continue.
awaiting your godlike instructions.
the next screen says, "if you have a custom recovery like twrp or cwm, that can be used to (try to) install the SU binary. this is recommended for HTC devices. how would you like to install the SU binary.
normal or twrp/cwm?"
normal, right?
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
doobius said:
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
Click to expand...
Click to collapse
Yay!! You have root!! Now that you have root. I will recommend you to flash a working recovery.
Pinging some people that may help creating the stock recovery: @k4y0z @bibikalka
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
doobius said:
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
Click to expand...
Click to collapse
Ok. DON'T DO ANYTHING UNTIL YOU RESTORE WORKING RECOVERY.
First we need to create a working recovery image. Can you check if there's install-recovery.sh in system/etc and in system/bin please?
i dont see that, but i'm probably not looking in the right spot then. how do you suggest i check for this?