[Q] HDX 7 Advice and a little help needed... - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

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

Related

[A] Help: Cant unroot or Reroot

Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
This Also Seemed to Work...
My root went through fine, but after the root my "n" buttom quit working and
I wound up in almost exactly the same place as above. I got out of it by:
1) Downloaded the "acclaim_update.zip" image found in the thread about Nook 1.4.0 from SDCard above, putting that on an SDCard and the rebooting to run and load it. When it first rebooted, the "n" worked but as is typical with Android
there were "leftovers" (files, etc.) still left from the previous installs.
2) So I went in to Settings and ran the "Erase and Deregister" option which seemed to clean out the leftovers and leave everything where it should have
been.
Hope this helps someone else.
Rev
albertwertz said:
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
Click to expand...
Click to collapse
This fix worked for me as well.
I had my tablet rooted and when the ota got pushed out it broke my root. So I went back to 1.4.0 and re-rooted. But the script died halfway through and had the same symptoms listed above. Not fully rooted, but not fully unrooted either.
I had to sideload the superuser app and then unroot. Then start the root process all over again.
Unroot NT but it stops in the registration
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
andrea89 said:
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
Click to expand...
Click to collapse
Albert Wertz posted a video showing how but I'm not allowed to post outside links yet. Go to youtube and search for this video: sAASnHPn4PM
albertwertz said:
Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
Click to expand...
Click to collapse
Hi Albert
sorry to be bothering you , but i know your prolly the only one that can help me with this problem i have with my nook tablet
im replying to your reply :
so regarding this , im in need of your help here , same thing happend to me , didnt have superuser and was not fully rooted or not fully unrooted , but i did as you said i sideloaded superuser and unroot off this therd you posted and still the same probleam eco worked problem , what am i doing wrong ... the superuser doesnt seem to pop up when i run unroot ... how can i make superuser work properly ?
hope to can help
- Erik
Hopefully Albert has the answer for you. He's a clever one.
If this post helped click the thanks button!

[Q] Does factory reset remove root?

Would a factory reset remove root?
My config:
Apollo, FireOS 14.3.2.3.2
Rootmethod: towelroot
factory reset on new rom slot after installed safestrap or factory reset on stock rom?
stapler85 said:
factory reset on new rom slot after installed safestrap or factory reset on stock rom?
Click to expand...
Click to collapse
ROM Slot. The safestrap for 14.3.2.3.2 is in development and not existent as far as I know.
dimi5 said:
ROM Slot. The safestrap for 14.3.2.3.2 is in development and not existent as far as I know.
Click to expand...
Click to collapse
Then no. changes on rom slots wont affect stock, which is where you shouldnt mess with
stapler85 said:
Then no. changes on rom slots wont affect stock, which is where you shouldnt mess with
Click to expand...
Click to collapse
Soory stapler85. I'm posting bull****.
Again: I don't have safestrap, therefore, I've only the stock rom. However, at I'm going to do a factory reset in the near furutre, and was just curious, whether the device must be rooted afterthat or the factory reset would not affect the system apps/data.
Its funny when people post a question, get an answer, and then claim they dont like that answer.
Perhaps if you gave correct information you would get the answer related to what is going on. You said you were on a ROM slot, so factory reset of that slot will NOT make you lose root just like stappler85 said. Now you just said you are not on a slot but on regular stock, so yes a factory reset probably will make you lose root of your stock system.
If you think about it. You are going to root the stock rom anyway. Why not factory reset FIRST so you know it wont mess up. Then root and SS etc.
But im sure factory reset on rooted stock rom will mess some things up. This device seems unpredictable and probably amazon intention to deter messing around with.
EniGmA1987 said:
Its funny when people post a question, get an answer, and then claim they dont like that answer.
Perhaps if you gave correct information you would get the answer related to what is going on. You said you were on a ROM slot, so factory reset of that slot will NOT make you lose root just like stappler85 said. Now you just said you are not on a slot but on regular stock, so yes a factory reset probably will make you lose root of your stock system.
Click to expand...
Click to collapse
If you read his post he explained that safe strap does not exist for his version of kindle. Therefore he did not receive an answer for his question and your entire post is in error, as well as utterly useless. As for this particular device I can't say but on MOST android devices I've owned root stays even after a factory reset. Must re flash or Un root on many of my other devices I've had to reset, just re downloaded supersu.
conan1600 said:
If you read his post he explained that safe strap does not exist for his version of kindle. Therefore he did not receive an answer for his question and your entire post is in error, as well as utterly useless. As for this particular device I can't say but on MOST android devices I've owned root stays even after a factory reset. Must re flash or Un root on many of my other devices I've had to reset, just re downloaded supersu.
Click to expand...
Click to collapse
No
You should not lose root by doing a factory reset on a working system. You may however lose superuser app if you do not have it installed into system . Open superuser be sure binaries are updated scroll down in settings and be sure superuser is installed into system and you will be fine . To do a factory reset per security settings . Keep in mind if you want to do a reset it will wipe Sdcard and everything you have copied to tablet so backed them up onto your PC and put them back if you wish to keep it
jimyv said:
No
You should not lose root by doing a factory reset on a working system. You may however lose superuser app if you do not have it installed into system . Open superuser be sure binaries are updated scroll down in settings and be sure superuser is installed into system and you will be fine . To do a factory reset per security settings . Keep in mind if you want to do a reset it will wipe Sdcard and everything you have copied to tablet so backed them up onto your PC and put them back if you wish to keep it
Click to expand...
Click to collapse
Thanks to all who are commenting on this post. I started a similar thread earlier because I didn't realize this one was asking a question similar to what I would like to better understand.
I rooted an HDX 7 running 13.3.2.2 using Towel root. All works well. I may sell this tablet in the very near future in order to upgrade to an 8.9 HDX. Is there a simple process for fully UN-rooting this tablet and resetting it back to stock as if it just came out of the box? I am not concerned with losing any personal data on the tablet.
I stress simple because my skills are limited and I do not want to risk bricking. If the risk is too high, I would rather sell it as rooted and erase all user data.
rootnooby said:
Thanks to all who are commenting on this post. I started a similar thread earlier because I didn't realize this one was asking a question similar to what I would like to better understand.
I rooted an HDX 7 running 13.3.2.2 using Towel root. All works well. I may sell this tablet in the very near future in order to upgrade to an 8.9 HDX. Is there a simple process for fully UN-rooting this tablet and resetting it back to stock as if it just came out of the box? I am not concerned with losing any personal data on the tablet.
I stress simple because my skills are limited and I do not want to risk bricking. If the risk is too high, I would rather sell it as rooted and erase all user data.
Click to expand...
Click to collapse
Open su /setting/ full unroot/ bam
Security/ factory reset/bam
Love it! Thank you!

[Q] Un-root after Towel root

What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
To do that, you must uninstall the Towelroot app (shouldn't be too hard) then, to finish it off, try running these commands in an adb shell:
Code:
su
mount -o rw,remount /system
rm /system/bin/su
rm /system/xbin/su
mount -o ro,remount /system
exit
You are now unrooted!
Sent from my Nexus 7 using Tapatalk
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
blade22 said:
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
Click to expand...
Click to collapse
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
i have done the same steps and factory reset..faced no Issues.
and may be people facing issues might not have uninstalled xposed module and xposed framework
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
Thanks for all the great feedback. I should have provided more detail to start. I have a follow up question/clarification. This is what did:
1. Run Towel root - success
2. Followed directions to block ota updates and install supersu. - success
3. With root confirmed, Installed exposed frame work and module from here: http://forum.xda-developers.com/showthread.php?t=2618158 (to get play store and other google apps). - success
4. Activate exposed module and update. - success
5. Installed hdxposed.Apk, enabled it, Rebooted, and play store worked. - success
6. In any order, installed the files from the link. - success
Install play services
Install framework
Install Google account manager
7. Overall, all worked well.
Question:
What is the best way to undo everything I did?
Enable OTA updates?
Update to the latest firmware (basically to get prime music and fix wifi issues I'm having)?
Re-root?
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
brooklynstar220 said:
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
Click to expand...
Click to collapse
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Davey126 said:
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Click to expand...
Click to collapse
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
brooklynstar220 said:
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
Click to expand...
Click to collapse
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
I was able to get that version of Safestrap installed and was able to flash roms again but ADB is still not connecting when attached to the computer. Do you think a nanroid restore from my original setup could help fix this?
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
Thank you for your help with this. What is crazy but was probably a driver issue the whole time, I udated my laptop to Windows 10 and somehing told me to try it again and it worked immediately with the Toolkit and re-enabled the OTA updates. Thanks again.

[Q] 13.3.2.1 - Using device and securing Custom ROM possibility

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.

[HELP NEEDED] Bricked Kindle Fire HDx 7' 3rd gen- Sort of, Not really

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.

Categories

Resources