Related
Hi,
When I go to gPlay on the Q and click on "Apps" I only get like 150,000 results available for download, only a small fraction of the total apps available. When I go there on my computer browser to try to download an app to the Q it says "This app is not compatible with this device" for 90% of the apps. So, no dice with either method.
I have been sideloading apps and most of them work just fine. So I want to get around this gPlay restriction on the Q so I can just download apps directly from gPlay rather than having to sideload them.
(I am fully aware that the reason why gPlay keeps track of which devices are compatible is to avoid more "broken" apps than necessary, but in the case of the Q their own system appears to be broken itself, so I want to get around it.)
So, I bought the Device Spoofer app for $1.50USD
https://play.google.com/store/apps/details?id=com.scheffsblend.devicespoof&hl=en
which, despite the reviews worked just fine for me on both the Nexus 7 and on Nexus Q. It changes your build.prop file to spoof Google Play into thinking you are a different device of your choosing. Note that, as it says in the instructions, you need to spoof the device using the app, reboot, go to gPlay, *download an app* (any app), and from then on gPlay will register your device as a different one.
That works for me -- I select for example "Galaxy Nexus", go thru the steps above, and voila, gPlay in my computer's browser has now replace "Nexus Q" with "Galaxy Nexus". Pretty cool.
HOWEVER, and I am now getting to the point, this doesn't allow me to download any more apps than I had access to before! It still says "This app is not compatible with this device ["Galaxy Nexus"]" for the same apps that were incompatible before. Browsing gPlay on the Q also doesn't yield any new opportunities for downloading apps.
I think what is happening is that even though the build.prop file is being changed, the Q is still reporting to gPlay that it doesn't have, for instance: GPS, phone functionality, etc etc, long list of items. And that means that any apps that require any one of those functionalities is "not compatible" (despite the fact that sideloading many of them means they work just fine).
So, my point is, does anyone know how to spoof gPlay so that the Q reports to gPlay that it has all of the bells and whistles? (GPS, phone functionality, etc etc)
Thanks
I downloaded all the .xml files from my Q's /system/etc/permissions folder and compared them to those downloaded from my Nexus 7. There are about half the number of files and indeed many things are not supported, no surprise.
Is it safe to just copy all the .xml files from my Nexus7 to my NexusQ? (plus a few .jar files that are linked to in the .xml files).
And perhaps then gPlay will show more apps?
OK sorry for multiple posts, but what the heck I just tried it. And can't see any more apps on gPlay. Tried downloading one that was visible as I thought it might only report its permissions at download-time, but nothing changed after the download. Drawing blanks here.
FIGURED IT OUT!
That's right folks, you can now download any app directly onto the Q! No sideloading, no adb.
Followed these instructions for a different device. Basically I was on the right track but needed to change the .xml's file permissions back to rw-r-r and then clear gPlay cache, reboot, etc, then it worked.
Pasting the steps from this page http://www.slatedroid.com/topic/34849-guide-to-fix-market-to-get-more-apps-compatible/ below, with the small modification that I got my .xml files from my Nexus 7, not from his/her link, and I only loaded the tablet_core_hardware.xml so far (I have not attempted loading on any of the Nexus 7's other .xmls but most of them don't seem useful). Thanks go out to bosondehiggs of slatedroid.com. I have made a note in square brackets at which point my Nexus Q gPlay started suddenly showing all apps.
A. Backup /system/etc/permissions (just take a copy with ES file explorer or root explorer.recommended just in case)
B. copy the xmlfiles files into /system/etc/permissions (android.hardware.location.gps.xml, android.hardware.location.xml, com.android.location.provider.xml, tablet_core_hardware.xml) agree to over write all of them
C. Make sure the file permission are rw-r-r (with ES file explorer, long tap then change properties on each file..to help you out all files in that directory need to be rw-r-r)
D. Go to settings->apps->all and tap Google Play Store
E. Click on Clear data
F. REBOOT tablet
market still not working
Go to settings->apps->all Go to “Google Play Store” again
‘Clear Cache’ if it lets you then ‘Force Stop’ — DO NOT Clear data
back and Go to “Google Services Framework”
‘Clear data’ then ‘Force Stop’
REBOOT your machine. [After rebooting, the Nexus Q worked with gPlay just fine!]
Then after reboot market is still not working.. then go into..
settings->apps->all google play store again open it but this time clear data if it lets you..
thats it exit open market up, login and you should now have full market access....Youtube...Facebook....
Click to expand...
Click to collapse
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
sonikot said:
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
Click to expand...
Click to collapse
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
Click to expand...
Click to collapse
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
davidnhutch said:
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
Click to expand...
Click to collapse
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
sonikot said:
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
Click to expand...
Click to collapse
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
UKROB86 said:
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
Click to expand...
Click to collapse
Sorry, I assume you have already followed the instructions by kornyone here to root and install a launcher:
http://forum.xda-developers.com/showthread.php?p=28484300
There are other ways of doing this too. Some folks have gotten CM9 working on it.
I just made this quick video which shows Trebuchet and the Google Play showing most apps available, near the middle of this video.
What Can You Do with the Nexus Q? : http://youtu.be/6rb4iQDBom0
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Click to expand...
Click to collapse
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
mrjaymillz said:
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
Click to expand...
Click to collapse
Sorry, I mean the keyboard page on my website: davidnhutch.com/nexusq, click on Keyboard > Special Keys.
Basically, the "menu" button on android is mapped to the same keycode as the "menu" button on Windows keyboards, which usually has an icon that looks like a drop-down menu with a pointer hovering over it. (http://en.wikipedia.org/wiki/Menu_key)
You also can do all this from the command line without ES File Explorer, I'm just trying to make it a bit more visual, plus, ES is useful.
I am very interested in what you described you are working on, as I am hoping to try the same thing when I get some time. Please post your results and steps!
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
Click to expand...
Click to collapse
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
xMemphisx said:
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
Click to expand...
Click to collapse
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
mrjaymillz said:
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
Click to expand...
Click to collapse
I didn't get a chance to play with it too much yesterday, I would imagine that if you install a 3rd party keyboard and set it to your primary input method it (might) work. I'm going to have a better chance to really look at the Q tonight here in a few hours, so I'll report back with what I can figure out.
[Edit]
I still have had no time to test this yet. The company I work for is at deadline with new software and we have been working 65+ hour weeks here recently, so my Q has just been sitting there. I'm still anxious to test it, but it might still be a few days before work slows back down and I can really get after it again.
mrjaymillz said:
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Click to expand...
Click to collapse
Hm, weird that two people have said the .xml file is not downloadable -- I tried today and yesterday and it was available both times. Maybe the hosting site was down or something. Anyway it looks like someone else offered the same .xml file at another link so we're all set. I'll leave the .xml file there for a year or so though.
Steps 6-15: Yes, enter everything as quoted. No extra "adb" or "su" or anything is needed, other than what I wrote there. Just follow one step at a time, typing each one and then hitting enter. Shouldn't need a command prompt code entry as it is already, just without the code tags and with extra double-quotation marks. Please let me know if there are any errors though.
As for your last paragraph, it seems there are two issues. 1) Not being able to open gPlay on the launcher. Can you please provide more info? What happens? Does it try to open then crash? Is the gPlay app missing? 2) Can't get a keyboard to show up on the screen. -- You will never have an on-screen keyboard on the Q. You need an external keyboard, plugged into the USB port. If you want mouse + keyboard simultaneously, you need a "unifying mouse and keyboard wireless receiver" -- just search amazon for that -- what it is is a mouse+keyboard with just one USB dongle that serves both.
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
300k said:
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You're right, you technically don't need Trebuchet. It just makes life easier than launching everything (e.g. gPlay) via "adb shell am start ..." commands from your computer.
Regarding Google updating to JB, perfectly possible. Possible that everything will be standard in the next Q hardware release. However the real questions are, why was this functionality not included in the first place? Why was the hardware so very limited by the software? And the bigger question, why was the public release of the first Nexus Q sales indefinitely postponed? Presumably they are coming out with something better than what they showed at IO. Whether it's much better or just marginally better remains to be seen.
The best app/function in the video is being able to use OnLive (3D streamed games) in my opinion. Now, OnLive is expensive and I did have a few problems with the keyboard mapping, the mouse not working while OnLive was playing, etc, but it works and shows the potential for streamed games. The Q doesn't have to be the core device either, presumably a tablet would work too. I just think they should have done the hardware differently and made an Xbox competitor (Xsphere?) instead of a competitor to precisely no-one.
On steps 8 and 9 I get
sh: cannot create /sdcard/permissionsbackup: Is a directory
I don't think that I am typing it in wrong and I have copied and pasted as well just in case...The directory is made correctly... Thanks for your help.
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
drivers
I found the correct address for the drivers for this tablet, and 2 others from Azpen.
www.mediafire.com/azpensupport
The links on their webpage incorrectly spell mediafire and also include .com in the last part of the link.
Note: I recently got an email from Azpen telling me the exact same url that I had already figured out. Their email is about week to a week and a half after I sent them a request for the proper address. Also, as of the time I am posting this update, they have not corrected the address on their website.
Tried methods
I have tried SuperOneClick which reports that the system is rooted, but ADB Wireless says it is not.
I have tried Bin4ry's Root Many Android! (options 1, 3, and G) and briefly got temp root on option 3 but I lose wireless functionality (I get one or the other message from ADB Wireless (no root or no wireless), verified that Wireless connection has been turned off and won't turn back on until reboot which loses me the root again).
Retries
Ok, finally rooted the Azpen A701.
What I did:
First, I went back to SuperOneClick, and choose Unroot to reverse anything it did.
Retried Bin4ry's Root Many Android! v31, option 1 (new standard method), test, failed, unroot, 3 (old method), test, failed, unroot, then G (Google Glass method), test, WORKED this time.
Verified by using a root browser (can see files/folders(subdirectories) in /data after giving permission), a root checker (note: do not turn on SuperUser's Autoanswer, gives false information from some checkers), and ADB Wireless works while in range of a wireless router/source.
I am guessing that somehow the leftovers from SuperOneClick were affecting my results with Bin4ry's collected scripts.
Props to all that developed each of those programs and scripts.
I don't know if anyone will be seeing this but I hope it helps anyone needing the info.
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
no idea
BizarreMan said:
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
Click to expand...
Click to collapse
I have absolutely no idea. The only additional rom I have seen ANYWHERE is the Jellybean update for it (see driver link above). This seems to not be a very popular tablet to work with, going by the fact I received no help from anyone here. All research on this so far has been done by me. I stumbled on to Bin4ry's rooting method by accident. I'm not a ROMer, I don't know how to build one. Also I don't know which ROM backup method to use on it/will work with it.
Alright
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
trying again...
BizarreMan said:
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
Click to expand...
Click to collapse
It may have been the sequence I used. Tried SuperOneClick several times (as above it said tablet was rooted but several apps said it wasn't) which installed su, busybox, and superuser. Then found Bin4ry's method, got temp root (tryied 1, 3, and Glass). Then went back to SuperOneClick and unrooted, returned to Bin4ry's and finally got it with Glass method.
Don't know if that helps
Well
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Good to see that your were able to root.
BizarreMan said:
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Click to expand...
Click to collapse
So I think we can safely say that using both methods together + patience will root this tablet (don't know why one or the other wouldn't do it).
Not having any luck
CyberSpiderPrime said:
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
Click to expand...
Click to collapse
I have been trying to root AZPEN A701 for the past week, I have tried everything written on this forum. Any help PLEASE!
clean slate
Are you willing to do a full restart on the tablet (factory reset)? I had to do that before my root took, as I found on other systems that I have rooted some programs you load can interfer with rooting. Save any personal data before you do this, programs can be reinstalled from Google Play or (hopefully you saved them if you downloaded them) your computer
Factory reset:
Press and hold up volume button then press and hold power button. The screen will remain black (no backlight)
Wait 4 seconds then release both buttons (backlight will come on). Shortly the android on it's back with the open torso (the sick android) will be displayed.
Press the down volume button. You should see 5 options available- You are now in the System Recovery program.
Using the up or down volume button to highlight an option then press power to select the option.
1) select Wipe Cache Partition
let the unit reboot, then turn it completely off
reenter System Recovery again.
2) select Wipe data/factory reset
let the unit reboot, then turn it completely off
The system is as clean as it is going to get now.
On your pc (don't know for MAC's) download the drivers, Android programs needed (Android Debug Bridge -ADB- is part of the Android Development kit and some Java Development Kits), and both SuperOneClick and Bin4ry's root software. Install all software and drivers as per their instructions. Run SuperOneClick and Bin4ry's root programs. Busybox and SuperUser will be added automatically by these root programs.
While having wifi and internet access (McDonalds anyone?), re-sign up for Google Play (sorry, but the settings got wiped earler). Go to Google Play and let all the programs update. Update Busybox and SuperUser if needed/possible.
Download any root enabled file system browser (FSB) (permission will have to be granted in program to use root functions) - I used Ghost Commander for mine. It may take a bit to find it in the directory structure for the FSB you downloaded but you need to get to the root system folder.
Ghost Commander has a Local Storage option press it and an new list of folders/files will be displayed, move to the previous folder level (double dots at the top) and give permission to move to a system folder, move to the previous folder again to get to root directory, "/mnt" is the directory you just came out of and is highlighted but you will be at the root of the file system.
Enter the "/data" directory. If you can see files listed there, you have root; if not rooting attempt failed.
Once rooted, doing a system cleaning and Factory reset will not remove root but will remove SuperUser and Busybox (re-run one of the root programs to re-install then update the next time you are on the internet/web). Updating/upgrading the rom will remove root if the rom does not have root activated - I don't know of any custom roms for this tablet (there is a Jellybean upgrade in the Azpen website, if they haven't updated to the correct web address then use the one I listed on the front page, mediafire is spelled wrong in the address). Nandroid level system backup is not available yet for this tablet to my knowledge.
For several reasons, do not turn on SuperUser's automatically give permission option (the one that affects all programs), except on a one for one basis: 1) some root testing programs will fail if this option is turned on, 2) security: turning this on will allow ALL programs - including some malicious ones - to have super-user rights, 3) you will get to know which programs are asking for root permissions beforehand not after, you may want some to have automatic access (like DroidWall in my case, a firewall) and not others.
Also other information that can be useful:
/sdcard does not refer to the removeable SDCard but to the internal user data area. All programs that can be moved to a SDCard (like by Apps2SD) will be moved to this directory by default (some may allow re-assignment of the destination location) instead of the removeable SDCard (blame Azpen, it was their decision to use the directory and name that way). On most other systems /sdcard is the removeable SDCard.
/extsd is the removeable SDCard, when installed, maximum size is 32Gb.
/usbhost1 is for any usb flashdrive connected by a USB-OTG cable (OTG means On-The-Go, special usb cable that puts the tablet into host mode, similar to connecting a flashdrive to a computer, the cable is not a standard Data Connect/transfer cable, one USB-OTG comes with this tablet). Note about USB-OTG cables: if one is connected you can connect either a flashdrive, usb keyboard, usb mouse, combo keyboard/mouse unit, or a powered usb 2.0 hub. Only one flashdrive can be connected at a time (anyone know of downloadable software that would allow 2 or more? I know some modified kernels can allow more than one) so with a hub you can connect a flashdrive + keyboard + mouse (I use the RII wireless combo keyboard and mouse with mine). Maximum size appears to be 8GB, format must be FAT32; will be testing with a 16GB key shortly.
Azpen A701 and Jelly Bean
Shortly after I wrote the above I had to re-flash my tablet, but Azpen had deleted the ICS image (after a request it was restored to the site, get it while you can) and had to flash Jelly Bean. I found there were troubles with this image.
First: I could not write to either the external SDCard (called extsd) nor an attached USB flash key; reading was unaffected. I found this out when I attempted to reassign my backup location to the external sdcard and it was unable to create the directories.
Second: I couldn't find a rooting program.
After a little research, I found that the external media had not been given R/W permission in the platform.xml file - I could actually navigate the FS and read the file even without root.
Also I finally found after 2 days of searching a root program, VROOT, http://forum.xda-developers.com/showthread.php?t=2434453, that would work. Be prepared to deal with Chinese for a little bit and follow the instructions on that page (press the buttons to see screenshots). The superuser app needed to fix/replace the Chinese app is SuperSU (Google Play) which supposedly fixes problems found with other superuser apps. Once you have downloaded SuperSU, had it download/update its binaries and have rebooted, you will have to disable the Chinese Superuser app as you are unable to uninstall it using the app manager: I located it by its icon (shield with cog) in /system/app and appened '.old' to the name: "Superuser.apk" => "Superuser.apk.old'. I didn't use Titanium Backup as suggested because I am not a fan of the program .
platform.xml is located in /system/ext/permissions. After you have root, open platform.xml in what ever text processor you want locally or transfer it to your computer and work with it. You will have to add '<group gid="media_rw">' to the 'WRITE_EXTERNAL_STORAGE' group, on the line after '<group gid="sdcard_rw">' (don't type the single quotes but the double quotes are needed) and write the file back to its location (need root for that, adb pull/push may be possible to fix this). Remember on this tablet, sdcard refers to the internal user storage, media_rw will give permissions to the extsd (external sdcard) and USBHost1 (using included USB-OTG cable and a flash drive). I rebooted the tablet and tested the RW state of extsd, and voila, it now is write capable.
I wish there was more aid on this tablet but since it is not mainstream (not made by a big manufacturer like LG, Motorola, Samsung, etc.) I doubt that it is coming (I am not a ROMmer but have been using computers since the 80's, so I know a few tricks and am always learning). I will keep adding info as I find or fix it.
I will probably go back to ICS as some of my programs are not working right, and JB is sluggish.
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
johncro13 said:
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
Click to expand...
Click to collapse
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
comstar said:
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
Click to expand...
Click to collapse
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
cheeb said:
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
Click to expand...
Click to collapse
Glad it worked for you! I started this thread for the A700 http://forum.xda-developers.com/showthread.php?t=2532464 - No activity in it yet. But if you come across anything good post it over there.
Sent from my Transformer TF101 using XDA Premium HD app
Update
I am glad to see that others are taking an interest in this tablet.
I found 2 methods that worked and am glad that others are finding more.
Now if I can get the boot loader cracked I could finally make a nandroid copy and save myself 4+ hours restoring everything when it goes wonky. This has happened twice- OS partition fills up (and don't know why) and the device resets to near factory reset level (even some of the factory apps are missing) and won't install anything but the smallest of apps which are deleted on the next reboot; the only solution is to re-flash the tablet. Note that I have gone back to using ICS as JB has other problems (external media including its own sdcard partition is not rw enabled for one).
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").
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.
Hi there,
this is my very first time attempting to upgrade my Desire 610 to a higher os version. I read around on how to install newer os to this phone, and there are still some things that confuses me.
Yesterday I managed to unlock bootloader on the Desire 610 and resetted the phone back to it's original state.
Next I tried to install a file manager because I actually have those files, WRP Recovery App and Kingoroot on the SDcard. The next hurdle is that I'm in China and I can't get into Play Store to search for apks without VPN. I'm using Expressvpn and it my current OS is not supported and I can't get connected. And when I try to use different sites like apkpure or the page doesn't even load up. Well anyway, I went to both the app's websites and managed to download WRP Recovery App and Kingoroot to the phone.
I'm using this tutorial as my guide How to install the latest Android version on any phone or tablet
Now I'm still downloading these apps through the phone.
So I download the Lineage OS 16.
1) Does android OS 9 works on this phone? Coming from the mac world, certain OS are only for certain machine, so that puzzles me. If it doesn't which OS would you recommend?
In WRP Recovery App, I've already downloaded the HTC Desire 610 image onto the phone.
After that I go to Gapps site, I select Platform - ARM, Android - 9.0, Variant - Pico
Then the querying slider at the bottom just runs nothing allows me to download. (I actually have this file on my SD card)
Next I try to root my phone with KingoRoot on the PC but it doesn't even seem to find the phone, eventhough I can view the files on the phone, internal and sd card.
I'm able to reboot in recovery mode, when I select Recovery it restarts and I get a blank screen with a triangle & exclamation mark.
All I just want is to run a music app that I bought on Play Store and run VPN on this phone.
So I'm confused as to how I should proceed? How to install file manager onto the phone, view my SD card contents and what is the next step I should take to upgrade the OS.
I hope that an expert could offer me some advice on this.
Best