Related
So I just soft-bricked my Kindle Fire HDX 7. It does not boot any more but I still have ADB access.
I just tried to follow the steps as described here: http://forum.xda-developers.com/showpost.php?p=60307966&postcount=187
I successfully updated to 3.2.5 and now was about to downgrade to 3.1.0 when I used the .bat from this thread to apply the downgrade: http://forum.xda-developers.com/showpost.php?p=53382929&postcount=1
Even though I tried it several times, I could not downgrade because it said the requested version is lower than the one currently installed.
So le stupid me went on and found out which files the bat was generating/pushing on my HDX, and then manually replaced the /system/build.prop with the one generated by the batch.
I'm not doing this for the first time, so I made a backup of the old build.prop naming it build.prop.backup [afaik].
I then shut down the kindle (to go for a reboot) but apparently it doesn't work and the screen stays black.
Still, it seems like a pretty stupid move afterwards because otherwise it wouldn't cause a brick, right^^ Anyways, I unfortunately have no recovery installed atm.
I rooted the 3.2.5 with towelroot before btw...
However, if I try to copy/replace the build.prop backup it just can't find that file. I tried rebooting/pressing the power button but it doesn't help either.
Can anyone please help me to repair it -.-?
Edit: Turns out that I was accessing my blueStacks emulator with adb, which, even though it wasn't running at the time, caused the commands to not work.
The bluestacks service in windows was responsible for it. Charging the kindle atm and hope to be able to get adb :S
FINAL EDIT: So I messaged amazon Support, told them that it was bricked during an update and got a new kindle without any problems. Didn't mention the downgrade obviously^^
I followed this tutorial and was able to upgrade, downgrade, install TWRP and unlock my bootloader successfully: http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82
For everyone: Just keep in mind that if you are running BlueStacks on your computer you will need to stop all bluestack services in order to make the tools work properly and not end up with a bricked device!
Otherwise some adb commands will fail because it doesn't know which device to use.
Tersus said:
So I just soft-bricked my Kindle Fire HDX 7. It does not boot any more but I still have ADB access.
I just tried to follow the steps as described here: http://forum.xda-developers.com/showpost.php?p=60307966&postcount=187
I successfully updated to 3.2.5 and now was about to downgrade to 3.1.0 when I used the .bat from this thread to apply the downgrade: http://forum.xda-developers.com/showpost.php?p=53382929&postcount=1
Even though I tried it several times, I could not downgrade because it said the requested version is lower than the one currently installed.
So le stupid me went on and found out which files the bat was generating/pushing on my HDX, and then manually replaced the /system/build.prop with the one generated by the batch.
I'm not doing this for the first time, so I made a backup of the old build.prop naming it build.prop.backup [afaik].
I then shut down the kindle (to go for a reboot) but apparently it doesn't work and the screen stays black.
Still, it seems like a pretty stupid move afterwards because otherwise it wouldn't cause a brick, right^^ Anyways, I unfortunately have no recovery installed atm.
I rooted the 3.2.5 with towelroot before btw...
However, if I try to copy/replace the build.prop backup it just can't find that file. I tried rebooting/pressing the power button but it doesn't help either.
Can anyone please help me to repair it -.-?
Edit: I might bricked it completely, because I can not gain w permissions on /system *__*
Click to expand...
Click to collapse
** NEVER MESS WITH BUILD.PROP **
(unless you are an expert and have robust recovery options)
Well, you had the right idea as the modified build.prop never made it to your Kindle which is why you were getting the version mismatch message. It saw 13.1.x was lower than 13.2.5 and bailed. The modified build.prop tricks your Kindle into thinking it is at 13.0.0 so processes the 13.1.x .bin as an upgrade.
None of that really matters as I'm guessing permissions are messed on one or more files that were copied to your device. Options are few if you can not gain write access (obviously bootloader remains locked). You can try a system restore from stock recovery (if working) which can be accessed by pressing the power and volume-up buttons simultaneously from a cold start. I don't hold out much hope that will fix your problem. Fastboot cables are ineffective.
There are several unbrick threads you may want to explore. I have no direct experience with a device in that condition so can't offer much guidance. Perhaps someone will jump in with a better answer ...
I just noticed that if I press power for about 20 secs I get the first boot screen.
But it never reaches the one with the golden kf logo...
I can get to the stock recovery, but a factory reset doesn't change it either.
Any way to get into fastboot from ADB?
Tersus said:
I just noticed that if I press power for about 20 secs I get the first boot screen.
But it never reaches the one with the golden kf logo...
I can get to the stock recovery, but a factory reset doesn't change it either.
Any way to get into fastboot from ADB?
Click to expand...
Click to collapse
After you shutdown your kindle, you can get into fastboot mode by holding "volume -" button while pressing shortly power button (2-3 sec) ... Unfortunately that will not help you, because fastboot mode on HDX tablets is only usable with unlocked bootloader...
I am watching several unbrick threads here over time, some people claims they do not need root for restoring system, some failed because of no root, hard to tell, what will work in your case, but from what you are describing, seems to me, that you are very close to permanent brick, sorry...
But I strongly suggest you, that you at least try this unbrick method or this one, maybe luck will be on your side...
if you somehow lost root access, try this: http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Turns out that it was accessing my blueStacks emulator with adb, which, even though it wasn't running at the time, caused the commands to not work.
The bluestacks service in windows was responsible for it. Charging the kindle atm and hope to be able to get adb :S
I will try to get root and restore the build.prop backup, fix permissions and it should reboot... still need adb for it-.-
So I messaged amazon Support, told them that it was bricked during an update and got a new kindle without any problems. Didn't mention the downgrade obviously^^
I followed this tutorial and was able to upgrade, downgrade, install TWRP and unlock my bootloader successfully: http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82
Big thanks to anyone who helped me! You can close this thread...
I am in a bootloop that takes me to the "choose language" over and over. I have adb access but am having trouble figuring out which file to download and the commands to get a good file on my HDX 8.9.
I've done a bunch of searching but nothing seems to match what I need. Any help or links would be greatly appreciated!
Thanks
This is an easy one, but don't feel bad. It vexed me too. It is because it wants a to connect to the server and verify your account and device (in doing so, it will also try to push an update).
The solution is to click the orange "complete registration later" (or something like that) text which shows up centered on the bottom.
I'm rooted and connected to wifi already..I'm downloading update kindle 14.5.2 but I'm guessing that I'll lose root.Tthe screen blinks on the desktop of the kindle then goes back to the language...like it doesnt know what to do next.
I also see an update file thats rooted but it doesn't appear to be the right one for me...
So many instructions and downloads that it gets confusing.
Also, thanks leko for the great help with adb!!!
Oh_wow said:
I'm rooted and connected to wifi already..I'm downloading update kindle 14.5.2 but I'm guessing that I'll lose root.Tthe screen blinks on the desktop of the kindle then goes back to the language...like it doesnt know what to do next.
I also see an update file thats rooted but it doesn't appear to be the right one for me...
So many instructions and downloads that it gets confusing.
Also, thanks leko for the great help with adb!!!
Click to expand...
Click to collapse
You can root 4.5.2. If the update fixes the issue then just root and you'll be good. Once your rooted, find instructions to disable OTA here so you don't automatically update to 4.5.4, like what happened to me.
-Zman8881
Is there a rooted download I should use instead? I'm still not positive that I'm doing the right thing which is why I asked for help. And I'll definitely block those ota's..thanks for that tip
Oh_wow said:
Is there a rooted download I should use instead? I'm still not positive that I'm doing the right thing which is why I asked for help. And I'll definitely block those ota's..thanks for that tip
Click to expand...
Click to collapse
There is no pre-rooted 4.5.2; you have to root if needed. Whether you retain root from an earlier install depends on where you came from and the method used to upgrade.
The looping problem you describe has happened to others. You'll need to poke around to find the solution. Hopefully someone will pop in with a direct link or more specific instructions. Point is it's solvable. Don't do anything radical while searching/waiting for resolution.
Sent from my Kindle Fire HDX 7 using XDA Forums Pro.
I've already learned the hard way that jumping in without knowledge is painful (R.I.P my 1st kindle). This device is twitchy but the searching I've done so far has be a great learning experience! And that's the thing, I really want to learn how to do this stuff...unfortunately I may not explain the problem correctly and am terrified of getting shot down by more knowledgeable folks. I've survived modifying the Droid x, note 2 and note 3 so I know I can do this...eventually☺
Oh_wow said:
I've already learned the hard way that jumping in without knowledge is painful (R.I.P my 1st kindle). This device is twitchy but the searching I've done so far has be a great learning experience! And that's the thing, I really want to learn how to do this stuff...unfortunately I may not explain the problem correctly and am terrified of getting shot down by more knowledgeable folks. I've survived modifying the Droid x, note 2 and note 3 so I know I can do this...eventually☺
Click to expand...
Click to collapse
The only time you'll get shot down around here is if you do bad stuff (eg: flash incompatible components) that have been well covered in the forums. People are willing to help if you ask questions before getting into trouble. Kindles (at least HDX models) are tough to tame and easy to ruin.
Are you having difficulties now? You reported a soft bootloop (stuck on language screen) in a earlier post. Has that been resolved?
Davey126 said:
The only time you'll get shot down around here is if you do bad stuff (eg: flash incompatible components) that have been well covered in the forums. People are willing to help if you ask questions before getting into trouble. Kindles (at least HDX models) are tough to tame and easy to ruin.
Are you having difficulties now? You reported a soft bootloop (stuck on language screen) in a earlier post. Has that been resolved?
Click to expand...
Click to collapse
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (if I'm quick, I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Oh_wow said:
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (f I'm quick it there that I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Click to expand...
Click to collapse
This is a really random thought and I'm not sure if it will work, but when you get into the desktop try to power off and power back on. You need to be quick, but it might work.
Random is good...but it didn't work in this case.
Thanks
Oh_wow said:
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (if I'm quick, I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Click to expand...
Click to collapse
Sorry for the delay in responding; was out with family.
Like many others I am the beneficiary of the experiences, suggestions and knowledge generously shared by others. It's the collective community you need to thank
Have you looked at this thread? Post #2 seems to offer a solution. Others noted the need to disable (or more correctly not enable) wifi during initial setup which suggest a factory reset may be part of the solution. Another thread indicated the 'language looping' problem was related to corruption in the default launcher. Installing another (eg: Nova) via ADB restored some control and ability to further diagnose from within FireOS. However, this was for the prior version of FireOS (3.x "Otter") and may not be applicable to Fire OS 4 ("Sangria").
Davey126 said:
Sorry for the delay in responding; was out with family.
Like many others I am the beneficiary of the experiences, suggestions and knowledge generously shared by others. It's the collective community you need to thank
Have you looked at this thread? Post #2 seems to offer a solution. Others noted the need to disable (or more correctly not enable) wifi during initial setup which suggest a factory reset may be part of the solution. Another thread indicated the 'language looping' problem was related to corruption in the default launcher. Installing another (eg: Nova) via ADB restored some control and ability to further diagnose from within FireOS. However, this was for the prior version of FireOS (3.x "Otter") and may not be applicable to Fire OS 4 ("Sangria").
Click to expand...
Click to collapse
There's a chance it's me being stupid, but don't you need root access to do that solution? If not, do you think this kind of idea could work to get around the earlier version error or even disabling OTA without root access?
Zman8881 said:
There's a chance it's me being stupid, but don't you need root access to do that solution? If not, do you think this kind of idea could work to get around the earlier version error or even disabling OTA without root access?
Click to expand...
Click to collapse
@Oh_wow indicated in a earlier post that his device remains rooted. Otherwise most of the recovery techniques discussed in the links would not work. Sorry to dampen your hopes ...
You could try installing an alternate launcher. That should work. However making it default is annoying. If the install works and helps with the screen, I can help with setting it as default.
Download the launcher (I like Nova)on your computer. You can probably find it on apkmirror. Then, run this command.
Adb install and drag the file.
A little note. The and install command is potentially dangerous, but for some apps it is safe, and I am mostly certain a launcher counts.
Also, have you tried clicking the register later button?
lekofraggle said:
You could try installing an alternate launcher. That should work. However making it default is annoying. If the install works and helps with the screen, I can help with setting it as default.
Download the launcher (I like Nova)on your computer. You can probably find it on apkmirror. Then, run this command.
Adb install and drag the file.
A little note. The and install command is potentially dangerous, but for some apps it is safe, and I am mostly certain a launcher counts.
Also, have you tried clicking the register later button?
Click to expand...
Click to collapse
Bonanza! That solved the language question but it is annoying that Nova won't stick as default. I'd love to know how to set it! Thanks!
Now what? Gapps? Wait, safestrap or TWRP?
Nevermind---I lost root and the toolkit isn't working,,,good grief
Oh_wow said:
Bonanza! That solved the language question but it is annoying that Nova won't stick as default. I'd love to know how to set it! Thanks!
Now what? Gapps? Wait, safestrap or TWRP?
Click to expand...
Click to collapse
Getting 3rd party launchers to 'stick' has been a issue on newer releases of FireOS. However, regaining some control over your device does offer the opportunity to fix the problem with Amazon's launcher if it can be identified (eg: missing/renamed file) or rolling back to 3.2.8 and followed by an upgrade to 4.5.2 (there is risk in doing this; make sure you understand the procedure before diving in).
Native TWRP is not an option on 4.5.2. Nor would it help.
You could install Safestrap v4 followed by a patched version of 4.5.2 which should fix the launcher problem. You could continue running FireOS under Safestrap or remove it; the version installed under Safestrap would remain as the default OS. If you keep Safestrap you also have the option of running Nexus v4 or CM11 which offer a more native Android experience and full access to the Google Play store, services and apps.
You should still have nova though. So, you can download cve
Here
, and then have unfettered (well mostly) access.
As far as your other question.
You can run these commands from adb or the app command runner (if you can find it, they took it out of the play store).
There are two ways...
#1 If you do not want to use the stock launcher at all, run this command...
Code:
pm block com.amazon.kindle.otter
To undo, run
Code:
pm unblock com.amazon.kindle.otter
To just make it so the launcher does not work, but the other kindle pieces do (like your library), use this command.
Code:
pm disable com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher
To reverse this, run...
Code:
pm enable com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher
I do not think you even need root for these commands if you run them from adb, but I could be wrong.
Some words of caution. If your device upgrades through ota while otter is blocked (or probably disabled), you will brick your device (unless you have a working recovery/unlocked boot loader and know how to use them to completely restore your system.
If you block otter without a working alternate launcher, you may brick your device, but and could save you by reversing the command.
Good luck.
~Leko
Thank you for all those instructions!
I'll report back how it works for me...
Oh_wow said:
I am in a bootloop that takes me to the "choose language" over and over. I have adb access but am having trouble figuring out which file to download and the commands to get a good file on my HDX 8.9.
I've done a bunch of searching but nothing seems to match what I need. Any help or links would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
Did you install gapps an got
stock on setup
Hi everyone,
i have a rooted Kindle Fire HDX 7" which is kind of softbricked. Maybe even hardbricked but my knowledge doesnt reach that far to determine.
Here's the thing. I already got in touch with Amazon, they checked my Amazon Account and were pleased to send me a new Kindle since i still got warranty on it.
Okay so far so good.
But here comes the real deal.
I'm pretty sure my warranty doesnt really cover the whole root -> brick story.
I told the Lady that after a factory reset the Tablet keeps trying to start the Setup over and over again. Which is indeed the case. I did not mention anything else.
So. My plan was, since i'm still able to go into safestrap recovery, to delete everything that could point out that the Tablet was rooted. Atleast on the first view.
TL.DR:
Is it possible to delete Safestrap/TWRP via the Terminal Command?
I know you can browse through the Tablet, but i couldnt find where the Folders are located.
Even if the Tablet doesnt Boot at all after deletion, i wouldnt mind.
Cause then i could still keep my new Tablet and hope they cant find anything on the broken one.
Hope anyone can help me.
If it is hard to understand what i meant i can give you further informations.
It's kind a hard for me to describe such technical things in a foreign language.
If you can access safestap, you can unbrick your device mate.
Well i kind of tried everything possible.
It's not on topic but i can describe what i did, maybe it helps other to not do the same mistake.
I had my Kindle rooted on 13.3.2.4 with the HDX Toolkit.
Everything worked fine since one day the Google Store stopped working.
Well at that time i wasnt using the Tablet on a daily basis so i didnt mind much and got a little off touch with the whole rooting thing, and the do's and dont's.
Then after a couple of weeks i got a bit frustrated over the fact that the integrated Prime Video Streaming is so out of date, that you cant even watch movies USK18 or switch languages within the Movie.
So i decided to use the Kindle as it was meant to by amazon and remove everything.
I really shouldve read more about the prodecure, i know that now.
But here's what i did:
1. Wiped and Removed my non-StockROM
2. Booted on StockROM and did a Factory Reset
3. Sh#t got weird so i went into recovery and wiped the StockROM aswell
4. Now i can still go into Recovery, but when i try to Boot i kind of dont have a FIrmware installed. It trys to re-do the Setup where you have to choose ur language over and over again.
So by now i already know what i should've done instead.
But at this point; my Kindle doesnt get recognized by my PC nor by ADB.
And i dont know what i can do with the Safestrap Recovery at the beginning.
So far, any more ideas?
Should i still try to unbrick it or just wipe my fingerprints off of it and hope i can keep the new one.
KDroidB said:
Well i kind of tried everything possible.
It's not on topic but i can describe what i did, maybe it helps other to not do the same mistake.
I had my Kindle rooted on 13.3.2.4 with the HDX Toolkit.
Everything worked fine since one day the Google Store stopped working.
Well at that time i wasnt using the Tablet on a daily basis so i didnt mind much and got a little off touch with the whole rooting thing, and the do's and dont's.
Then after a couple of weeks i got a bit frustrated over the fact that the integrated Prime Video Streaming is so out of date, that you cant even watch movies USK18 or switch languages within the Movie.
So i decided to use the Kindle as it was meant to by amazon and remove everything.
I really shouldve read more about the prodecure, i know that now.
But here's what i did:
1. Wiped and Removed my non-StockROM
2. Booted on StockROM and did a Factory Reset
3. Sh#t got weird so i went into recovery and wiped the StockROM aswell
4. Now i can still go into Recovery, but when i try to Boot i kind of dont have a FIrmware installed. It trys to re-do the Setup where you have to choose ur language over and over again.
So by now i already know what i should've done instead.
But at this point; my Kindle doesnt get recognized by my PC nor by ADB.
And i dont know what i can do with the Safestrap Recovery at the beginning.
So far, any more ideas?
Should i still try to unbrick it or just wipe my fingerprints off of it and hope i can keep the new one.
Click to expand...
Click to collapse
So you can open safestap ? If you can, then try ADB on a Linux/Mac machine. It will work. Windows has a problem with the drivers. Also I am not sure about this, but if you access the stock kindle recovery and do a factory reset from there, you might wipe safestap.
Hey guys I desperately need help here. I got this Kindle Fire 8.9" years ago, and got abandoned by my Dad because we live in SEA, can't do much with it, I cannot even get the free apps through Amazon Appstore. I can use fake US CC in this matter to get the free apps but Is that even legit? I have real CC and a legit Amazon account I bought real stuffs from Amazon too back then (books, some shirts and some gadgets) but that doesn't seem to help much.
Anyway sideloading apps from Google Play don't help much since the compatibility are horrible, and sideloading the Google Playstore itself just don't work. I've attempted to install all the Playstore requirements, some installed and some spit out "Parse error - There was a problem parsing the package".
I figure I needed to convert it to a full Android. So searching around I found about "fastboot" but I'm not familiar with it. I only got my hands dirty on Odin and SP Flash Tool.
I followed the instruction here :
http://forum.xda-developers.com/kin...t-install-twrp-android-fire-os-8-5-1-t3278286
Works very well, rooted with KingRoot (which I already have offline), installed FireFlash, flashed the bootloader and recovery (100% like the instruction told me), got into TWRP, did a full backup of the current ROM and reboot. I can get it to the Carousel just fine. I attempted to flash Gapps package for ICS (gapps-ics-20120429-signed.zip) from here (found from googling around, checked the content too) :
https://docs.google.com/file/d/0B6zwjGaKK0GVUll5Sm95LWpNaDg/edit
The installation went quite well, after running Play Store, it crashes constantly. Found another tutorial on installing Google Apps on another forum, which I lost the link, so I want to attempt another Google Play install before went to CyanogenMod.
I noticed something, after each reboot, I need to re-flash TWRP and reboot. When I attempt to reflash TWRP I notice that kfhd8freedom-boot-8.4.6.img didn't have any warning anymore.
The tablet was a gift from my brother in law to my Dad. It was never been reset ever since. In fact after I installed Google Play, it still got my brother in law login in it, even though it doesn't have the Google Play store. So I figure I need to do a factory reset and start 100% fresh, just to be sure.
And this is where it went wrong. After the factory reset the device rebooted into fastboot mode. I don't know why. I see the orange Kindle Fire logo, then the screen went red then "fast boot mode" appear on screen. At this point I cannot do anything to it. Followed every power button tutorials out there, like pressing the power for 20 seconds then release then hold it for 2 seconds, or power plus volume up/volume down, no luck.
I plugged it into my PC, it shows as "Android", and below it "Android ADB". So I tried to use ADB console for it, it didn't respond. However it responds to "fastboot" commands, tried some commands from here :
http://forum.xda-developers.com/showthread.php?t=1474566&page=2
These commands works :
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
But it went straight back to fastboot mode. My guess is that the culprit is kfhd8freedom-boot-8.4.6.img.
Looking around in the forum there're so many obsolete solutions, like Kindle Fire HD First Aide download link are dead and it was intended for Fire 7.
So the questions are :
How would you recommend me to fix this? Fastboot command definitely still working from PC to my Kindle, if that is any help for this case. I really have no clue on what to do next. I only experienced with Odin and SP Flash Tool. I have no experience with fastboot.
I don't have any stock rom at hands, neither can find any googling around. Can anyone provide me with one? Just in case anything bad happen again after I fix this.
Will this work for 8.9"? Since he posted it in Fire 7 forum : http://forum.xda-developers.com/showthread.php?t=1951254
Info on my devices :
Kindle Fire Jem 8.9"
Latest stock (8.5.1_user_5159720) was installed
Rooted with KingRoot before went brick
I have no fastboot cable, but the fastboot command mentioned earlier works on regular USB (OnePlus One's stock cable)
Gapps for ICS was installed within too
I got both Windows 10 and Windows XP PCs at my hand. XP seems to recognize it better as ADB something under "android" in device manager.
I also got Ubuntu 16.04 installation, if needed.
Please help.
Thank you in advance!
Managed to boot into Fire OS
I just use fastboot to flash both kfhd8-twrp-2.8.7.0-recovery.img and kfhd8-u-boot-prod-8.1.4.bin.
After a reboot I went into TWRP, it does a few stuffs then rebooted again automatically.
Blue logo came up, then the orange logo, but it took longer than usual, I was a bit panicking. Forgot that on each first boot Android would take longer than usual.
But then kindle fire up the first time setup *phew*
First I want to get Gapps working on this device. If that working well, I'll stick with stock + GAPPS and custom launcher.
Only after that I will try CM12 on it.
I'll update on this thread later on how it goes.
Did anyone still have the stock recovery.img and boot.img?
Also after completing the initial setup my navigation and status bar went missing
The navigation bar blinks for a second then went black. While the status bar which displays wifi icons and hide the settings are missing. I cannot swipe from above at all.
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Finally SOLVED.
I forgot I can download ES file explorer from Silk. But turn out my Amazon appstore account allowed me to download it instead. Probably because my dad and brother's credentials was wiped clean from it.
I went to find flashfire.apk in my internal storage. Install it, then the unknown source popup warning appeared. Luckily it got the settings button which lead me to that particular option. After I tick it, I need to shut my kindle down, reboot then went to install it again, because there's no navigation bar available.
After it installed, turn out Kingroot's root are still intact. Kingroot's root permission pop up appeared.
Reflashed TWRP and Freedom boot. Shut my Kindle down, volume up + power and I'm in TWRP!!!
I decide I'll just go full CM this time. So, continued this :
http://forum.xda-developers.com/kind...8-5-1-t3278286
Now I'm currently updating the default Google apps from Google Play within CM 12. A little laggy but most definitely far better than FireOS.
I'll be using this Kindle for a week, I'll report here and hopefully can contribute to CM's bug report.
So far : camera, bluetooth, WIFI, GPS works out of the box. Brightness settings don't work.
Just one question, does this fastboot cable thingy "standard"? I saw one seller in my local online shop but it's for Xiaomi. Can I use it for OnePlus One and Kindle?
Oh yeah I got TWRP backup of the stock kindle, but I would still need both stock boot and recovery image. If someone kindly enough to provide me I'll be very thankful.
Checking in
Root are enabled by default, just found out about this. It got build in, barebone SU management, on which you can allow an app to have root access or not, but didn't see any comprehensive root access management like those found in SuperSU.
So installed SuperSU, told SuperSU to just update through TWRP, update binary was a breeze, all done automatically.
Watching YouTube on it was quite convenient. The screen obviously have near-retina display. Much better than viewing it on my Note 10.1 2012 obviously.
No problem browsing on Chrome.
Installed couple of other root apps, transfered it from my cheap chinese phone (Mito) using Bluetooth. All works well.
Tried to play Shooty Skies on it but it stuck on the intro screen. However on my OPO Shooty Skies refuses to run too and stuck on the intro screen. I've unlocked all characters on it I'll just wait for an update then.
Did some theming, custom boot animations works, styles applied, icons and everything applied without any problem at all.
One complain, the sound are too low, even when maxed out. Perhaps because the Dolby isn't supported by this CM yet?
My dad complained that there're too many updates after the initial setup so I use System Cleaner 2 to merge the updates into the system. The app did wonderful job on my Mito :
https://play.google.com/store/apps/details?id=com.flaki.systemcleaner2
Merged all updates into the system. If I don't do this everytime I wipe the device, the device will keep asking for updates. At least on the Gapps. It stuck at the middle, so I restart the System Cleaner 2 and it continue to do its job.
Then when I install Link2SD, which often do better job and more comprehensive apk management, weird things started to happen. It's said SuperSU are not installed. That and also couple of Google Apps. When I run Link2SD, their size is 0.
I think it's most likely caused by System Cleaner 2, couple of apps got interrupted when I merge the updated apk into the system?
So I reboot, then after I got into trebuchet, all the supposedly installed apps are gone. I don't know why. Thus I wipe everything clean again, reflash CM12, and just go into unrooted mode, update the gapps, remove my account and let my dad login using his and do whatever he want with this kindle.
Another minor update.
Since I've downloaded ICS (CM11), I figure I might just try it anyway. Since on whatever softwares I use I prefer older, stable version than bleeding edge and feature-rich but unstable ones.
Take a note I'm not saying CM12 is unstable, no problem so far, only those I pointed out in the previous post. But mostly because CM11 was marked "stable" on CyanogenMod download site.
First impression? It's snappier than CM12, and much more familiar than Lollipop. (since most devices I own still using JellyBean, with the exception of my OPO which already running Marshmellow).
My dad should be familiar with it too. Quite happy with it. But unfortunately the gapps are too outdated. It throws me server errors, and I cannot reach anything within Google Play. I can browse google websites without problem, even google play itself inside the default browser, so it's not connection problem definitely.
Updating the google play manually doesn't fix this. So any solution for this? Perhaps updated gapps for CM11/4.0.4?
Edit : eh nevermind, the Gapps provided for CM12 works with CM11. And very stable too.
Edit : CM11 for Kindle 8.9 is JellyBean 4.4, not ICS.
I guess I'll stick to CM11 for awhile then.
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
stubbe said:
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
Click to expand...
Click to collapse
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Hey Davey. Thanks for the response.
Davey126 said:
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Click to expand...
Click to collapse
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
stubbe said:
Hey Davey. Thanks for the response.
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
Click to expand...
Click to collapse
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
- fastboot cables do not work with this device
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Davey126 said:
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
Click to expand...
Click to collapse
Ah dang. Not that much of a problem though. I just like to keep stocks ROMs around just to be safe. I won't be returning this thing to Amazon anytime soon, and I guess judging by my brief experience with the FireOS it won't be much of a use for our locals using the stock ROM if I or my dad actually decide to sell it.
- fastboot cables do not work with this device
Click to expand...
Click to collapse
Mmm... okay.
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Click to expand...
Click to collapse
Ok fair enough and besides I don't go to the recovery much other than doing a backup.
Thanks Davey.
stubbe said:
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Click to expand...
Click to collapse
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Praxxer1 said:
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Click to expand...
Click to collapse
Answered elsewhere (one 48 other threads you posted to with the same question)
Stuck in Fastboot. I can flash and write and reboot, but 100% of the time it returns to FB. I had flashed freedom boot 8.46 2x. I most recently had lineage 14.1 and twrp 2.78.
Tried every tool in the book zero have worked.
UPDATE 6-9, out of fastboot, now stuck on kindle logo.
tia
KF 8.9hd jem
Hey all,
I've never rooted a phone before so since I have a spare model, I figured I'd give it a go.
Hearing about this forum, I checked it out and was sent to the Sony site. I understand I needed to unlock the bootloader first, which I did and can confirm I get that alert as my phone starts about it not being safe.
Hint for future readers: don't do this in a virtual environment, I had issues doing this until I used an actual computer and not a VM (mods and folks with more experience: feel free to correct me on this or shed some light). To be clear, I have a separate host running Proxmox (Type I hypervisor) and was able to forward my USB connection to test with ADB and such. I do most things in a virtual environment to not mess up my physical computer.
This was all done last week. Well today, Monday, I decided to continue with my rooting excursion, only to run into the issue I am currently facing.
After many, many Google attempts and following whatever links in this, I finally found this link. Well, I was within a VM, downloaded the linked flashing tool, and ran the first two commands:
- adb devices
- adb reboot bootloader
After doing this, my phone turned off and I wasn't sure what to expect, so I pressed the Power button to see what would happen - nothing. So then I remembered that Friday I was having issues communicating with my mobile phone in the VM to unlock the bootloader in the first place, so I figured I'd try to move it to my physical computer....then I was stuck on a reboot cycle!
To be clear, my issue is that I am stuck on a boot loop. It prompts the error of the device being unsafe, waits 5 seconds, then displays the Sony splash screen. Rinse, wash, repeat; same thing.
I have a Sony Xperia XA1 (G3123) model.
Can anyone shed some light?
Am I screwed?
Please halp!
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
tryingToSurvive said:
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
Click to expand...
Click to collapse
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
keifus.rahn said:
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Hey @keifus.rahn for following up.
I did find that thread after continued poking, which I am still checking now. And I eventually made a post on there just now discussing my current dilemma.
I downloaded the Flashtool but didn't understand how it worked, nor do I still yet. I tried debugging it and the issue is that the "java -version" call doesn't work within the directory's own structure. I do have java installed on my test Linux VM though.
Past that, I tried with the latest boot.img as well as the recovery.img that I found. I think that the build numbers are off, or maybe I am just not understanding where I am lacking.
You can look at the bottom of the last page for a breakdown of what I did:
https://forum.xda-developers.com/xa...21-built-sources-t3622886/page94#post80481385