yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] joshm.1219:
everyone is having play store issues right now, nothing to do with you.

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[G2 Accessories] MoNsTeReNeRgY22:
Figured it would be helpful for a list of chargers and cables that DONT show the slow charging notification. I will continue to update this list with name, price and link as people post.

Stock LG charger + cable from box

BlackBerry ACC-39343-301 OEM Original High Capacity Folding Blade Micro-USB Charger

$7.99

http://www.amazon.com/dp/B005OD89MY/ref=pe_385040_30332200_pe_309540_26725410_item
[Galaxy Note 3 Q&A, Help & Troubleshooting] Swanseatom:
SO i debranded my N3, it was UKcarrier branded and flashed BTU rom no issues. Knox stayed at 0x0

Only thing ive noticed so far is when i plug into KIES it says "Your devise's current firmware version is not supported to update firmware via KIES.

I assume this is because even tho i flashed the BTU rom, my CSC stays as VOD untill i change it?

Example, when i boot to recovery it still shows the message about applying VOD CSC.

I guess OTA will be no issue still, but KIES doesnt like the different CSC mismatch.

I'm gona assume the only way to truely debrand/change csc is gonna be with root once it is eventually able?

I remember on my s3 i did it by dialing *#272*IMEINUMBERHER# or somethign along those lines but as far as i know that stopped working on newer phones/FW's?
[Galaxy Note 3 Q&A, Help & Troubleshooting] johnzoids:
Hi there

Did you just flash a btu rom over existing Vodafone branded rom to debrand it.

John
[Galaxy Note 3 Q&A, Help & Troubleshooting] Damskibeat:
Also interested - did you just flash the stock rom from sammobile?
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
Did you do a factory reset? It generally resets the CSC.
[Upgrading, Modifying and Unlocking] achille2005:
Hello, I have the universal, the MDA pro.

How can I unlock this device? it's a PU10.

and

Can I update with the I-mate rom without unlocking?

Thank you
[Upgrading, Modifying and Unlocking] george12:
Yes you can I did upgrade mine from German to English but SIM lock is still there

GM
[Upgrading, Modifying and Unlocking] akkay:
i need it eng rom too. can i get a link?
[Pebble] JonBsbB:
Ok i know these are "concepts" But can anyone make these? Or has anyone? Especially the, "you and your friends" one and the "Cartesian coordinates".

How hard would it be to make the Cartesian coordinates watch face?

Also I'm really surprised there isn't a section with faces for download that devs and/or people here have made.
[Moto X Q&A] Slusho:
I might need to send my phone back and it's rooted. Can I just factory reset?
[Moto X Q&A] thepolishguy:
No.

Here's a guide with video and all...

http://xdaforums.com/showthread.php?t=2446515
[Moto X Q&A] Slusho:
Thanks. Will it be detectable that it was rooted?
[Moto X Q&A] planktoid:
Yes.
[Moto X Q&A] Slusho:
So it can't be completely reversed? My phone has multiple physical defects and I dread the thought of having another broken phone for two years. :(
[Moto X Q&A] thepolishguy:
I am not sure what [MENTION=4810209]planktoid[/MENTION] was referencing as far as it "being detectable". But if you follow that tutorial and use RSDLite to flash the original firmware you will be able to warranty return your phone without any problem.

---------- Post added at 08:14 AM ---------- Previous post was at 08:07 AM ----------

Which carrier are you with? If you are with a carrier that offers a bootloader unlock and you performed the bootloader unlock and rooted then you are not going to be covered by warranty. They definitely know if you unlocked your bootloader.

If all you did was root via jcase's PwnMyMoto - you will be fine to restore via RSDLite and do a warranty exchange.
[Moto X Q&A] Slusho:
I just used jcase's root. Thanks, I was really worrying about this!
[Moto X Q&A] planktoid:
I am talking about the q/e bit.
[Moto X Q&A] thepolishguy:
I've never met a CSR smart enough to check that.

---------- Post added at 12:26 PM ---------- Previous post was at 12:11 PM ----------

I have to apologize. There is a very small chance that you could get the only CSR smart enough to look for the "tampered flag". I doubt that this is going to be the case. But I would also hate to see you get busted after I advised you to go ahead an return it.

If you want 100% piece of mind you can follow the instruction here...

That Pesky QE

...and reset the flag to 0/1 so that you are absolutely safe for a return.

Again - I apologize and props to Planktoid for bringing it up. I have never had a problem returning a device that has been rooted. But whose to say they won't check. This will solve that small possibility.
[Moto X Q&A] Slusho:
Okay, they probably have a procedure that doesn't include checking for the QE, but just to be sure, let me make sure I understand this. Will following these steps work?:

1. Follow the steps in the video.

2. Issue commands "fastboot erase userdata" and "fastboot reboot" using adb, and use "fastboot getvar all" to check the QE status.
[Moto X Q&A] thepolishguy:
I would just follow the instructions from P3Droid's tutorial at AOSP.us... http://aosp.us/?p=901

adb shell
su
echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379
exit
exit

3) Make sure your system is stock.

Now to make sure your system is stock:

fastboot flash boot boot.img
fastboot flash system system.im

You can pull these images from the SBF file by unzipping it with something like 7zip. If they won't flash for you then you'll have to use the other tutorial with RSDLite. They would not flash for me in Fastboot for some reason. Make sure you download the proper SBF for your phone.

If they do flash for you then you can move on to the next step in P3Droids tutorial...

fastboot erase userdata
fastboot reboot
[Moto X Q&A] Slusho:
Okay thanks. You've been hugely helpful, and I will be sure to name my firstborn "thepolishguy".
[Moto X Q&A] thepolishguy:
Don't thank me until it has worked. Hopefully "thepolishguy" doesn't end up becoming a curse word around your house...

"son of a polishguy"

"that dirty rotten polishguy"
[Moto X Q&A] bhundven:
If you still have problems, and aren't on windows (:sigh: still having issues with that os), you could check out my thread:

[TOOL] Moto X FXZ Flashing Script (100% back to stock) [10/03/2013]
[Moto X Q&A] Slusho:
My new phone should come on Tuesday, so your fate will be determined then. And bhundven, thanks, I did see your thread and I'll be sure to keep that in mind.
[Moto X Q&A] BMAF:
Just curious if this would work on a Droid Maxx. I have the 1/1 qe flag in the bootloader. Been doing some google searches, but haven't found anything except this thread, and instructions to reset it to 0/1 on a Moto X. But I'm not sure if the location to reset would be the same. Any ideas?
[Moto X Q&A] thepolishguy:
I have no idea but you can try hitting up [MENTION=1604771]P3dRo[/MENTION]id on Twitter. He'd know (if he has time to get back to you).

Also there's a G+ community for the MotoX Developer Version - you can ask there and see if someone chimes in.
[Moto X Q&A] Slusho:
When I get to the part in which I have to type "echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379", I get back "cannot open for write: Permission denied".
[Moto X Q&A] thepolishguy:
I asked someone with a lot more intelligence than me to visit your question. Hopefully he does. Sorry.

Just to help with some trouble shooting... after you enter

adb shell

su

what does it return? I believe that you should start with a "$". And then after you input "su" you should get a "#" on the return. Do you?
[Moto X Q&A] jcase:
you have to be root
[Moto X Q&A] thepolishguy:
It says [MENTION=2376614]jcase[/MENTION] is a taco vendor - so do whatever he says. No seriously - this is the man that created #PwnMyMoto.

So did you already unroot preparing to return your phone? Because it looks like you have to have root to perform the procedure and then when you are done you will not have root anymore.
[Moto X Q&A] Slusho:
Okay I got past that part. It was asking for SU on my phone and I didn't notice. But now when I try to run fastboot flash boot, it just says "< waiting for device >".
[Moto X Q&A] jcase:
are you in the bootloader? if so sounds like PC side issue
[Moto X Q&A] shaya4207:
Will this work even if I unlock the bootloader through Motorola? I was under the impression that that one can't be reversed....
[Moto X Q&A] Slusho:
I don't see any instruction in the procedure to boot into the bootloader, but I tried it and adb doesn't see the device as connected.
[Moto X Q&A] thepolishguy:
The reason that you don't see instructions is that for people that are pretty familiar with this stuff - they just assume that if you see...

fastboot flash boot boot.img

...that you already know that you have to be booted into bootloader/fastboot. You cannot issue adb commands in bootloader/fastboot and you cannot issue fastboot commands in "regular android". Even though you issue the commands from the same terminal/command prompt window - while you are booted into Android you would be using ADB, and when you are booted into bootloader/fastboot you would be using fastboot.

So with your phone plugged in and booted into android enter into the command prompt...

adb devices

It should return your device serial#. If it does not you either do not have the proper drivers or you need to change your USB settings from MTP to camera.

Then to enter bootloader/fastboot...

adb reboot bootloader

Now...

fastboot devices

It should return your device serial#. If it does not you either do not have the proper drivers or you need to change your USB settings from MTP to camera. If you need the drivers install Motorola's crappy software and you should be good http://goo.gl/DiRvpE

When you are booted into bootloader/fastboot and know that your device is recognized than continue with the procedure...

fastboot flash boot boot.img

fastboot flash system system.img

fastboot erase userdata

fastboot reboot
[Moto X Q&A] Slusho:
Okay I did everything and the phone looks as if it's been factory data reset. The qe still shows 1/1. I reboot into recovery, it booted into the normal phone OS and I tried

adb shell getprop ro.boot.write_protect

which gave back a 0. I did a reboot from the on-device power menu and tried again, and it returned a 1. So I'm pretty sure it's still rooted and all the procedure accomplished was the same as if I went into settings and did a reset. Of note possibly is that when I entered

echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379

I just got back something like "latform/msm_sdcc.1/by-name/misc bs=1 <" and then the line I could type on was ">" and I had to open a new command prompt window as it just fed me back whatever I typed in. I remember doing it before and it did something different and the whole exit exit thing made sense. Not sure if it only can be done once as I don't understand what that step does.
[Moto X Q&A] thepolishguy:
Okay lets make sure we are on the same page. This half of the instructions...

adb shell
su
echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379 *** Thanks to JCase for this shortened version. ***
exit
exit

...has to be executed using ADB while booted in regular Android.

When you finish this portion you then boot your phone into bootloader/fastboot by executing...

adb reboot bootloader

Then this part of the instructions...

fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
fastboot reboot

has to be executed while in bootloader/fastboot.

Is that how you did it?

####EDIT####

Also - the syntax has to be exactly right. If you are using copy and paste - well I believe there is a syntax error on AOSP.us here...

echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379

There are 2 spaces between "bs=1 seek=5379". There should probably be only one space like this...

echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379

I could be wrong. But I think syntax is pretty important when executing these commands.
[Moto X Q&A] Slusho:
That's exactly what I did.
[Moto X Q&A] thepolishguy:
Did you check my edit above about "possible syntax error"?
[Moto X Q&A] Slusho:
I typed that part out, so I'm sure there was only one space.

I'm supposed to be booted into the normal OS, not the write-protectionless "recovery", right?

And now I'm trying to run it again to show what it's doing, but when I enter "su" in adb shell, it outputs "/system/bin/sh: su: not found" and then instead of "shell@ghost:/ $", it's "127:shell@ghost:/ $". That part worked fine before.
[Moto X Q&A] thepolishguy:
Well - I am at a loss. Yes - you should be in "regular android". Did the system.img write correctly? If so you lost root because you replaced your system.

---------- Post added at 08:19 PM ---------- Previous post was at 08:04 PM ----------

Okay man - I might have found something. It seems that AOSP.us may have missed a step. In this post [MENTION=2376614]jcase[/MENTION] posts a suggestion...

https://plus.google.com/110773150384694258853/posts/FperrekMBbS

...he says, "Why not use this...?"

echo -ne "0"| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379

[with two spaces so I am not sure if it is a typo or not] But then he adds this line...

rm /data/property/persist.qe﻿

AOSP,us seems to have forgotten that line [unless it doesn't matter]? But the "rm" i believe indicates "remove" which would make sense. So because this command has been left out of the instructions the data is not being removed. That's all I can think of.
[Moto X Q&A] Slusho:
Okay so I've found a few things. When I try to use su (in adb shell or even installing SuperSU) it says the phone doesn't have su (su not found or There is no SU binary installed). But if I reboot into recovery, I get the Android OS with write protection 0 from the adb shell command. Could the process have removed su but left a recovery without write protection (seems like this is a contradiction). I noticed a recovery.img with the other imgs. Should I flash this?

Note that I can't get to the step where you type in the long string or the thing jcase puts in after it as it stops me at su in adb shell.

Just so I understand what's going on here, writing system.img replaces root. What does that long string do (this is where I'm most confused), what does writing boot.img do, and what does erase userdata do? Which part gets rid of qe?
[Moto X Q&A] thepolishguy:
Man - I really don't know what to say at this point. But yes - you are correct in the fact that you still have the "other recovery" and not the stock recovery.

I think that I would try (but really at this point why try what I suggest?) stating completely from scratch. Use the RSDLite method from the video tutorial so you have a completely stock system, recovery etc. Reroot with PwnMyMoto. And then go straight to the instructions for resetting your QE. Then use RSDLight again to do a complete restore of system, recovery, etc.

Or, re-run PwnMyMoto now and see if you can get it to work.

I really don't know what else to try.

I guess my name is going to be a curse word in your home after all. Sorry.

---------- Post added at 09:00 PM ---------- Previous post was at 08:54 PM ----------

I don't know all the technical details. Sorry. But I do know that these guys (especially [MENTION=2376614]jcase[/MENTION]) know what they are talking about. So they say, "This is how you do it." Well - it is how you do it.

If you can't get to "the step where you type in the long string or the thing jcase puts in after it as it stops me at su in adb shell" - then it is not going to work. I am not sure what that does exactly - but I am sure it is essential to resetting the QE portion.
[Moto X Q&A] Slusho:
And by that do you mean follow the full instructions again, or a part of them that's specific to resetting the QE?

Another weird thing is that the haptic feedback on both of the Moto X devices I have is stronger when not rooted (and also in the weird state the one I'm trying to unroot is in). Strange to think that part of the root affects haptic feedback (as well as cause strange flashes on both debices) but I guess that's a different problem to be figured out later.
[Moto X Q&A] thepolishguy:
I would follow the full rsdlite tutorial. Then you will have to root. I would just use RootMyMoto instead of PwnMyMoto. Then you won't get that weird recovery right? Then the full QE tutorial.
[Moto X Q&A] Slusho:
That did it! After installing SuperSU, the initial setup kept failing but I tried to gain su in adb shell anyway and SuperSU asked for verification. I also put in the additional line jcase suggested in the Google+ post, and all went well. My recovery looks like this:

and has no options. Is this normal? Also, I confirmed the qe is 0/1. If that recovery is normal, I'll send it back, name my firstborn thepolishguy, and open another thread for the haptic feedback/flashing issues. Thank you guys so much!
[Moto X Q&A] thepolishguy:
Well - hotdogski [that's Polish for "awesome"]. I am almost positive that that is the normal recovery. Try this... Boot to recovery. Hit volume up [and hold it] then press power [while holding volume up] and release them. Hopefully it gives you the "normal" recovery menu that you are used to seeing. Then just choose reboot or factory data reset.
[Moto X Q&A] Slusho:
That worked. It even shows the qe value in there (which I hope is normal).

...and I found out what the deal with haptic feedback is. Apparently Moto sets it at 20ms for keyboard vibration duration but rooting sets it to Android default. Rooting also turns off the lock screen unlock sound but turns on navigational sounds. We're just learning all kinds of things today.
[Moto X Q&A] jayboyyyy:
so was the right code with two spaces or one? I'm having difficulty with this currently because that command is not working. Let me know if there was supposed to be one space or two? thanks so much

---------- Post added at 05:43 PM ---------- Previous post was at 05:37 PM ----------

hey PolishGuy. Looks like you have been putting in some pretty hard work helping this guy out. Because of this, you will receive a simple yet extremely beneficial reward that took me a couple hours of research trying to figure out. So you said you couldn't flash the system.img in fastboot, which as you might recall I ran into the same error. The problem is that Motoroa's dont work well sometimes with the SDK version of fastboot. SOOOOOO they create a moto fastboot for us to use. Check out the link: http://xdaforums.com/showthread.php?t=1953948

then download that mfastboot.exe file put it where your fastboot is. instead of using fastboot do "mfastboot flash system system.img" and enjoy the hell out of watching it work like it seems to for everyone else not on Vzw.

Your welcome in advance lol
[Moto X Q&A] Slusho:
I used one space.I think inputting that code worked one other time, so I think it's something that needs to be entered once and then it doesn't do anything afterwards. It seems like that second line was crucial.
[Moto X Q&A] thepolishguy:
Thanks for the mfastboot link, appreciate it,
[Nexus 7 (2013) General] sevenslugs:
I have owned a Nexus 7 2nd gen for a couple months now and have just started to get random flashes of black (occurs for not even a quarter second) ...

I am wondering what causes this...

I have not damaged the Nexus in any way and bought it brand new..

I have only used CleanRom and PA ROM...

The functionality of the tablet remains great, but the flashes are very annoying ...I have tried clean installing multiple times but the flashes still happen...

Any feedback/solutions would be a big help...

Thanks
[Nexus 7 (2013) General] player911:
The whole screen?

I've noticed black lines when playing Terraria for hours but its only the background of certains areas. I chalked I up as game glitches.

I haven't seen anything outside of that.

Give us some more details.
[Nexus 7 (2013) General] sevenslugs:
Yes...the whole screen...

This is not a set of lines the entire screen flashes black for a millisecond....
[Nexus 7 (2013) General] kdo23:
I had that happen soon enough for a return to be viable. Do some more Google searching and you'll find people who fixed this as a hardware issue. They had to open the back and fiddle a connection. Didn't sound to hard but I just went to best buy instead.

Happy hunting, sorry I don't have a link.
[Nexus 7 (2013) General] player911:
Yea I would exchange it before it is too late. Doesn't seem that troublesome but if it got worse, or worst, disconnected entirely, it would bring bad news.
[Nexus 7 (2013) General] sevenslugs:
Could you please post the link? I am having trouble finding it on Google.

Thanks a lot..
[Nexus 7 (2013) General] sevenslugs:
Its very intermittent...some days it won't do it at all and some it does it just a bit ....I bought it off eBay around the time it was first released so I'm not sure how I would go about exchanging it ....
[Nexus 7 (2013) General] mlovesu:
i am also facing the same problem..the screen flashes for nano second...its very annoying..i read about the problem in other forum it seems to be a hardware problem..i am from india and imported it from us ...so i dont think i can resend the nexus 7 ...any help will be great..
[Nexus 7 (2013) General] sevenslugs:
What specific piece of hardware is causing this?

I still have this issue from time to time ..

I've notices it happens a lot less if I turn off auto brightness and manually turn brightness above 45-50 percent...
[Nexus 7 (2013) General] player911:
Just because you bought it off ebay doesn't mean it doesn't still carry the 1 year manufacturer warranty on the hardware. It would require you to send it in, but worth a shot.

Once you pop the back and start fiddling with hardware, you run the risk of doing enough damage where Asus will void the warranty. I think I would check with Asus first before resorting to hardware modifications.
[Nexus 7 (2013) General] sevenslugs:
I should send it in to Asus you say?

What are the requirements to have it repaired/replaced under warranty as I have already rooted it with a custom rom
[Android Q&A, Help & Troubleshooting] dantexaiver:
Hi Guys

I have started up my own VPN service I have a website but am curious as to what it would cost to get an android app developed that will allow users to browse services pay for services and contact us for support.
[RAZR i Q&A, Help & Troubleshooting] radzer0:
So ive added the songs to my library that I want and it appears to be doing something when im on wifi at first but when I goto on device it doesnt show any of the music. Wont play anything in my car which is what I want to do in the first place.

I have the 6 months free all access with my razr maxx. And even when I goto my library it keeps sucking up my data trying to stream.
[RAZR i Q&A, Help & Troubleshooting] amarie82:
What does it look like its doing on WiFi? Do your play lists show? Does it just buffer when you try to play? More details plz!

Sent from my Galaxy Nexus
[G2 Q&A, Help & Troubleshooting] zxrax:
[Q] [AT&T D800] Trying to flash back to stock, get "Download FAIL!!" in LGFlashTool?

I dropped my phone today and the touch screen is cracked and no longer responds to touches. Since my phone is rooted, I need to set it back to stock before I go to the AT&T store to make a mobile insurance claim on it (I think? Please correct me if I'm wrong...). But when I try to use LGFlashTool to go back to stock, I get this error:

http://i.imgur.com/wULC8f1.png

Any suggestions are welcome
[G2 Q&A, Help & Troubleshooting] zxrax:
Tried a different USB port and now it's working. No clue what was going wrong, but I'm glad I got it fixed.
[General Questions and Answers] noobsgs2:
Hello there,

I was wondering if there exists an app which allows you to create a widget/icon for automatically send a pre-maded SMS (to a predefined contact) just by clicking it.

even a gesture could be fine

Regards
[General Questions and Answers] noobsgs2:
Anyone pls?