Related
It looks like we have to move our discussion here, so I went ahead and started a thread.
As of now, there is root for the mediapad, but the only way to root the springboard is by flashing it with a rooted mediapad cust.img - which gives you root but loses your 4g.
So for us Springboard users, we either need root or a way to get 4g back if flashing it as a mediapad. Anybody with thoughts or leads or any know-how?
Finally,
Special room for Huawei Media Pad created,
Thanks to TS
I'm very glad,
Now i'm waiting the master in here to modified this device
cause i still newbie
Actually I Prefer The 3G More THan The 4G For Some Reason I Felt 4G Wasnt Stable Enough....So Im Enjoiying My Mediapad In 3G More Than My Springboard In 4G......
from the other thread, Rumbi wrote:
Yap, only thing you have to do is install Superuser and Busybox from Market and copy "su" from /hwcust/oversea_hk/preload/fixed/bin/ to /system/xbin (e.g. with ES File Explorer with root and r/w enabled), and you are ready to go
I've installed SU & BusyBox. I cannot move the SU file over to /system/xbin. A message tells me that I am not root.
However, when I run Root Check Basic I am told I have root.
I ran Root Check before & after I installed S7-301u V100R001C232B012(Root_version) and Root Check said I did not have root.
So the real question is, How do I really know if I have root?
*****
Actually I installed BusyBox Installer. I'm asked to pick a version to install:
1.19.3
1.19.2
1.18.5
1.18.4
1.17.1
None of these will install.
I also have the option to install a "Custom Tune" is there one? I'd gladly pay for BusyBox pro to get BusyBox running
*******
I powered off the device. Put my sdCard back in (the rooted firmware was removed from it). Then installed the SuperUser update from the market.
Ran that - it said everything was OK. Then I forced it to update - it crashed - so I force closed it. I then realized I could not run the original SuperUser app anymore.
Next, I opened up Root Explorer and was able to move the su file over to the xbin. But now BusyBox is not acting right - It said that it was having problems installing, and I'd need to reflash (or reload - I can't recall) the rom.
I'm rebooting, and going to try to install BusyBox....to be clear on which BusyBox..it's this one:
https://market.android.com/details?...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
*****
Just realized in Root Explorer, to tap the little gray box at the top. After you tap it it should read "Mount R/O"
Now you can long press a folder/file and change the read/write permission.
Rumbi,
You said to r/w enabled the su file....is that check ALL the boxes?...Read, Write, Execute Special?????
IIRC, i had some problems with busybox, too. Copy the file from the attachment to /system/xbin and try the installer again.
And i said to enable r/w support for the /system folder. There are two checkboxes in ES File Explorer. First checkbox is enable root permission for ES File Explorer and second checkbox is "Mount / and /system writable".
Now you should be able to copy whatever file you want to /system/xbin. That's how i have done it. If you have any further questions, feel free to ask. I'll try to explain.
PS. You don't ne to alter file permissions of the su-binary but mine are "rwx r-x r-x".
Rumbi, how do you feel about the High resloution mode, does it slow the tablet down? Have you had a chance to use any tegra 2 devices and if so how does the mediapad with the snapdragon compare when in standerd/high-res mode?
Nothing to complain about the Hi-Res-Mode but i don't have any Tegra2-Devices to compare, sorry.
Haven't tried any games in hi-res-mode but normal usage is just fine.
Thanks. Ill try this out. When i try to install busybox it hangs first, then i force close and run again. Then i get the message about reflashing Rom. But i know i have root. I installed connectbot and ran su and got #
Heres how i got root (im away from my pc right now so i try to be as accurate as possible) :
Installed Hauwei modified rom (its the one that says "(root) " in the file name.
Installed Root explorer
Installed Superuser
Install busybox
Install Connectbot
Put my microsd back in (with the firmware AKA dloa folder removed)
I could not get root explorer to allow rw permissions until i slid the sd card out and back in whil the device was on.
Then i ran connectbot as local and typed su hit enter then superuser popped up asking fo allow connectbot to access. Hit allow an type su hit enter an you should get # This took 3 reinstalls of the firmware to work wjthout errors. The first times resulted in superuser needing to be force closed.
I also ran superuser and went into settings and updated it eventhouh its not neede. There i got a read out saying that busybox is not installed, but it does say i have root.
Sent from my HUAWEI MediaPad using xda premium
Honestly i havent noticed a big difference between high resolution an standard.
The only issue with high res is the small icons and buttons are difficult to hit sometimes
Sent from my HUAWEI MediaPad using xda premium
Do i need to unzip this file first?....
.... Nevermind... I unzipped it and put the busybox file in th system/xbin folder.
I installed busybox installer by JRummy16. This time and it worked!!!!!!!
Now its on to figuring out 4G and tryiying to use it as a phone.
What is the xml file i need to edit?
Sent from my HUAWEI MediaPad using xda premium
Good, that you have worked it out now What exactly do you want to do? To get to the hidden menu, you have to open the calculator and type: ()()2846579()()=
To edit the XML-Files, you have to extract the cust.img... But now that you have root, yo can edit whatever is available via root explorer
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
after updating my mediapad to S301uV100R001C232B012, i have problem with 2x Client (RDP client) now, few second after conecting to rdp session, is app 2X client crashing, with error 2x Client has stopped unexpectedly (process com.tux.client), is here anybody with this problem? thanks...
Rumbi said:
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
Click to expand...
Click to collapse
How about this - link
I'll look at it, thank you And these are the libs from an unmodified Springboard, aren't they?
yes indeed. I broke the silly thing, so I haven't played with it much. guess I will have to call about how to get it fixed.
knoxjon said:
How about this - link
Click to expand...
Click to collapse
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
The *.so files are a bit like drivers for the internal components. I'll try to find differences between T-Mobile and Huawei so maybe we get 4G working again.
tedbone said:
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
Click to expand...
Click to collapse
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
knoxjon said:
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
Click to expand...
Click to collapse
Honeycomb
I've been Googling searches like that, and end up with actual screen shots of Honeycomb os..I'll keep looking...
Tried this (from here), but no luck:
Screen capture
Android natively supports the ability to capture a screenshot by method of pressing both the power and volume-down buttons at the same time on an Android device. This native support was first included within the Android 4.0 (Ice Cream Sandwich) update, which is first seen on the Galaxy Nexus smartphone.[86] Previously, Android did not feature native support for screen capturing which would have likely been due to security concerns. Furthermore, prior manufacturer and third-party customizations as well as using a PC connection (DDMS developer's tool) were the only known methods of capturing a screenshot on Android.
I've looked through the *.so files and many of them are exactly the same, but some are different. One file caught my interest. I've attached it here for anyone who wants to try. Please only use it, if you have a T-Mobile Springboard with flashed root Firmware. Copy the content of the zip-file to /system/lib and overwrite the existing file. But make a backup first! After copying you have to set the correct file permission (rw- r-- r--) and reboot the tab. Hopefully 4G works again with this little trick.
All Current rooting options appear to not be compatible with Fire OS 4.1.1. The most recent option I have found was Root_with_Restore_by_Bin4ry_v35. This contains a .bat file that is not consistent with the current file structure of the OS 4.1.1. It appears to be moving the file Special.ab (as part of the restore procedure) to a location on the fire that is no longer a valid path. Attepmting to back up/restore the file com.android.settings, which is not a file on the Fire Hd.
Also, all instructions regarding the process to Root, discuss Endabling ADB via settings>security. There is not a Security selection under Settings; there is Security and Privacy selection.
And the option to enable installation from unknown source is not under Settings>Device, it is located under Settings>Applications.
I seem to get very close but Amazon seems to have it so locked down that I may be buying a new REAL tablet soon.
Has anyone found a viable solution to rooting this Fire Hd?
AFAIK the last gen HD tablets weren't rootable either. I wouldn't get your hopes up. Having CM/PA would be nice but using the Google apps/Launcher hacks you can at least make it much closer to a custom ROM.
Root_with_Restore_by_Bin4ry_v35 is for the 2012 Kindle HD (tate). Using this on our 2013 soho Kindles will result in a permabrick.
Fire HD 6 Under OS 4.1.1 and USB Debugging
I have seen people saying that they 'removed USB Debugging' from Fire HD 6 and 4.1.1.
That is not true.
You go to Settings->Device Options and click 7 times on the Serial Number.
You will find that USB Debugging is already turned on when it comes from the factory; how to turn USB Debugging OFF is the problem for some people with their Fire HD 6 under OS 4.1.1.
And, as someone else said, "Apps From Unknown Spaces" should be checked and that is in Settings->Applications
Have not found a method, yet, of rooting the device. However, you can get to what is not rooted. To install APK files, for example, just go to the Amazon App Store (go to Silk, search for 'Amazon App Store' and create a bookmark. Then you will be able to install free apps such as ES Explorer.
You can plug your Fire HD 6 into your computer, open up a folder and go to the Download folder. Then, using ES Explorer you can double-click on the Download folder and install APK files that you have put there.
In that manner I installed a program I had created and it ran perfectly on the Fire.
Thus, if you have the APK for an App; you can install it.
Do you know if there's a way to install the Google Play Store? Isn't it just another APK? Also, I'm trying to install some google apps (gmail, music, youtube etc) and it's not working since I don't have the google services .apk installed. I tried installing the google servies .apk but just get an parcing error
Sthornton71 said:
All Current rooting options appear to not be compatible with Fire OS 4.1.1. The most recent option I have found was Root_with_Restore_by_Bin4ry_v35. This contains a .bat file that is not consistent with the current file structure of the OS 4.1.1. It appears to be moving the file Special.ab (as part of the restore procedure) to a location on the fire that is no longer a valid path. Attepmting to back up/restore the file com.android.settings, which is not a file on the Fire Hd.
Also, all instructions regarding the process to Root, discuss Endabling ADB via settings>security. There is not a Security selection under Settings; there is Security and Privacy selection.
And the option to enable installation from unknown source is not under Settings>Device, it is located under Settings>Applications.
I seem to get very close but Amazon seems to have it so locked down that I may be buying a new REAL tablet soon.
Has anyone found a viable solution to rooting this Fire Hd?
Click to expand...
Click to collapse
Fire OS 4.1.1 IS NOT Android 4.1.1! It's 4.4.4 renamed
taylooor said:
Do you know if there's a way to install the Google Play Store? Isn't it just another APK? Also, I'm trying to install some google apps (gmail, music, youtube etc) and it's not working since I don't have the google services .apk installed. I tried installing the google servies .apk but just get an parcing error
Click to expand...
Click to collapse
There is a great tutorial on how to get GAPP's working on the HD 6 which only requires a little bit of ADB knowledge.
http://forum.xda-developers.com/fire-hd/themes-apps/how-to-install-gapps-fire-hd6-hd7-t2933523
Unfortunately, the Play Store will not work as it needs root to perform the hack which isn't possible on this device yet (if ever).
No root, but still usable.
Just got three for my kids assuming we would be able to re isntall a decent version of an os on here.
Unfortunately looks like that is not the case.
I had purchesed minecraft from the play store, and when I went to load it up I was being charged the 7 bucks again from the amazon store. Not cool with that.
Fortunately as WowSoftware stated you can still side load any apk you want with out a problem.
Here is what I have been doing:
1) on a device that is linked to google play store:
Install titianum backup, es file explorer
use titanium backup to backup your application
go into the titatium backup folder and find your apk.gz file
move this to a network storage device (jsut for ease, you can copy to your computer if you like)
un .gz the file into a folder.
2) on the fire hd
go to settings and check the box that says allow unkown softwtware to be installed (cant remember the exact wording)
open es file explorer
browse to network store and click on the apk
This will load up what you need (you may need to do the gapps installation if you get no network connectivity issue).
You will need to manually run updates this way.
It's a hack but it works. I'm confident that there will be a root for this device some day, in the mean time I would suggest not running any updates fore fire os.
I have actually been thinking that there may be a way to block the advertisement feed at my router. Just to stick it to the man. If I do this I'll post some info on that.
And the Google play works with this method?
Ado40 said:
And the Google play works with this method?
Click to expand...
Click to collapse
AFAIK no.
PS: There is an ongoing discussion about a possibility of rooting new devices here - h**ps://plus.google.com/communities/115612726860884592519
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
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.