i have a amazon fire 7 running amazon os 5.1.2(rooted) and tried to install xposed framework on it. when it rebooted to, what i assume complete the framework download. it just stays on the fire logo screen. would love any help as i dont want to go tinkering any more on it in case of data loss. thanks
juxt4posed said:
i have a amazon fire 7 running amazon os 5.1.2(rooted) and tried to install xposed framework on it. when it rebooted to, what i assume complete the framework download. it just stays on the fire logo screen. would love any help as i dont want to go tinkering any more on it in case of data loss. thanks
Click to expand...
Click to collapse
Did you have adb authorized ? Can you do anything via root ?
Otherwise, just boot into recovery, sideload 5.1.2, Kingroot, etc.
Rovo's xposed is not supported on fire os 5,go with the one by romracer.
Related
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
trungamox34 said:
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
Click to expand...
Click to collapse
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
jimyv said:
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
Click to expand...
Click to collapse
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
trungamox34 said:
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
Click to expand...
Click to collapse
Not to be rude but first thing's first if anybody here is going to help you you're going to have to know details and exactly what you had prior to your current state .ie answer any questions with as much detail as possible . And if it all possible find out what they did to your device . If you cannot provide any of this .I cannot provide a help . I don't know anybody that has a crystal ball I can borrow LOL
The question was had you installed xposed framework on your stock slot?
What your original firmware was?
Then you might want to add exactly what rhomb you attempted to flash?
What error did it show. Can you or can you not still get into safestrap?
First guess though I would venture to say you have a paperweight and less you can get them to warrantee it for you. Personally I would have uninstalled safe strap recovery and lock root access out before I loan my device to anybody period but that's just me
My OS was cancelled, also the stock os, idk how, there is just the safestrap, the normal kindle recovery and the fastboot. Any help on how i can back to my custom rom/normal rom??
I was trying to flash a new rom, i do a wipe and probably i wiped all. system too. And now, every time i reboot it, the safestrap say 'No OS installed! Do you want to continue?'
If i say yes, black screen
The more information you post, it`s more likely someone can help you...
futzmaster said:
The more information you post, it`s more likely someone can help you...
Click to expand...
Click to collapse
edited
Sideload via adb in safestrap an OS of your choice and install.
Actually i am not an experienced person, Just get some help from youtube and this forum & rooted my Kindle fire HDX 7 using KFHDX toolkit to install google apps. Its perfectly done and i download number of apps. Then i tried to install Kitkat (thor) on it. During all this activity i go to recovery option and press the Wipe button "Cache and Dalvik Cache". after that my Kindle fire HDX 7 boot and stuck on Kindle fire starting Grey logo. I tried to factory reset but still keep stuck on start logo. While connected to PC, only hear one connectivity beep with PC but no device shows in my computer. Tried many trouble shoot find on google and this forum but issue still there. Please assist any solution. As already mentioned that i am not an experienced person. So please assist step by step.. Thanks in advance
How did you flash the ROM? Did you already have TWRP installed?
Also, do you have adb running? Do you know what version of the kindle os you had before flashing the Rom?
I had installed android 4.2.2 (thor) before and had installed TWRP. I flashed new rom 4.0.1 through TWRP and then immediately Nexus gapps v2.1. After that tablet stuck in grey logo. Unfortunately I haven't running abd now.
tishotch said:
I had installed android 4.2.2 (thor) before and had installed TWRP. I flashed new rom 4.0.1 through TWRP and then immediately Nexus gapps v2.1. After that tablet stuck in grey logo. Unfortunately I haven't running abd now.
Click to expand...
Click to collapse
With a vocubulary that includes 'flash' and 'twrp' it would appear you are more experienced than the average Kindle owner . However, you didn't read the cautions/prerequisites for installing 4.0.1. Bootloader must be unlocked (here). Not easy/intuitive but if you get through it 4.0.1 will boot just fine.
You can reflash Nexus v2 to restore functionality while working on the bootloader unlock. Our simply restore your system from the backup you made before flashing 4.0.1. To access TWRP directly press power and vol-up from a cold start. Release the power button when the grey logo appears; vol-up can be release a few seconds later.
Caveat: I assume you are not referencing the Safestrap variant of twrp. If that's the case then you are in a whole 'nother world of hurt ...
When I press power and vol-up from a cold start, It open only stock recovery (not TWRP). After reset to factory ( second options)...the result is the same - stuck logo.
tishotch said:
When I press power and vol-up from a cold start, It open only stock recovery (not TWRP). After reset to factory ( second options)...the result is the same - stuck logo.
Click to expand...
Click to collapse
Then you had Safestrap installed which emulates twrp but provides few real protections. You likely overwrote key portions of your device when flashing Nexus v4 which is incompatible with safestrap and has other prerequisites (ie: unlocked bootloader) which you ignored. There is no known recovery. Sorry, mate.
Thanks for the explanation, despite the bad news
Whether my Amazon warranty is valid in this case ?
tishotch said:
Thanks for the explanation, despite the bad news
Whether my Amazon warranty is valid in this case ?
Click to expand...
Click to collapse
Amazon is pretty good about providing replacements/refurbs during the warranty period which is typically 1 year from the date of purchase. I would not mention safestrap, twrp, nexus, rooting or any other 'key word' that suggest you were using your device in a manner other than Amazon intended. If honored the replacement will likely be more difficult to root and probably will not permit the installation of Safestrap v3 without some risky gymnastics. Safestrap v4 is in development but not yet ready for prime time (no pun intended).
Good luck.
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!
I need to know if any progress has been made on rooting a 2014 Kindle Fire HD 7 on Fire OS 5.3.1.1. I would prefer if I didn't need to use ADB as I don't have a computer to run it with. Thanks!
OrphanedPixel said:
I need to know if any progress has been made on rooting a 2014 Kindle Fire HD 7 on Fire OS 5.3.1.1. I would prefer if I didn't need to use ADB as I don't have a computer to run it with. Thanks!
Click to expand...
Click to collapse
Just wanted to second this request. I was able to find a used 2014 Kindle Fire HD 7 for a REALLY great price. Unfortunately, it was already upgraded to Fire OS 5.3.1.1 and factory reset. I would love to be able to root it, but there are no instructions on how to proceed with this firmware version.
I'm willing to use Windows, Linux, or files on the Kindle itself. I'm familiar with general rooting, mostly with the Samsung line of devices.
Any help would be greatly appreciated. :highfive:
Sincerely,
Wookie
You'll need to use ADB, and downgrade to 4.5.3 before rooting, but you can flash back to 5.3.1.1 afterwards and still be rooted - this is the tutorial to follow: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 (you can get the 5.3.1.1 firmware from https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=201596850)