Hi all,
Putting it briefly....
Factory reset of hdx 7" on 4.5.2
Stuck at Kindle Fire logo
Shows in PC as Internal Storage but just empty folders Music, DCIM etc...
Can get ADB connection (good news?)
That's it....now here's the interesting bit.....
If I use Kindle Fire Utility and try to root using Towelroot the device goes straight go lock screen. I slide to open and am confronted with Towelroot app. Click on Make It Rain but nothing happens.
If I try other things like installing SU it returns with permission errors.
I can also get to the devices settings too. No other apps installed just HDXPOSED and TOWELROOT.
Got me baffled... Any ideas how to fix?
You can NOT use Towelroot for 4.5.2! You must use Kingroot. Read about this, I've no experience with it. From what I've read it's possible it requires internet connection, I also read this could be for optional download of some browser or whatever, so try to disable such options, if available. You should avoid internet connection, or have it as short as possible, to avoid OTA upate from Amazon to 4.5.4.
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
myotai said:
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
Click to expand...
Click to collapse
Nothing comes to mind. Generally being stuck at the grey Kindle logo is terminal on a device with stock recovery and a locked bootloader. For future reference HDXPOSED is obsolete and may have contributed to your woes. It was never designed for FireOS v4 and doesn't work well on later versions of FireOS v3.
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
myotai said:
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
Click to expand...
Click to collapse
Assume you tried another factory reset. Being stuck at the orange logo offers some hope but there is no Rx that I know of.
Obtaining root is obviously desirable. You can try installing Kingroot via adb install and hope it executes (like towelroot apparently does) and continues to completion. If successfully you could try to repair the damage that is preventing FireOS from fully booting.
I recall someone saying installing a different launcher (eg: Nova) allowed their Kindle to boot.
Another path is to place the 3.2.8 rollback file into the root of sdcard and hope it takes.
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
myotai said:
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
Click to expand...
Click to collapse
You probably won't find that (not aware of any forum postings). Here's the deal. You are operating in uncharted waters trying to revive an unlocked/unrooted device that got borked for unknown reasons. You are going to have to a bunch of research and take some chances. FireOS can be a bxxch to repair. If the device is under warranty your best course of action is to engage Amazon for an exchange.
Kingroot is a longshot idea which I would not have mentioned if not for your experience with Towelroot. I have no idea if it will work.
Google (or another search engine) is your friend. A couple representative links below that popped up on the first attempt. I have no experience with either site an can not vouch for the content. Just a starting point ...
- Kingroot
- ADB Info
Thanks for your feedback!
I guess nothing ventured n all that!
Its a paper-weight at the moment so can't get much worse.....I'll wander around those un-charted lands and see what I come up with!
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
So you're on 4.5.2 rooted & OTA disabled now? Then try to install Safestrap v4. If it works, backup your stock slot (even if it doesn't work, who knows what it'll be good for), and move it to your PC. As the secondary slots won't work with WLAN atm anyway, you can install one of the Safestrap v4 compatible ROMs, e.g. Nexus, or CM11 in the stock slot, don't create any secondary Slots (yet).
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
To confirm you are now on rooted 4.5.2 but can get beyond the FireOS settings menu. If you install an apk via adb can you retain enough control to launch the app UI? You can do this via an adb shell command; unfortunately, the specifics are beyond my knowledge. Hopefully someone else can jump in or you can research on your own (if needed).
There is no safe way to repair FireOS directly with a locked bootloader. On many Android devices you would simply reflash/reinstall the ROM. Unfortunately, Amazon neutered the stock recovery environment as you discovered. If something goes wrong you are in a world of hurt. I think there is a very good chance your device can be revived. Just need to proceed carefully and not bork things to the point were you don't get past the grey logo. That generally means you own a door stop.
Thoughts (sorry if these are obvious):
- Keep in mind OTA is probably enabled on your device. Stay off wifi if you get that far; best to use a tether for file transfer, etc. until the problem is fixed. You can also rename the OTA apk via adb ... but your focus should be elsewhere at this point.
- It appears the FireOS launcher is hanging during initial setup (as you did a factory reset). You may find joy by installing another launcher (eg: Nova via adb) which often set themselves as the default when installed. Once you regain some control you can then install Safestrap v4 which is the pathway to other roms or repairing 4.5.2. Be aware FireOS will try to reset the default launcher on reboot. If this method works don't mess around trying to fix stuff. Install Safestrap v4 immediately (you also need to open the app and install Safestrap recovery) so you retain some control over your device during further troubleshooting.
- If a different launcher does not work try going for Safestrap v4. You will probably need to get smart around adb shell commands as you have to launch the UI to install the Safestrap recovery environment.
Thanks all taken in - my knowledge of ADB and its various commands are being added to as the hours go by - never really used it before.
Determind though........!
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
myotai said:
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
Click to expand...
Click to collapse
Yep - just flash 4.5.2 rom from here (don't use any other - you'll be rewarded with a brick). I strongly suggest you backup your existing stock slot (containing CM11) and reflash that to a secondary slot that you'll need to create. You won't be able to use wifi on the secondary slot but it will give you a rom to boot into in the event something goes wrong with the FireOS flash. Once you get FireOS working in the stock slot you should be able uninstall Safestrap. The operative word is 'should' as the system and recovery partitions need to be consistent for FireOS to boot properly. From what you have shared there is no reason to believe this is not the case - but the risk can not be dismissed. The other option is to leave Safestrap installed which only adds an annoying splash screen on boot but otherwise does not impact performance. What it does do is give you a pseudo-recovery environment which can be quite handy as you have discovered! It's also the vehicle for installing other roms such as CM11, Nexus v4, etc.
Take note of the cautions in the linked OP, in particular OTA. After flashing 4.5.2 you'll need to root and rename the OTA apk before enabling wifi. Amazon is aggressively pushing 4.5.4 which can not be rooted. Don't ruin your day - block OTA (yea - that was stupid).
Thanks so much. Its worth listing the procedures that got me this far...
I think installing TOWELROOT via ADB despite the fact I knew it wouldn't work was oddly the only thing that got me as far as 'settings' from a stuck Kindle logo. Then I had to resgiter the device in order to go to 'new offers' in the books setting to access the browser.....emails......Kingroot......finally Safestrap....boom!
Related
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
ok sorry
mkid89 said:
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2786190 and that's why we have safestrap so you don't modify your stock http://www.youtube.com/watch?v=K6fPF5UZsWw
There are a few Devs still working on a way to flash something from fast boot no ETA means no promises seems the only fix for you may be to call Amazon . And maybe someone will chime in with a way to sideload an app I'm not sure. Good luck
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
well
mkid89 said:
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
Click to expand...
Click to collapse
If your patient somebody savvy enough will come by. and actually I know that I have read that someplace here I couldn't tell you where sorry. And if you're hoping for somebody to drop off the apk for you probably should let them know which firmware you are. Or you could always download the Bin file of your current firmware and exract it. Downloaded to an android rename it .zip and extract
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
well
mkid89 said:
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
Click to expand...
Click to collapse
8.9 is 14.3.2.4 https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.4_user_324002120.bin
Thank you for your help! I actually got it working shortly after my last post but got right into installing safestrap. ?
I'll post a write up tomorrow on what needed to be done in case anyone else has the issue. It's late where I'm at so I need to get some rest before trying to write it all up!
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Fyi that Chinese root method which is posted early on in the rollback thread it will root with ADB only.. And the factory reset thing has not really been consistent throughout each user.. But more or less we have been advising people not to because the chances are greater that you will lose the superuser binaries and you definitely will lose safestrap if installed. What is hard to get through to people is when they are in a boot loop they get in a hurry and start factory resetting and that is not always the best option. Depending on exactly what is going on. Most of the time it is people losing their ADB access and cannot figure out how to uninstall the MTP drivers first then install the ADB drivers..
Good job getting your device back online and thank you very much for the closing write up .
mkid89 said:
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Click to expand...
Click to collapse
could i use this way to fix my fault at this link bro?
http://forum.xda-developers.com/kin...p-kindle-fire-hdx-8-9-doesnt-able-to-t2816663
I took a look. That's a totally different issue than my issue. Mine wasn't getting stuck on the recovery screen. Sorry.
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
BRPW said:
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
Click to expand...
Click to collapse
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Davey126 said:
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Click to expand...
Click to collapse
Hi,
thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Your play store issue is probably Google play services. Download version .99 from the internet or the general thread.
As for your next steps.
It depends on how involved you want to go.
You can use safestrap and run the nexus Rom. Some people feel that is less risky because you are not modifying the system as much or recovery at all. However, if something goes wrong, you have almost no way to fix it (it is possible to brick with safestrap).
Or,
Downgrade to 2.3.2 (you have to do this because the 2.6 bootloader will not load any other recoveries or roms. Then put twrp on and use cm11 or similar. This gives you a working recovery to fix some issues which could go wrong.
Finally, you could rollback and unlock your bootloader. If you do that, it is the most involved, and a little risky. However, if you succeed. You will be able to put more rooms on it and this gives you the most options to recover from an error.
Many people are playing with cm12 after this.
It all depends on how you are willing to take your risks. It will all require a lot of reading on the forums.
Good luck.
Sent from my KFTHWI using Tapatalk
BRPW said:
Hi,thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Click to expand...
Click to collapse
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Davey126 said:
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Click to expand...
Click to collapse
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
BRPW said:
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
Click to expand...
Click to collapse
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Davey126 said:
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Click to expand...
Click to collapse
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
BRPW said:
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
Click to expand...
Click to collapse
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Davey126 said:
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Click to expand...
Click to collapse
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
BRPW said:
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
Click to expand...
Click to collapse
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Davey126 said:
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Click to expand...
Click to collapse
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
BRPW said:
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
Click to expand...
Click to collapse
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Davey126 said:
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Click to expand...
Click to collapse
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
BRPW said:
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
Click to expand...
Click to collapse
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Davey126 said:
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Click to expand...
Click to collapse
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
BRPW said:
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
Click to expand...
Click to collapse
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Davey126 said:
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Click to expand...
Click to collapse
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
BRPW said:
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
Click to expand...
Click to collapse
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Davey126 said:
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Click to expand...
Click to collapse
First option worked. Right, I side-loaded flashify. I'm guessing Im choosing the recovery image option, which then asks me to choose a recovery option; I choose TWRP, which then takes me to a device option. I don't see HDX 8.9 anywhere there. Which device am I choosing?
Edit: Scratch that; figured out what I had to do. Right, everything is done. TWRP's installed and working fine; bootloader is installed (though I don't know how to check it installed correctly). I think I'm ready for ROMs unless there are more checks to do?
Second edit: After some research, I think I've decided on CM11 (That's KitKat, right?). It seems that everything works on that; wifi works nicely, the Kindle app works nicely (had a HD7 that had issues after I flashed an Android ROM), even the camera works nicely. Just need a clear guide on how to flash it, so will wait for you to come back. It's things like "do I wipe dalvik cache, etc" that I'm confused about also. I'd rather not mess it up on the last hurdle trying to rush into it.
To specify, I'm looking at this one: http://forum.xda-developers.com/kin...rom-cm-11-20150228-unofficial-apollo-t3042776
Does it come pre-installed with gapps or no? Can't quite figure that out, since some ROMs specifically mention that they have gapps already loaded in.
Thanks.
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?
Hello, hoping one you experienced Kindle fire HDX 8.9 users can help me. Ok, my kindle fire HDX is running a stock factory rom/ software. The current firmware is 14.3.10. I rooted it a year ago with one of the programs I found on the net.
I kept getting the add pop-ups, so I used sql editor to change one or two of the fields to stop the add pop-ups as per instructions on the net. What ever root program I used, also disabled OTA updates. I installed the common files for getting the google playstore on the device. So over time, the playstore crashed, kept getting the error most people get about playstore has stopped working. I went in and uninstalled the playstore files. Then I decided to do a factory restore. BIG MISTAKE!!
Kindle fire HDX reset, and put me back to the registration screen. I was able to re-register it, then it went to the grey language screen. I choose English. So the problem is: It keeps looping to the language screen. I can choose English, then ok at the bottom of the screen, but it just goes back to the language screen. I can power it down, and back up. I get my unlock screen, and I can see the icon screen, and even go into the settings for about 20 to 30 seconds before it loops to the grey language screen. The kindle does not do any auto re-booting, it just stays stuck on the language screen until I power it down and back up.
Next, I can connect it to my PC through the USB cable, and the kindle is recognized. I have downloaded the program from XDA developers KFHD SRT 2.0. I can start that program, and it recognizes the Kindle , and it will put it into Fastboot mode. The kindle says fastboot and ready on the screen. I'm not sure what to do at this point. I dont want to jack up my kindle anymore than it already is. I read somewhere, that I may have to order a special USB cable for fastboot. I'm not sure if this is true. I never installed any recovery software on the Kindle, nor did I make a back up that I know of.
So what is the easy fix to get it back to stock and get it out this soft loop. I'm sure it can be repaired being I still have some access. I Thank any of you who will take the time to guide me through the process or point me to the right programs and files needed to get it working again.
Thanks
All you need to do is temporarily re-enable OTA updates (HDX Toolkit?)
rlkellyjr said:
Hello, hoping one you experienced Kindle fire HDX 8.9 users can help me. Ok, my kindle fire HDX is running a stock factory rom/ software. The current firmware is 14.3.10. I rooted it a year ago with one of the programs I found on the net.
I kept getting the add pop-ups, so I used sql editor to change one or two of the fields to stop the add pop-ups as per instructions on the net. What ever root program I used, also disabled OTA updates. I installed the common files for getting the google playstore on the device. So over time, the playstore crashed, kept getting the error most people get about playstore has stopped working. I went in and uninstalled the playstore files. Then I decided to do a factory restore. BIG MISTAKE!!
Kindle fire HDX reset, and put me back to the registration screen. I was able to re-register it, then it went to the grey language screen. I choose English. So the problem is: It keeps looping to the language screen. I can choose English, then ok at the bottom of the screen, but it just goes back to the language screen. I can power it down, and back up. I get my unlock screen, and I can see the icon screen, and even go into the settings for about 20 to 30 seconds before it loops to the grey language screen. The kindle does not do any auto re-booting, it just stays stuck on the language screen until I power it down and back up.
Next, I can connect it to my PC through the USB cable, and the kindle is recognized. I have downloaded the program from XDA developers KFHD SRT 2.0. I can start that program, and it recognizes the Kindle , and it will put it into Fastboot mode. The kindle says fastboot and ready on the screen. I'm not sure what to do at this point. I dont want to jack up my kindle anymore than it already is. I read somewhere, that I may have to order a special USB cable for fastboot. I'm not sure if this is true. I never installed any recovery software on the Kindle, nor did I make a back up that I know of.
So what is the easy fix to get it back to stock and get it out this soft loop. I'm sure it can be repaired being I still have some access. I Thank any of you who will take the time to guide me through the process or point me to the right programs and files needed to get it working again.
Thanks
Click to expand...
Click to collapse
Careful what you read on the "net"; fastboot (special USB) cables are useless on a HDX. KFHD SRT is for a different device. Factory resets on a HDX often result in more harm than good as you discovered.
Stock launcher is likely hosed. Common fix is to sideload a third party launcher (recommend Apex or Nova) to regain temporary control over your device and then repair the problem. The latter is best accomplished by allowing FireOS to upgrade (thus replacing the botched components) but that may create to further headaches given the extensive modifications already made to FireOS and lack of detail around exactly what was done.
You'll need to learn some adb commands to install Apex/Nova via USB tether. A slimmed down version of ADB can be found here (Windows host).
Given your firmware version I suggest flashing TWRP (here) which will give your a 'real' recovery. From there you can install Nexus v2 (new rom) which frees your device from the limitations of FireOS and supports full access to the world of Google including the play store. You can stay on Nexus v2 or take the next step and unlock the bootloader which will open the door to additional roms including Nexus v4, CM11 (both KitKat) and CM12 (lollipop). Note the above is not an Rx; I have left out several steps in the interest if brevity. Will fill in the details as needed.
If you want to keep FireOS then you have to unblock OTA (suggest HDX toolkit) and upgrade to a newer version of FireOS (suggest 3.2.6). There is some risk involved but safer than tinkering with your current install which you lead to an unrecoverable situation.
Update !!!
Thanks for your help. I used HDX tool kit to re-enable updates. The kindle took and update, so it is at 4.5.2. But now it wants to install the newer update as soon as I power it on. What should I do?? Is the newer update (4.5.3 or higher / unknow at this time) still going to allow root.
rlkellyjr said:
Thanks for your help. I used HDX tool kit to re-enable updates. The kindle took and update, so it is at 4.5.2. But now it wants to install the newer update as soon as I power it on. What should I do?? Is the newer update (4.5.3 or higher / unknow at this time) still going to allow root.
Click to expand...
Click to collapse
You'll need to root via adb. You can then disable OTA updates by renaming a system file.
- enable adb via settings -> device -> enable ADB
- tether via standard USB cable
- install minimal adb and fastboot (Windows host)
- open command window, switch to adb directory and issue command 'adb devices'. If no responses install drivers, reboot Windows and try again
- (optional) some lite reading on adb command
- grab kingroot apk, place in adb folder and then issue command 'adb install <package-name>.apk'
- install ES File Explorer in a similar manner
- run kingroot from your HDX. If it requests Internet connectivity enable WiFi briefly (<30 sec) until it completes then immediately disable (or place in airplane mode)
- replace Kinguser with SuperSU (here)
- enable root support in ES File Explorer via toggle in left side panel navigate to /system/priv-app/ and search for DeviceSoftwareOTA.apk
- use ES File Explorer to rename DeviceSoftwareOTA.apk to DeviceSoftwareOTA.old (or whatever name you want provided it does not end in .apk)
At this point you can safely enable WiFi. I strongly suggest installing Safestrap v4 before making any other changes to your device. This tool offers:
- enhanced recovery capability (it is not a full recovery but better than Amazon's tools)
- ability to make a complete backup of your device; essential should something go wrong
- ability to install other roms including Nexus v4 or CM11
Good luck.
final steps in re-rooting and preventing update
What file do I need to rename to prevent the pending update from installing. My kindle is powered off currently, if I turn it on its going to go straight to the kindle fire screen and state installing the update. What do I need to rename the file to? I'm assuming I can do all that you tell me to do thru windows 7 , with the kindle connected via USB and it being powered off????
Thank you for your time in helping me getting it going again.
rlkellyjr said:
What file do I need to rename to prevent the pending update from installing. My kindle is powered off currently, if I turn it on its going to go straight to the kindle fire screen and state installing the update. What do I need to rename the file to? I'm assuming I can do all that you tell me to do thru windows 7 , with the kindle connected via USB and it being powered off????
Thank you for your time in helping me getting it going again.
Click to expand...
Click to collapse
Assuming you missed my prior post given close timestamps. Details here. Kindle must be powered on to issue adb commands. To prevent and immediate OTA either: 1) place device in airplane mode; or 2) move to an area where it can not connect to WiFi.
Follow up, needing help still
Davey126 said:
Assuming you missed my prior post given close timestamps. Details here. Kindle must be powered on to issue adb commands. To prevent and immediate OTA either: 1) place device in airplane mode; or 2) move to an area where it can not connect to WiFi.
Click to expand...
Click to collapse
Thank you Sir. I guess I need to clarify what I meant by update. My kindle has already downloaded the update, so it is trying to install or apply the update upon start up. So I just press and held the power button to power it off. However as soon as I power it back on, the kindle will go back to the screen where it's trying to install the update. Is there a way to stop it from applying the update, and still accomplish what you suggested.
Thank you for any help that you can provide.
rlkellyjr said:
Thank you Sir. I guess I need to clarify what I meant by update. My kindle has already downloaded the update, so it is trying to install or apply the update upon start up. So I just press and held the power button to power it off. However as soon as I power it back on, the kindle will go back to the screen where it's trying to install the update. Is there a way to stop it from applying the update, and still accomplish what you suggested.
Thank you for any help that you can provide.
Click to expand...
Click to collapse
Well that's a problem. Are you certain it is trying to process fully downloaded OTA upate to FireOS (likely 4.5.5) vs completing the 4.5.2 install? The messages look a bit similar. If it is trying to update to a higher version I would let it complete as the risk of interrupting the update mid-stream could leave you in a worse state. You would then need to perform the 3.2.8 rollback / 4.5.2 update again. Or just stay with 4.5.5 depending on your passion around root and/or running an alternate rom (via Safestrap) on this device.
Davey126 said:
Well that's a problem. Are you certain it is trying to process fully downloaded OTA upate to FireOS (likely 4.5.5) vs completing the 4.5.2 install? The messages look a bit similar. If it is trying to update to a higher version I would let it complete as the risk of interrupting the update mid-stream could leave you in a worse state. You would then need to perform the 3.2.8 rollback / 4.5.2 update again. Or just stay with 4.5.5 depending on your passion around root and/or running an alternate rom (via Safestrap) on this device.
Click to expand...
Click to collapse
I think it might be trying to install the 4.5.5. Could be wrong?? So if you suggest, I will let it finish what it's trying to do. But I do want to obtain root again, and install the playstore. I'm not sure if these most recent updates lock the bootloader, where I can not install another custom OS. Or if a roll back will re-enable it. I'm still new to the Kindle. It's been rooted for over a year, and I never had a reason to mess with it, until the start of this thread.
Thank You.
rlkellyjr said:
I think it might be trying to install the 4.5.5. Could be wrong?? So if you suggest, I will let it finish what it's trying to do. But I do want to obtain root again, and install the playstore. I'm not sure if these most recent updates lock the bootloader, where I can not install another custom OS. Or if a roll back will re-enable it. I'm still new to the Kindle. It's been rooted for over a year, and I never had a reason to mess with it, until the start of this thread.
Thank You.
Click to expand...
Click to collapse
If there is no way to stop the installation, then I might as well power it back on , and let it finish. Is there not a way to make it do a factor reset, or boot loader menu I could put it in, providing a little time to modify a the update file to prevent it from updating??
Thanks
rlkellyjr said:
I think it might be trying to install the 4.5.5. Could be wrong?? So if you suggest, I will let it finish what it's trying to do. But I do want to obtain root again, and install the playstore. I'm not sure if these most recent updates lock the bootloader, where I can not install another custom OS. Or if a roll back will re-enable it. I'm still new to the Kindle. It's been rooted for over a year, and I never had a reason to mess with it, until the start of this thread.
Click to expand...
Click to collapse
Updating to 4.5.2 eliminated the path to an unlocked bootloader. However, there is an alternate solution (Safestrap v4) that permits loading other KitKat based roms (currently Nexus and CM11) but you must be running FireOS 4.5.2 first. Note 4.5.5 can not be rooted at present.
I strongly discourage layering gapps onto FireOS. Amazon and Google components don't play nice; you can get it to work (mostly) but maintenance is a nightmare as each version change seems to bring new headaches. A better solution is to use one of the previously mentioned roms which turns your HDX into a 'normal' Android tablet with full access to the Playstore.
As previously mentioned keep WiFi off until your tablet completes whatever updates it is trying to apply. Post back the final version number which will dictate future steps.
Davey126 said:
Updating to 4.5.2 eliminated the path to an unlocked bootloader. However, there is an alternate solution (Safestrap v4) that permits loading other KitKat based roms (currently Nexus and CM11) but you must be running FireOS 4.5.2 first. Note 4.5.5 can not be rooted at present.
I strongly discourage layering gapps onto FireOS. Amazon and Google components don't play nice; you can get it to work (mostly) but maintenance is a nightmare as each version change seems to bring new headaches. A better solution is to use one of the previously mentioned roms which turns your HDX into a 'normal' Android tablet with full access to the Playstore.
As previously mentioned keep WiFi off until your tablet completes whatever updates it is trying to apply. Post back the final version number which will dictate future steps.
Click to expand...
Click to collapse
Ok, its sitting at 4.5.4 airplane mode is on. So what is my next step from here.
Thanks
rlkellyjr said:
Ok, its sitting at 4.5.4 airplane mode is on. So what is my next step from here.
Click to expand...
Click to collapse
To secure root and Safestrap v4 you will need to rollback to 4.5.2 via 3.2.8 (there is no direct path). There is risk involved; procedures need to be followed carefully to avoid permanently bricking your device. Don't take that lightly; new causalities are reported with surprising frequency from individuals who skipped steps or simply made a mistake. Amazon devices are unforgiving. Also note there are no step-by-step guides or videos. It's your responsibility to understand the end-to-end process and associated procedures.
First have a read through this thread. Everything you need is there but like most of the forums it is disorganized and full of off-topic commentary.
Before starting I recommend downloading the following into the suggested folders (you'll need to create these; name them as you wish):
- 3.2.8 rollback file for Apollo (here) -> 328RB folder
- 4.5.2 update file for Apollo (here) -> 452UD folder
- ES File Explorer (here) -> Tools folder
- Kingroot (here) -> Tools folder
Thoughts:
- keep above files in respective folders until needed
- make sure you can see/communicate with your device via USB tether. Vital for transferring files and performing certain functions should things go wrong.
- keep WiFi off at all times unless instructed otherwise. Keep airplane mode engaged (on). If possible stay away from open hotspots; skip WiFi setup when prompted
- WARNING: If you device takes an OTA update during rollback it will almost certainly brick with no chance of recovery. OTA updates are delivered via WiFi.
- WARNING: Never perform a 'factory reset' from the HDX recovery menu unless specifically instructed to do so.
Ask questions if unsure. Good luck.
Thanks for your help
Davey126 said:
To secure root and Safestrap v4 you will need to rollback to 4.5.2 via 3.2.8 (there is no direct path). There is risk involved; procedures need to be followed carefully to avoid permanently bricking your device. Don't take that lightly; new causalities are reported with surprising frequency from individuals who skipped steps or simply made a mistake. Amazon devices are unforgiving. Also note there are no step-by-step guides or videos. It's your responsibility to understand the end-to-end process and associated procedures.
First have a read through this thread. Everything you need is there but like most of the forums it is disorganized and full of off-topic commentary.
Before starting I recommend downloading the following into the suggested folders (you'll need to create these; name them as you wish):
- 3.2.8 rollback file for Apollo (here) -> 328RB folder
- 4.5.2 update file for Apollo (here) -> 452UD folder
- ES File Explorer (here) -> Tools folder
- Kingroot (here) -> Tools folder
Thoughts:
- keep above files in respective folders until needed
- make sure you can see/communicate with your device via USB tether. Vital for transferring files and performing certain functions should things go wrong.
- keep WiFi off at all times unless instructed otherwise. Keep airplane mode engaged (on). If possible stay away from open hotspots; skip WiFi setup when prompted
- WARNING: If you device takes an OTA update during rollback it will almost certainly brick with no chance of recovery. OTA updates are delivered via WiFi.
- WARNING: Never perform a 'factory reset' from the HDX recovery menu unless specifically instructed to do so.
Ask questions if unsure. Good luck.
Click to expand...
Click to collapse
Thank you for all your help.
A tad more info needed
rlkellyjr said:
Thank you for all your help.
Click to expand...
Click to collapse
Can I apply the downgrade with 4.5.4, or do I need to let the kindle update to 4.5.5 before attempting the downgrade. ???
Thanks again.
can rollback be done with firmware 4.5.4 ?
rlkellyjr said:
Thank you for all your help.
Click to expand...
Click to collapse
can the roll back be applied to 4.5.4? or do I need to update all the way to 4.5.5 before doing the roll back. Thanks..
rlkellyjr said:
can the roll back be applied to 4.5.4? or do I need to update all the way to 4.5.5 before doing the roll back. Thanks..
Click to expand...
Click to collapse
rlkellyjr said:
Can I apply the downgrade with 4.5.4, or do I need to let the kindle update to 4.5.5 before attempting the downgrade. ???
Thanks again.
Click to expand...
Click to collapse
You can begin the rollback from any variant of FireOS v4 including 4.5.4.
I have a root Kindle Fire HDX 7 on Fire OS 4.5.2 and it is rooted and adb working. The problem is, when I boot it, the screen flashes, but the home buttons and notification bar still shows. I can pull down the notification bar, but I cannot access the settings or any built in launcher apps. I know how and where to type in commands and I fully understand adb. Also I do not have TWRP or Safestrap installed, nor have i tried to install a custom rom. The device has boot issues, so if I reboot it, I have to go in CMD and type "adb reboot recovery" and then factory reset just to get passed the boot screen. I cannot install a new update to fix it because I cannot access the settings. I have posted quite a few posts on Q&A but never got answers. Somebody please help. Could it be possible that there is nothing I can do? Am I screwed? I have looked nearly everywhere on the internet and can only find things for the original Kindle Fire.
KyleCreel123 said:
I have a root Kindle Fire HDX 7 on Fire OS 4.5.2 and it is rooted and adb working. The problem is, when I boot it, the screen flashes, but the home buttons and notification bar still shows. I can pull down the notification bar, but I cannot access the settings or any built in launcher apps. I know how and where to type in commands and I fully understand adb. Also I do not have TWRP or Safestrap installed, nor have i tried to install a custom rom. The device has boot issues, so if I reboot it, I have to go in CMD and type "adb reboot recovery" and then factory reset just to get passed the boot screen. I cannot install a new update to fix it because I cannot access the settings. I have posted quite a few posts on Q&A but never got answers. Somebody please help. Could it be possible that there is nothing I can do? Am I screwed? I have looked nearly everywhere on the internet and can only find things for the original Kindle Fire.
Click to expand...
Click to collapse
Try installing an different launcher (suggest free version of Apex or Nova) via adb which may allow you to gain some temporary control over your device. Not sure where to go from there as the default launcher will quickly revert to stock and can not be easily changed. If a warranty exchange is not possible your best option is to downgrade to 3.2.8 which should overwrite the contents of the system partition. Not sure you will be able to initiate the downgrade given the state of your device; it may also brick given the stock launcher is borked. I don't believe an upgrade to 4.5.3 or 4.5.5 will fix the launcher problem. Good luck.
Davey126 said:
Try installing an different launcher (suggest free version of Apex or Nova) via adb which may allow you to gain some temporary control over your device. Not sure where to go from there as the default launcher will quickly revert to stock and can not be easily changed. If a warranty exchange is not possible your best option is to downgrade to 3.2.8 which should overwrite the contents of the system partition. Not sure you will be able to initiate the downgrade given the state of your device; it may also brick given the stock launcher is borked. I don't believe an upgrade to 4.5.3 or 4.5.5 will fix the launcher problem. Good luck.
Click to expand...
Click to collapse
The thing is i cannot install a different launcher or anything that requires accessing settings because i cannot access my wifi. Maybe a possible way to install an apk through adb?
KyleCreel123 said:
The thing is i cannot install a different launcher or anything that requires accessing settings because i cannot access my wifi. Maybe a possible way to install an apk through adb?
Click to expand...
Click to collapse
There is. In a previous post you stated that you fully understood ATB so I assumed that was the case. A little searching will yield the answer; google is your friend.