Related
I feel like there is a huge gap of information I'm missing with regard to certain things people have been posting, like roms, apps and kernels.
I was able to root my SII i989 (tmobile usa) I have downloaded some apps from the Play store, as thats pretty straight forward. What confuses me is how to download these roms onto the phone. do i have to do it from my phone, or from my PC to phone?
a lot of times I dont even understand what certain things will do, im obviously steering clear of doing anything I dont understand. but I think there is a lot of implied knowledge in many posts (I dont blame you guys) but id appreciate a VERY VERY SIMPLE AND CLEAR guide.
thanks in advance :highfive:
Hi the guides are out there in the sticky threads at the top of list. My advice would be to find the forum specific to your model version and read. Once you know how to root and have acquired the necessary software then read how to recover your phone should anything happen. Once you have all this information and software then start to root. I have no background in software, IT or programming and I learnt the basics on this site. All the best
Sent from my GT-I9100 using xda premium
HANDSY said:
Hi the guides are out there in the sticky threads at the top of list. My advice would be to find the forum specific to your model version and read. Once you know how to root and have acquired the necessary software then read how to recover your phone should anything happen. Once you have all this information and software then start to root. I have no background in software, IT or programming and I learnt the basics on this site. All the best
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
thanks for the reply! I have been modding phones since my Nextel phones and through to my iphones, but I got this SII a couple months ago, I rooted it yesterday, but I feel like the guides youre talking about dont give enough details, lol. what im asking for is for someone to hold my hand the first time. lol
If you've already rooted it then that's the biggest step, in my opinion. Installing a new rom is relatively easy. Most devs give an installation guide in their thread, as you don't have the same model as me and all ROMs aren't installed in exactly the same I'm hesitant to "hold your hand". Have you found the forum specific to your model?
Users there may be better qualified to guide you. Happy flashing.
Sent from my GT-I9100 using xda premium
DiploDroid said:
thanks for the reply! I have been modding phones since my Nextel phones and through to my iphones, but I got this SII a couple months ago, I rooted it yesterday, but I feel like the guides youre talking about dont give enough details, lol. what im asking for is for someone to hold my hand the first time. lol
Click to expand...
Click to collapse
Why did you laugh out loud twice writing that?
You're in the wrong forum, and if you don't understand the terms you describe, ignore the stuff on this site and continue to enjoy your phone.
KERNALS
Sent from my GT-I9100 using xda premium
Thanks for everyones replies, i found the correct forum.
Sent from my SGH-T989 using xda app-developers app
I thought it'd be handy for me to give you some of the following brief definitions.
Stock ROMs - Original/OEM Phone Firmwares made & developed by manufacturers i.e. Samsung, Sony, HTC, themselves. Comes with your phone.
Custom ROMs* - Firmwares that are developed by individuals (often built from Android Open Sources). Requires root to install these ROMs.
Apps - Android applications.
Kernels - Essential Android component; Execution of your Android operating system. Speed and battery life of your phone can be said to be mainly connected to it.
*Here's a compiled list of custom ROMs managed by Recognized Contributor GaboWinter.
To install (A.K.A. flash) a new ROM, it is done via your phone itself.
Usually the steps are:
1. Download the ROM in .zip format
2. Transfer the .zip to your phone (if you downloaded it into your computer)
3. BackUp your existing app data (using Titanium Backup App)
4. Reboot your phone into ClockWorkMod recovery mode
5. Perform a NANDRIOD Backup
6. Wipe Cache Partition + Wipe Dalvik Cache + Wipe Data/factory reset
7. Choose .zip file from your phone storage
8. Flash the .zip (You've installed a new ROM at this stage)
9. Reboot back into your system
10. Enjoy your new custom ROM.
Please correct me if I made a mistake somewhere.
don't forget to add
RIL
MODEM
it's KERNEL not KERNAL
keith: NANDROID backup also?
kmetek said:
keith: NANDROID backup also?
Click to expand...
Click to collapse
Yeah! Added Thanks
Hello XDA!
I opened a new thread hopefully to open a discussion about improvements I think are beneficial, my experience over the last 24 hours that a couple sticky edits would have saved me (and others) time.
My Story:
Yesterday (5/3) I saw I had around a 250 mb OTA. Excited (hoping for 4.2, assuming was the 4.1.2 that VZW released recently) I kick on WiFi, download and watch as it reboots and appears to install successfully. Time for work to end, grabbed phone off charger as it appeared to be rebooting after successful install, and ran out to catch train home.
Downstairs, at train stop, take a look at phone and heart sinks as it is in a fast splash screen loop, blinking the VZW Galaxy Note 2 screen for about 1 second in endless loop. As I had never seen before was thinking firmware update bricked it and I was looking at least until Tuesday before I'd have a working phone. Luckily, I was able to quickly see that I could still get into download mode, so knew I was (likely) going to be ok.
Get home and a Quick Robin, to the Internetz! later I'm browsing XDA and following the t=t=2024207 walkthu to restore stock. FYI, my device prior to the failed OTA was unrooted stock. At this point I'm not sure if it's going to restore, so I'm trying to do the true stock, no unlocked bootloader in case it has to be RMA'd. I've downloaded all my files, waited patiently for the slow hosting service for the FXZ(?) to download and am grinding through it and of course it fails at the system.img. Luckily, blessedly the awesome community here had released the image that included the unlocked bootloader which I was (after waiting to download, etc etc again) able to successfully get installed via Odin, booted up and working successfully.
So, while the first post section regarding restore to stock does indicate users with latest firmware "L4 OTA Only" shouldn't be attempting to use the Official VRAL I didn't think it applied to me. I would say that a fair amount of individuals looking to take the drastic step of a full restore to stock might be in a scenario like mine, where something significant has happened and likely confirming what OS/firmware/etc you are on might not be feasible. In my case, I assumed never rooted/unlocked vanilla device should be about as receptacle to an "official" restore as any. In this scenario, where a 100% for all devices stock recovery ("alternative") works, 'I feel that it should have been pushed harder than the official or at least blurbed with if you don't know what you are on, use this' While I understand that it is the "official" image, it has requirements for it to work. A co-worker had an ASUS TF300T that tried pushing a recovery image for ICS after he had upgraded to JB and it hard bricked his tablet, with ASUS wanting to charge him about 60% cost of the tablet to replace motherboard. That's heartbreaking, and I am sure since a hard brick wasn't a likely scenario here, why it wasn't mentioned.
Also: The download link for the Alternate Restore lists the file as: I605_VRALJB_Restore.tar.md5.xz which requires that it be unpacked using 7zip AND also that once extracted, it needs to be renamed to kick of the extra extension md5 in order for ODIN to see it properly as a PDA image file. (I605_VRALJB_Restore.tar.md5 ) Neither step is mentioned in the original post, and I had to read through to I believe the 11th page or so before realizing that was the problem. I'm sure with most of the people that are daily users of this forum knew automatically that these steps were required, but I would counter that a thread explaining how to restore Stock is one of the few threads that is likely to reach a larger, inexperienced demographic who would need to know such details.
Lastly, since (I thought) I had an unlocked bootloader, but otherwsie working phone again (Thank you, thank you thank you!) might as well get it rooted, and grab a ODEX'd stripped ROM with the OS release because getting the Software Update nag and not being able to complete or even brick my phone makes my OCD gland flex mightily. Was delighted to see an on-device APK root option which threw me back to the ease of z4root a few years ago with my Droid X. APK installs, and it roots so easily, like it had the functionality out of the box. I grab goo.im manager and install TWRP. Go to boot into custom recovery so I can install my sexy updated OS ROM and enjoy my fun device without all the yucky bloatware I've just ignored/dealt with for the last 2 months and I get the dreaded and in my opinion illegal "VZW unauthorized software" software brick.
Back to the forums, see I need another stock 'alternative' restore to fix AND a little confused, but believe I need to run a "jailbreak" bootloader unlock (CASUAL ?t=2118348) Which I haven't done yet. I have all files downloaded, just paused to post my experiences here.
So, this was main reason for my post, as I can understand some of why walkthru is laid out the way it is above, but why not have this included as part of the stickied root walkthru? It's mentioned thusly:
section 1a is a old method and no longer needs to be used unless the end user wants root only. proceed to Adam Outler's "JAILBREAK" thread linked at the bottom of this section for rooting and unlocking bootloader so custom roms can be flashed!!!
Click to expand...
Click to collapse
I couldn't find the link it refers to at bottom of section? I ended up googling to find guide. ((t=202420)
if this is still a requirement for root, custom ROM/Recovery, I would have made this steps 1-x of the root guide. is it because another person authored it? It would be nice to be able to credit and quote, I know alot of what drives contributors is the 'Thanks" and Donations, be great if XDA admins could round table and find a solution that allows for a consolidated guide for each device and still give each contributor a way to get their +1's and plug donation/web/twitter handle url's
So, is my understanding incorrect of what is needed or do folks agree with me that current setup is not the most efficient way XDA community could be offering instructive guides on Root/Mods? It would be wonderful if XDA Mods upon announcement of devices, when creating the forum threads for device (Development, OG Development, General, etc etc) created a blank thread for the how to root et.al and then allowed it to be edited by the community as a Wiki. Or even if an individual created, allow that person to allow x amount of other community members to edit, add and adjust.
I see droidstyle created a thread about questions for softbrick, and I might have to look at the original sticky thread about how to stock restore, but it seems he/she might have better saturation if this info was included in the original post. The stickied How To recover stock is direct accessible from a google search. I doubt his Q&A thread is or definitely not going to be one of the highest page-ranked sites.
So, please let me know if I'm just out of my mind, off the mark. I will give myself a small escape clause based on the fact that I probably scored about 2 hours of sleep last night messing around trying to get the note running again. I am actually concerned that the instructions for Return to Stock/Root/Etc for the VZW i605 doesn't have the link to unlock bootloader via casual and am hoping that following that process before rooting/customrecovery/ROM is correct, and not going to be another BrickGate for me. I know as OS versions are updated and/or Big Red and Big Blue constantly push patches trying to lock people out of their phones that instructions change and methods break. As new directions are implemented it's easy to lose steps as edits occur on the fly.
Most importanly! I hope this thread comes across as constructive criticism/suggestions, I have nothing but the highest respect for this community and it's contributors. Even skewed, outdated and conflicting information is better than no information and I SUPER appreciate the hard work required to get it out to us. I am most definitely not expressing displeasure with my experience or the content, only using the threads I mentioned as examples of what I personally see as opportunity for improvements XDA could implement that would allow for easier dissemination of the information the community is sharing so unselfishly. I only open it for discussion, so that others like me can access the information quicker with less confusion. I read comments of disgust and exasperation as people are directed to search, rather than post, and they are right, the information is invariably there, and most often or not within the first 5 posts of a thread. But sometimes when a developer talks to another developer, the tiny and considered minor details are not mentioned because it's considered common knowledge, and thats where the noobs, soccer moms and Grandmas can get left scratching their heads trying to puzzle how you got from point a to b. (Stereotypes used for comedic effect, please take no offense) I believe it would save alot of people having to answer the same questions over and over again time and frustration and freeing them to focus their talents on making us the next epic ROM/Kernel/App
thanks for reading! Also, I'm not just drive-by b*tching, if anyone is interested, I would love to show a mock-up of the i605 guide these great contributors have created as I would compile it. I'm passionate about mobile technology and customization, sadly my talents don't lie in the creation of such, only the enjoyment of it. But I'm a hell of a document admin. I create wiki's and KB's/sharepoint admin for a living, and would love to contribute what I know in that way
Being newly interested in rooting and tweaking my devices (started with my S3) there are a lot of terms that are mentioned in customizing threads that I do not understand, and a lot of those threads don't have detailed instructions for someone that's new to tweaking. Is there one post somewhere on xda that lists terms, methods, etc for newcomers like me?
I don't trust any forum other than xda because I simply think its the best forum for tweaking, etc so I don't really trust links outside xda. I also know that the way some things need to be done is device specific.
I'm confused about how to "flash" something in "recovery' (such as removing the wifi notification thread), flashing a custom recovery, using Goomanager to flash, etc. Don't get me wrong; I can follow detailed instructions as long as they are there......but if they aren't, that leaves me and a great deal of newcomers in the dark.
Some of these things are done via the phone and some have to be done via PC....and many times there aren't detailed instructions so I'm unsure what I an supposed to do and don't want to brick a $700 device.
So....is this information contained in all separate posts throughout the forum? Or is there one thread per device that details it? Being as some of these things are device specific, I'm hesitant to even look in other device forums.
Thanks for reading, and any assistance is appreciated.
wolfgrrl said:
Being newly interested in rooting and tweaking my devices (started with my S3) there are a lot of terms that are mentioned in customizing threads that I do not understand, and a lot of those threads don't have detailed instructions for someone that's new to tweaking. Is there one post somewhere on xda that lists terms, methods, etc for newcomers like me?
I don't trust any forum other than xda because I simply think its the best forum for tweaking, etc so I don't really trust links outside xda. I also know that the way some things need to be done is device specific.
I'm confused about how to "flash" something in "recovery' (such as removing the wifi notification thread), flashing a custom recovery, using Goomanager to flash, etc. Don't get me wrong; I can follow detailed instructions as long as they are there......but if they aren't, that leaves me and a great deal of newcomers in the dark.
Some of these things are done via the phone and some have to be done via PC....and many times there aren't detailed instructions so I'm unsure what I an supposed to do and don't want to brick a $700 device.
So....is this information contained in all separate posts throughout the forum? Or is there one thread per device that details it? Being as some of these things are device specific, I'm hesitant to even look in other device forums.
Thanks for reading, and any assistance is appreciated.
Click to expand...
Click to collapse
Well, this can be a complex arena to play in. For the S4, you'll want to download Odin v3.07 and a copy of the stock ROM just in case you break something.
> http://forum.xda-developers.com/showthread.php?t=2289325
> http://forum.xda-developers.com/showthread.php?t=2189539
ROM = read-only memory - this is the part of your phone's internal storage you're not really supposed to be able to play with (like /system, or the phone's radio for example)
The act of "flashing" is writing data to ROM
Recovery just means that you should always be able to boot your device into this mode to RECOVER from a software problem; IE: flashing a bad ROM (IE: one that doesn't work and you can't start your phone anymore).
I don't really know a whole lot more than that, I just poke around and pretend like I do =)
OverkillSD said:
Well, this can be a complex arena to play in. For the S4, you'll want to download Odin v3.07 and a copy of the stock ROM just in case you break something.
> http://forum.xda-developers.com/showthread.php?t=2289325
> http://forum.xda-developers.com/showthread.php?t=2189539
ROM = read-only memory - this is the part of your phone's internal storage you're not really supposed to be able to play with (like /system, or the phone's radio for example)
The act of "flashing" is writing data to ROM
Recovery just means that you should always be able to boot your device into this mode to RECOVER from a software problem; IE: flashing a bad ROM (IE: one that doesn't work and you can't start your phone anymore).
I don't really know a whole lot more than that, I just poke around and pretend like I do =)
Click to expand...
Click to collapse
Thanks As I learn more, I think I'm going to make a post that contains everything I learn, so others have it all in one place.
Well, there's a LOT to learn...like I said; complex arena. So much so that there's no way to make a single post take you from newbie to knowledgeable newbie in one read.
Then there's Google;
"what is rom"
"what is flashing rom"
"what is recovery mode android"
Eliminates the need for said post
Plus, by the time you get it all written, it will have all changed ^_^
Would it be posssible at all to cook up something like a fastbootable rooted tft? I tried several rooting/modding methods but was unabler to acheive what I wanted. I'm a little inbetween kind of geek knowing a little about UNIX/LINUX and still learning. The closest i came was the step where i was to flash CWM via fastboot but got shot down by a prompt telling me that remote command was not allowed. I even got to the point where I unlocked (or at least think i did) voiding all guarantee. Still optimistic since the device is extremely well made with many "root functions" built into the stock rom. But for some activities I believe I need root (wanting to optimize and tailormake my device). I think I would be able to rreach that point with the knowledge I have if I only could have fastboot allow me to flash a custom recovery. Any advice or pointers are highly appreciated since3 now that I am a sitting duck at least could get a small step forward. I realize the fact that I am vague in this questions but still no luck in this ball of confusion.
Happy weekend!!
Stop right here. Do not do anything to your device.
Grab a cup of coffee and read up.
Try to understand the basics about linux and android in general and not to forget to understand how the SONY Xperia phones work as they uses .ftf images and have no cwm to begin with..its not difficult if you come from another android device. Just some minor differences.
But:
Read, understand and learn before you attempt and proceed to do anything.
But:
Read, understand and learn before you attempt and proceed to do anything.[/QUOTE]
I appreciate your honest advice. Though I did mention that that was what I had done. I've spent hundreds If not thousands of hours reading. The reason why I posted was actually because despite reading and practising som of what I've read, I still cannot get root. I've had serveras devices built on linux (Android) as well as I'm starting to grasp the Linux CLI. I'm not saying that I have all information available but that I need help because there are several apps which I'd like who demands root access. These are mainly such apps that allows me to become more effecient and also customizing the UI. I hope you understand. Still in a humble mode I ask again for tips on how to root my ZU. There are actually quite a number of apps and guides that demands root and I feel that I've come to the point where I cannot get further without it. Though having said this I do understand your reply du to me being vague. Cheers!
But:
Read, understand and learn before you attempt and proceed to do anything.[/QUOTE]
I appreciate your honest advice. Though I did mention that that was what I had done. I've spent hundreds If not thousands of hours reading. The reason why I posted was actually because despite reading and practising som of what I've read, I still cannot get root. I've had serveras devices built on linux (Android) as well as I'm starting to grasp the Linux CLI. I'm not saying that I have all information available but that I need help because there are several apps which I'd like who demands root access. These are mainly such apps that allows me to become more effecient and also customizing the UI. I hope you understand. Still in a humble mode I ask again for tips on how to root my ZU. There are actually quite a number of apps and guides that demands root and I feel that I've come to the point where I cannot get further without it. Though having said this I do understand your reply du to me being vague. Cheers!
well its fairly simple on stock rom except on .257
*download fastboot files (if you have old version downloaded it will not work) http://developer.android.com/sdk/index.html
*download http://download.chainfire.eu/204
*download fastboot driver http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
*Install fastboot driver
*unlock bootloader http://unlockbootloader.sonymobile.com/
*flash custom recovery http://forum.xda-developers.com/showthread.php?t=2426739
*start phone and transfer CWM-SuperSU-v0.94.zip to internal memory
*reboot in to CWM and flash CWM-SuperSU-v0.94.zip
*start playstore and update supersu
*done
If you are on 257 and want to keep stock rom its a bit more tricky
http://forum.xda-developers.com/showthread.php?t=2502185
http://forum.xda-developers.com/showthread.php?t=2490613
If you do not want to keep stock rom then just unlock the bootloder, install cwm and transfer any rom and flash away
"If you are on 257 and want to keep stock rom its a bit more tricky"
Just my regular luck. Starting to feel like Donald Duck. I was not on .257 when I was ready to root. However since I made some tries with little reult I choose to upgrade to .257 so that is where I am now. Is there any tool like a tft flash tool so that I could downgrade to a previous tft and use your prescription?
Donald Duck Luck
"If you are on 257 and want to keep stock rom its a bit more tricky"
Just my regular luck. Starting to feel like Donald Duck. I was not on .257 when I was ready to root. However since I made some tries with little reult I choose to upgrade to .257 so that is where I am now. Is there any tool like a tft flash tool so that I could downgrade to a previous tft and use your prescription?
Everything SOLVED
Sorry about asking befor reading instructions but its ok now. I have CWM + root so satisfied. Thanks.
Hi,
I just got my HDX und now i want to install custom recovery and root the device. I have just a few questions before i do so an got no exect answers by searching the forum:
1. If I do a backup with custom recovery can I go fully back to stock?
2. Is there some sort of Factory Image to download to override custom revocery?
3. Can I Undo and go back to stock recovery If i have to send the device back to Amazon?
I just want to know if I can totaly revert all changes bevore I change something.
thx
maroc84 said:
Hi,
I just got my HDX und now i want to install custom recovery and root the device. I have just a few questions before i do so an got no exect answers by searching the forum:
1. If I do a backup with custom recovery can I go fully back to stock?
2. Is there some sort of Factory Image to download to override custom revocery?
3. Can I Undo and go back to stock recovery If i have to send the device back to Amazon?
I just want to know if I can totaly revert all changes bevore I change something.
thx
Click to expand...
Click to collapse
If you are new to this device you probably should read the first post here http://forum.xda-developers.com/showthread.php?t=2786190.. And the answer to all your questions are technically yes. If you do not brick or break your tablet anywhere along the way and providing that you are willing to do all homework necessary and then some before attempting to do anything.. You probably need to read through all the threads about brick devices to know what things not to attempt that will cause you to break your device.. Remember all the information is here if you learn how to use this forum and remember each section of the forum has several pages of threads of information.. You have a whole lot of reading to do if you do not want to end up another of this devices victims lmao
Don't get me wrong. I own a nexus 5 and the nexus 7 (2013) (rooted, custom kernel, exposed etc.) but due to the open system and bootloader so as the asop makes it easier to handle it. I already read the warnings but the Windows supported root tool should be a easy way.... not?
Okay obviously
maroc84 said:
Don't get me wrong. I own a nexus 5 and the nexus 7 (2013) (rooted, custom kernel, exposed etc.) but due to the open system and bootloader so as the asop makes it easier to handle it. I already read the warnings but the Windows supported root tool should be a easy way.... not?
Click to expand...
Click to collapse
there is not a problem getting it rooted you may have read the warning but you're not understanding it.The problem is not rooting the device. The problem is what people are deciding to do with their root access . And it may be my imagination or may not but this seems to be a favorite tablet for mommy and daddy to buy the kiddies.. Then they come here not knowing how to do their own research and find the easy way to root their device , There n fine there again not a real problem it's what they are doing ...BRICKING! There again not really a problem for me but when they come to this forum acting like somebody owes them something or somebody better step up and hurry hurry come help them fix their device before mommy and daddy find out ... Burying perfectly good information that I like to access under redundant questions because they are too lazy to do their own homework .. Repeatedly asking the same questions over and over again that have already been answered over and over again they just refuse to read the information and expect others to first to come to their special lil thread and inform them like this is kindergarten again . And somebody should be holding their hand because mommy and daddy bought them a special kindle fire..THAT IS LOCKED DOWN.. With no fast boot capabilities currently working there is a lot of talk about it but no consistent.... Repeat there is not a one click fix for this device ....... unlike most other tablets like I said one of your questions asked if you can just flash and fix ... At this time NO. If you really know what you are doing and you are not afraid of or can afford to turn your tablet into a paperweight.. There are ways to get your system flashed too repair mistakes or goofy behavior (even return to stock) but not from BRICK STATE. Long story short your 1 Click Easy Way to root.. Through ignorance, laziness , and the comprehension level of a fruit fly .. For this device in the wrong hands might as well be a sledge hammer ... Repeat in no way is a Nexus 5 ,at the moment remotely similar other then android base, to this tablet... Is what you should have gotten from the thread that I posted a link to... flash and modify at your own risk and Responsibly.. Nobody here is responsible for anything you do to your tablet. Or responsible for coming to rescue you if or when you screw it up... Please read all the brick threads to save everybody lots of famed face palms and headaches... Us and yourself trust me.
Thanks. I know it can be depressing to tell people "you question or problem was answered just two days ago, just read and collect the right information you need" I don't want to change necessary files like build.prop or do things where there is an exact warning to do so because it's not really stable...
The warning pinned to this forum just got me unquestioning if there are serious problems in every usually customisation (root, custom recovery, gapps) so doing just that could probably brick the tab because maybe the closed system makes everything risky and unpredictable in contrast to a vanilla android device.
well
maroc84 said:
Thanks. I know it can be depressing to tell people "you question or problem was answered just two days ago, just read and collect the right information you need" I don't want to change necessary files like build.prop or do things where there is an exact warning to do so because it's not really stable...
The warning pinned to this forum just got me unquestioning if there are serious problems in every usually customisation (root, custom recovery, gapps) so doing just that could probably brick the tab because maybe the closed system makes everything risky and unpredictable in contrast to a vanilla android device.
Click to expand...
Click to collapse
Well for example I am only a mechanic I'm 42 years old I am not well-versed in computers but android have been a hobby of mine for about five years .. But I have very little problems following directions. And I have been able to accomplish anything I wanted to do with many many phones and tablets including this one... So if you're willing and have the understanding that this thing is very fickle and likes to actup
Where other devices would not be problems... It can be a very nice device for the right person and a very big headache for the wrong one. There are currently a lot a bugs with pretty much anything that you try to do with this thing if not done with absolute precision and patience. And perseverance. I currently own three different HDX tablets with several other Samsung.. And I switch frequently. I do have Google on my HDX but I do not depend on them for all of my Google needs. Remember at least for now while these things are locked up tight they are pretty much only an Amazon media device along with if you are willing to brave and yada yada yada you may get some Google services working like many of us have. Enjoy all of my HDX thoroughly but I also have a understanding of the current limitations.