Database Develop

HTC Reviewing Its Bootloader Policy - Facebook Update

HTC are reviewing the locked bootloader policy.
http://www.facebook.com/notes/htc/update-on-bootloaders/10150305151453084
and ...
http://wakeuphtc.blogspot.com/

If this works, it'll be the best rhing htc did in a long time.
Sent from my HTC Incredible S using XDA App

This is a post to shut up the masses stay loud my friends, stay loud until they clearly state that they will unlock those bootloaders
Sent from my PC36100 using XDA App

Jbcarrera said:
This is a post to shut up the masses stay loud my friends, stay loud until they clearly state that they will unlock those bootloaders
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I don't thinks so. This statment even more gives power to our voices. Look at Google and see a lot of big tech forums like "androidpolice" refer to.

Well they had better, i dont want to be moving to samsung, HOWEVER, push comes to shove and no root for my currently s-on incredible s? it will be done :/

I think it is time to let companies know the power of the pro-user. I am constantly recommending people against buying an HTC. They trust me for all their review. On every forum, we must absolutely not recommend anyone an HTC. All of it can be done without lying.
Example:
n00b question: "hey, should I buy the HTC sensation?"
Reply: "No. The bootloader is locked. You'll only be able to run what HTC wants you to run. You either buy a Samsung, or simply get an iPhone."
Yes, the opinion is slightly biased, and hides some information (like the user might never need root). However, as someone who has the privilege of recommending devices to others - How much I disclose, and how neutral I should be, is not covered by the any covenant. So.. screw you HTC. Everyday, I'll try and persuade, at least, one person to not buy an HTC - till you unlock!

eternalhate said:
I think it is time to let companies know the power of the pro-user. I am constantly recommending people against buying an HTC. They trust me for all their review. On every forum, we must absolutely not recommend anyone an HTC. All of it can be done without lying.
Example:
n00b question: "hey, should I buy the HTC sensation?"
Reply: "No. The bootloader is locked. You'll only be able to run what HTC wants you to run. You either buy a Samsung, or simply get an iPhone."
Yes, the opinion is slightly biased, and hides some information (like the user might never need root). However, as someone who has the privilege of recommending devices to others - How much I disclose, and how neutral I should be, is not covered by the any covenant. So.. screw you HTC. Everyday, I'll try and persuade, at least, one person to not buy an HTC - till you unlock!
Click to expand...
Click to collapse
I feel the same way
HTC- YOU LOCK WE WALK!!!!

eternalhate said:
I think it is time to let companies know the power of the pro-user. I am constantly recommending people against buying an HTC. They trust me for all their review. On every forum, we must absolutely not recommend anyone an HTC. All of it can be done without lying.
Example:
n00b question: "hey, should I buy the HTC sensation?"
Reply: "No. The bootloader is locked. You'll only be able to run what HTC wants you to run. You either buy a Samsung, or simply get an iPhone."
Yes, the opinion is slightly biased, and hides some information (like the user might never need root). However, as someone who has the privilege of recommending devices to others - How much I disclose, and how neutral I should be, is not covered by the any covenant. So.. screw you HTC. Everyday, I'll try and persuade, at least, one person to not buy an HTC - till you unlock!
Click to expand...
Click to collapse
Count of people I got to buy non HTC phones = 12 and counting
I love sense. The only reason I say no is the boot loader. Free our phones. Now!

cooljais said:
If this works, it'll be the best rhing htc did in a long time.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Actually, it'll just be undoing the worst thing they've done in a long time.

I wrote a two page letter to HTC today one part with personal data and why the S-ON device is not good for me and the other part from the example letter that is posted to the first post blog.
I send it via e-mail directly to some addresses and also via the HTC support..
and here's the reply..
Thank you for contacting us,
We cannot comment on whether or not HTC has blocked any customer from rooting or hacking their phone. Rooting the phone may open the phone up to virus attacks and other unsecure activities, as well as introduce unintended functionality, and as such is very difficult for us to support.
You are a valued HTC customer, thank you so much for your feedback, we will be communicating them to the department in charge, please note that we are glad to offer assistance whenever needed, if you have any further inquiries kindly don't hesitate to contact us.
Click to expand...
Click to collapse
How typical..

It goes without saying that there are benefits to making it difficult to root your phone. A prime example is that once you root your phone. All of your account passwords are unencrypted.
That said, perhaps if the phones were easier to root people would put resources into making sure they're re-encrypted with a good ROM.
But ultimately every user deserves freedom of choice and if rooting my phone is the best/simplest/easiest way for me to uninstall bloatware/configure it as per I need it, then its clearly the best option. Freedom is the key here. Every single user should have a choice.

For Virgin Mobile Canada Users!!!

I emailed HTC and Virgin Mobile Canada the other day, and they said this,
"Thank you for taking the time to reply. We currently do not have the information available to us. At this time the Incredible S's that are slated to receive the ICS update are the ones in the European regions. You may visit htc.com, twitter.com/htc and facebook.com/htc for update information as it becomes announced."
Virgin Mobile said this,
"You've reached ****** with Virgin Mobile! First, allow me to apologize for the delay in my response. Your patience and understanding are appreciated. I'm happy to escalate your feedback about the Android 4.0 update. I know this is important to you and I'm happy to point you in the right direction.
******, I've escalated your email to ensure it's reviewed. Thank you for taking the time to share your feedback." This could mean that we
IncS users might see an Android 4.0 update! Virgin Mobile is BAD for updating their phones, but as you may already know, HTC has been working their hardest to work with carriers, and as VMC's update stated that they are happy to point me/us in the right direction, and will escalate it to ensure its reviewed!
Edit!: I emailed Virgin again, and they said that they are working very hard to get this update available! NOW im excited!
Sent from my HTC Incredible S using XDA

Good to hear. I'm with SaskTel which is in a similar vain, and even though I'm installing custom ICS ROMs anyways, it would be nice to see everyone get the update and move to ICS.
Though then, I'd have to stop joking that I'm in the 1%.

I rooted once, but i had to send my phone to get fixed, because it had a charge port malfunction, and they charged $200 to fix it because of the root access, so i am running all stock, which is why i am excited for VM to work out something with HTC
Sent from my HTC Incredible S using XDA

So you came at XDA-Developers to find help? (Beginners Thread)

So you came at XDA-Developers to find help? Well, this is your thread!
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime"​
Hello new user and welcome to XDA-Developers. We are a developer’s forum, with the purpose of development. Our work can be used in several ways, and, we know that sometimes it could help you. So, in order to maintain our forums clean and properly organized maintaining a proper development environment while at the same time to give you a chance to join our forums we created this thread.
This thread is for sensible questions from new or inexpert users. If you think your question may be a little basic for a developer forum then this is the place to ask it.
Here you shall find an atmosphere free of prejudice, where we will try to help you in your problem, answer yourmost basic questions and aid you on troubleshooting your device. We know that learning all the technicalities takes time, however they are necessary in order to interact with us.
Bare in mind that we are not technical support, we do not work for any company or get paid to help, we are just independent developers gathered in a community called XDA-Developers. Therefore all we will do is guide you into troubleshooting your device yourself, but under no circumstance we are abided to do so.
We want you to become the kind of user we see as productiveto a developer’s community, and why not?, to be a developer yourself!
Note to General users:
This is a chance for more advanced users to “give back” at XDA-Developers the knowledge we have gathered together in a decade of development. This is a thread to behave in a tolerant way, taking into consideration that the user posting queries might have never even heard words such as “adb” or “ROM", so, if you are not willing to be helpful, I kindly invite you to browse into another thread.
"Time has changed, Users have changed and so will XDA-Developers"​
Moderators will not tolerate "flaming" or "trolling" in this thread as it is specifically provided for those who are still learning the basics.. We will delete and sanction without warning any post that show intention other than to help the new user.​

Okay, then, I have a newbie question: can someone explain exactly what "S-Off" means?

Take S-Off for Security Off. With S-Off you can directly write to kernel, bootladers and radio, while S-On devices would need a second device (a PC) to write to those areas. Its like a protection mechanism for us not to brick our phones (at least not as easy).
There is plenty of explanations at our forums if you want t get into technical details or just want another explanation. Just try using the search button in the right top corner of XDA pages, you will be amazed how much you can find .
D.O.C
XDA Developers Senior Moderator

I'd go on with another newbie question.
If I'm not wrong rooting breaks warranty (in most of the cases at least) but I think (again im not sure) we can reboot our device to factory settings before giving it to technical service to fix its problems.
What happens if the device is not working? Is there an external way to fix the rooted system back to normal?

I am going to go with a NO in that subject.
Although there are plenty of methods that have been successful in several handsets in the past by using third party hardware, it can get complicated even for a advanced users to do so, since it might involve technichal aspects only manufacturers know about.
Normally, these methods are developed and posted here, depeding on the handset, it might be easy or not. Not so many years ago, these methods were as easy as flashing a "untouched" firmware, but lately, manufacturers have been implementing methods to detect if we have touched the bootloader and have increasingly making it harder for developers to break them, thus returning to a "factory untouched" state is getting harder with every new device.
In short, If you want your warranty intact beyond the existence of any doubt, do not root.

And why is my galaxy tab crushing with cm 10 mod with latest gapps. I dont really think it is a noob question.

Guys, please keep your questions device specific.
We can't be discussing Galaxy Tabs here.
Thanks

I have a problem and I'm new here, so I just reply in this topic. I'm sorry for my little English.
I have a HTC One S and I dropped it a few days ago, now the volume down button is dented and I can not use it anymore. Since you can still set te volume by pushing the volume up button and swipe the volume down, i thought it was ok.
Now I wanted to turn my phone off and this is what I've got:
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
HBOOT
<VOL UP> to previous item
<VOL DOWN. to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
Using the volume up button I can select one of the items, but pressing the powerbutton brings me nothing. I have no idea what to do or how I can fix this.
Please help!
I see this is the wrong topic but I am unable to delete this message, I'm sorry.

Well, it is a hardware fault since its broken, so not much we can help you here. Try maybe reading the HTC One S specific forums to find a workaround, but honestly, you better replace the handset.

I have two good question. What is the difference between the HTC One developer edition and the regular one (ha).
What I've seen made it look you would struggle with putting roms on the regular one.
Also, how soon is the one likely to have roms and people putting the latest android on it (like pure nexus jelly bean)? Like a couple months, a year?
Thanks for your help

TaderTot said:
I have two good question. What is the difference between the HTC One developer edition and the regular one (ha).
What I've seen made it look you would struggle with putting roms on the regular one.
Also, how soon is the one likely to have roms and people putting the latest android on it (like pure nexus jelly bean)? Like a couple months, a year?
Thanks for your help
Click to expand...
Click to collapse
The difference of the Developer Edition and regular one is that it is already S-Off, unlocked bootloader(no need to go to HTC dev) and has 64GB storage. And it comes only on one variant which is a US LTE type. So LTE won't work on Europe or Asia.
Regarding AOSP(pure nexus ROM) probably less than a month after the release of kernel source code by HTC on which I dunno when it would come.

So this will be my first non-nexus device. Will there be custom roms that will be up to date with the latest version of Android so I don't have to wait for HTC? If so, how will their stability be?

xGary said:
So this will be my first non-nexus device. Will there be custom roms that will be up to date with the latest version of Android so I don't have to wait for HTC? If so, how will their stability be?
Click to expand...
Click to collapse
Give it time and there will be. I'm sure they'll be stable enough when released anyway.
I'm also coming from a Nexus and is a first for me to be getting a HTC.

It is possible to use the EU version of the HTC One in the US? I'm debating between the developer version and the EU since I'm located in the US (and want an unlocked bootloader), but it looks like the EU version would work on AT&T?
HSPA/WCDMA:
Europe/Asia: 850/900/1900/2100 MHz
GSM/GPRS/EDGE:
850/900/1800/1900 MHz
LTE:
EU: 800/1800/2600 MHz
US (AT&T): 700/850/AWS/1900 MHz
US (TMO): 700/AWS MHz
US (Sprint): 1900 MHz
Asia: 1800/2600 Mhz
Click to expand...
Click to collapse

Yeah it looks like it, but, if you want an unlocked bootloader, developers edition should be your choice (that is what I would do)

Hi ! i am totaly new to Android Os so plz help me !!!
Hi
recently i bought HTC Desire A8181(Bravo).
i want to upgrade its software to Android v4.xxx . so i need help which firmware should i install on my HTC Desire so it work perfectly and has no Bugs ... Plz help me and guide me so i update my Phone
Thanks and also plz tell me Whats are Those ROMS ???

naeembabakheil said:
Hi
recently i bought HTC Desire A8181(Bravo).
i want to upgrade its software to Android v4.xxx . so i need help which firmware should i install on my HTC Desire so it work perfectly and has no Bugs ... Plz help me and guide me so i update my Phone
Thanks and also plz tell me Whats are Those ROMS ???
Click to expand...
Click to collapse
Hi naeembakakheil.
First thing you might want to do when looking for firmwares for your mobile device, is look in the correct section. Try here for your device specific info.
Second, please browse through those forums, read the OP of each thread which includes the description of the ROM you are about to flash, and then, read through the replies your fellow users have left to see their impressions, you can usually find all the help you need by reading. This would be a good place to start. If you still have any doubts, then ask in the appropriate thread. If after extensive search you still do not find the appropriate answer to your question, then ask in the Q&A forum of the device (although if you do know how to search, you will hardly ever need to open a new thread, almost every question is already answered).
What you must not do ever is.....ask without reading or even worst, read the incorrect information (as in not your phone's forum), you could easily break your device useless by making that mistake.

When can we expect 4.2 ROMs for the HTC One?

amarshonarbangla said:
When can we expect 4.2 ROMs for the HTC One?
Click to expand...
Click to collapse
No one can possibly tell you that. As a matter of fact, XDA was founded because of the same queries arouse between members...until they started building themselves. So, I kindly invite you to join our developer communitty and build yourself a 4.2 or at least get invokved in the process.
I wouldnt recommend coming to xda with expectations of the arrival of something, since it can be a very long and boring time . Its best to be involved in the making of things here at xda, that way I guarantee you will not get bored and eventually, you will get what you want.

D.O.C said:
No one can possibly tell you that. As a matter of fact, XDA was founded because of the same queries arouse between members...until they started building themselves. So, I kindly invite you to join our developer communitty and build yourself a 4.2 or at least get invokved in the process.
I wouldnt recommend coming to xda with expectations of the arrival of something, since it can be a very long and boring time . Its best to be involved in the making of things here at xda, that way I guarantee you will not get bored and eventually, you will get what you want.
Click to expand...
Click to collapse
I am a long time iOS user who recently switched to Windows Phone 8. Seeing how customizable Android is, I am thinking of making the jump soon. I have a lot of things to learn about this wonderful operating system, which is why I joined XDA
What goes into making a custom ROM? Do we need any specific files/firmwares/kernels/drivers from HTC to make a 4.2 ROM? Are there not any devs working on 4.2 ROMs for the One?

Google does NOT care if you root your Nexus!

I've seen a lot of people fretting about being able to RMA their nexus after unlocking/rooting/trying different ROMS & kernels. Likewise there are conversations about & guides about how to reset the device to hide the fact it has ever been unlocked. This is all an absolutely unnecessary worry.
So, to put everyone at ease I share with all XDA'rs the answer I got from Google when I asked "Hey guys, will rooting wreck my warranty?" I think you will all find this to utterly unambiguous.
Thank you for contacting Google!
Warranties and RMA are still covered *regardless* if a device was rooted.
We are not trying to prevent customers from unlocking the bootloader and installing a new operating system that allows for "rooting".
Android has always provided customers the ability to do that on Nexus devices, and encouraged other OEMs to do the same. So in that sense we are not against "rooting."
This being said, we can't guarantee full advertised/promised functionality if the source code for the Android OS has been modified as the functionality may have changed.
Click to expand...
Click to collapse
There you go folks, it's a developer's device so use it to it's full potential. This appears to be Google boilerplate so you're looking at an off-the-cuff response from some random support staffer. (I couldn't import the pretty formatting.)
Think any other brand/manufacturer would have a similar answer to the same question?
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
EDIT: Just to clarify, this about Google's North American policy - it appears that they follow this throughout Europe as well, and that European law probably reinforces this. Still, it can't hurt for anyone to check with Google themselves. Also, as per the thread title, this is about Google. If your warranty is held by anyone else this info may have no relevance at all.

NotFromMountainView said:
I've...
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
Click to expand...
Click to collapse
Is this real? I know they don't care, but would they really say it in writing? Do you have the actual email?

aooga said:
Is this real? I know they don't care, but would they really say it in writing? Do you have the actual email?
Click to expand...
Click to collapse
Yes, I just cut & pasted the actual response as I got it -- but lost the *bullet point formatting. Other than that I omitted the Dear [my name] & the rest of the boilerplate about contacting Google for any other follow-up or other questions.
I understand your question it sounds almost too good to be true.

This is fantastic. Thanks for sharing.

NotFromMountainView said:
Yes, I just cut & pasted the actual response as I got it -- but lost the *bullet point formatting. Other than that I omitted the Dear [my name] & the rest of the boilerplate about contacting Google for any other follow-up or other questions.
I understand your question it sounds almost too good to be true.
Click to expand...
Click to collapse
Cool. Good to know.

They provided us with the tools to unlock/lock our bootloader and set up a website to show us exactly how to do it. I think it couldn't be anymore obvious that they don't care that you stuck some binaries on the /system partition so you could run Titanium Backup

NotFromMountainView said:
I've seen a lot of people fretting about being able to RMA their nexus after unlocking/rooting/trying different ROMS & kernels. Likewise there are conversations about & guides about how to reset the device to hide the fact it has ever been unlocked. This is all an absolutely unnecessary worry.
So, to put everyone at ease I share with all XDA'rs the answer I got from Google when I asked "Hey guys, will rooting wreck my warranty?" I think you will all find this to utterly unambiguous.
There you go folks, it's a developer's device so use it to it's full potential. This appears to be Google boilerplate so you're looking at an off-the-cuff response from some random support staffer. (I couldn't import the pretty formatting.)
Think any other brand/manufacturer would have a similar answer to the same question?
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
Click to expand...
Click to collapse
Sorry little edit. Its not advertised as a developers device. Nowhere in google's ads or their nexus page does it says "developer". I'd still be wary of RMA with root if you highly modified system apps and such.
Sent from my Nexus 5 using xda app-developers app

monkeypaws said:
Sorry little edit. Its not advertised as a developers device. Nowhere in google's ads or their nexus page does it says "developer". I'd still be wary of RMA with root if you highly modified system apps and such.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
It never hurts to be wary. And it anyone managed to overclock the device so astronomically that it burst into flames there may be some pushback from Google. But the email is, as I said, unambiguous.
As to the suggested edit, I never said anything about advertising, but certainly you can tap 7 times and be rewarded with "Congratulations, you are now a developer!" That, as well as well as crachel's point seem to weigh towards it being referred to as a developer's device -- at least casually.

yup. ive always told people that if its a hardware issue, google will rma it, even if its rooted. but if its a software issue, most likely they wont. google themselves looked for a way to give us the means to unlock our bootloaders, and fastboot oem unlock is the gift they gave us with the nexus one
i myself have sent in devices that are still rooted, with custom roms, to get rma'd. google never gave me issue.

simms22 said:
yup. ive always told people that if its a hardware issue, google will rma it, even if its rooted. but if its a software issue, most likely they wont. google themselves looked for a way to give us the means to unlock our bootloaders, and fastboot oem unlock is the gift they gave us with the nexus one
i myself have sent in devices that are still rooted, with custom roms, to get rma'd. google never gave me issue.
Click to expand...
Click to collapse
simms22: My guess is that if there's any question of the problem actually being a custom OS issue just re-flash/reset to stock & any remaining hardware issues will be dealt with by Google. My key point was that nobody need worry about resetting any flag that it had been unlocked at some point. From your experience & what they've said and done I think it would take some phenomenally destructive code before they'd even raise the issue.

NotFromMountainView said:
simms22: My guess is that if there's any question of the problem actually being a custom OS issue just re-flash/reset to stock & any remaining hardware issues will be dealt with by Google. My key point was that nobody need worry about resetting any flag that it had been unlocked at some point. From your experience & what they've said and done I think it would take some phenomenally destructive code before they'd even raise the issue.
Click to expand...
Click to collapse
when the nexus one just came out, there was a big name google developer that stopped in xda and helped us out every once in a while. i wish i could remember his name. sometimes we even got "leaked" code directly from google. that would never have happened if google cared that we had root.

simms22 said:
when the nexus one just came out, there was a big name google developer that stopped in xda and helped us out every once in a while. i wish i could remember his name. sometimes we even got "leaked" code directly from google. that would never have happened if google cared that we had root.
Click to expand...
Click to collapse
That is just great! And just one more reason that I find it really hard to become overwrought over rattling buttons.
An obvious extension of this is that on support calls (or email) one can mention root/kernel/ROM without fear. Heck, Google might even want to know how mods perform.

But this is till the time we can RMA it which google is handling but when our warranty will expire we will have take it to Lg service center and I doubt that they will also give the same reply.
Policies for both of them must be different.

LG will most likely not be so understanding regarding rooting in country`s where there you can`t buy a Nexus in the Play store but in a shop.

gee2012 said:
LG will most likely not be so understanding regarding rooting in country`s where there you can`t buy a Nexus in the Play store but in a shop.
Click to expand...
Click to collapse
LG wont be understanding, period. Its only google that will except rooted devices.

If you bought another/extended warranty from your carrier or if your carrier import and service your phone then I think you have to keep hands in yr pockets they may not have a user friendly policy as Google's seems to ...

simms22 said:
LG wont be understanding, period. Its only google that will except rooted devices.
Click to expand...
Click to collapse
What do you think could be the reason Google doesn`t offer Nexus devices in all country`s instead of in selected country`s only?
Besides the obvious $$ reason for LG making more money

gee2012 said:
What do you think could be the reason Google doesn`t offer Nexus devices in all country`s instead of selected country`s only?
Click to expand...
Click to collapse
there could be many, most likely legal though. maybe even something with taxes or the currency being used in that country.

Hi,
I asked too about root, unlocked bootloader/custom rom (custom Android Kit-Kat software) and warranty LG/Google, the French support is light and evasive (even if I detailed all the points):
Google traduction D):
Thank you for contacting the Google team about your Nexus 5. My name is and I'm Rozenn your contact today.
I understand your desire to rooter your phone because it is of course one of the benefits of owning the Nexus 5 and the android system.
However, if you need to claim warranty, we will ask you to return the phone to the Android version of Kitkat.
Also, be aware that we can not guarantee the functionality of the device if it is Roote.
If your phone is a concern and you need to claim warranty, from the moment he received no trace of shock or been in contact with water, simply contact us. If we can not resolve your concern, we will offer you an exchange. Your product is guaranteed for 2 years.
Click to expand...
Click to collapse
But the general idea seems the same as the reply from Google in the OP, less detailed.

viking37 said:
Hi,
I asked too about root, unlocked bootloader/custom rom (custom Android Kit-Kat software) and warranty LG/Google, the French support is light and evasive (even if I detailed all the points
Click to expand...
Click to collapse
If I'm not mistaken there's an European law about that. Basically if we have bought a device in Europe the manufacturer must repare our device even if the software has been modified. (Instruction no. 1999/44/CE of E.U.)

[Q] Can my phone get root?

I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...

a10fjet said:
I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...
Click to expand...
Click to collapse
I have an AT&T Moto X running Kit Kat 4.4 (from OTA) and I'm also not clear on whether I can root my phone. I'm also unclear about whether I can unlock my phone
I would also appreciate guidance and direction.
Many thanks!

The AT&T branded Moto X cannot be unlocked, but the GSM unlocked DE will work on AT&T and is unlockable. The TMobile Moto Maker Moto X will work on AT&T and has an unlockable bootloader, too, but if you unlock the bootloader on it, your warranty is void. So I would stick with the GSM unlocked DE. There may be some issues with 4G LTE on AT&T using the TMobile devices but I am not sure. That is probably covered in the forum somewhere if there are any issues.
Click to expand...
Click to collapse
Okay, so I can root, but not unlock. I think I'll wait till an easier and simpler root method is developed like there was for my Samsung GS2.
I appreciate the guidance.

CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
Thanks for the thoughtful and informed reply, Cartland. My last phone was a Samsung GS2 and it was easy to root (all automated). Though I have rooted and flashed ROMs on a number of phones, this process seems complicated and readily screw-upable (not a real word, I admit). I like being rooted, so I can flash tweaked-out ROMs that are better than stock.
I'll explore rooting more and see how comfortable I am with it.
Much appreciated.

CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
CartlandSmith said:
It takes some time to do it. I did it on a relative's phone. There are unfortunately some pointers that are left out of the original posts that help everything to go smoothly if you know them. You can find them in the threads, but the threads have gotten so long it makes the process take longer when you have to read through them to find all of the pointers.
If you are only flashing using RSD Lite - RSD Lite will stop you from bricking your phone.
You are never going to get a simpler method with a locked bootloader Motorola phone - it is only going to get harder and I predict the devs won't invest much energy in it going forward because it is just not worth it when there are developer editions available to us. I think those that are doing it get a kick out of it, but when it becomes too time consuming, well, they have their day jobs they have to make sure they focus enough time on to pay their bills. They get donations for this sort of thing, but I am sure the donations don't compensate them very well for all of the time they take trying to find exploits the more secure Android becomes.
With a locked bootloader, you can't flash ROMs because you don't have a custom recovery. But what you can do it use Xposed Framework and its modules like Gravity Box if you are rooted.
I spent some time this weekend rooting a relative's Verizon Moto X with a locked bootloader due to the 4.4.2 OTA coming. You have some breathing room on AT&T right now to root, but don't wait too long or you will lose the opportunity once the OTA comes.
Click to expand...
Click to collapse
I don't think I have the time or energy to go through the process of finding those pointers and then going through the root method. I'm wondering if anyone will compile those pointers (as you suggest, I have noticed with previous rooting and flashing methods, some key steps aren't described which can cause major problems).
A clarification. You say that if I just want to flash ROMs, I can use RSD Lite. But then you say that with a locked bootloader, you can't flash ROMs.
I do appreciate your taking the time.

POINTER - sell or trade your phone for a Dev edition

It is difficult to root if you can't unlock your bootloader. There is a thread in this forum telling you how to root your device with both locked and unlocked bootloader.

Rooting this device isn't difficult. If you can read and type verbatim, letter for letter, you can get root. People need to stop psyching themselves and others out.

CartlandSmith said:
Yes you can get root, but it takes a bit of work
First you have to downgrade to 4.2.2 by flashing the sbf firmware for your device.
Click to expand...
Click to collapse
can you specify what sbf is? searching didn't help. Try not to use so many acronyms for us dummies.
CartlandSmith said:
Then use RockMyMoto to get root on 4.2.2. Then use MotoWPNoMo to disable write protection.
Then reflash 4.2.2 and use SlapMyMoto.
Click to expand...
Click to collapse
do i use ODIN? what do i use to flash?
CartlandSmith said:
You will be rooted on 4.4 and write protection will be disabled when you are done with all of that.
Once you have root, be sure and freeze MotorolaOTA to stop the 4.4.2 OTA. If you take the 4.4.2 OTA, you may keep root, but write protection will be enabled.
Click to expand...
Click to collapse
Does motorolaOTA automatically download the latest updates and install them without warning you?
thanks for giving me hope!
EDIT: does anyone know if http://forum.xda-developers.com/moto-x/orig-development/script-root-moto-x-root-script-locked-t2603051 will work?

I'm getting close to knowing what to do!
But the individual steps are not very well written.
For example on the RockMyMoto page, he just starts giving you commands. He doesn't tell you what to type them into. In the video, everything is already open. I tried the command in cydia impactor and it didn't do anything. I though maybe you do it in adb, I don't really know what that is but I found adb.exe and launched it but the command window it opens goes through a bunch of commands and then closes. I can't even get past step one because he never said how he got to the point where he starts!
CartlandSmith said, in the third post, that i am supposed to reflash 4.2.2 at the end.. Did he mean 4.4? Or 4.2.2 then slapmymoto then take 4.4 over the air?
It would be really helpful (to me at least) if someone could put step by step instructions. Like humiliatingly degradingly redundant instructions for a complete idiot. I will put them up if I ever figure it all out. It's so frustrating when the instructions are so detailed from where they start, but they never show you how they got to where they are.
Thanks to everyone for the help.
EDIT: probably stupid question but does the phone ever need to be connected by USB? none of the posts mention it but all other devices i've used needed it. adb (here is a tutorial)/ isn't recognizing my device with USB connection or not. Both connected to same router, all drivers and everything updated, Debugging enabled...

No offense intended...at all....but if you value your phone, you really need to study up and read LOTS of stuff here. Until you understand what you are about to do, don't do anything.
Just trying to save you from a bricked phone. You seem very unsure of everything at this point. No one can post anything here that isn't already covered in the guides. Look at the stickies, complete Moto x guide is there.
Good luck.
Sent from my Nexus 5 using Tapatalk

Hmm i rebooted my computer and factory reset my X and now everything is connecting. Guess you should always try the IT Crowd's advice before doing anything else lol
I agree that everything is covered on this site, it's just not organized.

It seems unorganized when you don't understand. Read enough of it and it all makes sense eventually. This has everything about bootloaders, rooting...etc. BUT, you need to know what applies to your situation. And again...that comes when you understand the stuff.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my Nexus 5 using Tapatalk

CartlandSmith said:
It's even more clear how unorganized the info here is the more educated you become.
The thing that becomes the most clear eventually is how much misinformation is posted.
Sorry but the "it only appears disorganized and unreadable and full of misinformation" because you don't understand it won't fly with those of us who do understand it.
Click to expand...
Click to collapse
The OP of the thread I linked is well organized. Its about the only one that is. Its also stickied, so should be incredibly easy to find.
As far as misinformation goes, that's due to people being quick to post advice when they clearly don't have a handle on this stuff themselves.
How to avoid the clutter and misinformation? Maybe point people to good threads that already exist instead of filling new ones with more misinformation. No? Or God forbid, suggest they search for the information that already exists? Instead of helping to grow yet another repeated thread with both good and poor information within it.
Xda's number one rule was created for a reason. To keep clutter and thread after thread of similar content to a minimum. A lot of inaccurate information gets repeated over and over as well. But, so many refuse to search cause its too much work, and just as many others condone this behavior by answering.
I know most don't agree with what I'm saying, as the forums prove with the repeated information here in truck loads. And I also know when any of us remind people of rule number one here on xda....we're called trolls, flamers and much worse....even when the reminder was posted respectfully.
So who exactly are the flamers? LOL
Its looking like reminding members to search and read and actually help them help themselves is becoming a dangerous practice. I'm tired of the misinformation and cluttered forums....and if reminding is just going to start drama at every turn, I suppose reporting the offenders is the easier option. Tho not my first choice.
But if you read this carefully, you'll see I'm completely agreeing with you. LOL. So lets agree to agree and leave it at that.
And as a member who's been around a while, I won't stop doing my part to try to cut down the misinformation and lack of respect for the xda rules. Not abiding by rule number one is EXACTLY why the mess of confusing information exists. You see that, right?
If the newer members want to make me the bad guy for this, fine. I'll be the bad guy.
And I help more people here than most as well.....but that's forgotten if you disagree with anyone or remind anyone of the rules here. Fine. Again.....call me the bad guy. Better get used to it too, I'm not going anywhere.
I'd apologize for the off topic, but this thread should have been closed anyway.
Have a good one!
Sent from my Nexus 5 using Tapatalk

CartlandSmith said:
The most confusing thing of all is why someone with a Nexus 5 self-appoints themselves to be the "hall monitor" of the Moto X forums. *shrugs*
Click to expand...
Click to collapse
Um, perhaps I own both.
How bout you drop it and stop commenting on multiple posts of mine since you appear to dislike the things I say. K?
Try the ignore member feature.
Sent from my Nexus 5 using Tapatalk

Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM

kennyglass123 said:
Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM
Click to expand...
Click to collapse
Ninja'd .....:good: