Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
trungamox34 said:
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
Click to expand...
Click to collapse
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
jimyv said:
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
Click to expand...
Click to collapse
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
trungamox34 said:
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
Click to expand...
Click to collapse
Not to be rude but first thing's first if anybody here is going to help you you're going to have to know details and exactly what you had prior to your current state .ie answer any questions with as much detail as possible . And if it all possible find out what they did to your device . If you cannot provide any of this .I cannot provide a help . I don't know anybody that has a crystal ball I can borrow LOL
The question was had you installed xposed framework on your stock slot?
What your original firmware was?
Then you might want to add exactly what rhomb you attempted to flash?
What error did it show. Can you or can you not still get into safestrap?
First guess though I would venture to say you have a paperweight and less you can get them to warrantee it for you. Personally I would have uninstalled safe strap recovery and lock root access out before I loan my device to anybody period but that's just me
Related
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
none.
tuilakhang said:
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
Click to expand...
Click to collapse
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
jimyv said:
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
Click to expand...
Click to collapse
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
ok
tuilakhang said:
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
Click to expand...
Click to collapse
There are multiple pages to these forums, for example if you open up the general section and you look at the bottom of the page it gives you option to go to the next page several pages worth of information there same goes with each subsection. There is also a( search this thread) option in the right upper of your page. If you are still reading by chance and you will find that updates you need for either Apollo or Thor on the bottom of page four in the general section.
Didnt already bricked one of your devices here? If you are one of the fellows that bricked I would advise you to learn how to use these forums efficiently before you break another device. If not then at the very least you need to do more homework at least figure out how to use this site efficiently into everyone's benefits. Most of us are here to help those that first at least are trying to help themselves. Good luck and enjoy.
Apparently pressing "ESC" in this window deletes all the text without being able to undo this.... so here goes again....
Sorry for the late reply, but i just saw your post in the developer's forum (Cpasjuste's Thor Gapps), where i cannot post due to my lurker nature.
i'm on the same FireOS version as you: 13.3.2.1
i had trouble getting Cpasjuste's ROM to work, because i was trying to use thor-gapps-13.3.0.0-v2. i didn't dare using thor-gapps-13.3.2.4-v1, because of the several warnings.
i then saw someone else having success with thor-gapps-13.3.2.4-v1 on an earlier version and thought i'd give it a try after all. i took the risk of closing the door to an unlocked bootloader, i took the risk of bricking my device. i decided to do this, because of my year long experience with custom ROMs, also on devices that were not intended to have them (Nook HD+, Kindle Fire...). i'm not sure, if the kernel is touched during the flash process, but i assum(ed) it isn't. i can boot into FireOS which still shows 13.3.2.1 as version, but who knows what has happened under the hood.
The ROM feels stable so far for such an early version. i haven't tested much, but the few apps I've been using regularly worked well. Ironically the amazon appstore crashed after about 20 seconds. Makes me think they are trying to block the "freed" devices, but it might just be a bug after all.
So, again, if you feel like risking to lose the possibility of an unlocked bootloader, if you want to risk or can afford to brick such an expensive device, you can try using thor-gapps-13.3.2.4-v1.
All i did, was to follow the instructions provided in Cpasjuste's thread exactly as they were.
Don't hold me accountable, it's already been a week, but if i recall correctly, these were my steps:
DIsable WiFi / Enable Airplane mode in FireOS (just to prevent automatic OTA updates)
Root device (i used towelroot)
Install Safestrap (i had to use Safestrap-Thor-3.75-os3.2.4-B02.apk, despite the instructions in the safestrap thread telling to use 3.72 on our version - another risk i took)
Boot into Safestrap
Backup Original ROM
Create ROM Slot (keep this new slot active/activated)
Restore Original ROM backup, but only the DATA partition
Wipe Cache + Dalvik Cache
Flash thor-gapps-13.3.2.4-v1.zip
Wipe Cache + Dalvik Cache
Boot into system
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Timmetjuh said:
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Click to expand...
Click to collapse
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Davey126 said:
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Click to expand...
Click to collapse
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Timmetjuh said:
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Click to expand...
Click to collapse
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Davey126 said:
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Click to expand...
Click to collapse
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Timmetjuh said:
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
Click to expand...
Click to collapse
Timmetjuh said:
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Click to expand...
Click to collapse
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Davey126 said:
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Click to expand...
Click to collapse
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Timmetjuh said:
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Click to expand...
Click to collapse
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It's not that I don't like the Nexus ROM, I just like to experiment with these things..
So I just installed TWRP with Flashify (started Flashify from NEXUS) and now I seem stuck at the grey Kindle fire logo. I'm just going to leave it alone for a few hours, hopefully it boots later today.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Timmetjuh said:
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Click to expand...
Click to collapse
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Davey126 said:
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Click to expand...
Click to collapse
I'm stuck at the grey Kindle logo..
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Timmetjuh said:
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Click to expand...
Click to collapse
Congrats! Had a bad feeling after your earlier post; glad that was misplaced. Enjoy CM11 and all the goodness that comes from a liberated HDX.
At some point you should consider unlocking the bootloader. That will provide an important fail safe should things go wrong and opens the door to newer roms. Unlike previous flashes there is little/no risk in unlocking. It will either work or not with no adverse consequences. Unlocking can be a frustrating ride as the process involves multiple steps in unfamiliar territory but ultimately the benefits outweigh the effort IMO. Nothing that needs to be tackled right away but keep it on your radar ... especially if you plan to experiment with other roms.
Unlock bootloader
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
No. You can NOT unlock the bootloader! You can NOT downgrade to 3.2.4 and then further to 3.1.0/3.2.3.2! DON'T attempt to do so, you will brick your HDX!
Your only available option is to stay on 4.5.2 and use Safestrap v4 with either Nexus and/or CM11.
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Davey126 said:
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Click to expand...
Click to collapse
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
slothdabski said:
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
Click to expand...
Click to collapse
I actually just got it working by running the following as SU in terminal emaulator
# ip route add default dev tun0 scope link
Not sure yet if I have to do this every time I tether, but if so, i think i can just make a script to execute automatically?
Hi
Newbie here. We bought a kindle which turnout to be blacklisted so we can't register it. Obviously it is useless as we can only use internet.
My kindle was running on latest firmware which meant I couldn't root it. Thanks to one of you xda geniuses. I was able to rollback to firmware 13.3.2.8
I change oat filed to avoid upgrades. I installed es explorer.
I then rooted my kindle and did root checked which confirms it is rooted on Kfthwi android 4.2.2
I installed su super user. Seems to work fine
After that I tried to install boot loader fireflash but it keeps stopping
I finally managed to install and launch Rashr but when I boot recovery with twrp or any other files my kindle boots and stops saying can't boot and offers me to do factory reset or starts again as if nothing happened. I haven't chosen factory reset as I don't think this will help.
I have added su super users to system hoping this would help but no success.
I have also tried loads of kfu from pc but although adb is ok it says boot status unknown and fails every time as if it can't find the path or something...
I have ran out of ideas. I don't know what to do anymore
My aim is to install cm12 or other versions... anything to make this kindle become android
Please help me!
Thanks
worldita said:
Hi
Newbie here. We bought a kindle which turnout to be blacklisted so we can't register it. Obviously it is useless as we can only use internet.
My kindle was running on latest firmware which meant I couldn't root it. Thanks to one of you xda geniuses. I was able to rollback to firmware 13.3.2.8
I change oat filed to avoid upgrades. I installed es explorer.
I then rooted my kindle and did root checked which confirms it is rooted on Kfthwi android 4.2.2
I installed su super user. Seems to work fine
After that I tried to install boot loader fireflash but it keeps stopping
I finally managed to install and launch Rashr but when I boot recovery with twrp or any other files my kindle boots and stops saying can't boot and offers me to do factory reset or starts again as if nothing happened. I haven't chosen factory reset as I don't think this will help.
I have added su super users to system hoping this would help but no success.
I have also tried loads of kfu from pc but although adb is ok it says boot status unknown and fails every time as if it can't find the path or something...
I have ran out of ideas. I don't know what to do anymore
My aim is to install cm12 or other versions... anything to make this kindle become android
Please help me!
Thanks
Click to expand...
Click to collapse
Sorry - will not provide assistance for a blacklisted device. Read the forums.
Davey126 said:
Sorry - will not provide assistance for a blacklisted device. Read the forums.
Click to expand...
Click to collapse
Hi I am sorry I misunderstood the terms. It is NOT blacklisted. It is unregistered.
We have called Amazon and it does not belong to anyone. We don't know how it happened we bought it second hand. The tablet is not letting registered but it is not blacklisted. Can you still help ?
You can NOT unlock the bootloader, use TWRP and CM12 anyway. You'd need 3.2.3.2 or lower for that, and you can NOT downgrade below 3.2.8.
Ok thanks for replying to me and for the info. So no more hope? I should just bin it?
So sad.... was supposed to be for my kids.
I guess this shows you really can't buy these tablets second hand!
Thanks again for your time.
worldita said:
Ok thanks for replying to me and for the info. So no more hope? I should just bin it?
So sad.... was supposed to be for my kids.
I guess this shows you really can't buy these tablets second hand!
Thanks again for your time.
Click to expand...
Click to collapse
You likely toasted the device by installing stuff that is not valid for a HDX.
Wow Davey126 thank you so much for all your positive feedback.
So helpful
worldita said:
Wow Davey126 thank you so much for all your positive feedback.
So helpful
Click to expand...
Click to collapse
Sorry for the prickly response. Reacting to: 1) device that will not register which is a bright red flag waving; and 2) installing fireflash which is for a different model and likely destroyed your device. You can not install twrp on a HDX that has been upgraded past 3.2.6 and you can not rollback to any version below 3.2.8 from any version above 3.2.6. A little reading would have quickly revealed the sensitivity of HDX models to 'hacks' other than the limited suite described in the forums. Your device joins countless others in the tower of bricks created by owners failing to research proper procedures.
tldr;
So Optimal solution would be to get Gapps working on Stock 13.3.0.5, and from there I'll install and android launcher. But to do this, the Xposed problem will need to be fixed.
Has anyone else had a problem with Xposed where every menu leads to just a blank white screen?
Not-so-optimal would be to do all the upgrading, OTA blocking, flashing, and backing up to get it on like CM11 or something.
Hey all,
I just made my XDA account, I've been kinda lurking on the forums for a little while though.
I won a Kindle Fire HDX 7" (idk What gen or how to determine what gen it is. Its got 2gb RAM and 32gb Internal) that says its running 13.3.0.5 and so I decided to do a little research about custom roms and rooting and found this wonderful forum. I've had a bit of experience with custom roms, I loaded CM9 onto an LG Thrive (look that one up, its a bit of a pain to flash as well) And I'd love to see about flashing this brand new FHDX.
Now, I didn't purchase this tablet, so it is of no expense to me, however, I would rather not be reckless in my attempts to mess with it.
What I want:
Google Apps -- Play/Music/Gmail/Calendar/etc
Root
Android JB or KK OS or Android-like Launcher or Ubuntu Touch (idk about this one, it seems really cool, I've heard about it for a long time and never got the chance to play with it)
I'd love to stay away from bricks, but I'm not afraid of them enough to not flash it. I'm a computer engineer and kinda have some experience with android and flashing.
Now, as to my progress so far:
I've rooted it with towelroot and installed ES FileManager, SuperSU, and I've tried to install Xposed/HDXposed multiple times but it simply will not work correctly. Xposed gives me a white screen when I go into any of the menus and doesn't allow me to install after clicking "Framework". I've tried many different renditions of Gapps packages, but almost all of them result in a process failing or stopping.
Thanks and if you need more information or I've left something out, feel free to ask away!
b1nary
UPDATE:
I turned wifi on for a little bit and my Kindle decided it wanted to update, so now its running 13.3.2.5 :/
I've put it in airplane mode, and I'm thinking about doing this to downgrade it.
b1nary.v01d said:
UPDATE:
I turned wifi on for a little bit and my Kindle decided it wanted to update, so now its running 13.3.2.5 :/
I've put it in airplane mode, and I'm thinking about doing this to downgrade it.
Click to expand...
Click to collapse
I'm not sure what you're up to, but I'd suggest to downgrade to 3.1.0 using the procedure in the thread you linked to (be sure to scroll down for the procedure for 3.2.5/3.2.6 because you can NOT use the edited build number anymore!), then install TWRP, unlock the bootloader and flash a ROM of your choice.
You're up to that? Or what's on your mind?
Yea, sounds great! I'll post my progress as I get things going.
btw I love your name if its a play on Tom Clancy. Love those books and the games inspired by them!
b1nary.v01d said:
Yea, sounds great! I'll post my progress as I get things going.
btw I love your name if its a play on Tom Clancy. Love those books and the games inspired by them!
Click to expand...
Click to collapse
Alright, basic approach is here. Lots of info to read, so any questions just ask, before you brick your HDX.
I'm now Rooted running on 13.3.1.0
I've disabled OTA updates as well. From here I'll pick the rom I want to d/l, get TWRP installed, unlock bootloader with python/.unlock file, and flash the rom.
(I'll edit this post as I finish things)
Thanks!
b1nary.v01d said:
I'm now Rooted running on 13.3.1.0
I've disabled OTA updates as well. From here I'll pick the rom I want to d/l, get TWRP installed, unlock bootloader with python/.unlock file, and flash the rom.
(I'll edit this post as I finish things)
Thanks!
Click to expand...
Click to collapse
OK, don't forget to make a backup of Fire OS in TWRP (and move it to your PC) before you flash any custom ROM. Might be useful one day.
Alright!!
I'm backed up, unlocked, custom recovery'd, and flashed to the new Nexus KitKat 4.4.4!
Thanks so much for the help Cl4ncy both in this thread and all the others.
And thanks to the XDA community for hosting all these awesome tools!
Now to have some fun with my new psuedo-nexus 7" tablet >
b1nary
Hi,
I have an Amazon Fire HD 7(Ariel).
I wanted to get Android 5.2.2 on this and root it so I could get GAPPS and many more.
My Fire was on 4.5.5 so I used this guide to downgrade to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
All went well and I followed all the instructions on the guide. I got root, installed TWRP and now I wanted to install lollipop.
So I followed this guide :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I went to TWRP, flashed everything and in the end, when I had to reboot to recovery, I accidentally swiped the "Swipe to install SuperSU" prompt.
Now my Fire is stuck on a black screen. It won't do anything when it's connected to a computer except connect/disconnect constantly.
I think it's in a bootloop where the screen does not turn on.
All I see on the few moments it stays connected in Device manager is MT65XX Preloader.
Do I need to get it to fastboot ? Do I need to buy a factory cable ?
What can I do now ?
Trix123 said:
. . .
All went well and I followed all the instructions on the guide. I got root, installed TWRP and now I wanted to install lollipop.
So I followed this guide :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I went to TWRP, flashed everything and in the end, when I had to reboot to recovery, I accidentally swiped the "Swipe to install SuperSU" prompt.
. . .
What can I do now ?
Click to expand...
Click to collapse
Problem wasn't installing SuperSU, which was correct thing to do. See below.
dardack said:
I bought a used one off eBay. Booted up fine. Side loaded king root. It failed to root. After settings screen was blank flickering. So I rebooted. Same flickering. So booted into recovery and did factory reset. Now it's in boot loop. It gets to upgrading then back to fire logo. Then starting applications then back to logo. Then stays on logo. Been 30 minutes. Tried twice. Any help.
Click to expand...
Click to collapse
Sounds like Amazon OTA updated you at just the wrong time.
If you haven't been following these forums, see this. Sorry to say, you guys are bricked. If you're still under warranty, contact Amazon for replacement.
Hmm. I disabled OTA updates via JMZ FireTools on 4.5.3. That shouldn't have happened.
Well, is there anything I can do as a last resort without replacing it ?
It has been constantly rebooting. It gets recognized as MT65xx preloaded in Device Manager, goes offline and comes back on again ?
I've let the battery drain completely, so what do I do now ?
If you can help me get it into fastboot or adb then I can fix it myself.
-Thanks.
Trix123 said:
Hmm. I disabled OTA updates via JMZ FireTools on 4.5.3. That shouldn't have happened.
Well, is there anything I can do as a last resort without replacing it ?
It has been constantly rebooting. It gets recognized as MT65xx preloaded in Device Manager, goes offline and comes back on again ?
I've let the battery drain completely, so what do I do now ?
If you can help me get it into fastboot or adb then I can fix it myself.
Click to expand...
Click to collapse
You overrode and wiped JMZ's OTA block when you upgraded in TWRP. The best explanation is in the post I linked to above. If you look at other threads you'll see this happened to several people yesterday. You can't get out of the loop, so can't get into fastboot or adb. All you can do is contact Amazon for a replacement for a bootlooping tablet. (If you can't think of a plausible explanation, wait a few days until tablet would get update (which it can't, of course) and blame it on that.)
DoLooper said:
You overrode and wiped JMZ's OTA block when you upgraded in TWRP. The best explanation is in the post I linked to above. If you look at other threads you'll see this happened to several people yesterday. You can't get out of the loop, so can't get into fastboot or adb. All you can do is contact Amazon for a replacement for a bootlooping tablet. (If you can't think of a plausible explanation, wait a few days until tablet would get update (which it can't, of course) and blame it on that.)
Click to expand...
Click to collapse
I contacted Amazon and they will be sending me a replacement.
Is there any way to make this tablet work again ?
That way, I could just cancel the replacement from Amazon and that would save a lot of time.
Thanks.
Help me please )':
Hello i am french sorry for me english
i have identical problem
What would I say in sav amazon for replacement my kindle fire please :l
Thanks you !