I was wondering if anyone can shed some light on this. I woke up this morning and did a factory reset on my kindle fire HDX. When I checked the device version it stated I was on 13.3.2.3.2 whereas before I was on the latest update. Not being one to pass up on opportunity I rooted the HDX and accessed the system and renamed the otacerts. Anyone have any suggestions on what to do next? I'm a big noob when it comes to this tab it's way different from the other tabs I own.
backing up
Been doing some work. Risked installing hdxposed framework and module...which I have no idea what I would've done if I bricked it. Installed apex launcher and image 2 wallpaper app to fix the no wallpaper. Also widgets work. It seems to me you can do more with the root I'm just afraid I might brick it and not know what to do. What's the best way to backup my device in case it all goes wrong
Related
Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
umm
kobayashimaru said:
Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
Click to expand...
Click to collapse
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
jimyv said:
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
Click to expand...
Click to collapse
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
lol
kobayashimaru said:
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
Click to expand...
Click to collapse
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
jimyv said:
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
Click to expand...
Click to collapse
Thanks, i'm always scared with such new devices.
"Update failed". Perfect.
i got the Thor GAPPS working by now, so i'll try using that for now.
Hi all,
Have a new Kindle HDX 7 13.3.1.0 and have rooted with KFHDX ToolKit v0.94 and installed SU and blocked the OTA updates. Also have installed ES3 file manager and Titanium Backup Pro. I have not installed Safestrap (yet) as I need to read more before that happens, if it ever does.
So, here's my issue---when I select setting/device/storage, the storage screen only appears for about 1/2 second and then reverts to the previous device screen. I know this was working before, so it's something I did inadvertently, or maybe a file corruption? All else on the tablet works fine and I have Google Play installed thanks to the forum here.
I'm thinking a factory reset will cure this, but not sure. Before I do a reset (a last resort) I thought I should seek the advice from the experts here just in case a file replacement or something else could be tried.
Thanks in advance--this is a great forum!
touchy
kico42 said:
Hi all,
Have a new Kindle HDX 7 13.3.1.0 and have rooted with KFHDX ToolKit v0.94 and installed SU and blocked the OTA updates. Also have installed ES3 file manager and Titanium Backup Pro. I have not installed Safestrap (yet) as I need to read more before that happens, if it ever does.
So, here's my issue---when I select setting/device/storage, the storage screen only appears for about 1/2 second and then reverts to the previous device screen. I know this was working before, so it's something I did inadvertently, or maybe a file corruption? All else on the tablet works fine and I have Google Play installed thanks to the forum here.
I'm thinking a factory reset will cure this, but not sure. Before I do a reset (a last resort) I thought I should seek the advice from the experts here just in case a file replacement or something else could be tried.
Thanks in advance--this is a great forum!
Click to expand...
Click to collapse
This device is very fickle with behaviour after reset. I advise if you need to do a factory reset then to undo your OTA block from the toolkit uninstall the and Xposed framework ,and make sure supersu is installed into system via supersu apps settings. And the binary has been updated if needed
jimyv said:
This device is very fickle with behaviour after reset. I advise if you need to do a factory reset then to undo your OTA block from the toolkit uninstall the and Xposed framework ,and make sure supersu is installed into system via supersu apps settings. And the binary has been updated if needed
Click to expand...
Click to collapse
jimyv,
Thanks for the reply...I will heed your advice if I decide to do a reset. Not sure what you mean "very fickle with behavior after reset". Do you mean a reset does not always work with the HDX?
Pretty new at this and am trying to read and understand as much as I can so I don't make any stupid moves.
kico42 said:
jimyv,
Thanks for the reply...I will heed your advice if I decide to do a reset. Not sure what you mean "very fickle with behavior after reset". Do you mean a reset does not always work with the HDX?
Pretty new at this and am trying to read and understand as much as I can so I don't make any stupid moves.
Click to expand...
Click to collapse
I just mean make sure you undo your modifications before you do a reset otherwise to reset may screw you all up
I had Safetrap v4.01 running on my rooted kindle (4.5.2)
I have a copy of stock rom.
Long story short, I flashed gappz from Nexus v4 over the stock rom.
I still have Safetrap but it is disabled. Root doesn't work on my 4.5.2
And to make matters worse, I had rename the devicesoftwareota.apk to BAK to stop receiving updates. I have ADB yes, but not root. I checked. That's why it is semi bricked but I still have access to the system and SDCARD. -____- help is appreciated but it looks impossible. After taking care of root and stuff all the time, I feel like such a noob Ugh.
Luxen said:
I had Safetrap v4.01 running on my rooted kindle (4.5.2)
I have a copy of stock rom.
Long story short, I flashed gappz from Nexus v4 over the stock rom.
I still have Safetrap but it is disabled. Root doesn't work on my 4.5.2
And to make matters worse, I had rename the devicesoftwareota.apk to BAK to stop receiving updates. I have ADB yes, but not root. I checked. That's why it is semi bricked but I still have access to the system and SDCARD. -____- help is appreciated but it looks impossible. After taking care of root and stuff all the time, I feel like such a noob Ugh.
Click to expand...
Click to collapse
Problem solved.
After factory resetting (cringe) I know I know. Somehow I didn't encounter a brick but Safetrap was still installed and I had no home, back buttons ... So I tried the latest Kingroot.. And it didn't work.
HOWEVER thanks to a forum I read up on suggesting to try version 4.5.0 of Kingroot, I now have Root on my 4.5.2 Time to restore my stock kindle without the borked up version
Update: Even after receiving root, I couldn't access Safetrap. It was borked. I removed it, and re-installed. I pushed my backup Stock into TWRP/BACKUPS without deleting anything (just in case) and Restore said it failed but upon booting, I have my home button and back button again. ~ The end.
Hopefully, it helps someone with a similar issue.
Hi. Sorry if someone may have posted this already but I cant find my issue on here. I recently updated my kindle to the newest OS. Its never been rooted. The next morning after update my fire was on the system recovery. I tried reboot system and i got the amazon logo bootloop. I went back into recovery and tried to factory reset. It still bootloops and never reset. How can I put this kindle back to where it was after update but before recovery screen? I dont wanna root as to I just want it to be a kindle fire as originally intended. Any help would be appreciated. If u have instructions could u please make them easy to understand? Thanks again for any help.
Also, i bought a brand new kindle thats coming today. can i just copy something from that to fix the old one?
Hi,
So a while back(couple years ago), I successfully rooted my kindle fire hdx and installed cynogenmod(i think cm11) using safestrap because I think I remember reading something about how this specific kindle could not install twrp. Everything was running fine and my root was working. Anyways, fast forward to now I discovered that certain apps that detect root such as banking apps do not allow use on rooted devices. I found something called Magisk which is an alternative root that is hidden from apps. I then downloaded the Magisk manager and tried to install it directly using the app without first unrooting my current SuperSU root.
My device is now stuck in a bootloop with the kindle fire logo. I have tried resetting to factory defaults but it did not help. Does anyone know how to solve this problem? Thanks.
yumsty said:
Hi,
So a while back(couple years ago), I successfully rooted my kindle fire hdx and installed cynogenmod(i think cm11) using safestrap because I think I remember reading something about how this specific kindle could not install twrp. Everything was running fine and my root was working. Anyways, fast forward to now I discovered that certain apps that detect root such as banking apps do not allow use on rooted devices. I found something called Magisk which is an alternative root that is hidden from apps. I then downloaded the Magisk manager and tried to install it directly using the app without first unrooting my current SuperSU root.
My device is now stuck in a bootloop with the kindle fire logo. I have tried resetting to factory defaults but it did not help. Does anyone know how to solve this problem? Thanks.
Click to expand...
Click to collapse
Bootloop was 100% assured regardless of what you did with SuperSU. You'll need to intentionally 'brick' (not entirely accurate) and unlock you device to recover. Upside is you will score a more versatile gizmo that can run a newer version of Android. Downside is procedure is not for the faint of heart. You'll receive little assistance along the way as these devices have fallen out of favor despite being superior to most other <$200 USD Android tablets on the market today. Good luck.
https://forum.xda-developers.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014