yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] jamfitz86:
Hi all :)

When you've installed something like TCPMP from the cab, do you then need to keep the cab? I would have thought you dont, but do you?

Also, is it worth getting rid of stuff like windows media player if your using TCPMP or something similar. If so, can it be done easily.

Thanks

JAmes
[JASJAR, XDA Exec, MDA Pro General] yadvani:
nopes you don't need to keep the cab file and if you install the cab from the device, it should delete it automatically though.
[Nexus 4 Q&A, Help & Troubleshooting] dEris:
The second attached screen shot is an image I sent to a friend.

Upon clicking the image in hangouts, you will notice the image to be extremely grainy. However, if you look at the original image... It's clear and sharp.

Does this happen to anyone else and is there a way to fix it?

Original

http://m.imgur.com/pONRQ5M

Image after being sent through hangouts

[DEVICE : NEXUS⁴]❌[ROM : PSX]❌[KERNEL : FRANCO]​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ali7000:
So I have a Teus S3 I747M and its rooted with TWRP recovery, and I'm on stock 4.1.2 . Whenever I go to my settings and click on change ringtone, it says "Unfortunately, the process android.process.media has stopped.". Any suggestions on how to fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ali7000:
Anyone? Please help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ali7000:
Anyone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kckc:
I share how I fix it. I went to application manager and chose ALL tab, chose Media Storage tab Clear data. Then problem fixed
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] PhilPan:
Anyone know if there is a way to open air command without having to use the spen? Like with a Nova activity or something?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] jkuczy16:
I think the air commands is unique for the s-pen, so in order for it to open you must use the s-pen. Hope that helped
[T-Mobile Samsung Galaxy Note II] crazygerz:
friends please help me by mistake I gave odin nand eraser all, and when I start my phone lost the imei, and internal memory only tells me 0/0 gb can not pass anything Porodin and restored to stock and still can not solve please help
[T-Mobile Samsung Galaxy Note II] Coug76:
Have you tried using kies to restore the device?

Hastily spouted for your befuddlement
[T-Mobile Samsung Galaxy Note II] crazygerz:
no friend, not yet, but pit file and searched
[General Questions and Answers] PradeepMurugan:
i have a doubt how to create thread with options of click to show content button option i have searched all options in creating thread but i could not find it

some body please help me
[General Questions and Answers] xsenman:
use hide button on posting panel or

& [ /HIDE ]

&

Check this out! Links to useful Guides and " Banned " Documentaries ​
[General Questions and Answers] PradeepMurugan:
thanks now got it after your edit:good:
[General Questions and Answers] binoyw:
thanks

thanks
[T-Mobile HTC One (M7)] haZethew0rld:
Hello. After tons of tries, I finally achieved S-OFF so I was going to try to turn my phone into a GPe by using RUU. Everything was going fine, the install failed once like it should, but then, my phone just couldn't get found by my computer, I unplugged it, plugged it back, and when on fastboot, the pc won't recognize the device. Also, now I'm getting this when I boot into fastboot , BTW, I've been reinstalling drivers like crazy for like an hour now, nothing seems to work, when I boot the phone normally, it does find it though, any help? Thanks.
[T-Mobile HTC One (M7)] ilikecars212:
I'm having the same issue. Bought it w/ TWRP, s-off, and gpe rom. hboot is 1.54. The computer doesn't detect it in fastboot. Also, I'm not getting the tampered flag, just unlocked.
[Moto X Original Android Development] jcase:
My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.

First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.

SlapMyMoto requires you to be on the 4.2.2 Camera update, you can find the firmware for your device below:

ATT- http://sbf.droid-developers.org/download.php?device=0&file=22

Verizon - http://sbf.droid-developers.org/download.php?device=0&file=55

Step1)

Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage

adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar

Step2)

Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://xdaforums.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/

Connecting over telnet, and run Stage1 with this command:

dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step

Step3)

Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command

dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

Once the device has rebooted, please take the 4.4 OTA.

Step4)

Now that we are on 4.4, we can finish the process with adb shell:

adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper

Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
[Moto X Original Android Development] AaronCompNetSys:
After taking the 4.4 OTA in step 3, if you then take on the 4.4.2 OTA update afterwards, the write protection off will be reverted and /system/ will once again be locked. There is no known way at this time to reverse this for users with locked bootloaders.

If you are on 4.2.x, you will be prompted for the 4.4 OTA update before getting the 4.4.2 OTA. You should complete step 4

before

deciding to take on the 4.4.2 OTA or not.

Other relivent quotes from jcase:

^(From another thread, but a comon question in this one)^

Possible mirror, not verified: magnet:?xt=urn:btih:CDARPSOTRY7CO4EY6K6SNWVASPBPX46S

Note: I will be reviewing threads and duplicating posts here to ease others finding them. PM me if you feel you have been misquoted or have something I missed.
[Moto X Original Android Development] bejahnel:
You are the MAN!!! Amazing work!
[Moto X Original Android Development] freak4dell:
Says he won't release a root method for 4.4, has to deal with whiny, entitled people that think he's selfish for doing so, and still ends up releasing something. Now that's what I call a class act.
[Moto X Original Android Development] brewcrewwheels:
i just went from 6 to midnight. damn, i love this community. now just need xposed for 4.4 and all will be right in the world.
[Moto X Original Android Development] Coderedpl:
10$ sent to you sir.

Thank you!
[Moto X Original Android Development] jcase:
Actually, i didn't really release a new exploit, and I won't be. This is the same primary exploits as motoroot/rockmymoto/pwnmymoto, just instead of installing su, it plants a "backdoor". Since they allowed us to downgrade, we were able to do this.
[Moto X Original Android Development] freak4dell:
True, but a method is a method, in my eyes.

I gotta wonder if Motorola left the ability to downgrade as somewhat of a subtle way of making up to the community for not being able to unlock the AT&T and Verizon versions. They're just too good at making secure bootloaders to make me think that it was just overlooked.
[Moto X Original Android Development] a1exus:
Thank You!!!
[Moto X Original Android Development] monkespit:
Thank you for all the great and hard work you do for everyone in the consumer motox community.

I will not whine or nag, I will wait patiently until it is complete and ready. I don't have as much time for testing and tinkering like in the droidx days.

So again, jcase, thank you thank you!
[Moto X Original Android Development] goose71:
wifi tethering

This is awesome news, however, does anyone know if wifi tethering works on 4.4? I've heard that it's broken on kk.
[Moto X Original Android Development] icon123:
Thanks jcase! Rooting vzw on 4.4 worked great!
[Moto X Original Android Development] Corvida:
If I did these steps correctly, should I see the following message when opening SuperSU:

"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
[Moto X Original Android Development] Sinderan:
Do you mean gpt.bin and logo.bin? Those are only ones in the camera OTA. I really should have checked before pushing the setup.sh, cause now I just boot to fastboot and don't wanna flash the wrong thing.
[Moto X Original Android Development] jcase:
From the 4.2.2 camera firmware, I clarified in OP now.
[Moto X Original Android Development] Sinderan:
Ok, I thought so, but the .mismatched extensions made me a little nervous to flash.
[Moto X Original Android Development] GuestK0077:
Awesome! Can't test it yet though, as I am in Canada on Rogers and we haven't gotten the update yet. It's still a relief knowing that I can get root when I get the update though. Thanks!
[Moto X Original Android Development] ericizzy1:
can anyone confirm this?
[Moto X Original Android Development] mercado79:
[MENTION=2376614]jcase[/MENTION], i know we're waiting for an update/fix for the reboot recovery issue, but i thought i'd mention that step 5 didn't work as described for me:

the last part didn't happen. after pushing the recovery.sh file (to data local as setup.sh), then doing an adb reboot, the phone never automatically reboots to the bootloader. maybe i'm missing something though. are we supposed to "quickly reboot" or is this supposed to happen on its own?
[Moto X Original Android Development] imnotmikal:
It is supposed to do it automatically, but the Verizon model is missing some dependency for this method.

Jcase said he has a fix and will work on it soon, but for now, do not do this on the Verizon model. Return to 4.2.2 for now.
[Moto X Original Android Development] MaddHatt3r:
What carrier are you on? Maybe it's related to that.
[Moto X Original Android Development] eyc:
I give up. Every time I try to push the various files in step 6, I get a different amount of KB/s transferred. I have no idea why that's happening. I'm buzzed. ****.

*** Maybe I'll try this on my Mac.
[Moto X Original Android Development] MaddHatt3r:
Keep in mind, this is still just a beta release. There very well could still be some bugs in there.
[Moto X Original Android Development] eyc:
Holy balls. Tried on my mac and it worked first time. Like buttah! God, that was so satisfying.
[Moto X Original Android Development] tejaskary:
[MENTION=2376614]jcase[/MENTION]: Really stuck on last step....The command echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper fails with permission denied.....I retried step 6 multiple times....I also tried going back to step 5 and retried steps 5 and 6 still it gives the same error....

Should I repeat the whole series of steps again or is there a way out?
[Moto X Original Android Development] eyc:
I tried starting from step 6 a dozen times and I just couldn't get it to work. I never tried going back to step 1. I bailed and went to Mac and it worked fine.
[Moto X Original Android Development] pborner:
i get a message on step 4 saying (bootloader) variable not supported! error:cannot open 'recovery.img'

Any ideas what im doing wrong?

EDIT: I have a locked bootloader. Did some reading and realized that i cant flash a recovery image because of it. (Thats what i understood anyways)

Does this mean im screwed for rooting 4.4?
[Moto X Original Android Development] shane1:
You can't flash a custom recovery while locked. This root IS for locked phones.
[Moto X Original Android Development] deckard_67:
Slapmoto on .54 AT&T

I'm on .54 of AT&T with locked bootloader... Do i have to forget slapmymoto procedure ???

Because i know it's not possible backward from .54 to .51
[Moto X Original Android Development] pborner:
Its not a custom recovery...

Then how do i go about this part of step 4?

Wait for the bootlaoder screen to appear

Code:

fastboot flash recovery recovery.img

fastboot reboot

I get the error as mentioned above...

(bootloader) variable not supported! error:cannot open 'recovery.img'
[Moto X Original Android Development] shane1:
Did you try putting the recovery.img into whatever location your fastbooting from?
[Moto X Original Android Development] pborner:
i put it on my internal storage on my phone...

Does it need to be in my adb folder on my pc too?

EDIT: I feel like a dumb ass!

Sorry for the stupid questions...

That step worked now :sigh: i will try to continue on!
[Moto X Original Android Development] shane1:
I would try that. I have a folder set up for fastboot and put everything that needs to be flashed into it and had no problems.
[Moto X Original Android Development] pborner:
Thanks for your help!!! on last step now waiting 1-2 min then i will install supersu.

Many thanks to JCASE! You rock man!
[Moto X Original Android Development] shane1:
No problem glad it worked.
[Moto X Original Android Development] anotherfiz:
Are there any negative consequences to downgrading the bootloader in regards to 4.4 operation?
[Moto X Original Android Development] deckard_67:
With locked bootloader, is there any possibility to downgrade from .54 AT&T to .51 or the slapmymoto procedure is also valid for .54 AT&T firmware ???

Thanks in advance..
[Moto X Original Android Development] shane1:
I don't know the science of it but I have yet to notice anything. Everything is running as good as it was before.
[Moto X Original Android Development] nexus7lte:
Big props for this! I find myself hesitant to commit to trying this with many people running into issues. Im just tired of starting from scratch again only to run into an error message and then where does that leave me?

Does this work the same way as the rockmymoto in that you have to boot to recovery in order to write to the system?
[Moto X Original Android Development] :
Hrm, I'm running into the 0x56 error in the bootloader, trying to flash the 4.2.2 recovery.img, even though I'm running the 0.5c version.

edit: derp, trying the steps in the original post now.

---------- Post added at 11:39 AM ---------- Previous post was at 10:53 AM ----------

Anyone having trouble toggling Bluetooth in the instructions?

On my device, there's basically no delay at all between the command being entered in the adb shell, and the device rebooting. I don't really have any time to toggle Bluetooth after I hit enter in the adb shell - virtually immediate reboot.
[Moto X Original Android Development] shane1:
I also didn't have time to toggle Bluetooth but continued on and it worked.
[Moto X Original Android Development] Dark9781:
It didn't give me any time to toggle either, but I'm rooted so it shouldn't be a big deal.
[Moto X Original Android Development] :
Okay, I've gone through this about 5-6 times now. I'm experiencing the 0x56 error, so I'm at step 6.

I push the scripts using ADB successfully, and reboot. Run the ADB shell, and execute the command - IF I have the quick settings panel pulled down, I sort-of have time to toggle BT before the reboot happens. At least, when I long press the BT icon, I feel the device vibrate before the reboot. This all happens virtually immediately.

Then I run the second command - same deal as the first. If quick settings is pulled down, I can just barely get the device to vibrate an acknowledgement of the BT toggle before the reboot happens.

In either case, the device will reboot right away regardless of whether I toggle BT.

After the last reboot, though, the device sits for a while and SuperSU still complains that there is no SU binary installed.

Verizon Moto X, using 0.5c of the script.
[Moto X Original Android Development] ericizzy1:
i still get that it cant create the folder and permission denied (step 6 went well, did it over 10 timew, trying to get this to work))

guess will have to wait...
[Moto X Original Android Development] TheDave1022:
I'm going to hold off on this until more people report success. Is there any reason to use SlapMyMoto vs using a safestrap 4.4 stock rom, which just got released on rootz? I already have safestrap installed and didnt take the 4.4 upgrade.
[Moto X Original Android Development] shane1:
[MENTION=237516]binary[/MENTION] when you open su press install binaries if you've rebooted since the initial attempt make sure to boot through recovery first.
[Moto X Original Android Development] brad0383:
Thanks jcase! Worked great on my VZW Moto X!
[Moto X Original Android Development] natezire71:
Yeah, SafeStrap doesn't work on 4.4.
[Moto X Original Android Development] lowvolt1:
nevermind
[Moto X Original Android Development] tjohnstone3:
So I was able to get root to work for my phone following the instructions...but is anyone else having issues w/ GPS? I can't get a lock w/ any app (4Square, Maps, Waze, etc). Wondering if I just need to run through the steps again or if anyone has any suggestions/has run into this?
[Moto X Original Android Development] natezire71:
Check the location settings. ;)
[Moto X Original Android Development] tejaskary:
I am getting the 0X56 error as well using version 0.5c after the last command.....Were you able to fix it?
[Moto X Original Android Development] natezire71:
[MENTION=2376614]jcase[/MENTION], will there be issues (i.e., slow boots or something) because we're using the downgraded bootloaders?
[Moto X Original Android Development] tjohnstone3:
Appreciate the attempt at help, but don't you think that is the first thing I checked? Location is turned on, mode is on High Accuracy. It isn't the location settings.
[Moto X Original Android Development] shane1:
You get it yet?
[Moto X Original Android Development] :
Yes, I "fixed" it by doing a full re-image through RSD to the camera update version, wiping user data etc., then re-following the original steps.

I'm now rooted on 4.4!

Big thanks to jcase. Donation to follow.
[Moto X Original Android Development] MaddHatt3r:
Don't get snide with someone that is trying to help. Minor details are frequently overlooked. If you're going to have that kind of attitude, don't bother coming around here. Nobody here owes you anything.
[Moto X Original Android Development] lowvolt1:
Sweet! Fourth time was a charm.

Here's what I did. This may or may not be your fix.

I had previously rooted with Rock on 4.2.2. I also downloaded the first version of Slap 0,5. I decided that I would start with a clean slate.

I deleted my adb tools folder and everything in it. I then extracted adb tools folder again and moved Slap 0.5C to my fastboot folder. Then I moved the files I needed from 4.2.2 to my fastboot folder.

I followed the instructions exactly, even went as far as copy and paste into cmd. (Maybe everyone does that) The only difference in the instructions was that I didn't use telnet. I used "puttytel" but it is the same thing. I just like "puttytel" because telnet on my windows 7 machine doesn't play well with me.

I waited a good 5 or more minutes between reboots in the instructions. So every time the instructions said to reboot I would do that and then go do something for 5 minutes or so to let it all settle in. then continue.

After the last step I again let it sit undisturbed for about 5 minutes. Went to the playstore and downloaded SuperSu, Installed it and opened it up. It told me to install binaries, I did, and BAM! root.

Thanks for everyones input, and a Huge beast thanks To JCASE!!!!!!!

---------- Post added at 10:22 AM ---------- Previous post was at 10:17 AM ----------

Yeah, My word that was some work. But what a great learning experience.
[Moto X Original Android Development] tjohnstone3:
Not having an attitude, sorry it came off that way. I should have noted in my original post that I had already verified location settings were accurate and that I had toggled them on/off multiple times.

Also forgot to mention in my original post that I really appreciate the root method jcase, awesome work.
[Moto X Original Android Development] tejaskary:
Good to know, but did you do anything different the 2nd time? I am on the same route now, currently installing the 4.4 OTA
[Moto X Original Android Development] TheDave1022:
So this doesnt work?

http://rootzwiki.com/topic/108826-romsafestrapxt1060-stock-rooted-vzw-140455-kitkat/
[Moto X Original Android Development] natezire71:
Excuse me. I was quoting Hashcode for using Safestrap on 4.4. I didn't know someone made a Safestrap 4.4 ROM. My bad.
[Moto X Original Android Development] tejaskary:
No luck the second time too I still get an access denied on this

echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper

After the 4.4 update, my PC does not recognize the device through adb immediately....Takes around 60 seconds or so...This was not happening in 4.2.....I think this has something to do with it?
[Moto X Original Android Development] StephenMilone:
another successful verizon user here - thanks jcase!
[Moto X Original Android Development] forumsid987:
I have a few questions: can a Verizon user on 4.2 camera update that got root though the original motoroot method, before the camera update ota, and just had it survive the camera ota use this method without losing all my data? No system files were modified.

Also will this method take away my stock recovery or leave me with some big open vulnerability that someone could use to get into my data even though my phone is encrypted? Does this leave me with a way to factory reset my phone?

Thanks!
[Moto X Original Android Development] mistermojorizin:
i'm in a similar situation at 4.2 camera update wit original motoroot. did you upgrade to 4.4 yet? did motoroot survive or do you have to use motoslap?
[Moto X Original Android Development] zwolf4444:
I'm using 0.5c and still getting 0x56 errors. Any thoughts?
[Moto X Original Android Development] :
The first time, I attempted to keep my userdata by simply re-applying the various images without wiping anything.

The second time I just blew it all away on a standard RSDlite re-image, and started from scratch.

Root will not survive the 4.4 update. You will have to follow the process in the original post. I tried applying SlapMyMoto on top of a stock install w/ RockMyMoto for root, but it refused to install. You need to have a clean, unrooted install.

Did you proceed forward with Step 6 after the 0x56 error as it says in the original post?

After some trouble, I went back to a clean system with RSDlite, allowing it to wipe my user data etc., and it worked perfectly the first time.
[Moto X Original Android Development] jcase:
Stop by IRC and give me a ping

freenode #motox
[Moto X Original Android Development] forumsid987:
Haven't upgraded to 4.4, holding out. Looks like we have to start completely clean though - no big deal.

Jcase - can you touch on some of my other questions in the post above?
[Moto X Original Android Development] shane1:
You should be able to flash system and recovery to be able to take the update, its based off the same exploits so you have no recovery and I think you can do a FDR through fastboot.
[Moto X Original Android Development] ericizzy1:
ok, got it to work, what i did diffrently this time, and it wasnt clear to me in the instructions, is on step 3 , i repeated this command twice: dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

after that, everything worked well, rooted on 4.4 on a VZ moto x

thanks so much the the OP
[Moto X Original Android Development] eyc:
That's interesting. You're supposed to actually repeat that command three times, based on my interpretation. Are you sure you have root?
[Moto X Original Android Development] ericizzy1:
rooted and tethering now
[Moto X Original Android Development] forumsid987:
Thanks for that info. Does this still leave it open for someone to get access to my data even though the phone is encrypted?