Hey guys
I have a lgp500 phone and i am thinking of rooting my phone, as i hate the touchscreen bug that makes the cpu go 100%, soo laggy
anyways i have a few questions that i would like to know about rooting before i attempt it.
firstly ill start by listing my phone software etc
Android version - 2.2.1
Kernal Version - 2.6.32.9
Build Number - FRG83
Software Version - V10b-DEC-13-2010
and now my questions
1. Well the most obvious question. Is it possible to root my phone?
2. My main ques - What are the chances of bricking my phone? as in to a point that would leave my phone completely useless.
3.At what steps of the rooting process can the phone be bricked?
4. How does rooting work? - basically i just want to learn about everything so i know how the system works and how kernal etc work - so that i wont do anything stupid when im rooting
for now thats all, but ill probly have a alot more once i get answers to these
please help
thanks
first of all u will need to downgrade to android 2.2.then u can root it and enjoy!
Ramis93 said:
1. Well the most obvious question. Is it possible to root my phone?
Click to expand...
Click to collapse
Not yet. Android 2.2.1 is not rootable at the moment. A downgrade to v2.2 is necessary, as upendra_p said.
Ramis93 said:
2. My main ques - What are the chances of bricking my phone? as in to a point that would leave my phone completely useless.
Click to expand...
Click to collapse
Chances are very small, but there are.
Ramis93 said:
3.At what steps of the rooting process can the phone be bricked?
Click to expand...
Click to collapse
At the downgrade, when you have to flash the phone with a different Android version using an application that sometimes fails. But that's rare.
Ramis93 said:
4. How does rooting work? - basically i just want to learn about everything so i know how the system works and how kernal etc work - so that i wont do anything stupid when im rooting
Click to expand...
Click to collapse
"Rooting" simply gives various applications wider system rights, so that they are able to perform actions otherwise forbidden, such as messing with system settings and allowing critical system files to be modified or deleted. It also is an important step needed if you decide to install a custom ROM -- a modified and (usually) improved version of Android.
Rooting is not for the faint of the heart
However, keep in mind that you can find all the help you need on this forums...
masteryx said:
Not yet. Android 2.2.1 is not rootable at the moment. A downgrade to v2.2 is necessary, as upendra_p said.
Chances are very small, but there are.
At the downgrade, when you have to flash the phone with a different Android version using an application that sometimes fails. But that's rare.
"Rooting" simply gives various applications wider system rights, so that they are able to perform actions otherwise forbidden, such as messing with system settings and allowing critical system files to be modified or deleted. It also is an important step needed if you decide to install a custom ROM -- a modified and (usually) improved version of Android.
Click to expand...
Click to collapse
about the chances on bricking my phone, i understand they are small
but approximately how small? like a number?
i understand its different for each phone, so how much would it be for my phone?
Well it depends on how well you read and follow the instructions.
I have installed Custom ROMs on a total of 3 phones with 100% success.
And in short Rooting is like being Administrator in Windows, you can do anything you feel like doing, even if that means bricking your device.
Ramis93 said:
about the chances on bricking my phone, i understand they are small
but approximately how small? like a number?
i understand its different for each phone, so how much would it be for my phone?
Click to expand...
Click to collapse
It's not the phone it's usually the user. You should never attempt to mess with something unless you know what you're doing. Take that from someone who actually bricked his phone by not knowing enough.
Best advice against bricking is never try to flash something that's not meant for your specific device.
And if you wanna put a number on it post your IQ.
Ahmmm... i just used z4root and in just one click, im already rooted. Very easy XD. The part where you should be cautious about is flashing back to android 2.2 that is where a lot of p500 get brick. Just read the forums more.
Sent from my LG-P500 using XDA App
@OP, just take note of the important steps & thing you should check before proceeding like turning LG modem off in device manager. though my friends have downgraded even without checking that option, its always better to follow the instruction to be safe.
& also after rooting, take your time when installing custom recovery. it is also responsible for bricking quite a few mobiles. i'll advice copy paste the commands to avoid any typo.
Related
I tried searching for a how-to on this but apparently I'm searching inclined.
From what I can gather is it as simple as just dumping the zip onto the root of your SD card and doing:
3. Make sure phone is off then hold Power button and Call Button.
4. The menu opens quickly press the power key over the hboot option.
5. Follow onscreen instructions to install the update. the phone will reboot a few times.
you dont even need to search. go to the development section and then look at the top few, it will have very detailed instructions.
I guess I should have elaborated more and said I don't have my phone rooted and really don't want to go that route. I was just getting confused because everything i was finding on here was people running root but I came across a few things where people said the 2.1OTA Leak was just a straight upgrade, so that is my confusion.
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
but if you have root you can do the downgrade back to 1.5
Android22 said:
but if you have root you can do the downgrade back to 1.5
Click to expand...
Click to collapse
Oh right, I forgot about that, duh It just seems like root would be a better choice.
But to each his own.
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
yeah that is my question, can 2.1OTA just be flashed or does your phone need to be rooted?
I just feel like with root I'll be more likely to kill the phone but I'm going to check into it more again.
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
rheally said:
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
Click to expand...
Click to collapse
yeah I was just reading the thread on going from stock 1.5 to rooted 2.1. Can you give me some of the major benefits of rooting? I'm trying to find really practical stuff, not just the "Well it's cool cause it's like being root in Linux".
And just to clarify you can just flash to 2.1OTA? I'm skeptical of doing that now because I was reading some people think 2.1OTA has a time sensitive date on it.
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Marisa said:
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Click to expand...
Click to collapse
Can you point me to a good nandroid tutorial? tried searching for one but if you know of a good one I'd appreciate it.
I was trying to find a nandroid guide when I did it the first time, but once I discovered that Amon_RA's recovery has it built-in, I decided to wing it and see what happened. It was a lot easier than I expected to be honest.
Reboot your phone into recovery (VOL UP + Power), you should have a short list of options, one of which should be Backup/Restore. Trackball into it and select to make a backup. Let it do it's thing, should take a few minutes. Congratulations, you've made a backup of your phone. You can make as many as you like, they're given names based on the date and time they're created, but you can rename without harm (barring a few characters keep it A-Z a-z 0-9 and you should be good)
Restoring to that backup is as easy as entering the same menu but picking restore instead. You need to have made a backup first in order to restore something.
NOTE: I've written all this by memory, and while it should be fairly accurate, I can't turn my phone off currently to double check that the wording is all correct.
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
I have an application that I write to make going from 1.5 to root a lot easier with a gui application. It will be released very soon for everyone to use. Take a look at my thread for more info. Link is at the top of my signature.
Sent from my Eris using the XDA mobile application powered by Tapatalk
frankspin said:
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
Click to expand...
Click to collapse
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Marisa said:
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Click to expand...
Click to collapse
AWESOME! Thank you I am doing it right now.
NM: got it
Well I got 2.1 on but I did something wrong and can't load rooted 2.1. I get "signature verification failed" message when I load the zip file.
hi i just got an atrix, switched over from jailbroken iphone.
I went through rooting it and installed rom manager but when i try to reset permissions i get an error and when i try to reboot into recovery it says "failed to boot 2 starting rsd" and hangs.
I just want to reset the phone to stock and start the process over, can someone give me some help on this....
Id like to install the ninja rom. but im lost about what order to do things, root, backup/nandroid, and install new rom etc.
thanks
First, it would be nice to know what was on the phone when you started? 1.8.3, 1.2.6 or 4.9.1?
Next, where are you trying to go? You installed the ROM Manager, does that mean you were going to try to use a particular ROM?
Probably more important, the ROM Manager is not fully compatible with the Atrix (see thread).
Before going forward, I would suggest reading (and re-reading) this thread about the bricking potential. Don't get me wrong, it is possible to add custom ROMs to your Atrix, you just need to be cautious.
At this point, it doesn't sound like your Atrix is hard bricked. However, to help out, we need a little more information.
kwick60073 said:
First, it would be nice to know what was on the phone when you started? 1.8.3, 1.2.6 or 4.9.1?
Next, where are you trying to go? You installed the ROM Manager, does that mean you were going to try to use a particular ROM?
Probably more important, the ROM Manager is not fully compatible with the Atrix (see thread).
Before going forward, I would suggest reading (and re-reading) this thread about the bricking potential. Don't get me wrong, it is possible to add custom ROMs to your Atrix, you just need to be cautious.
At this point, it doesn't sound like your Atrix is hard bricked. However, to help out, we need a little more information.
Click to expand...
Click to collapse
ya its not hard bricked, i pulled out the battery and it starts and runs normal. it says its android ver. 2.3.4 and baseband 1.77.30p build number 4.5.91
you know to be honest im pretty happy with it out of the box... adding non-market apps would be nice and id like to be able to make full backups to boot from if i need to. id like to delete some apps i dont need.
it seemed like there was a problem with the rooting i did cause some stuff wasnt working like 'shootme' screengrab app and the permissions fixing wasnt working.
thanks for your help i really appreciate it!
You can try this to root:
http://forum.xda-developers.com/showthread.php?t=1182871
I don't know if that allows for enabling side-loading or not.
cmontboober said:
ya its not hard bricked, i pulled out the battery and it starts and runs normal. it says its android ver. 2.3.4 and baseband 1.77.30p build number 4.5.91
you know to be honest im pretty happy with it out of the box... adding non-market apps would be nice and id like to be able to make full backups to boot from if i need to. id like to delete some apps i dont need.
it seemed like there was a problem with the rooting i did cause some stuff wasnt working like 'shootme' screengrab app and the permissions fixing wasnt working.
thanks for your help i really appreciate it!
Click to expand...
Click to collapse
Enabling non-market apps is a built in feature for 2.3.4, go to Settings -> Applications, and put a check mark next to "Unknown Sources".
For rooting, try Gingerbreak.
For backing up, there's a CWM version that doesn't need an unlocked bootloader, but I am unlocked so I don't have experience installing it / using it.
Since most people are unlocked, I am not sure if the non-unlocked version of CWM was kept up to date, it might be obsolete / non functional by now.
xploited said:
Enabling non-market apps is a built in feature for 2.3.4, go to Settings -> Applications, and put a check mark next to "Unknown Sources".
For rooting, try Gingerbreak.
For backing up, there's a CWM version that doesn't need an unlocked bootloader, but I am unlocked so I don't have experience installing it / using it.
Since most people are unlocked, I am not sure if the non-unlocked version of CWM was kept up to date, it might be obsolete / non functional by now.
Click to expand...
Click to collapse
for rooting it again do i need to get it back to completely stock or just use gingerbreak on it as it is now?
thanks for all the help everyone.
cmontboober said:
for rooting it again do i need to get it back to completely stock or just use gingerbreak on it as it is now?
thanks for all the help everyone.
Click to expand...
Click to collapse
You can root at any point. Gingerbreak should work fine if you have usb debugging enabled.
how can i do a factory restore, setting it back to how it came out of the box? also, any tips on maintenance to keep it running fast?
thanks again for all the help
cmontboober said:
how can i do a factory restore, setting it back to how it came out of the box? also, any tips on maintenance to keep it running fast?
thanks again for all the help
Click to expand...
Click to collapse
That largely depends on your setup BL / CWM ,etc...
You might wanna read this guide to clear up many things:
http://forum.xda-developers.com/showthread.php?t=1154600
Ok I need help i have just Unlocked my prime , and I have a lot of questions. First let me say Im aking because i have already researched so please no smart a$$ comments! I am on ICS .28
1) what do I do next?
2) do i need to root or do the roms give me root
3) do i need to do nv flash i looked at the instructions and im lost.
4) I dont have any other progrms so not sure what i need
5) do I install clockwork recovery mod or twrp does it matter?
I really need help to make my prime great , please help!!!!!!
jaisan72980 said:
Ok I need help i have just Unlocked my prime , and I have a lot of questions. First let me say Im aking because i have already researched so please no smart a$$ comments !
Click to expand...
Click to collapse
Simple advice: read more! The questions you ask are all very basic and have been answered in depth on this forum. It is really important you understand what you are doing before proceeding further since Asus in their wisdom have adopted a policy which makes their devices particularly easy to brick.
It is a very good thing you are on ICS so whether you find it difficult or not your first step must be to understand and implement NVFlash. This is your insurance policy and you really should go no further without it .
Why exactly did you unlock your Prime? What was the limitation or the roadblock that you ran into that unlocking solved?
Jgrimoldy said:
Why exactly did you unlock your Prime? What was the limitation or the roadblock that you ran into that unlocking solved?
Click to expand...
Click to collapse
did you miss this part "to make my prime great"?
whycali said:
did you miss this part "to make my prime great"?
Click to expand...
Click to collapse
Actually, I saw that. I was a little curious about specifics. Among the countless threads of folks bricking their Primes, it's amusing to read a justification of "to make it great".
I partially unlocked in order to replace the stock ROM with one that didn't have a gimped download manager. The default download manager will give a fake error and then actively delete the file upon completing any .APK (yes, it judges on the extension) download from a website that doesn't give it specific headers, which is used to stop people from pirating apps via common file sharing sites (which are not set to give these headers)... but also stops a lot of normal android dev page downloads from working as well (for example emulator programs not available in the market).
Previously I needed to download things with Opera (which has it's own download manager and thus doesn't pass files to the stock one) in order to get around this anti-piracy code, but that's just a chore. After swapping ROMs, I haven't had that happen (though the ROM I swapped to forgot to remove similar protection on bluetooth files, which I'm going to report now as soon as I get 10 damn posts).
Also when I updated to Jelly Bean, I lost root (Voodoo root keeper was used but it failed, read around to see I'm not the only one that had the root backup wiped out when doing the official Jelly Bean upgrade), and so far unlocking in order to be able to flash custom updates is the only way to regain it.
Anyways the OP will want to install some recovery.flash thing like TWRP so they can flash their own files to the ROM, like the su binary, which is needed to root.
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Wow, a lot of demands. Why not start here, as it should answer many of your questions. Threads are stickied for a reason.
http://forum.xda-developers.com/showthread.php?t=2024207
Mandolin Bee said:
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Click to expand...
Click to collapse
Touch wiz is a style of ROM if you will.
Touch wiz roms for Samsung.
Motor blur roms for Motorola.
Sense roms for HTC
Aosp roms for nexus phones.
When you have a "touch wiz ROM"
It builds from the stock base code basically. They add freatures and themes and basically ROMs are endless to what they can do.
My phone never tells me about OTAs.
I believe the only time they do this is when on a stock rooted ROM is when something bad could go wrong
Never had any problems on custom ROMs however.
Next,
Bricked devices are very rare and only happen out of stupidity or carelessness in most cases.
Google will tell you how to fix. But I wouldn't worry about it.
As a very frequent flasher of ROMs I have experienced many of times a soft brick. Or a phone in boot loop.
This is when the device powers on but will not boot up. ( stuck on boot animation or splash screen are most common.)
ALL OF THESE ARE FIXABLE.
You can always wipe in a recovery and normally that fixes it.
Soft bricks normally happen from not wiping or bad download.
Also remember you have Odin as a last resort.
Also you can read the sticky threads in android development to figure out how to unroot
They will give you a better explanation on how to do so.
All this is answered by xda and Google.
They are what taught me what I know
They will teach you as well over time.
PM me if you have any other questions
Hit the thanks button so I feel important!
Haha
God bless the American people.
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.