Related
Help, (PLEASE) I just "re-rooted) my Archos 101it tablet....I missed the setup screen where you fill out all the information on who you are (the developer)...now when I power it on, it gives me the Archos logo, then developers logo (angstrom) but then goes to very itsy bitsy lettering :
The angstrom distribution archos-gen-8
Angstrom 2009.X-stable archos-gen-8 tty1
archos-gen8 log in:
It does not respond to the touch screen. I am just sick inside...I had this tablet since mid-2011 and never did anything much with it, then after a download from Amazon, I started getting this popup saying that certain things could not open...lots of people had this error message, thus the reason for googling to this forum. I thank ANYONE in advance who can help me out...any way to get back to the screen to put in my user information and log in passcodes??? Jeanie
ps...then the new op version (android for Archos) that the person who wrote the tutorial on how to re-root is no longer available. (scream) I will need to know how to download the new op if I ever find it 8-(
I also had the same problem!!: After applying sde versions and trying numerous times to re-download firmware, I finally got my aos back!!! Seems I downloaded the newest version using Chrome and it wasn't copying right, so I followed another forum's advice and used Internet Explorer...it worked!!! Now after a week, I now have a "Like New) Archos 101it. What a learning experience!!!
P.S. I don't really know if it was Chrome or IE, seems I kept downloading different versions of the aos files with the same name...thus it was renaming them
firmware_archos_android_gen8. (2)aos
firmware_archos_android_gen8. (3)aos
well, before I copied the file over to the 101it drive, I took out the (2) or (3), then it worked!!!!
Try to delete SDE, reformat device and flash it again. Use chrulri's method to root it.
(First post - must go in General forum). Hello. I think I have discovered why some of us are having problems rooting the Hisense Sero 7 Pro tablet. I have downloaded the files (abbreviated) Root.part1.rar and Root.part2.rar from the sero7 website. When I use 7zip to verifiy file integrity, I get a data error on one of the files in one of the archives. Specifically, in Root.part2.rar, the file cwm_touch_recovery.img has an error. Root.part1.rar integrity is fine, however, Root.part1.rar contains a copy of cwm_touch_recovery.img which is correct. I went to the xda thread on this subject (posted by XBOXEXPERT - [DEV/CWM/ROOT/ROM] Hisense Sero 7 Pro CWM Touch Recovery, Factory ROM & My XE-SeroROM) and downloaded the part 1 and part 2 files. In part 1 tests ok, but part 2 gets a data error on file busybox. However, in this set of files, part 2 files are duplicated (except for the usb driver folder, which is empty) in part 1, so what is the need for part 2? Anyway, I was able to recover from the busybox and cwm_touch_recovery files (since they were duplicated). So, should I put all the files in one place to do the rooting?
I want to do this properly and correctly. As an aside, here is a question: in lieu of restoring the stock image, is there a way to remove the Developer Menu from the settings once it has been invoked? Thanks, Dennis.
Problems rooting Sero 7 Pro more info...
Hello. After doing some more experimentation, I've come to the conclusion that there is something wrong with the RAR files (other than having duplicate files and empty folders). I have downloaded (again) the part1 and part2 files from both the sero7 site and the xda site. I can do a file integrity test and it comes out clean. If I run it again, I get an error, always a problem with busybox (crc or data error) or cwm_touch_recovery.img (data error). I have downloaded the files and run the file integrity test on Windows (with 7zip) and Linux (the utility that compresses - it reads zip/rar etc. and can do an integrity test). Maybe you should be using ZIP or other compression program other than rar? How about 7zip? I have cobbled together all the files, including good versions of the busybox file and the cwm_touch_recovery.img file. Hope that's ok. I still don't understand how running a file integrity test can cause a file to go bad. But it seems to be doing just that, but only with busybox and cwm_touch_recovery.img. All for now. Thank you, D.
Sero 7 Pro Root
I have 2 Sero 7 Pro tablets and both are rooted without any issues. I download both rar files and extracted them into the same folder. I did get a message saying "file already exists do you want to overwrite?". I overwrote the file and both rar files extracted into one folder without any errors.
I'm running Windows 7 x64 and had a heck of a time getting Windows to recognize the tablet. I solved this by:
1. Creating a file named adb_usb.ini in C:\Users\Use Name\.android
2. Added this code to the adb_usb.ini: 0x109b
3. Then saved the file and and ran adb devices to verify adb saw the tablet. The table should show up now.
I then ran XESeroRoot.exe and followed the onscreen instructions in the pop up window.
After the program finished. I rebooted my tablet twice and it was good to go....rooted with stock rom.
From there I copied the custom I wanted to install onto my external sd card. I booted into cwm recovery, I wiped everything and then flashed the custom Rom from my external sd card.
Works great.
---------- Post added at 05:26 PM ---------- Previous post was at 05:18 PM ----------
Also.....I was having an issue with apps crashing to the home screen, such as Adobe Photoshop Touch, and Sims Freeplay on my wife's tablet.
I discovered there was a missing font causing the crash. Check your /system/font folder and make sure DroidSans.ttf and DroidSans-Bold.ttf exist. Once I added the fonts, the apps ran just fine without error.
If install a custom ROM and install the Table UI mod and you experience app crashes. Try re-flashing the Table UI.
My wife's tablet was doing weird things and apps were crashing...turned out to be a corrupt Table UI...I re-flashed and that fixed the issue.
I followed the directions here http://forum.xda-developers.com/showthread.php?p=41875797
Also have windows7 64bit and no issues rooting mine
Sent from my SPH-L720 using Tapatalk 2
I rooted with the same files, I used Xubuntu to extract and combine the 2 rar's back to one file then copied them to Windows to root with no problems.
Sent from my M470BSA using Tapatalk 2
Hisense Sero Pro 7 will not turn on
usegnu said:
I rooted with the same files, I used Xubuntu to extract and combine the 2 rar's back to one file then copied them to Windows to root with no problems.
Sent from my M470BSA using Tapatalk 2
Click to expand...
Click to collapse
My tablet will not power on. When I connect it to the charger the screen flashes a blue lightning bolt (see picture) with what appears to be a charging cable. I left it on the charger for 24 hours, still nothing. Does anyone know what this means and how to solve it. Customer service for Hisense was no help. Told me to ship it to me. I have to pay for shipping.
Black night have you tried a different charger or cable?
rooted my hisense
i rooted my hisense sero 7 pro last week an everything went fine. i intalled a diferent font from rom toolbox an when it rebooted it stayed on the startup screen ,
richard41 said:
i rooted my hisense sero 7 pro last week an everything went fine. i intalled a diferent font from rom toolbox an when it rebooted it stayed on the startup screen ,
Click to expand...
Click to collapse
If its still getting stuck at boot (bootloop), you might try going into CWM recovery and run "fix permissions". I haven't tried messing with the fonts, but permissions world be my first guess. Fonts need to be in the /system/fonts folder with the permissions of rw-r--r--.
I posted a link below with several methods to change fonts. There is also instructions on how to change the font via adb. So if you can get to recovery you can fix it from there without having to restore a backup.
http://www.android.gs/how-to-change-fonts-on-any-android-device/
Sent from my Nexus 7 using xda app-developers app
Just use vroot app. For zero 7 Lt or pro. It'll install super user and its in Chinese. Just re download super user from Google market and delete the Chinese one after rooting.
sent from my Sero 7 using XDA Premium Tablet app
exs.advocate said:
Just use vroot app. For zero 7 Lt or pro. It'll install super user and its in Chinese. Just re download super user from Google market and delete the Chinese one after rooting.
sent from my Sero 7 using XDA Premium Tablet app
Click to expand...
Click to collapse
there are some newer root scripts in the dev thread from delorespark
Hisense sero 7 pro stuck in bootloop
richard41 said:
i rooted my hisense sero 7 pro last week an everything went fine. i intalled a diferent font from rom toolbox an when it rebooted it stayed on the startup screen ,
Click to expand...
Click to collapse
Richard41, I am having the same problem. I root my Hisense Sero 7 Pro a week ago and it worked perfectly. Then a few days ago I downloaded an app from Google play to change the font on my device. It worked just fine but a day or two later, I went in the app to change the font again, but it immediately took me to Google play where I downloaded it and on the top of the screen it said, "This app is not compatible with your device."
I don't understand why it would say that when I already had it installed. So I left that screen and went back to the font app itself. I selected the font I wanted, it asked if I'm sure I want to change the font to the selected one, I confirmed it and then another pop up screen came up in Chinese or Japanese letters. It looked like it was asking the same question but in another language. I choice what I thought would be yes in English since it was in the was in the same place and then another pop up screen came but I don't know what it said because it was in the same Chinese or Japanese letters with a mixture of a few English letters, but still couldn't comprehend the message. So I figured I just needed to reboot it. I rebooted it, and it has been stuck on the "Hisense Smart" boot introductory screen ever since.
Danaroxy said:
Richard41, I am having the same problem. I root my Hisense Sero 7 Pro a week ago and it worked perfectly. Then a few days ago I downloaded an app from Google play to change the font on my device. It worked just fine but a day or two later, I went in the app to change the font again, but it immediately took me to Google play where I downloaded it and on the top of the screen it said, "This app is not compatible with your device."
I don't understand why it would say that when I already had it installed. So I left that screen and went back to the font app itself. I selected the font I wanted, it asked if I'm sure I want to change the font to the selected one, I confirmed it and then another pop up screen came up in Chinese or Japanese letters. It looked like it was asking the same question but in another language. I choice what I thought would be yes in English since it was in the was in the same place and then another pop up screen came but I don't know what it said because it was in the same Chinese or Japanese letters with a mixture of a few English letters, but still couldn't comprehend the message. So I figured I just needed to reboot it. I rebooted it, and it has been stuck on the "Hisense Smart" boot introductory screen ever since.
Click to expand...
Click to collapse
I also rebooted my Sero 7 and ever since I am stuck. I tried to install other ROMs also including the latest 4.4 by randomblame, however it is stuck... forever.
dogood1 said:
I also rebooted my Sero 7 and ever since I am stuck. I tried to install other ROMs also including the latest 4.4 by randomblame, however it is stuck... forever.
Click to expand...
Click to collapse
I found out that you're suppose to flash the original stock ROM (unroot it) and start over from there. I never tried it. I just went out and bought a new one.
Danaroxy said:
I found out that you're suppose to flash the original stock ROM (unroot it) and start over from there. I never tried it. I just went out and bought a new one.
Click to expand...
Click to collapse
I have tried installing stock ROM (from xboxexpert's thread), and it didn't work. Anyways, I am not going to buy a new one. Will try to fix it.
Trojan in XESeroRoot.exe
There's a Trojan (Trojanware.win32.renfro dot something) in XESeroRoot.exe. Execution halted by Comodo, removed the file and a registry entry. What's up with that??? The usb driver installed just fine, but there's no ADB debugging selection on my Hisense Sero 7 Pro (and yes, I have developer status).
Found the latest install, rooting and new ROM worked like a charm, thx, dolorespark!!
Hi I just bought a new Kindle fire hdx , after root it. I am unable to access photo gallery and Kindle appStore:crying:. Would like to know , is anybody can provide 8.9" original rom of Kindle fire hdx 8.9". Thanks a lot.
Missing here as well ...
By the way, awesome work all!!!
Like the OP, I too am missing my "Photo Gallery" post root from last night. My device is a kindle fire hdx 8.9 appears to have rooted ok but with a couple curiosities .... I will continue to try and fix what I can or at least get a better understanding of what went awry and share what I find. However, if any of you experts have some insight into these "issues" I would very much appreciate your constructive feedback / input.
The first issue is the missing "Photo Gallery". Oddly, no apps which rely on it for loading / saving image data are able to find it ... I see a partial folder structure in DCIM (a couple sub-folders are gone when browsing to the DCIM folder inside "internal storage" via my USB to PC connection through Windows explorer); however, when browsing to the DCIM folder located inside of "emulated/0" via ES Explorer local to the device, I see an apparently complete (or more complete) list of folders and files than those seen from Windows in "internal storage/DCIM/". I was thinking about copying data from "emulated/0" to the "internal storage" location to see if that makes any difference. But im not sure what's an actual folder and what's just a symbolic link to a folder some place else in storage... and would prefer to not further "Bork" the device if possible.
Also, I think the "Photo Gallery" app itself is completely gone from the device ... I was hoping to find a way to restore it or find an alternative solution that allows my other apps, which need the "missing" Photo Gallery for normal operations, to function again. The error messages I get from apps trying to access photo data or that need to save new data don't state that they can't locate or save files, they state that they can't locate "Photo Gallery".
Second issue, also post root from last night ... I was not successful in removing the advertisements which appeared on the lock screen pre root. The root tool / method I followed seemed to work without error but the option to remove the ads didnt effect any noticeable change. I was going to try some apps that modify wallpaper etc to see if that wgorks ... but again, any insight or assistance with getting this resolved would be most helpful too.
Many thanks in advance!
Stock Rom
The Kindle App store is a known issue after rooting. If you are trying to get back to stock you can follow this http://forum.xda-developers.com/showthread.php?t=2582773 I did it on my HDX 8.9 and it worked without issue.
My Kindle Fire HDX 8.9" becomes a brick after replace the build.prop file
BroncoAG said:
The Kindle App store is a known issue after rooting. If you are trying to get back to stock you can follow this http://forum.xda-developers.com/showthread.php?t=2582773 I did it on my HDX 8.9 and it worked without issue.
Click to expand...
Click to collapse
Unfortunately, after I edit and replace the file in /system , my Kindle Fire HDX 8.9" becomes a brick now.:crying:
chen1911 said:
Unfortunately, after I edit and replace the file in /system , my Kindle Fire HDX 8.9" becomes a brick now.:crying:
Click to expand...
Click to collapse
How did you do it? I have had zero issues & I can pretty well GARUNTEE I have had more bricks, bootloops & soft bricks than any other HDX owner.
Did you edit on desktop & just copy over? If you edit on desktop instead of the live build.prop, you need to move it to another folder first, then chown/chmod before using adb to cp it.
Otherwise with root explorer & a few other explorers, it works fine, all of the billion times I have done it. Once again, since we are dealing with a Linux-ish OS, even then I always check the permissions (chmod) & ownership (chown).
Either that, or like a few others, you grabbed the wrong build.prop.
GSLEON3 said:
How did you do it? I have had zero issues & I can pretty well GARUNTEE I have had more bricks, bootloops & soft bricks than any other HDX owner.
Did you edit on desktop & just copy over? If you edit on desktop instead of the live build.prop, you need to move it to another folder first, then chown/chmod before using adb to cp it.
Otherwise with root explorer & a few other explorers, it works fine, all of the billion times I have done it. Once again, since we are dealing with a Linux-ish OS, even then I always check the permissions (chmod) & ownership (chown).
Either that, or like a few others, you grabbed the wrong build.prop.
Click to expand...
Click to collapse
I did not chown/chmod before using adb to cp it. I guess the file build.prop has corrupted. The problem is , I didn't backup my rom. Would like to have backed up original rom of kindle fire hdx 8.9". Anybody can help me that?
if someone can help me get root back, I may be able to help.
GSLEON3 said:
How did you do it? I have had zero issues & I can pretty well GARUNTEE I have had more bricks, bootloops & soft bricks than any other HDX owner.
Did you edit on desktop & just copy over? If you edit on desktop instead of the live build.prop, you need to move it to another folder first, then chown/chmod before using adb to cp it.
Otherwise with root explorer & a few other explorers, it works fine, all of the billion times I have done it. Once again, since we are dealing with a Linux-ish OS, even then I always check the permissions (chmod) & ownership (chown).
Either that, or like a few others, you grabbed the wrong build.prop.
Click to expand...
Click to collapse
I put an old build.prop at / folder, but I can't access adb shell and Windows 7 can't recognize the device, any suggestion for the issue? Once I can access the device , then copy original build.prop to /system, I guess the device will boot properly.
No no no, root doesn't mess with the app store on Thor. I'm rooted with Amazon appstore working. Changing some system files and blocking some ip's will do it (if you have android firewall disable it to use appstore). If you want to unroot just do it in supersu settings. btw I have the 7" model. Also safestrap is now on Apollo (the 8.9").
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.
Davey126 said:
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.
Click to expand...
Click to collapse
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?
Mcfinnipoop said:
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?
Click to expand...
Click to collapse
Sorry - afraid I can't be of much help. The latest situation is not uncommon after a reboot on a borked device. There is no way to enable adb via stock recovery; would be a security risk even if available. Amazon devices are unique beasts; many common recovery tools/techniques don't work due to component selection and a restrictive bootloader. Even if you did regain limited control pushing an OTA image via ADB would not cause it to be processed as you would need a higher version of FireOS than what's already on your device (4.5.5.1); none exist at present aside from v5. With one exception lower (rollback) versions are summarily dismissed.
Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
ok this may sound silly but there were 2 things i did to fix a friends kindle stuck on the settings screen as u describe, I went to applications and under that went to the default silk web browser then to most visited , and yahoo link which allowed me to get to the internet and download and install custom notification apk can be found here https://globalapk.co/apk/1/9085-custom-notification-ex-v221 from there it opened and i was able to place the alternate launcher i had adb installed as a shortcut in notification area which allowed me to navigate, and open the alternate launcher and had some control on device, I also think that simply going to an apk site you trust and installing an alternate launcher like that should also work it should pop right up after install depending on how bad your situation is or what was done with the specific kindle, just thought id give some suggestions for alternate way to perhaps fix it gain control over system again it may not work though, hope that helps.
Hopefully this will work
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
This is a nice write-up that will likely help someone in a similar situation. Thanks for posting
You can help me?
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you
Hello Mcfinnipoop,
I encountered the same problem as you, have you resolved the problem yet? I would appreciate it if you could tell me how to fix it.
Thanks!
VoadekS said:
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you
Click to expand...
Click to collapse
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
It works for me. Thanks!
I am furious. I did not realized that Fire HDX 8,9, (3rd generation) v4.5.5.1 is totally different OS from "normal Android OS" and now I wonder what can I do about it.
How can I uninstall Amazon Android OS and replace it with normal Android OS.
Can that be done? If yes HOW?
I have been searching and reading here, but I am even more confused (yes I am Fire HDX newbie). I would really appreciate if I can get clear and logical instructions HOW can I do that for my unit.
I managed to install Kingroot and was able to login to my Google Play account as I have 2 Android phones (Samsung S2 and Leagoo Lead 1), but when I login and tried to download RootChecker, Google Play does NOT show (recognize) my FireHDX, it only shows my other 2 phones. So that's not good for me.....
Any help will be greatly appreciated as the way is my Fire now is useless.
TIA
Ivone said:
I am furious. I did not realized that Fire HDX 8,9, (3rd generation) v4.5.5.1 is totally different OS from "normal Android OS" and now I wonder what can I do about it.
How can I uninstall Amazon Android OS and replace it with normal Android OS.
Can that be done? If yes HOW?
I have been searching and reading here, but I am even more confused (yes I am Fire HDX newbie). I would really appreciate if I can get clear and logical instructions HOW can I do that for my unit.
I managed to install Kingroot and was able to login to my Google Play account as I have 2 Android phones (Samsung S2 and Leagoo Lead 1), but when I login and tried to download RootChecker, Google Play does NOT show (recognize) my FireHDX, it only shows my other 2 phones. So that's not good for me.....
Any help will be greatly appreciated as the way is my Fire now is useless.
TIA
Click to expand...
Click to collapse
Likely find what you need in the following thread (one of several btw). Read, go slow, reread to confirm understanding, ask if unsure, ignore internet/youtube guidance from 'experts' not familiar with this device. HDX devices are easy to brick and tough/impossible to recover if you stray off the beaten trail.
http://forum.xda-developers.com/kin...artially-fire-os-to-proper-rom-t3421623/page4
fwiw - I am penning this on a 3rd gen HDX thor (7") running Fire Nexus which is my primary device (3-4 hours per day) despite having access to numerous other computing gizmos with far better headlines. Yep, lowly kitkat on a 2+ year old (unlocked) tablet. Go figure. You can duplicate that 98% of that config with minimal effort.
Thanks Davey, I am reading all the post in that thread you posted. Looks like I am on the right path.
I have 4.5.5.1 and Kingroot installed already on my Fire and working. Installed ES File Explorer and tested. I am rooted. !
Next step is to install Safestrap 4.0.1 - right?
After that I will go with HDX Nexus ROM v4 (as I red it's the best for my Fire HDX)
Then will proceed with HDX Nexus ROM installation ...
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery (HOW do I do that?)
- You should eventually end up in safestrap recovery
Once I do that the instruction is: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Which one do I download THOR or APOLLO? (little confused here)
Also, should I delete any or all aplications that I downloaded and installed from Amazon?
Will everything work normal such as: Wifi, AGPS etc? Any known issues with my FireHDX?
TIA
Ivone said:
Thanks Davey, I am reading all the post in that thread you posted. Looks like I am on the right path.
I have 4.5.5.1 and Kingroot installed already on my Fire and working. Installed ES File Explorer and tested. I am rooted. !
Next step is to install Safestrap 4.0.1 - right?
After that I will go with HDX Nexus ROM v4 (as I red it's the best for my Fire HDX)
Then will proceed with HDX Nexus ROM installation ...
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery (HOW do I do that?)
- You should eventually end up in safestrap recovery
Once I do that the instruction is: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Which one do I download THOR or APOLLO? (little confused here)
Also, should I delete any or all aplications that I downloaded and installed from Amazon?
Will everything work normal such as: Wifi, AGPS etc? Any known issues with my FireHDX?
TIA
Click to expand...
Click to collapse
Response to questions:
- HDX 7" = Thor; HDX 8.9" = Apollo (you want Apollo)
- reboot to recovery: you will be prompted (or just shutdown & restart)
- no need to delete existing applications
- everything works in Nexus - WiFi, Bluetooth, location services (no GPS unless you have LTE model), Play Store, etc. No significant issues.
Davey126 said:
Response to questions:
- HDX 7" = Thor; HDX 8.9" = Apollo (you want Apollo)
- reboot to recovery: you will be prompted (or just shutdown & restart)
- no need to delete existing applications
- everything works in Nexus - WiFi, Bluetooth, location services (no GPS unless you have LTE model), Play Store, etc. No significant issues.
Click to expand...
Click to collapse
Davey, I have not abandon the OS changing process, I am just VERY scared. Since my post, I have been reading and reading like crazy hundreds pages trying to understand between all the info what exactly is related to only my FireHDX, but did NOT found exact instruction. A lot for HD, HDX 7 etc. It looks like that my Fire is not very popular
I will write again my setup.
Fire HDX 8,9, 4.5.5.1, (3rd generation), 16GB, 4G/LTE, free space left 6.86GB, all stock. Only extra apps I installed are: Opera, GPS Test, KingRoot that I used to Root (working), ES File Explorer that I used to change the permissions like this > Root Explorer>Mount R/W>changed permission to RW in: /system and /mnt/sqfs
I have Windows 7, 32
I am a complete chicken to proceed further.
I imagine next step is to install Safestrap but I am not sure what is the latest version for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE
(it looks like Safestrap 4.0.1 is the one I should use - correct?) If yes should I follow your instruction BELLOW from other thread?
Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. You can snag the app from here (got the URL - np), be sure to select the appropriate format (APOLLO). Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. From home screen go into the backup section. Take a backup of your current FireOS installation (selection all partitions). You will want this should you every want to restore you device to it's current configuration. The resulting files will be quite large and should be copied to another device for safe keeping (will transfer to my PC.). Exit Safestrap and reboot into FireOS. Tether your device and copy the files to a suitable host. You seem to be familiar with ES File Explorer so should have no problem finding them. Should be in the TWRP directory located within sdcard (or just browse internal storage from the host machine).
What is the correct slot that I should use? I just found the answer = Stock slot!
Do I have to download some drivers to my PC for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE and transfer them to Fire directory? If yes, what drivers and where should I place them. (found the answer - installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard)
Apollo Nexus ROM will be my prefer choice, but wonder if everything will work.
I know that you answer that, but then you mention 4G/LTE, is that mean it will work as well or my SIM/phone/data will not work.
Is there any known issue (what will NOT work) on my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE once I change to Apollo Nexus ROM?
Also I like to ask you if CM11 will have any advantage over Nexus on MY Fire HDX. Just wonder (as you said it has nice GUI etc.)
I red tons and tons of yours and other people posts and I am VERY great full for all your time and help you offer to newbie like me. Your dedication is awesome.
UPDATE
I took the plunge and installed Safestrap and all is fine (checked few times)
I downloaded Nexus Apollo and placed it into folder that I created in the FireHDX Internal Storage. I don't see or know how I can create folder in the root directory in
my Fire sdcard.
I am trying to follow your instructions from your other post:
Nexus Apollo installation zip. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. (HOW) It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
That's exactly my concern - will my Apollo Nexus folder get deleted when I install it Nexus on the Stock Slot. Does it wipe ALL the folders in the Internal Storage?
Can I/ should I move the ApolloNexus folder using ES File Explorer 3.0.5 in to Fire Device directory or Root and will I be able to access it after the wipe.?
I am stuck..................!
TIA
Attaching image where is the folder now - is it safe there?
Ivone said:
Davey, I have not abandon the OS changing process, I am just VERY scared. Since my post, I have been reading and reading like crazy hundreds pages trying to understand between all the info what exactly is related to only my FireHDX, but did NOT found exact instruction. A lot for HD, HDX 7 etc. It looks like that my Fire is not very popular
I will write again my setup.
Fire HDX 8,9, 4.5.5.1, (3rd generation), 16GB, 4G/LTE, free space left 6.86GB, all stock. Only extra apps I installed are: Opera, GPS Test, KingRoot that I used to Root (working), ES File Explorer that I used to change the permissions like this > Root Explorer>Mount R/W>changed permission to RW in: /system and /mnt/sqfs
I have Windows 7, 32
I am a complete chicken to proceed further.
I imagine next step is to install Safestrap but I am not sure what is the latest version for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE
(it looks like Safestrap 4.0.1 is the one I should use - correct?) If yes should I follow your instruction BELLOW from other thread?
Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. You can snag the app from here (got the URL - np), be sure to select the appropriate format (APOLLO). Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. From home screen go into the backup section. Take a backup of your current FireOS installation (selection all partitions). You will want this should you every want to restore you device to it's current configuration. The resulting files will be quite large and should be copied to another device for safe keeping (will transfer to my PC.). Exit Safestrap and reboot into FireOS. Tether your device and copy the files to a suitable host. You seem to be familiar with ES File Explorer so should have no problem finding them. Should be in the TWRP directory located within sdcard (or just browse internal storage from the host machine).
What is the correct slot that I should use? I just found the answer = Stock slot!
Do I have to download some drivers to my PC for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE and transfer them to Fire directory? If yes, what drivers and where should I place them. (found the answer - installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard)
Apollo Nexus ROM will be my prefer choice, but wonder if everything will work.
I know that you answer that, but then you mention 4G/LTE, is that mean it will work as well or my SIM/phone/data will not work.
Is there any known issue (what will NOT work) on my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE once I change to Apollo Nexus ROM?
Also I like to ask you if CM11 will have any advantage over Nexus on MY Fire HDX. Just wonder (as you said it has nice GUI etc.)
I red tons and tons of yours and other people posts and I am VERY great full for all your time and help you offer to newbie like me. Your dedication is awesome.
UPDATE
I took the plunge and installed Safestrap and all is fine (checked few times)
I downloaded Nexus Apollo and placed it into folder that I created in the FireHDX Internal Storage. I don't see or know how I can create folder in the root directory in
my Fire sdcard.
I am trying to follow your instructions from your other post:
Nexus Apollo installation zip. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. (HOW) It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
That's exactly my concern - will my Apollo Nexus folder get deleted when I install it Nexus on the Stock Slot. Does it wipe ALL the folders in the Internal Storage?
Can I/ should I move the ApolloNexus folder using ES File Explorer 3.0.5 in to Fire Device directory or Root and will I be able to access it after the wipe.?
I am stuck..................!
TIA
Attaching image where is the folder now - is it safe there?
Click to expand...
Click to collapse
Looks like you made some progress (good!) but have the following questions/concerns:
>> Nexus zip location: fine where it is (as shown in your screen shot)
>>Compatibility: no rom is perfect including FireOS. While Fire Nexus is time proven and stable some issues remain:
- 4G/LTE voice does not work
- 4G/LTE data can be finicky; depends on your carrier
- Some Play Store apps (especially games and social media) show as 'incompatible' but typically can be sideloaded without further issue
- Some apps rotate screen 90/180 degrees from 'features' orientation; easily fixed using one of several methods
- Native spell checker crashes foreground application if a replacement word is selected (keyboard spell checkers work fine)
- some browsers/sites mistake big, beautiful, high-res HDX for desktop and do not automatically present mobile version (not a big deal)
- no OTG (external dongle/storage) support...nor is there on FireOS or any other rom for this device; hardware limitation
- GPS is slow and can not be used for driving guidance or games like Pokémon. Same with FireOS. However, static mapping apps are fine.
Yikes - seems like a long list!! Yet an equivalent FireOS manifest would consist of dozens of bullets and take up multiple pages. My wonderful mobile 'issue' list is 3-4x longer. Pick your poison.
Davey126 said:
Looks like you made some progress (good!) but have the following questions/concerns:
>> Nexus zip location: fine where it is (as shown in your screen shot)
>>Compatibility: no rom is perfect including FireOS. While Fire Nexus is time proven and stable some issues remain:
- 4G/LTE voice does not work
- 4G/LTE data can be finicky; depends on your carrier
- Some Play Store apps (especially games and social media) show as 'incompatible' but typically can be sideloaded without further issue
- Some apps rotate screen 90/180 degrees from 'features' orientation; easily fixed using one of several methods
- Native spell checker crashes foreground application if a replacement word is selected (keyboard spell checkers work fine)
- some browsers/sites mistake big, beautiful, high-res HDX for desktop and do not automatically present mobile version (not a big deal)
- no OTG (external dongle/storage) support...nor is there on FireOS or any other rom for this device; hardware limitation
- GPS is slow and can not be used for driving guidance or games like Pokémon. Same with FireOS. However, static mapping apps are fine.
Yikes - seems like a long list!! Yet an equivalent FireOS manifest would consist of dozens of bullets and take up multiple pages. My wonderful mobile 'issue' list is 3-4x longer. Pick your poison.
Click to expand...
Click to collapse
Thank you Davey for the detail explication.
Wow, what a disappointment with all the Nexus rom issues. Oh well, that will scrap my Vodafone appointment today. In that case I will research alternatives (if they exist). Basically I was going to use it MAINLY for Waze or Sygic navigation and calls. I am not in to games, music, movies etc.
Co you have any idea how is CM11 behave with my type of Fire? Or what would you suggest?
Thanks again for your time and help.
One more time my apologies rambling about the setup request. I have read about so many problems and bricking that put me in the panic mode.
Ivone said:
Thank you Davey for the detail explication.
Wow, what a disappointment with all the Nexus rom issues. Oh well, that will scrap my Vodafone appointment today. In that case I will research alternatives (if they exist). Basically I was going to use it MAINLY for Waze or Sygic navigation and calls. I am not in to games, music, movies etc.
Co you have any idea how is CM11 behave with my type of Fire? Or what would you suggest?
Thanks again for your time and help.
One more time my apologies rambling about the setup request. I have read about so many problems and bricking that put me in the panic mode.
Click to expand...
Click to collapse
You will not be able to use a HDX for dynamic navigation regardless of app or rom - including FireOS. The integrated GPS 'chip' is has proven unreliable and is too slow to keep up with rapidly changing locations. It is also slow to acquire satellites (minutes) and often needs a reboot if the GPS appears unresponsive. Works fine for static location apps/maps using Google's fused location services. Static mapping/location apps are less reliable on FireOS; many will not work at all. Sorry for the bad news ...
Davey126 said:
You will not be able to use a HDX for dynamic navigation regardless of app or rom - including FireOS. The integrated GPS 'chip' is has proven unreliable and is too slow to keep up with rapidly changing locations. It is also slow to acquire satellites (minutes) and often needs a reboot if the GPS appears unresponsive. Works fine for static location apps/maps using Google's fused location services. Static mapping/location apps are less reliable on FireOS; many will not work at all. Sorry for the bad news ...
Click to expand...
Click to collapse
What can I say, big disappointment and dumb decision to buy Kindle.
I may try to sell my Kindle that I used once or twice (just playing around ) and buy something else.
BIG thanks again Davey and sorry wasting your time.
Ivone said:
What can I say, big disappointment and dumb decision to buy Kindle.
I may try to sell my Kindle that I used once or twice (just playing around ) and buy something else.
BIG thanks again Davey and sorry wasting your time.
Click to expand...
Click to collapse
Not a waste of time if useful knowledge was exchanged. Despite the disappointment HDX tablets are wonderful devices that can perform many tasks better than contemporary high-end alternatives. Unfortunately, navigation is not one of them.
Davey126 said:
Not a waste of time if useful knowledge was exchanged. Despite the disappointment HDX tablets are wonderful devices that can perform many tasks better than contemporary high-end alternatives. Unfortunately, navigation is not one of them.
Click to expand...
Click to collapse
Oh well, your right. I am also believer that everything is good for something....
BTW: is it complicated to bring my KF back to stock with out any negative consequences?
Can I just delete Safestrap?
Ivone said:
Oh well, your right. I am also believer that everything is good for something....
BTW: is it complicated to bring my KF back to stock with out any negative consequences?
Can I just delete Safestrap?
Click to expand...
Click to collapse
Assuming you have not installed a custom rom simply uninstall Safestrap recovery from the within Safestrap app and then close and uninstall the Safestrap app itself.
Davey126 said:
Assuming you have not installed a custom rom simply uninstall Safestrap recovery from the within Safestrap app and then close and uninstall the Safestrap app itself.
Click to expand...
Click to collapse
Ok, thanks a lot... (no rom installed)
Just checking if there is any news on that matter. Or maybe any new stable Android I can install. As of now I'm just using my HDX 8.9 to watch movies when travelling. Thx!
antonioroc said:
Just checking if there is any news on that matter. Or maybe any new stable Android I can install. As of now I'm just using my HDX 8.9 to watch movies when travelling. Thx!
Click to expand...
Click to collapse
Your question is not entirely clear but it is now possible to install a wide array of high quality custom ROMs on any 3rd (not 4th) gen HDX representing Android 4.4 (KitKat) to 7.1 (Nougat). All offer full access to Google Play along with the amenities that come with native Android and a well stocked app store. That said, if you are only using your HDX to watch movies FireOS remains a solid choice
Thanks for replying. Do you have a tutorial on how to install 7.1 (Nougat) into 8.9 3rd Thor?
antonioroc said:
Thanks for replying. Do you have a tutorial on how to install 7.1 (Nougat) into 8.9 3rd Thor?
Click to expand...
Click to collapse
You have to root FireOS (or pursue a somewhat more complex alternative) and then unlock the bootloader to enable installation of Android 7.x based ROMs on this device. The prep work can be a bit daunting for those new to tinkering with Android devices. The following thread is a good starting point.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
I'm just not getting there
I've been following this post for some time trying to do the same with my 3rd Gen fire HDX 8.9. I'm on OS version 4.5.5.3 and can't seem to get into the system by doing any of the turn-on procedures (turn-on, wait then hold power button, power and volume up, etc.). Has Amazon locked us out with the latest update? Did I buy this and get stuck with a useless (nearly) box of rocks? I have ES File manager, Safestrap 4.01 and Kingroot installed and I'm able to get to the root directory, but I'm lost after that.
Bobkuwait said:
I've been following this post for some time trying to do the same with my 3rd Gen fire HDX 8.9. I'm on OS version 4.5.5.3 and can't seem to get into the system by doing any of the turn-on procedures (turn-on, wait then hold power button, power and volume up, etc.). Has Amazon locked us out with the latest update? Did I buy this and get stuck with a useless (nearly) box of rocks? I have ES File manager, Safestrap 4.01 and Kingroot installed and I'm able to get to the root directory, but I'm lost after that.
Click to expand...
Click to collapse
Not sure what you are trying to do but sounds like the wrong procedure. You can follow along in this thread as I assist another Apollo user with a similar configuration unlock the bootloader in preparation for installation of a custom ROM. Please note you will NOT be able to use this device for dynamic navigation regardless of ROM.
Just not getting there
Davey126 said:
Not sure what you are trying to do but sounds like the wrong procedure. You can follow along in this thread as I assist another Apollo user with a similar configuration unlock the bootloader in preparation for installation of a custom ROM. Please note you will NOT be able to use this device for dynamic navigation regardless of ROM.
Click to expand...
Click to collapse
I want to put a full version of Android on my Kindle Fire HDX 8.9 3rd generation. I've followed along on the website. and cannot seem to get a bootloader to open on my Kindle. Running OS 4.5.5.3. I have downloaded several ROMs (CM 12.1, CM 14.1 KK Nexus for fire, but cant get to the bootloader to run any of them. Is there a step-by-step guide anywhere? I was able to get my Nook to the CM 12 platform quite easily.