yashsingh1/xdaforums huggingface dataset:
[Moto X General] malcolmputer:
It's WORKING!!!

I did it. I now have an update.zip that you can flash from SafeStrap, keeping your recovery where it is at already.

This means that if you f- something up, you can just sbf back to stock 4.2.2, root, safestrap, my update.zip, and then be back at rooted 4.4.2, with WP off.

I have a road trip tomorrow, so I will be on my mobile, but in the mean time.

Here is the update.zip

http://www.leetnet.net/update_SafeStrap_4.4.2_RW.zip

here is what I flashed after the update.zip

fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

DO NOT FLASH RECOVERY!!! YOU WILL BRICK IT, OR WORSE NEVER BE ABLE TO FLASH 4.2.2 AGAIN!!!!

and I flashed the SuperSu.zip (in SafeStrap) after the first boot.

Real HOW TO guide to follow tomorrow evening (post 6 PM EST 5/1/14).
[Moto X General] RobertsDF:
Where did you get the files that you flash with fastboot?
[Moto X General] malcolmputer:
from the 4.4.2 update sbf. Same place I got the RW system image.

AKA here : http://sbf.droid-developers.org/phone.php?device=0

DO NOT FLASH RECOVERY FROM THERE !!!!
[Moto X General] RobertsDF:
Nevermind, I wasn't thinking right. Thank you for your help, I will do this shortly and report back!
[Moto X General] malcolmputer:
Don't forget WP no MO also. You should do that while still at 4.2.2
[Moto X General] RobertsDF:
Well here's an update. I successfully flashed the update and am now on 4.4.2. I am still able to get into safestrap and everything so that's looking good. I flagged the SuperSU.zip in safestrap but I still do not have root. I am going positive that I did the wpnomore and it worked because I got the zero when it checked for it.
[Moto X General] iKrYpToNiTe:
I extracted the system.img and threw together a Safestrap and Unlocked version tried uploading last night but it didn't upload correctly, I'm reuploading now will post the ROM later tonight as long as this upload is good!
[Moto X General] malcolmputer:
I bet you grabbed the wrong SuperSu.zip

Get the one from here: http://download.chainfire.eu/supersu

It should actually root your device for you, then install superSu

Let me know if that doesn't work.

---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------

But... I already got one :(

Seriously though, I would be more than happy to remove my rom if you come up with one. I just put mine together while we were waiting on yours. :angel:
[Moto X General] jbrukardt:
Heck no. This is going to take a bit of troubleshooting and bug fixing, and two minds are better than one. Props to you for getting it out first malcomputer, awesome work. This isnt about who was first though, its about getting a good product to the community, and combined efforts are exactly how that is done.

First step down, now the WpNoMO and SuperSU integration come (if kryponite didnt already do it). Gotta get our write protect unborked or root isnt worth much
[Moto X General] RobertsDF:
Well somehow I got into a boot loop!

It was working fine and I had gone into safestrap a few times trying to get SuperSU working but then I decided to try booting into my 4.2.2 rom that I had setup on slot 1. It booted into it but I could never get past the "starting apps" thing, so I restarted it and then it just boot-loops over and over again! It does show the safestrap boot screen where it gives you the option to go to recovery or continue, but when I select recovery, it just goes back into a boot-loop.

I am about to start completely over with the 4.2.2 sbf, I'll let you know how it goes.
[Moto X General] malcolmputer:
I checked mine out, and it seems to be whenever I use a slot other than stock it boot loops until I go into recovery and activate the stock slot.

Need to get that figured out before it is "prime time ready".

Hopefully Kryptonie's fixes it.
[Moto X General] jbrukardt:
holdon guys, i have some insight into that problem. I remember reading elsewhere that you had to use the stock slot and it gave a good explanation as to why. Lemme find it.
[Moto X General] jbrukardt:
ok, it was from Kryptonite, i knew it read it someplace

http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/

First post for his verizon safestrap rom.

Instructions to install this rom for Safestrap Users, read every step before you start...

1. You need to be rooted on 4.2.2 or 4.4 with Safestrap installed

2. You also need to have disabled write protection via MotoWpNoMo

3. Boot into Safestrap Recovery

4. Factory Reset the STOCK Slot in Safestrap DO NOT wipe the /system it can cause issues

5. Flash the Rom zip to the STOCK Slot (this will take a couple minutes)

6. Once the Rom has finished flashing, reboot to the Bootloader within Safestrap

7. Plug your Moto X via usb cable into your computer the Bootloader screen should say usb connected now

8. Unzip the "Moto X Kernel and Radio Flasher.zip"

9. Open the extracted folder and find the FlashMyMotoX.bat and run it

10. Choose option 8 within the FlashMyMotoX utility to flash the 4.4.2 KitKat Kernel

11. Once it finishes get back to the options and choose option 9 this will flash the 4.4.2 KitKat Baseband

12. Once it finishes successfully unplug your usb cable and reboot the phone

13. Enjoy 4.4.2 KitKat!

So im presuming that his rom once he gets it uploaded should address this.

It sounds like that may be a safestrap issue... any insight into that [MENTION=4850320]iKrYpToNiTe[/MENTION]? I can ping hashcode and see if he's aware of what might be causing it.
[Moto X General] jbrukardt:
A little more insight
[Moto X General] Rashed97:
You have to use the stock slot because of the system files that correspond to the bootloader and modem. What Safestrap does is use the files from the stock slot to load the other slots, only replacing the needed files for the new OS. By not updating the stock slot the phone won't boot because the 4.4.2 files aren't there.
[Moto X General] jbrukardt:
mmmm, there we go, that makes sense.

Would it be possible to still run a backup virgin rom in slot 1, after flashing the stock slot with the incoming safestrap compat 4.4.2?

Scenario 1) Another copy of the 4.4.2 rom that you keep as clean as possible to boot into in case you brick your stock slot rom

Scenario 2) A copy of 4.2.2 jelly bean for the same purposes. (The problem here might be that jelly bean wont boot on the 4.4.2 files, not sure if theyre backwards compatible)
[Moto X General] RobertsDF:
I remember reading that warning,so I did flash the 4.4.2 rom onto the stock slot, my "stock" 4.2.2 rom was the one that was on slot1. I am not able to go back into safestrap recovery to switch back to stock slot because it boot loops even after selecting the recovery option on the safestrap boot screen.
[Moto X General] jbrukardt:
hmm, ok. Any luck RSD'ing back to 4.2.2? (dont RSD to 4.4.2 or you'll lose your ability to remove write protect forever)
[Moto X General] iKrYpToNiTe:
Sorry I replied to jbrukardt's post that he linked from rootz to here and didn't see that you had posted yours. It doesn't matter to me I was just going to throw a thread up in the development section with the instructions, ROM, and altered Flashing Utility. It's up to y'all, I came in later so I don't want to step on someone else's progress.

Unfortunately rom slots are kind of useless, and cause more problems than they're worth, I recommend never to touch rom slots on the Moto X. Now to fix your phone, as soon as your phone goes black during the bootloop hold down the volume down button until you get to the bootloader screen. When your on the bootloader screen press the volume down button until bp-tools is highlighted, then press the volume up button to select bp-tools this should boot you back into Safestrap. Then delete the rom slot and boot to the Stock slot!
[Moto X General] jbrukardt:
Please toss yours up if you dont mind :) ?
[Moto X General] Rashed97:
Nope. The kernel and modem are set for 4.4.2 now, which won't work with 4.2.2
[Moto X General] iKrYpToNiTe:
I'm at work right now, but I will definitely post it later this evening when I get home.
[Moto X General] jbrukardt:
awesome. Thanks for putting it together.
[Moto X General] Rashed97:
Whats the difference in your packages? Does one work better than the other?
[Moto X General] malcolmputer:
Well... right now... mine exists ;)

In all seriousness, I assume that his will be more polished, and will most likely not require the SuperSu.zip update.

I haven't quite got my guide written, so he might beat me to it.
[Moto X General] Rashed97:
Ugh I hate SuperSU. I prefer Superuser (the CWM version)

Just a point of inquiry, are you wiping data before flashing?
[Moto X General] glarepate:
I really want to be able to have a rooted 4.4.2. I have been avoiding rooting because I didn't really need it and because the new 4.4.2 bootloader closes the write-protect removal workaround, thus killing all the real value of having root. Now I'm starting to get excited.

I got the OTA last night and told it to hold off for now and alert me at midnight tonight for another chance to update. So I am antsy to see if this can be done before then but still anxious too because if I brick then I am totally screwed and will only be able to afford a Moto G to replace it.

So for now I'm holding off on doing the RockMyMoto/WpNoMo and SS-recovery process but still on edge because it would be alpha-geek kEwL to have a rooted 4.4.2 phone!

Also, is it true that once WpNoMo is done it cannot be undone, even if you flash the stock 4.2.2/JB ROM back onto your phone? Something to do with how it modifies the Recovery or some-such thing? Or is it only un-undoable if you install the KK bootloader? That little complication is nagging at me and the possibility that it might come back to bite me later adds another layer of anxiety.
[Moto X General] jbrukardt:
Im thinking we're where you want to be (wp off, root on, 4.4.2) by this evening. That is, assuming you havent taken the ota, or the 4.4.2 bootloader in any way. If you have, no wp off for you. ever.

I dunno about that "perma-change" of WpNoMo. The dude that authored it was always super super vague about what he actually modified and ive been too lazy to tear apart the exe and find out or snoop the stream. I doubt its as permanent as he says it is. A reflash of the recovery (4.2.2 recovery) would probably clear that in my opinion, but i could be wrong.

Once we get the process defined, lets let one of those guinea pigs (lucky SOBs) that got their bootloader unlocked test it first ;)
[Moto X General] Rashed97:
Flashing the bootloader/recovery will undo MotoWpNoMo in a heartbeat. IDK why you're want to do that, but just throwing that out there. I'm about to test the whole process on my Moto X (bootloader is still locked, but I can fix it if I do brick it)
[Moto X General] jbrukardt:
have JTAG on it or something?
[Moto X General] malcolmputer:
I wasn't wiping data, and the update.zip I made leaves it alone. To be honest, I didn't even think about it.
[Moto X General] Rashed97:
Nope, I've bricked enough devices to know how to unbrick them though :P

Sweet. I'll won't wipe then :)
[Moto X General] iKrYpToNiTe:
Hahaha mine has existed for a couple days and my Verizon version for months I'm still on the factory shipped bootloader, I just have a slow upload speed ;)

It's up to y'all I don't mind posting it, everything is uploaded and all I have to do is copy and edit my Verizon thread to here. Just let me know I'm finally home from work!

Nope sbfing backwards doesn't reverse MotoWpNoMo I tested it several times before I unlocked! Also there was a couple people that updated and kept write protection off and root!
[Moto X General] malcolmputer:
Alright guys, my guide is up. See here:

http://xdaforums.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233/post52348028

[MENTION=4850320]iKrYpToNiTe[/MENTION] feel free to put your guide together, options are good for everyone. I won't feel like you are stepping on my toes or anything.
[Moto X General] Rashed97:
Dang, weird... I'd think it would. Other than the bootloader/recovery and system, I can't think of any other place that it would be safe from factory resets (and we know system is out)
[Moto X General] malcolmputer:
According to the developer it is a "magical place", that is nothing we have heard of I guess.
[Moto X General] iKrYpToNiTe:
Alright just wanted to make sure.

Well the Moto X has 40 partitions a bunch of which never get touched via OTA's unless the bootloader is flashed. But that still doesn't wipe the partitions normally, but if you sbf to 4.4.2 I'm pretty sure that definitely resets it!
[Moto X General] Rashed97:
More like a goddamn hidden partition thats being a pain in the ass.....

We ought to inspect those partitions and see if we can find a bootlocker exploit :)
[Moto X General] iKrYpToNiTe:
Well I was lucky and was able to unlock via the chinese guy. There is a thread on here that list all the partition's name, number, and size.

Also guys I posted the rom I threw together http://xdaforums.com/moto-x/development/rom-stock-rooted-republic-wireless-165-t2738275/post52349180
[Moto X General] Rashed97:
I'm on 4.4.2 (very nice) and I didn't even have to clear data. Quite enjoyable. Now to figure out a way to root this thing... Even though I still have safestrap.
[Moto X General] malcolmputer:
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip flashed from safestrap is what I use.
[Moto X General] slgooding:
You guys are doing a great job. Keep it up. I know a lot of people are patiently waiting for a solid guide on how to do this! THANK YOU! Seriously, THANK YOU for your efforts!
[Moto X General] RobertsDF:
I was able to get back to 4.2.2 just fine. I couldn't get RSD lite to recognize my phone so I had to do all the fastboot commands manually but t worked just fine.

Darn, wished I would have seen this before going back to stock! good to know for the future though. I couldn't wait for any replies, I had to be at work and needed a working phone.

---------- Post added at 08:42 PM ---------- Previous post was at 08:38 PM ----------

I'm pretty sure that's what I had flashed and still didn't have root. You are able to use root and also wrote to your system?
[Moto X General] Rashed97:
Reflection time:

Holy cow. 4.4 is amazing.

1. MUCH lower memory and battery footprints. I'm averaging about 10% less memory usage and about 3% less battery usage an hour.

2. Stuff actually works (yes, I hated 4.2)

3. ART is pretty cool (boots faster, overall smoother)
[Moto X General] glarepate:
I have been stalling so that I could see what results others were getting. Sooooooo, .....

Whose system did you use? I want to be done by midnight West Coast time, so type fast on your reply!!! :silly:
[Moto X General] Rashed97:
I just used malcomputers file. Opened safestrap, flashed it, rebooted into the bootloader and flashed the other files, then rebooted into safestrap again and flashed SuperSU
[Moto X General] glarepate:
Me too.

THANKS MALCOLMPUTER!!!
[Moto X General] slgooding:
I'm still on 4.2 and I'm getting ready to do the upgrade. I have root, but don't have write access to system when I'm booted into the OS. However, I can write to system from safestrap. Is that how it is supposed to work? If not, is there something I need to do before I update to 4.4.2?
[Moto X General] malcolmputer:
You need to have done MotoWPnoMO before you update. Follow my guide, and you will be fine.

http://xdaforums.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233

If you really don't want to flash back to stock, I guess you technically could start at step 4 if you already have root and safestrap, and you are on 4.2.2
[Moto X General] slgooding:
Excellent. I just realized that I have it all setup properly. I just rebooted via the safestrap app and it booted with r/w access. I'll install from step 4 and let you know how it goes!

---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------

A post was just called to my attention that has a full guide for installation:

http://xdaforums.com/moto-x/development/rom-stock-rooted-republic-wireless-165-t2738275/post52349180
[Moto X General] slgooding:
Write protection enabled?

When rebooting from safestrap to disable write protection, does the app then show write protection disabled (after you boot back to the OS)? Write protection is still on for my device after the reboot...

To clarify... I (stupidly) used the guide on this page...I'm not sure why I didn't just do what you guys did:

http://xdaforums.com/moto-x/development/rom-stock-rooted-republic-wireless-165-t2738275/post52372080
[Moto X General] malcolmputer:
The best way to check it is with ADB getprop (the line suggested in the WP disable thread)

On one of my phones I had to run it twice, not sure why.
[Moto X General] kellison007:
Sorry to beat a dead horse, but if we did following below...step by step. Are we screwed? As in no root ever?

Republic Wireless 4.4.2 update (I've given the update.zip to someone else to post; it's out there but I can't post outside links yet):

If rooted on 4.2.2, restore stock 4.2.2 using the Republic Wireless 4.2.2 SBF and RSDlite

If on stock 4.2.2:

1. Rename the update to update.zip and copy to the root of your internal storage (name it update.zip, it didn't work for me this way with the original file name)

2. Power down, then hold volume down while powering back on

3. Press volume down to go to recovery, then volume up to select it

4. When you see the red exclamation point android icon, hold volume up and press Power

5. In recovery, use the volume up/down icons to navigate and Power button to select. Choose Apply update from SD card.

6. Choose Update.zip and wait a few minutes

7. When the flashing process completed, just reboot. Remember to update the Republic Wireless app after the upgrade finishes.
[Moto X General] malcolmputer:
Yep. Totally hosed. You are stuck at 4.4.2 with WP enabled.

When you flashed the update.zip in your recovery, it updated your recovery/bootloader to the 4.4.2 recovery/bootloader. Unless by some miracle that didn't happen, you can't downgrade to 4.2.2 to follow my guide.

If you really want to be sure (and most likely brick your phone in the process) you could run the commands in the 4.2.2 sbf with moto fastboot one by one, and if none of them fail, you would be at 4.2.2 which would allow you to do my guide. But that probably won't work, and will most likely brick you phone.

Just wait until someone find a root and WP off exploit, or sell your phone, and buy one that wasn't updated.
[Moto X General] Rashed97:
If anyone wants to join me, I'm gonna try to find an exploit in this bootloader this summer. I will go through file by file and tear the bootloader apart if I have to. I want an unlocked bootloader...
[Moto X General] malcolmputer:
I could go for that. I don't know if I will have the time but I would love the unlock.
[Moto X General] LARBIFY:
I was honestly going to switch to a nexus 5 on the tmobile $30 plan if there was no bootloader unlock from republic, so if you could get an exploit that would make me so happy. I would help but I'm only just starting coding so i'd be in over my head.
[Moto X General] kicker22004:
You guys must not know the track record for moto bootloaders.. Only a few I know of have been exploited and they were of the same Qualcomm exploit. I'm not saying it can't be done... Im Just saying your playing against a loaded deck.

Sent from my XT1049 [Unlocked Bootloader]
[Moto X General] :
The thing is, the phones been out around 8 months and no one has unlocked it yet. So I'm sorry, but I don't think its happening. Have to be realistic. 8 months is a lifetime, literally, in the phone world.

Most things that can be done, are done in the first few months after a phones release.

As far as the guy selling the codes a bit ago....he obviously somehow attained them from Motorola.... He did not crack the boot loader.....he acquired a database of codes.

If anyone on a locked boot loader can't stand it....its probably time to sell the phone....get what you can for it, and put the money towards something you can unlock.

Just trying to be realistic here. :)
[Moto X General] Rashed97:
True true, but its worth the shot. No one has even tried yet (not to my knowledge). I think if we try hard enough we might be able to find an exploit somewhere.
[Moto X General] :
Honestly, I'll bet many have tried. Especially with that big bounty available. They just do it hush hush....so no one knows it didn't work. ;)
[Moto X General] slgooding:
I tried to do a little research to understand exactly what the recovery is. If I still have safestrap recovery installed, is it possible to revert back to 4.2.2? Or is that separate from the actual 4.4.2 "recovery"?

Worst case I can live with having to boot to safestrap recovery to write to system. Annoying, but manageable...
[Moto X General] iKrYpToNiTe:
Jcase, and a few others have tried to crack it, but Motorola has some of the most secure bootloaders. That's why Samsung started using their bootlloaders on their phones, also the government uses a lot of Motorola bootloaders.
[Moto X General] slgooding:
Good news?

I have some good news! When I was on 4.2.2 I had everything properly rooted, etc. The only thing that I did NOT do was run MotoWpNoMo. However, the safestrap app would let me reboot into a mode with R/W access

I updated to 4.4.2.

I then ran MotoWpNoMo (with 4.4.2 installed) and it seems to have worked. The following command: "adb shell getprop ro.boot.write_protect" results in 0, which is supposed to mean that write protection is disabled. Are there any other checks I should run to verify, or am I good?

I ran adb shell as root and attempted to write something under /system but it tells me that it is read-only.
[Moto X General] jbrukardt:
having a heck of a time getting WpNoMo working on a second phone. It fails at (clobbering 1)
[Moto X General] slgooding:
Do you get any sort of error? Clobber 1 took "forever" for me. I left and grabbed a drink. When I got back it was done.
[Moto X General] jbrukardt:
yeah, a "wtf: what are you doing" and exit error

i just RSDlite'd the phone back to 4.2.2 stock and am going to try again
[Moto X General] jbrukardt:
the process completed withotu error once i rsd'ed back to 4.2.2 stock. But im still at wp1. Gonna run it again, supersu crashed halfway through the process, and that cant have been good. Gonna try to cwm superuser instad
[Moto X General] malcolmputer:
For some reason WPnoMO didn't work well for me in linux, so that was the one thing I had to do on my win7 machine. You might try it there if it doesn't I think it had to do with a udev USB issue.
[Moto X General] jbrukardt:
Shoot, still WP1
[Moto X General] jbrukardt:
this one is 8.1, will try it on an 8 machine in a few. Dont have a 7 machine around anymore. Not that i cant reinstall

SuperSU and CWM Superuser are behaving wierd as **** right now too, i cant help but think thats tied to it. They keep flat out disappearing, and yet root remains, and any new app i install that needs root automatically gets it. No popup
[Moto X General] malcolmputer:
Sounds like you have some other issues. Be careful you don't screw something up :)
[Moto X General] princepavs:
Can anyone help me with settings up same IP address for phone and win7 PC.... The telnet is not connecting because of different IP address..

Sent from Pav$ HTC One by Tapatalk
[Moto X General] Rashed97:
Yeah I know that the DoD uses Motorola. What I'm hoping for is that we can somehow use the Moto X versions that do have an unlockable bootloader to unlock these.
[Moto X General] iKrYpToNiTe:
They are the same bootloaders as yours, all of them are unlockable but Motorola has to provide the unlock code to you. But they block Verizon, AT&T, and Republic Wireless models from getting their unlock codes from Moto's website. I have a retail Verizon model but was able to unlock via the Chinese guy. Because he had access to Moto's code generator, or a way to bypass Moto's model check.