yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] samwathegreat:
Well you won't find one for that much cheaper. They are selling used for ~$200 on Swappa and slightly higher on eBay. The fact that you got one on 4.2.2 is excellent - you probably won't find a used one that's not already on 4.4.2. This means that you could follow the safestrap guide to disable write-protect and use the safestrap-compatible 4.4.2 ROM which is the next best thing to having an unlocked BL. Once updated to 4.4.2, you can kiss the possibility of using safestrap goodbye...

Additionally if you return it, you are out shipping costs (~$10), and you will lose your $20 referral credit. So at most you will get $70 for all of your troubles and have to deal with all the hassle along with it. Not to mention getting a USED phone with no warranty as opposed to the full 1YR warranty you got with your new device.

I agree it is small and I just LOVE it. I hate the "phablet" fad that is going on. Anything bigger than the X, I can't fit in my pants pocket comfortably. And I'm a dude....so I don't carry a purse to put some massive phone in.

Until you decide whether or not you are going to keep it, you can enjoy limited root access via "TowelPieRoot" here: http://xdaforums.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059/post54850209

(Remember to "THANK" [MENTION=4850320]iKrYpToNiTe[/MENTION] for his awesome work combining TR and PIE for an effective temp-root solution.) Keep in mind this solution does NOT disable write protect, so DON'T update past 4.2.2 if there is any possibility that you will keep the device. If you decide to keep it, you will HAVE to be on 4.2.2 to disable WP and gain persistent root and write access. Of course, don't do the safestrap procedures unless you decide to keep it.

No idea if they will offer the X+1...we might find out in September. I'm sticking with the original X. I don't like big phones....I just don't get the appeal. To each their own...

Have fun playing with it.
[Moto X Q&A] dimex:
Good points, will keep that in mind. Well if I decide to keep the device, I'd like to forgo the safestrap methods altogether and unlock the BL via the middleman. I can deal with having write protection for a few weeks, as I'll still be able to install Xposed and all the root apps, correct?

You mentioned safestrap, but I was under the impression I could skip that completely with BL unlock. Are you saying that the temp root solution will require me to use safestrap in the future?
[Moto X Q&A] samwathegreat:
You will have serious problems trying to get Xposed to work without disabling WP. If you are able to use it, it will be lost upon reboot and you'll have to get it working again. It's complicated and messy trying to get Xposed working on a temp-root.

Most other root apps will work fine with TowelPieRoot. Ad-away will not as it requires write access to /system.

Um..no. If you unlock via middleman, none of this is relevant. You don't need safestrap or any other exploit. You device will essentially be an unofficial "DEV" edition.

Safestrap is an alternative for people who are not unlocked. It provides most of the benefits of a full unlock, but you MUST have never updated to 4.4.2 or above or you cannot use it as it has been patched.

If you plan to unlock, don't worry about updating or safestrap. Thing is....the middleman has failed to get codes for some devices, so better to play it safe and stay on 4.2.2 until AFTER you get a code from him and unlock.

Regardless of what you do, the temp-root solution won't affect any of it. Safe to use in the meantime - until you make your final decisions.
[Moto X Q&A] dimex:
Great, that's what I wanted to know, and was planning on doing that (staying on 4.2.2 until I decide what to do). I disabled automatic update immediately and keep postponing update requests every 24 hours. Wish there was a way to remove the update prompt altogether.
[Moto X Q&A] samwathegreat:
There is....if you have purchased Titanium Backup, install it. Use TowelPieRoot to root, and then run Titanium Backup and "FREEZE" "MotorolaOTA". The paid version of TiBu is required to freeze apps.

No more update notifications. And if you get a code from the middleman in the future...well unlocking resets everything to factory defaults so you can update then.
[Moto X Q&A] dimex:
Doesnt work.

Says Root Achieved within TowelRoot but SuperSU gives me error that binary cannot be installed amd TiBu gives me error regarding root access.
[Moto X Q&A] samwathegreat:
That's your problem. You don't use SuperSU with temp roots. Reboot, use TPR, and tibu should work without issue. Once don't this on several phones.. I know it works. Don't install SuperSU.
[Moto X Q&A] dimex:
Negative. I only installed SuperSU after TiBu gave me the error. uninstalled both, reinstalled TPR, got root confirm, rebooted, and TiBu still saying:

sorry I could not acquire root privileges
[Moto X Q&A] samwathegreat:
Strange. The problem then could be that you are on 4.2.2.

TPR is for 4.4+

I've only used it on 4.4.2 on which it works flawlessly. That's my best guess.
[Moto X Q&A] dimex:
Any other options? Or you think I should just deal with it for a few weeks until I make my decision?
[Moto X Q&A] samwathegreat:
You could use pwnmymoto. Technically it will void your warranty but as long as you do a full return to stock I doubt they could tell.
[Moto X Q&A] dimex:
Ok, just want to make sure before I proceed with this. TowelPieRoot may work for some people, but it's extremely limiting for me. Can't get Xposed to work, and I want to set up my phone completely with WiFi Tether working (via your guide) and all my daily apps so I can really see if this Moto X is going to work for me.

As it is right now, I keep my Xperia Z Ultra with me daily and only use the Moto X for calls because I'm limited with what I can do with it. I'd like to leave my Xperia Z Ultra at home and solely use the Moto X so I can accurately evaluate it.

With that said, I was going to use Pwnmymoto (http://xdaforums.com/moto-x/orig-development/root-write-protection-bypass-motox-t2444957). That doesn't seem too complicated and at least I can bypass write protection and apply changes in the "recovery" mode. I can deal with that for a few weeks.

But, reading other root methods, there seems like some irreversible changes are implemented when disabling write protection that remain after wipes, etc.

I just want to make sure, with Pwnmymoto I can go back to bone stock/unrooted with no trace of changes should I want to return this to RW?
[Moto X Q&A] samwathegreat:
The reason my last reply was written the way it was is because nobody knows what changes PwnMyMoto, RockMyMoto, SlapMyMoto, or MotoWpNoMo make to the phone to disable write protect.

We were never disclosed that information - the devs didn't tell us -- likely to slow down Moto pushing updates to disable them.

Anyways, I can not tell you that no one will be able to tell. Yes you can go back to stock/unrooted, but a well trained person could possibly tell that you had used it. Unless they are putting significant resources into checking returned phones, I doubt they will even check.

Do what you feel is best. Research if necessary and make your own decision.

P.S. If your 4.2.2 is on the camera update, PwnMyMoto is patched and you will have to use SlapMyMoto or RockMyMoto....
[Moto X Q&A] dimex:
True. It seems like most people hopping on the RW bandwagon aren't really into tweaking and modifying stuff (they're just looking for the best price).

Have been researching a lot. Just wasn't sure about the changes made to the device. Seems like this device compared to many of the other ones I've owned is heavily guarded by some carriers. Pwnmymoto seemed like the most innocuous method of all the exploits so far. How do you know if the device is patched with the camera update?

I was just going to attempt Pwnmymoto and if it doesn't work, obviously camera update is applied.
[Moto X Q&A] samwathegreat:
That's what I'd recommend. If PwnMyMoto fails, try RockMyMoto. SlapMyMoto is the most involved and complicated method, and is only for updating to KitKat. If you plan to stay on 4.2.2 until you make your decision, RockMyMoto will definitely work.

When you root the device use TiBu to freeze Motorola OTA to stop the update notifications.

If you decide to keep and use the Middleman, OR send back, use RSD Lite to return to full stock.

We do know for a fact that even if irreversible changes are made, it won't hurt your device should you decide to unlock the BL later (plenty of us used the exploits, then took advantage of the middleman's services when they came available). But you WILL need to do a full return to stock, THEN unlock, then do whatever you want. I also recommend updating to the latest version after you unlock, but BEFORE you flash TWRP and root because as you should know, OTAs will not install with Stock Recovery or a modified /system.
[Moto X Q&A] dimex:
Ok, cool. I assume I'm using "PwnMyMoto-1.4.3-Sprint-IHateToolKits.apk," ya?
[Moto X Q&A] samwathegreat:
? Probably. Never used it myself. Went straight from no root to unlocked (thanks middleman).
[Moto X Q&A] dimex:
Well PwnMyMoto didn't work so I had to go the route of RockMyMoto and MotoWpNoMo to disable WP. Everything worked perfectly and have been running that since I posted last.

I just received a bootloader unlock code and have decided to stay with RW for the time being. Hopefully in the next few months they will come out with the X+1 and I can always pray for the 5.9" Nexus X or Moto S.

I'm going to sell my Xperia Z Ultra and go back to using my Surface Pro 2 as a media consumption device. I've been neglecting it. 6.4" was pretty extreme for a phone even though I loved it.

I'm running TiBu right now to save all my apps/data, but since I'm obviously on 4.2.2 Post Camera Update, can I go straight to the "How to Unlock your Bootloader" section of http://xdaforums.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 and adb into the bootloader/flash the code?

That should wipe everything and from there I can flash TWRP/SuperSU? And after that I flash 4.4.4?

I guess I'm officially part of the club now (if the unlock code works!)
[Moto X Q&A] samwathegreat:
First, since you used the exploit, you HAVE to return to 100% stock. You need to do things in this order:

1. Unlock the BL using fastboot from the bootloader screen (AP Fastboot mode) This erases EVERYTHING. fastboot oem unlock YOURCODEHERE

2. Flash the ENTIRE Republic Wireless 4.4.2 SBF from sbf.droid-developers.org

3. Boot into android. If all is well, power off & boot back into bootloader mode. Flash TWRP following this procedure:

get the latest twrp from here: http://techerrata.com/browse/twrp2/ghost

Flash the .img file using fastboot: fastboot flash recovery twrp_file_name.img

type: fastboot reboot-bootloader when it reboots, VOL DOWN to recovery and VOL UP to boot into it.

Click EXIT - when you go to exit TWRP, it will offer to install SuperSU Installer for you. Boot as normal.

Once in android, you will have an icon for SuperSu installer. Run it and choose the PLAY STORE option.

That's it. You should be unlocked on 4.4.2, rooted, with write protect disabled.

By the way: There is no 4.4.4 for Republic Wireless. We might not get it at all (might go straight to android L), or it might be months before we get it. RW is always last on the updates because they have to implement and test the wifi features.

Also keep in mind that adb and fastboot are two totally different things. adb does not work in bootloader mode. adb only works in recovery, and while booted into android (assuming usb debugging is enabled). Best not to confuse the two.

Also, I'm not a fan of restoring apps to a different android version using TiBu or similar. It will probably work for you, but may cause issues. Personally, I *always* install from scratch, OR save my APKs for re-installation later. I've just seen too many people have issues with restored apps.

And finally, Step 4: Hit the THANKS button ;) ...to ALL the helpful posts.
[Moto X Q&A] dimex:
Hey Sam,

I ended up not unlocking the bootloader and I'm returning that phone for the trial period. I was able to pick up a brand new Moto X with unlocked bootloader for $250 so it's saving me a few bucks.

Just want to make sure, to return this one to RW, I just follow the directions you gave me starting from step 2 to return this to stock unrooted, write protected enabled. Correct?
[Moto X Q&A] samwathegreat:
Only step 2. Yes
[General Questions and Answers] silenthkc:
I want root my phone lenovo a316i, but I've tried a lot of ways it didn't work at all.

Thanks before
[Windows Phone 8 General] jrob127:
Hello everyone,

I found a way to unlock tethering on my Nokia Lumia 520. This may work for other models and possibly for AT&T as well. Basically, I followed this guide:

Thread Here

I flashed the 059S340 RM-915 VAR APAC AU CV firmware, and after setup, just happened to try tethering and BAM, it's working perfectly. It was blocked before while using Cricket's original firmware. As far as I can tell there's no disadvantage to flashing this firmware, as you can change your region and language to US during setup, and Windows Phone 8.1 Preview is working great as well.

Happy tethering, I hope this helps someone else out there!

If anyone tries this on AT&T GoPhone or Postpaid, and it works, let us know!
[Windows Phone 8 General] GoodDayToDie:
Cool! Thanks for sharing.

Any chance you could follow the steps here so this could be made possible for people who don't have Nokia phones and/or don't want to re-flash their firmware? It would be even better if I could also get the info from the original ROM (to see what changed), but if it works now when it didn't before, that's very good to know.

Thanks again.
[Windows Phone 8 General] jrob127:
Absolutely! I'm downloading the Windows Phone SDK to do a Dev Unlock right now, and I'll attach the results to your thread over there!
[Windows Phone 8 General] jrob127:
I'm having a little trouble getting my phone to dev unlock, not sure why but i'm beginning to think it might be the new firmware... I'd also like to add that I discovered Double Tap to Wake is working on this firmware, but not in the original from Cricket... strange...
[MX Player] roguemedic:
Please forgive me. I clicked the link from Google Play and MX Player and was directed here. Please feel free to move to appropriate location.

I have a camera that uses a micro SD (duh). When using a USB Female to Micro USB Male Adapter and my HTC One along with a card reader, the video plays perfectly with MX Player. When using my Samsung Tab 2, with OTG Adapter Cable for Samsung Galaxy Tab, the tab will only play the audio from the video recording, does not play the video. Please help.
[MX Player] bleu8888:
HW decoder depends on device's capability. Use HW+ or SW decoder instead.
[MX Player] roguemedic:
OK so do you think I need to down load a codec or something? Or keep playing with other players?
[MX Player] bleu8888:
MX Player have three decoders, but HW+ decoder is disabled by default.

Please check Settings > Decoeer > HW+ decoder and try again.
[MX Player] CDB-Man:
So does SW or HW+ solve your problem?
[MX Player] roguemedic:
Sorry to take so long to get back. The recording device took a dump and does not appear to work any longer, thanks for the assistance though much appreciated.
[T-Mobile Samsung Galaxy S 4] rebel1699:
Just a quick question on using the T-MO S4 on AT&T. Will this phone be able to use the 3g from at&t (after I carrier unlock, of course)? I could care less about lte, as I dont live in an lte area, and rarely travel to one. 3G is my only concern.

There is a ton of info on the web about taking an att phone to t-mo, but barely any the other way around. Thanks in advance.
[G3 Q&A, Help & Troubleshooting] dimabrook:
I chose the Google keyboard as my default. No problem. Now on every reboot I get this message. Switching back to LG keyboard the issues goes away.

Looking for help how to solve this.

Few notes

* this happened prior to me rooting

* I've disabled several bloat apps from LG and ATT using the built in disable method, did not freeze or delete any apps

* I don't want another keyboard. I like Google's.

* All Google services and apps are up to date

* ATT D850 10d
[G3 Q&A, Help & Troubleshooting] radicalisto:
Happened to me also, and always after I rooted. It has however stopped recently and I have absolutely no idea why. There is many many theories on it. But it's a mystery.

Google keyboard apparently causes it. But I use it still and it's gone. So God only knows. Sorry I can't help you, but I understand the annoyance of it.
[G3 Q&A, Help & Troubleshooting] rjpmb:
I know that the G3 is picky when talking about keyboard. It does the same thing with me when i use swiftkey, so i believe it's a bug from the way lg implements their keyboard. Despite giving that error there aren't any real consequences (as far as i can see) in normal operations, just an annoyance every time we turn the phone on.
[G3 Q&A, Help & Troubleshooting] siraltus:
Google Keyboard is causing it on my G3 as well. If I switch your default input method back to the LG Keyboard, the error stops appearing. Googling reveals SwiftKey also causes this issue. The error itself is harmless - the keyboard itself works perfectly fine.
[G3 Q&A, Help & Troubleshooting] intraCore:
I saw a fix online about re-enabling any Google apps you've disabled. That did the trick for me. Good luck!
[G3 Q&A, Help & Troubleshooting] muiriddin:
Fleksy Keyboard Also!

Fleksy seems to also cause this problem to occur. As others have stated the only way to get the error not to occur on start is to boot with the LG keyboard as the default input device. However I prefer Fleksy to LG's keyboard. I have tried many of the work arounds suggested in several threads and the only one that makes the problem go away, is to have use the LG default keyboard...
[G3 Q&A, Help & Troubleshooting] kartikk76:
got it !

I am also facing the same problem after rooting my phone when i reboot the device it shows my normal keyboard even in appdrawer android keyboard is not showing however it is showing in app manager.Then i notice that i have moved the keyboard on sd card. then I had moved it to phone back and after every thing is working fine.So just check it out that if you have also moved it to sd card. Good Luck:good:

and sorry for my bad english :p
[G3 Q&A, Help & Troubleshooting] prabandh91:
You can find the better solution here: http://technogiga.com/how-to-fix-com-google-process-gapps-has-stopped-error-in-android/ Don't forget to hit the thanks button
[G3 Q&A, Help & Troubleshooting] kartikk76:
In my case reset app preferences didn't work.I just moved play services to internal storage and the error vanishes.:D
[Windows Phone 8 Q&A, Help & Troubleshooting] xtrapsp:
Hey guys,

I bought a Windows Phone [Tania] From ZTE phones a while back and they refused to fix it when it was broken from the start. This issue I'm having is that it randomly reboots and when it is running it won't let me scroll in the menu etc before it crashes and reboots.

I had a feeling that if I flash it and change the firmware it might fix the issue at hand.

I was wondering if you guys could possibly give me some insight, point me in the right direction, explain if I'm right/wrong :)

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] zephirop:
Hello i just bought a factory unlocked galaxy s4 from t-mobile and im trying to activate it to metropcs but the lady said that it cannot be possible to activate it because some problems with t-mobile i think and i have to call to tmobile to see whatsup.. but oviously i dont have an account and the user from ebay he said it dosnt have problems so he is not willing to offer a refund :/ its there any other way to activate it ? because i think the imei has been blacklisted on tmobile or something please heelp :(
[Galaxy S 4 Q&A, Help & Troubleshooting] zephirop:
bump
[Galaxy Note 3 Q&A, Help & Troubleshooting] @Class:
Are there any hacks for the Note 3 to increase BT Audio Quality? Tons for older devices from replaced system libraries (.so files) to you used to be able to edit the audio.conf file.

Anything like that for the Note 3?
[T-Mobile Samsung Galaxy Note 3] xmuertex:
Hi, my issues with my sensors are the following.

Accelerometer not moving, ( stuck )

Proximity sensor won't read

Gyroscope fails on the test done via *#0*#

Its like they all have wrong data, i tried mostly everything, stock restore doesn't help

Im willing to try anything, any help is very appreciated, i even tried taking out the sensors folder from another Note 3 N900T and it said i had no permission and gave error also,

Advice or help please, im desperate, been like this for a while.
[T-Mobile Samsung Galaxy Note 3] xmuertex:
If someone can push it out with ADB and make it flashable would be even better
[T-Mobile Samsung Galaxy Note 3] louforgiveno:
How did the issue start? Drop or software mod
[T-Mobile Samsung Galaxy Note 3] xmuertex:
Don't remember if it was a software installed or i deleted something by mistake, i saw few post about EFS, i did back up efs on nb4 and did restored modem on ne6 , i tried most easy steps, but now an expert on force calibration or sensor files replace might be the option but im no expert
[T-Mobile Samsung Galaxy Note 3] louforgiveno:
You have a custom recovery? Have you tried a full wiping including internal sdcard? Just earlier today i flashed a mod to get optical reader working and the version i flashed ended up overwriting a few lib files.....next thing I know my sound isn't working....i was able to look through the zip and see which libs it wrote and took the original files out of the rom zip I'm currently running and got my sound back. My long point is that you may need to really wipe your phone down then odin stock rom.

---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------

Also where is the location of the sensors folder you mentioned?
[T-Mobile Samsung Galaxy Note 3] xmuertex:
Sys / class / Sensor

I have TWRP recovery

I have done, format, wipe and everything before i odin to stock

I got since nb4 with this issues
[T-Mobile Samsung Galaxy Note 3] louforgiveno:
http://www.infotales.com/samsung-galaxy-note-3-proximity-sensor-issue-fix

I know you mentioned a bunch of sensors not working maybe this will at least prove or disprove where the issue lies (software or hardware)
[T-Mobile Samsung Galaxy Note 3] xmuertex:
Thanks
[T-Mobile Samsung Galaxy Note 3] louforgiveno:
just for kicks why not try the tip in post #16

http://forums.androidcentral.com/ve...-3/326747-note-3-proximity-sensor-issues.html
[T-Mobile Samsung Galaxy Note 3] xmuertex:
Is not dust i tried lol, its just not reading at all, its like all my sensors are in 1 single set up value and it won't read nothing else, like my gyroscope and accelerometer won't even move nor nothing
[T-Mobile Samsung Galaxy Note 3] thewalkingdude:
I am having the same problem. I was running Darth Stalker and one day all of my sensors stopped working. I have tried everything I can find on the Internet. I very rarely post but I really want this fixed.
[JASJAR, XDA Exec, MDA Pro General] Longlife:
Hey all,

I have been using Agile Messenger since june or so..so far I have downloaded "new version" of the app into my phone twice. The last one is really cool and I have been using it for about two weeks w/o any probs, but when I turned the app on yestreday, it displayed message "Thanks for trying this trial version, you have 7 days left". Is Agile Messenger not free anymore? And if it's not, do you think I could continue using one of the older versions? Thx for any suggestions :) Longlife
[JASJAR, XDA Exec, MDA Pro General] eelco_akker:
Having the same problem, the subscription fee is pretty high.

Don't know about the old versions...

Eelco
[JASJAR, XDA Exec, MDA Pro General] cktlcmd:
I think I have the old version of Agile. If you guys want, you can try it and let us know if it will work or if we actually have to pay after the trial period.