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.
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
droiduzr2 said:
My device is "bricked". I screwed up safestrap install and my device just boots to the grey kindle screen.
Click to expand...
Click to collapse
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
draxie said:
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
Click to expand...
Click to collapse
my device boots up and stays at grey kindle screen
nothing happens after
That doesn't tell us anything.
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Bruder Torgen said:
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Click to expand...
Click to collapse
If you're not booting into TWRP, then it probably didn't install.
Try using Flashify.
Great, I had to sideload Flashify apk and install it via adb install, then it worked , I could see the difference
Till now all seems great although the way to reach it is not described perfectly (as I normally have only to do with windows systems, too many steps I had to find out by myself and I never knew if the tablet will be still alive after the next step )
Pretty Good Work , thanks a lot for all your effort !!!!
Factory Reset?
droiduzr2 said:
my device boots up and stays at grey kindle screen
nothing happens after
Click to expand...
Click to collapse
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
droiduzr2 said:
I can get into that weird looking recovery that does not allow fastboot.
Click to expand...
Click to collapse
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
draxie said:
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
Click to expand...
Click to collapse
Thank you for the detailed response.
Yes, I did install safestrap. I admit I did not fully understand what I was doing. I thought I would just wipe everything to have a clean system as we usually do for most devices. I wiped the system also which deleted the system rom.
Upon reboot it just sits at the grey kindle screen never booting past. I played around with the buttons and stumbled upon the power and vol+.
I got into Kindle system recovery and did the wipes but nothing boots up because I deleted the system os.
Would ADB work from the Kindle recovery screen?
Remember I have no OS on the device now.
Please let me know what to do now?
Where are the Kindle drivers for Win7 which has ADB driver for it. The problem is windows will not recognize the device I don't think.
14.3.2.4 can have twrp?
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
vandy_andy said:
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
Click to expand...
Click to collapse
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
EncryptedCurse said:
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
Click to expand...
Click to collapse
Thank you for the answer.
So , so far no easy way.
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
jimyv said:
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
Click to expand...
Click to collapse
Well, if you have adb access and root, you can try this
jeryll said:
Well, if you have adb access and root, you can try this
Click to expand...
Click to collapse
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
jimyv said:
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
Click to expand...
Click to collapse
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
jeryll said:
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
Click to expand...
Click to collapse
Apollo first release of TWRP started at (.0) flashed renamed files each increment up to and including( .2.4 )I know I can redo the downgrade and anything else I need to do once I get a usable ui
not unless the recovery is black screen also. What is strange is when it is booted and I tried adb shell I did get su prompt ,,, just no launcher or notification bar etc..this is what I'm thinking let me know if I am mistaken. I should grab and flash a stock recovery image via the same as flashing this recovery with PC. Push. 3.2 build prop file to system then try this. http://forum.xda-developers.com/show....php?t=2793253 with .2.4 WiFi was off before black screen and OTA had been re- enabled I believe.and this is probably important to I do actually have a lock screen. And poweroff menu I am going to try that command now..
access denied going to reboot everything and try again
this is double posted in main thread with @ggow
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Bruder Torgen said:
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Click to expand...
Click to collapse
It's as simple as flashing the new image.
This is no different than any other device.
I thought the root for 4.5.2 and there's no root for 4.5.3 this is why I didn't update and disabled OTA. How can this method is for 4.5.3 only and it requires root? I think I miss something here. Please, help me to get it
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!
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.
After doing a decent amount of research I have not been able to find information concerning my situation.
About six months ago I rooted and installed the Kindle hdx Nexus rom with no problems. Then suddenly while playing Minecraft pe the device shuts off. I restart and it goes to the nexus boot with the four dots exchanging genetic material(lol) It got stuck at this point whenever I tried to restart. I hadn't changed and settings or software it just crashed
I am able to boot into safestrap recovery so I tried to reinstall stall the Thor rom since I still had the file on the Kindle. Theni got the boot loop from the colored dots stage and sometimes the boot would go to "initializing apps 1 of 50) or somthing like that and then it would loop.
I tried to restore to whatever previous back up and version I had and one of them must have been from the stock rom bc the loading "kindle logo" was the stock yellow and white... all I got was a loop so I reinstalled the Thor rom...
I probably should not have but at this point I tried to remove some apps via the safe strap file manager bc i know in my experience with phones certain apps can cause problems and my device was too full to preform backup via recovery
And in my last desperate attempt to not loose some of the things not backed up on the Kindle I connected to my computer to find out my computer can't recognize the device at this point...
I checked the plugins I checked the versions for compatability
I tried to use safestrap side load and came up with command not recognized for internal or external device (somthing like that)
Are there any other options for me? Does this mean it's a hard brick and what could have went wrong?
I think my mistake originally was I didn't create a separate rom slot before flashing(I don't think that bit of information was in the write up I followed)
Side note: for the record I did try to connect to my computer earlier than I stated with the device not being recognized while off or from ss recovery to try save some files
Zavxda said:
After doing a decent amount of research I have not been able to find information concerning my situation.
About six months ago I rooted and installed the Kindle hdx Nexus rom with no problems. Then suddenly while playing Minecraft pe the device shuts off. I restart and it goes to the nexus boot with the four dots exchanging genetic material(lol) It got stuck at this point whenever I tried to restart. I hadn't changed and settings or software it just crashed
I am able to boot into safestrap recovery so I tried to reinstall stall the Thor rom since I still had the file on the Kindle. Theni got the boot loop from the colored dots stage and sometimes the boot would go to "initializing apps 1 of 50) or somthing like that and then it would loop.
I tried to restore to whatever previous back up and version I had and one of them must have been from the stock rom bc the loading "kindle logo" was the stock yellow and white... all I got was a loop so I reinstalled the Thor rom...
I probably should not have but at this point I tried to remove some apps via the safe strap file manager bc i know in my experience with phones certain apps can cause problems and my device was too full to preform backup via recovery
And in my last desperate attempt to not loose some of the things not backed up on the Kindle I connected to my computer to find out my computer can't recognize the device at this point...
I checked the plugins I checked the versions for compatability
I tried to use safestrap side load and came up with command not recognized for internal or external device (somthing like that)
Are there any other options for me? Does this mean it's a hard brick and what could have went wrong?
I think my mistake originally was I didn't create a separate rom slot before flashing(I don't think that bit of information was in the write up I followed)
Side note: for the record I did try to connect to my computer earlier than I stated with the device not being recognized while off or from ss recovery to try save some files
Click to expand...
Click to collapse
No, creating a separate rom slot is not problem/solution (explicitly not recommended). What symptoms is your device exhibiting now? Which version of Safestrap?
Davey126 said:
No, creating a separate rom slot is not problem/solution (explicitly not recommended). What symptoms is your device exhibiting now? Which version of Safestrap?
Click to expand...
Click to collapse
Ok thanks good to know.:highfive: I thought I read somewhere some people do that.
Ss 4.01 (TWRP v2.7.1.0)
Basically the same as before, bootloop at the four loading dots not recognized by the computer
Zavxda said:
Ok thanks good to know.:highfive: I thought I read somewhere some people do that.
Ss 4.01 (TWRP v2.7.1.0)
Basically the same as before, bootloop at the four loading dots not recognized by the computer
Click to expand...
Click to collapse
Safestrap v4 has no native ability to communicate with the outside world. Not recognized via tether is expected with a non functioning rom. Suggest the following:
- perform a 'factory reset' from the Wipe menu (slider at bottom)
- reinstall Nexus rom using zip resident on the device
If symptoms persist it suggests corruption in the system partition which can not be wiped in Safestrap (option exists but is ignored behind then scenes as it would also destroy Safestrap recovery). Not much you can do about that short of replacing boards.
Note: There is an untested option that *may* work with a secondary slot. Try the above first and report back results.
Where would the nexus rom be located?
Davey126 said:
Safestrap v4 has no native ability to communicate with the outside world. Not recognized via tether is expected with a non functioning rom. Suggest the following:
- perform a 'factory reset' from the Wipe menu (slider at bottom)
- reinstall Nexus rom using zip resident on the device
If symptoms persist it suggests corruption in the system partition which can not be wiped in Safestrap (option exists but is ignored behind then scenes as it would also destroy Safestrap recovery). Not much you can do about that short of replacing boards.
Note: There is an untested option that *may* work with a secondary slot. Try the above first and report back results.
Click to expand...
Click to collapse
Well anyway doing factory reset and reinstalling the rom zip was not working... now when I go to restore or install option no rom file comes up
Zavxda said:
Well anyway doing factory reset and reinstalling the rom zip was not working... now when I go to restore or install option no rom file comes up
Click to expand...
Click to collapse
A zip file doesn't just disappear unless the file system is damaged. Look around with the Safestrap file manager. Without a rom zip on board your options are very limited.
Davey126 said:
A zip file doesn't just disappear unless the file system is damaged. Look around with the Safestrap file manager. Without a rom zip on board your options are very limited.
Click to expand...
Click to collapse
Yeah seems like it's missing... i think it went away after one of the factory resets I did...
I have this exact same issue - I can boot into Recovery, but I have no way of getting a ZIP onto the device to flash a ROM? Is there a way?
skoop99 said:
I have this exact same issue - I can boot into Recovery, but I have no way of getting a ZIP onto the device to flash a ROM? Is there a way?
Click to expand...
Click to collapse
Nope - no file transfer capability without a functioning ROM or custom recovery (requires an unlocked bootloader)
Zavxda said:
Yeah seems like it's missing... i think it went away after one of the factory resets I did...
Click to expand...
Click to collapse
Davey126 said:
Nope - no file transfer capability without a functioning ROM or custom recovery (requires an unlocked bootloader)
Click to expand...
Click to collapse
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
skoop99 said:
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
Click to expand...
Click to collapse
Update - I have now successfully pushed another ROM to the device, using:
ADB push <path to rom zip> /sdcard
Flashed said ROM, booted OK. Then re-installed the device in Windows as a "normal" Kindle portable device again, to enable drag & drop file transfers. Dropped Gapps zip on it, rebooted into Recovery, flashed Gapps. All good again!
So, Safestrap 4.xx DOES allow ADB connectivity to a device. As long as you can still boot into Recovery.
skoop99 said:
Update - I have now successfully pushed another ROM to the device, using:
ADB push <path to rom zip> /sdcard
Flashed said ROM, booted OK. Then re-installed the device in Windows as a "normal" Kindle portable device again, to enable drag & drop file transfers. Dropped Gapps zip on it, rebooted into Recovery, flashed Gapps. All good again!
So, Safestrap 4.xx DOES allow ADB connectivity to a device. As long as you can still boot into Recovery.
Click to expand...
Click to collapse
Whoa!! This is new and potentially great news for those with 'bricked' devices with a bootable Safestrap v4 recovery installed. I believe this was attempted in the past w/o success. Something changed or earlier tests were flawed.
Although it may not matter can you answer a few questions:
- Apollo or Thor?
- which rom was installed in the STOCK slot when the inadvertent wipe took place?
- what was the base version of FireOS (4.5.2 or 4.5.5.1) when Safestrap v4 recovery was first installed?
- ROM currently installed (the one that booted after adb push)?
- anything else unusual about the device or its history?
Again, this is a nice find a casts a shadow over previous statements, many made by me, that there was no resolution to this dilemma.
skoop99 said:
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
Click to expand...
Click to collapse
Davey126 said:
Whoa!! This is new and potentially great news for those with 'bricked' devices with a bootable Safestrap v4 recovery installed. I believe this was attempted in the past w/o success. Something changed or earlier tests were flawed.
Although it may not matter can you answer a few questions:
- Apollo or Thor?
- which rom was installed in the STOCK slot when the inadvertent wipe took place?
- what was the base version of FireOS (4.5.2 or 4.5.5.1) when Safestrap v4 recovery was first installed?
- ROM currently installed (the one that booted after adb push)?
- anything else unusual about the device or its history?
Again, this is a nice find a casts a shadow over previous statements, many made by me, that there was no resolution to this dilemma.
Click to expand...
Click to collapse
- Thor
- Nexus: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
- 4.5.2
- CM11: http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Nope.
Bootloader is also still locked.
I only figured this out when I noticed that device manager DID detect the device, but couldn't find a driver. So I installed the ADB driver, and hey presto: ADB DEVICES sees it.
C:\Users\KoopS\Dropbox\Downloads\android-sdk-windows\platform-tools>adb devices
List of devices attached
D070A0A0348300GD recovery
Hope it helps someone else. Again, though - you need to be able to boot into Recovery...
skoop99 said:
- Thor
- Nexus: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
- 4.5.2
- CM11: http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Nope.
Bootloader is also still locked.
I only figured this out when I noticed that device manager DID detect the device, but couldn't find a driver. So I installed the ADB driver, and hey presto: ADB DEVICES sees it.
C:\Users\KoopS\Dropbox\Downloads\android-sdk-windows\platform-tools>adb devices
List of devices attached
D070A0A0348300GD recovery
Hope it helps someone else. Again, though - you need to be able to boot into Recovery...
Click to expand...
Click to collapse
Freaking amazing! Such an obvious and simple solution that has gone undetected for years. There are some tentative caveats (device type, older ROMs) but not sure any of it matters for basic adb access. Time will tell as others stumble into this situation.
For clarity, which recovery are you referencing? Stock or Safestrap? If the former adb access may offer a small measure of hope for those with other types of soft 'bricks'.
I unlocked the bootloader and flashed TWRP on all my HDX devices long ago and haven't loaded Safestrap for testing in months. Just continued to reference previous (mis)understandings around recovery capabilities which was generally bad news. I will likely create a new thread referencing you findings for those who may have shelved their romless but still functioning devices.
Thanks again for sharing. @skoop99 is the man of the day!
See pic. This is my KFHDX...
Wow this is fantastic news! has anyone else here had a chance to try this? I can't remember if the PC responded at all when I plugged in the Kindle
What was the first ROM you tried that didn't work?
Is there a reason you didn't flash the Nexus ROM again?
Zavxda said:
Wow this is fantastic news! has anyone else here had a chance to try this? I can't remember if the PC responded at all when I plugged in the Kindle
Click to expand...
Click to collapse
I'll try this soon. I have a Kindle HDX 7 (that I retrieved from the bin after reading this) that will boot to safe strap, but has no rom, and no zip file of a rom to install.
I'm guessing I need to download and use ADB devices?
Does this work with windows 10?
HDX is too nice to throw away, I hope this works....
Nagoyablue73 said:
I'll try this soon. I have a Kindle HDX 7 (that I retrieved from the bin after reading this) that will boot to safe strap, but has no rom, and no zip file of a rom to install.
I'm guessing I need to download and use ADB devices?
Does this work with windows 10?
HDX is too nice to throw away, I hope this works....
Click to expand...
Click to collapse
- works with Win 10
- you may need to install drivers (although Win 10 often gets it right)
- also consider Minimal ADB and Fastboot (here)
So, I pushed the zip of CM11 unofficial to my HDX. And installed it. I'm pushing the GAPPS now....
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
And cyanogenmod is booting up! It works! My Kindle fire HDX 7 is saved! Amazing.