yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] evandena:
Pardon my ignorance, but can I install the camera update that just appeared in Google Play?

I'm not sure if the camera is still a dependency of root, even once rooted.
[Moto X Original Android Development] cvhovey:
Okey doke ... appreciate that clarification.

Now a question for anyone who knows the answer. I haven't used stock recovery for ages and for all the searching I've done, everyone seems to automatically understand "write protection off in recovery boot when you want to modify files in /system" ... is that a setting in stock recovery (wouldn't seem so)

or

write protection off by default when booting into stock recovery?

After several years rooting, I've been demoted to Total Noob ... at least when it comes to stock recovery. :rolleyes:
[Moto X Original Android Development] rift999:
When they are talking about recovery boot they are not talking about the stock recovery at that point. If you want to take a OTA you need to flash the stock recovery from the camera update. This root method overwrites the stock recovery with the boot image so that you can boot it as the normal OS but with WP off.
[Moto X Original Android Development] robotphood:
Any mirrors to the image links?
[Moto X Original Android Development] mistermojorizin:
I understand all of that and I know where you're making your mistake.

please try to understand: Root and Write Protection OFF are 2 different things. Pwnmymoto did root the pre-camera 4.2.2, BUT it also REMOVED STOCK RECOVERY to achieve write protection off. This removal of stock recovery would cause updates to fail. Root doesn't cause updates to fail. You don't have to be 100% stock to take the 4.2.2 camera update.

So that's the first place you made your mistake.

The second place is this:

You did NOT have to root using pwnmymoto pre-camera update. I rooted using motoroot which was the first root app that jcase put out for the Moto X (and it worked on my Droid Maxx). Now motoroot gave you pure root WITHOUT MESSING WITH STOCK RECOVERY. You could take the camera update, even though you had root, because you still had the stock recovery.

TL;DR:

1. if you had stock recovery, you could take the camera update, even though you had root;

2. pwnmymoto was not the original root method for pre-camera;

3. pwnmymoto was more than a root method, it also removed your stock recovery to achieve write protection off.

Please don't say my info is "screwed" - I've been following these specific phones and root methods since August 20th; you probably joined the party a bit later than that and are confused on this fine point.
[Moto X Original Android Development] Rebel908:
Just an FYI for anyone who might be in the same boat I am in (Used Beaups WP mod and can't get through the SlapMyMoto process anymore), I talked to JCase on IRC and he said he might have the time to fix procedural issue in SlapMyMoto tonight. Hope he has the time to do it :)
[Moto X Original Android Development] h1ghland3r:
Hello,

I was with RockMyMoto in 4.2.2, but I flashed 4.2.2 (and of course I lost root), then I got 4.4 OTA. Is it possible to use SlapMyMoto or is it impossible after these procedures?
[Moto X Original Android Development] Rebel908:
Yes you should, just follow the procedures to the T in JCase's original post.

HOWEVER, this assumes you don't have the WP mod from beaups. If you turned off write protection, SlapMyMoto in its current form will not work.
[Moto X Original Android Development] h1ghland3r:
? I don't get it

I'm now with 4.4 and I can't start telnet. Probably because I didn't start SlapMyMoto in 4.2.2. =/
[Moto X Original Android Development] trimax84:
Someone had that VZW 4.2.2 image, right? Could someone upload those please?

I got stuck on the fastboot gpt/motoboot/logo part (Step 5) and want to start over. Got error: cannot load 'gpt.bin' : No error

Thanks in advance!
[Moto X Original Android Development] wctaylor79:
Bump for anyone that can provide the files.. Stuck on #5 as well.. missing the extra files needed... I am sure there is a nice soul in the community that has them?? :) thanks in advance..
[Moto X Original Android Development] Rebel908:
Why are you trying to use Impactor and puttytel on 4.4?

Instructions, per JCase's first post are:

DOWNGRADE TO 4.2.2 w/camera update. It even states that if you started with a previous version, go to 4.2.2 and start from there.

Unfortunately the site hosting the files seems to be down. You also need to be able to use RSD Lite to flash the 4.2.2 file. Other than that just follow the instructions.
[Moto X Original Android Development] simo24:
Also looking for copies of the necessary files.
[Moto X Original Android Development] lowvolt1:
I have vzw ones

via my slapped KIT KAT moto X

---------- Post added at 08:23 PM ---------- Previous post was at 08:14 PM ----------

Weird. So why is it that everyone but you lost root when updating?

via my slapped KIT KAT moto X
[Moto X Original Android Development] kilgil27:
mind sharing? :D
[Moto X Original Android Development] lowvolt1:
Files are uploading to Dropbox. I will post when done. Probably in the morning.

these file right?

VZW_XT060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.XML
[Moto X Original Android Development] Toys Samurai:
My Moto X should arrive tomorrow. Assuming 4.2.2, pre-camera OTA is pre-installed, according to the following step:

I can just take the camera OTA, but don't take the KitKat update, do nothing else, and then I am good to move forward to step 2? Or, if my phone comes with the camera OTA pre-installed (but before KitKat), I can go straight to step 2?

If so, can someone tell me what the build number should be after the camera update?
[Moto X Original Android Development] kilgil27:
that's the one. Thanks!
[Moto X Original Android Development] niteglo:
I can't tell you the build number, but I will say that you will still need the sbf file listed for your phone linked in the OP, or another user can link you the correct file... I have only done this process once, but I believe that's required in order to restore the stock recovery at a later step.
[Moto X Original Android Development] mistermojorizin:
It is because you don't know that not everyone did (unless you asked EVERYONE). but just to prove my point, i did a very quick search and found another member sharing his experience with keeping root through the camera update and he even included screenshots as proof.

http://xdaforums.com/showpost.php?p=47287232&postcount=3

Now let me ask you, what is your source of info and why are you so sure about what happened with EVERYONE? Like i said, my source of info was JCase directly over gchat and my own personal experience following his advice (to not worry about the camera update messing anything up as long as i have stock recovery in place).
[Moto X Original Android Development] enjoimadcow:
I have ATT_XT1058_4.2.2-13.9.0Q2.X-116-X-17-54_CFC_1FF.xml and I want to upload it for download. Am I allowed to post a torrent link?
[Moto X Original Android Development] j.bruha:
I'll add my issue I'm facing to the mix now. I can also upload the SBF files everyone is looking for if that Dropbox link doesn't come through as I still have those files.

I followed this guide for the second time on a second Moto X and something must've gone wrong when trying to downgrade the bootloader. I tried finishing the process and followed the additional steps repeatedly to overcome this issue, but it looks like it won't budge.

The device is now on 4.4, not rooted, and using RSD Lite to try to drop it back down to 4.2.2 immediately fails with an error message "Failed to hab check for gpt_main: 0x35 preflash validation failed for GPT". The device still boots, still wipes just fine, but it looks like I can't do much else with it.

Not sure what else to try at this point. Kinda desperate and would be very grateful to anyone that could help.

Edit: MAYBE I SHOULDN'T HAVE BEEN TRYING TO RESTORE THE MOTO X WITH THE XT1080 FILES? MIGHT HAVE SOMETHING TO DO WITH IT???

I'm an idiot...
[Moto X Original Android Development] oplix:
I've tried everything but I can't get telnet to connect to the phone. Cydia Impactor loads properly, all phone settings are properly configured but it times out trying to connect 192.168.1.116 2222 (my phone's wlan).

No idea what to do. Tried both on my PC and my Mac.
[Moto X Original Android Development] zhp pilot:
If you post such a large file from dropbox and numerous people start downloading it there's a good chance your dropbox account will be temporary suspended for too much bandwidth. If you send me the link in PM, I'll upload it to my afh account.
[Moto X Original Android Development] ohmimpotence:
Just responding to say I got everything to work perfectly.

The main issue I ran into was trying to flash 4.2.2 from this link.

I had to add the line <step operation="erase" partition="userdata" /> to it otherwise I would get stuck in a bootloop.

Once I was over that hurdle, following the instructions were no big deal.

Much thanks to users flashallthetime and mschumacher69.

Just wondering if there is a way to install custom recovery with a locked bootloader? I see in the twrp thread it mentioned for unlocked bootloaders only. What about Xposed and Titanium backup?
[Moto X Original Android Development] Toys Samurai:
That's why I was lost when I read the instruction of step 1. It says "You need to get the camera update from http://sbf.droid-developers.org/ghost/list.php and flashing back to it." Now, assuming my phone arrives with 4.2.2, pre-camera update. If I take the OTA camera update, doesn't that mean I DON'T need to get that update from that URL (or from another source if it's no longer available.) If I do that, what does it mean to "flashing BACK" to it, when I am already ON that build, and NOT on KitKat? More specifically, if I am on 4.2.2, post camera update, with nothing else changed in the system (ex, on stock recovery, non-root, 100% stock), what else do I need to do to proceed with step 2?
[Moto X Original Android Development] XTRoRDiNAiRE:
Any word on getting an easier root for moto x Verizon? I'll donate if I need to for an easy root
[Moto X Original Android Development] wctaylor79:
Thats what I went with.. Got all the way to step 5... Issue then though is there are files that are needed through that download to proceed with the process.. At least that has been my understanding. . When you get to step 5 you need three files to push back. Those files are within that downlaod that is down.. Looking at the SBF site thought it appears he is working to get it back up.

From http://sbf.droid-developers.org/

Yeah, 2 HDDs had a failure ... reconstructing.
[Moto X Original Android Development] zhp pilot:
Its my understanding you still need the file as you have to pull parts from it for downgrading the bootloader. If you are already on the camera update then you can just start at step 2.
[Moto X Original Android Development] wctaylor79:
So.. you were able to use the dev edition SBF.. make the change and it worked with the non-dev vzw moto x? I just need a couple files out of the download. not the whole image.. I was hesitant to try since I am on non dev.. if you did use on the non dev I understand that if I try you are not responsible if I brick my own phone.. Just figure I would disclaimer myself before you reply.. :)
[Moto X Original Android Development] Toys Samurai:
Great. Thanks for your help! Now, I just need to wait for the link to come back up ...
[Moto X Original Android Development] skepian:
hello to All

can you please give me VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip this camera update link broken)

and tell me, i'm on 4.4 KitKat xt1060(non dev!), how to flash camera update? and will i get root access with this method?
[Moto X Original Android Development] mohlsen8:
If I'm rooted on the camera update already, can I get back to stock by flashing the stock system and recovery images, thereby avoiding wiping my data? Anyone do this (or is there an easier way)?
[Moto X Original Android Development] StephenMilone:
so i have to wipe and downgrade? I'm on 4.4 on a vzw x that root was never attempted. was going to attempt it now, but i'll wait til tomorrow, need my phone as is for tonight.
[Moto X Original Android Development] mj0528:
everything went as it was supposed to as i got no errors and followed every step but I can't update binary for su. Am i missing something?
[Moto X Original Android Development] mohlsen8:
did you reboot into "recovery" to do that? that's what you need to do.
[Moto X Original Android Development] mj0528:
yes, i did and then rebooted and tried again only to be meet with something that says that recovery is not supported so i did the last step and trying to boot into recovery now.
[Moto X Original Android Development] mohlsen8:
ah sorry, i dunno. i'm waiting to see if i have to wipe data or not before trying this, i just know the handful of times i've rooted my at&t and my wife's vzw i've always had that problem and had to remember to reboot with write protection off.
[Moto X Original Android Development] mj0528:
ugh, same thing happened. back to stock I go for now

---------- Post added at 09:52 PM ---------- Previous post was at 09:46 PM ----------

followed the directions to a T but no luck. I'll try in a few weeks
[Moto X Original Android Development] Coderedpl:
Jcase deserves all the credit, hard working guy for sure. Worked on my phone for a while and root & r/w bypass were achieved on Verizon Moto X with 4.4 OTA

Stay tuned, I'm sure he will be posting more info when he has the time.
[Moto X Original Android Development] jayboyyyy:
you don't have to wipe data. you just need to make sure everything is stock. You can use rsdlite, take out the commands of wiping user data, and be good to go. Or manually flash the things you need to without wiping user data found here

http://xdaforums.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
[Moto X Original Android Development] mohlsen8:
oh cool so i can just flash everything else and retain data. thanks.
[Moto X Original Android Development] jayboyyyy:
make a back up of your data first obviously, but i don't believe data should play a role in any of the hacks.
[Moto X Original Android Development] murso74:
i feel like i missed something, this worked much easier for me on rockmymoto... after the first dalvikvm command it says to run 'adbreboot' but i get sh: adb: Permission denied.

maybe i shouldn't be doign this hung over

edit: nevermind, brain is deff fried right now
[Moto X Original Android Development] brianr134:
SlapMyMoto0.4.1d works with Verizon MotoX
[Moto X Original Android Development] jcase:
try 0.5
[Moto X Original Android Development] murso74:
ok so i got about half way through the process (took the 4.4 update after running the dalvikvm commands 3 times through telnet) and it looks like the process has changed in the OP... i can't get the phone to respond to adb commands anymore. am i stuck on 4.4 without root now? not sure what step to go to now.. i was attempting to pull kkboot when i noticed the changes

ok, after replugging the phone into the computer i got a mac address confirmation that i ok'd and it let me run adb commands again, however i'm still unsure what i'm supposed to do now that the order has changed in the OP... i think the SlapMyMoto got updated while i was trying this out and now the new commands dont' apply to me
[Moto X Original Android Development] id0l:
Followed it by the books but every time I push setup.sh to /data/local/tmp/setup.sh when I check to see if the file is there it says it does not exist. So when it reboots su does not get installed. I do have rw access in recovery though but I just can't get su to work.
[Moto X Original Android Development] jcase:
Please make sure you post what version of SlapMyMoto you are having issues with, if you want help on it
[Moto X Original Android Development] murso74:
i was working with 4.1b. i had just installed the 4.4 update, and i think the OP had said to pull the kitkatboot? not sure. unfortunatly i refreshed the page and the command dissapeared and we were at SlapMyMoto .5
[Moto X Original Android Development] aFancyTickler:
so after all the steps the phone rebooted into bootloader cause it failed to boot in recovery so i reflashed recovery and su didnt work so i redid step 6 and my phone didnt reboot so i booted to recovery manually and it stoped me at bootloader so i reflashed the kkboot to recovery and did a normal boot and tried the su and it failed so booted again into recovery and it worked and su installed. lol , did this on 0.5 VZW consumer moto x
[Moto X Original Android Development] hank110:
Using 0.5, finished all steps. After pushing the script files and doing the adb reboot, the phone automatically rebooted as expected. However I'm now getting a bootloader error when trying to boot to recovery: "Failed to nab check for recovery: 0x56"

Edit: I can successfully boot up normally, just not into recovery (which should be system RW mode).
[Moto X Original Android Development] ohmimpotence:
I have a Tmobile Moto X so that''s why the dev edition worked.
[Moto X Original Android Development] lowvolt1:
I sent the link to zhp pilot. He should upload it soon.

via my slapped KIT KAT moto X
[Moto X Original Android Development] skepian:
is this method give me a root access? i got locked XT1060 VZW non dev

what if i want to stay on 4.2.2 is there a easy downgrade method on forums?
[Moto X Original Android Development] wctaylor79:
Ah ha.. well thats that.. Glad I asked.. :) Thank you
[Moto X Original Android Development] lowvolt1:
If you want to stay on 4.2.2 and you have the camera update, root with RockMyMoto. If you want 4.4 and roit , you have to start on 4.2.2 camera update and use SlapMyMoto.

If your already on 4.4 you can downgrade to 4.2.2 using the files I sent to pilot. They will be posted here soon.

via my slapped KIT KAT moto X
[Moto X Original Android Development] skepian:
i'm now on 4.4

please write a code to flash 4.2.2 via adb/fastboot.... (using the files I sent to pilot. They will be posted here soon.)

THNX
[Moto X Original Android Development] lowvolt1:
Just use rsdlite and downgrade to 4.2.2 using the files when they are posted.

via my slapped KIT KAT moto X
[Moto X Original Android Development] h1ghland3r:
Can I downgrade to 4.2.2 without unlock my bootloader?
[Moto X Original Android Development] skepian:
is there is a problem if i got LOCKED bootloader?
[Moto X Original Android Development] zhp pilot:
If you're on win8.1 such as myself, you can use the method from here if RSD is not working.

http://xdaforums.com/showthread.php?t=2560571

I'll have the sbf file uploaded in a few minutes. TWC up speeds blow, 2Mbps.
[Moto X Original Android Development] skepian:
so waitin' for your upload...

what about bootloader? i got it in LOCKED.... it's a problem?
[Moto X Original Android Development] lowvolt1:
You can root with a locked boot loader. But you can't install a custom recovery.

via my slapped KIT KAT moto X
[Moto X Original Android Development] zhp pilot:
Ok peoples, here is the VZW camera update file.

VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip

Edit: I have updated the above linked file. The new one already has the "get var" line omitted from the xml.

There original unedited file can be found here
[Moto X Original Android Development] lowvolt1:
I'm mobile right now. Can I do it from mobile?

via my slapped KIT KAT moto X
[Moto X Original Android Development] zhp pilot:
Only if you have the original file on your phone. Most file explorers will give you the md5 as part of the file properties. Md5 reported by afh is b349f480216cad3bce9e32a32c20304b
[Moto X Original Android Development] skepian:
if i flash it with SRDlite - i got stock 4.2.2 right?

im now on 4.4 with LOCKED bootloader
[Moto X Original Android Development] zhp pilot:
Yes, It will wipe all data too so back up whatever you need.
[Moto X Original Android Development] lowvolt1:
Remove get-var line

via my slapped KIT KAT moto X

---------- Post added at 08:23 AM ---------- Previous post was at 08:23 AM ----------

I don't. Will have to check tonight

via my slapped KIT KAT moto X
[Moto X Original Android Development] zhp pilot:
I should of just removed that from the xml before uploading
[Moto X Original Android Development] skepian:
sucсess

roll back with RSD Lite

thanx to All!!!

thank you zhp pilot for the link!

will stay on 4.2 until next update,

on 4.4 i got no data, only voice :( (Ukraine, Intertelecom, ruim card), 4.4 can't read APN from ruim card i think.....
[Moto X Original Android Development] sarshadd:
Does this method work if I've already accepted the 4.4 update?

Or is step 1 re-flashing 4.2.2 so the subsequent steps will work??

I'm trying to brute force root my Dev Edition so I can back up before unlocking the bootloader (and subjecting myself to it's corresponding wipe)...
[Moto X Original Android Development] skepian:
step 1 re-flash your device to 4.2.2
[Moto X Original Android Development] kilgil27:
Wait for the bootlaoder screen to appear

Code:

fastboot flash recovery recovery.img

fastboot reboot

nothing happens when I do this. I get "fastboot is not recognized as an internal or external command" where should I be running this from?
[Moto X Original Android Development] zhp pilot:
I have updated the VZW camera update sbf file in post 593 to include a pre-edited xml file with the "get var" line omitted.
[Moto X Original Android Development] rockingondrums:
Someone posted in the rockmymoto thread this interesting tidbit:

So if I keep the BL locked, install the OTAs to get up to KK (I just received my 4.2.2 in the mail and haven't even activated the phone yet), and then root 4.4... what they're saying is that if I ever need warranty service on the phone, I can unroot it and send it back without an issue? Because from what I understand, Moto would either check the device (standard procedure of OEMs) or see if the device has been given an official unlock code (which voids the warranty). If my device has never received that code, and all KK devices show that flag set off, then they can't prove I've ever rooted it, correct?

Or is there currently no way to remove signs of root without unlocking the bootloader?
[Moto X Original Android Development] Dark9781:
Yup. As long as it hasn't been unlocked and you are on KK. If you have a Dev edition Moto no longer voids the warranty if you unlock it.
[Moto X Original Android Development] rockingondrums:
I know that Moto no longer voids the warrany on dev phones, but I do not have a dev phone. But if the flag is always set off b/c of KitKat, all I'd have to do is unroot. The question is, can I unroot? Or perhaps, if I simply erase the supersu / superuser apk, will there be plausible deniability? I mean, I don't foresee needing the warranty and I bought the Accidental Damage protection. I just like to know. Knowing is half the battle (for those of you old enough to get that reference)
[Moto X Original Android Development] Dark9781:
You should be able to do either or. If you go the route of erasing supersu you may also want to delete su in the xbin directory or just use the unroot option in supersu.
[Moto X Original Android Development] robotphood:
For clarification, if I'm downgrading from stock 4.4 there is no way to avoid a data wipe? Also which file for t-mobile (xt1053)?
[Moto X Original Android Development] sheltem:
I got this working on my T-Mobile Moto X! Once I got my telnet and ADB issues out of the way, it was very straightforward. Thanks jcase!

Would this also work? Assuming you are on 4.4, use RSDLite to downgrade to 4.2.2 camera, then take the 4.4 OTA update? That way the root check flag wouldn't impact you because of 4.4 and the updates should eliminate the SU traces?
[Moto X Original Android Development] Dark9781:
Have not tried it. I was rooted on 4.2.2 before upgrading to 4.4 so there isn't anyway for me to test that. From past experience with Moto they have never checked to see if I was rooted. I've warranty exchanged with them twice. Once before Google took over and once after. Both phones were rooted and they didn't give me any issues.