yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] mj0528:
Sweet

---------- Post added at 06:03 PM ---------- Previous post was at 05:41 PM ----------

That didn't work for me :( actually i could install an app but i couldn't get quick reboot installed. I noticed that supersu from the market updated automatically and seemed to have overwritten the su that was flashed. Is that an issue? could that be my problem and if so, how can i go back to the su that was flashed. I couldn't uninstall the update so can i just uninstall it and then flash from trwp? Everything else is working good except i can't install quick reboot.

weird
[Moto X Android Development] remicks:
I installed the latest SuperSU from chainfires site. No update needed.

Sent from a White Moto Xposed
[Moto X Android Development] luniz7:
I have no issues installing quick boot....
[Moto X Android Development] mj0528:
everything else works like s champ and can install other apps just fine. I have the reboot control app from motoxposed so no loss. Actually it's better than quick reboot since it's integrated well.
[Moto X Android Development] freak4dell:
I'm using this on an XT1058, and it seems to work perfect. Even if WiFi is connected, the cell data icon is still there (for example, there's an E right now between my WiFi icon and my cell signal icon. Is this a normal part of the T-Mobile ROM?
[Moto X Android Development] doobie711:
It's pretty standard for what I use, the stock VZW and this both seem to have it. I thought it was odd when I first had the phone but it seems like it's a part of the default system.
[Moto X Android Development] freak4dell:
Gotcha. The AT&T stock ROM just has a gap there. Figures that as soon as I get rid of the carrier label in the notification bar, I get a persistent cell data icon. We just can't seem to win. :p

Thanks for posting this ROM, though. If you feel bored one day, you should do it for all the carriers and post a megathread of flashable stock ROMs.
[Moto X Android Development] doobie711:
The only concern I have is that I wouldn't be able to test for everything else. What I might end up doing is have the ROM without any carrier specific parts and then just have flashable zips that have the files that are for carrier dependent like build.prop.
[Moto X Android Development] freak4dell:
Yeah, that's a good point. I think your idea would work well. There are already AT&T and of course T-Mobile zips, but WiFi just doesn't seem to work on them for most people. For whatever reason, there isn't a Sprint one yet. I'd be interested in giving that a shot to finally put the Google Wallet issue to rest.
[Moto X Android Development] luniz7:
This was great until it got a mind of its own last night. Started doing all kinds of weird stuff. It shut my phone off. I turned it back on and it says your phone is activated. Automatically logs me out of Facebook. Opens and closes Facebook. Weird stuff.
[Moto X Android Development] remicks:
Been running smooth for me here, no random issues or anything so far. Using SafeStrap 3.63a on a XT1060 (Locked of course) with 3200mb for data, 1000 for system, 400 for cache.

Sent from a White Moto Xposed
[Moto X Android Development] dmbfan13:
Will this disable OTA updates? I'm getting the new camera patch update. I'd rather not keep deferring daily.
[Moto X Android Development] jayboyyyy:
yes it should. but you can just freeze the OTA stuff in on your phone so you don't get that notification all the time. very simple.
[Moto X Android Development] dmbfan13:
Oh that's right!!
[Moto X Android Development] dmbfan13:
Hopefully this rom gets updated with the new OTA so I can just flash this! :D
[Moto X Android Development] mercado79:
[MENTION=2357688]doobie711[/MENTION], does it make sense to create a new/updated flashable zip using the official VZ update?
[Moto X Android Development] doobie711:
Unfortunately I got the dumb the other day and flashed the OTA. Now I don't have root. maybe I can pull the system though and make that flashable. Will update if I get it figured out.

UPDAT: And easier than anything, the files are pulling. I'll upload the VZW OTA and see if it even boots for anyone. But there will be gigantic disclaimers about it since I won't be able to test it.
[Moto X Android Development] stastnysnipes26:
So correct me if I'm wrong, flashing this ROM is equivalent to taking the OTA, minus the new baseband, thus we get the camera improvements with out the call quality improvement? Wouldn't that only make it a matter of someone making a flashable zip of the baseband package, then we would be totally up to date?
[Moto X Android Development] doobie711:
Exactly. I'll do that this weekend when i get free time.
[Moto X Android Development] stastnysnipes26:
You sir are fawking awesome...can we get some feedback here from people that have flashed this already? How is this baby working? Also this is a much safer route I feel because if anything gets really screwed up we can just restore our stock backup that we made when we first installed safestrap :) this is gonna be a good weekend

Sent from my XT1060
[Moto X Android Development] doobie711:
No, it really doesn't. But I will make a radio flasher for vzw though.
[Moto X Android Development] mercado79:
Maybe a stupid question (sorry, I don't have much experience with SafeStrap or Moto phones), but... should I be able to flash this over the stock slot? I just want to update my phone without taking the OTA. There's simply not much room on our 16gb models. However, when I try flashing over top of stock, it never boots. I imagine I could start from scratch, but... that's kind of a pain. Is that the only way to go?

FYI, the same thing happens if I restore my backup to slot 1 and try to update using the OP's script. Am I missing something?
[Moto X Android Development] doobie711:
I did at one point have this flashed over stock instead of using safestrap, but I don't recommend it unless that extra space is really really really really really important. Restoring the backup to a SafeSlot never worked for me. I think it had something to do with the size of the slot not being large enough. Also, what version of safestrap are you using? It could be out of date.

Edit: It took me a second to remember. You can't just flash this over stock without doing a factory reset. If you want to use it instead of stock you have to wipe before you try installing this.
[Moto X Android Development] freak4dell:
I have mine on the stock slot. For whatever reason, none of these ROMs seem to like a previously existing data partition. If I didn't wipe data, it would boot loop. If I restored data, it would boot loop. If I just started from scratch, it works perfectly fine. It doesn't bother me much, because other than SMS and call logs, I don't have much to back up.
[Moto X Android Development] mercado79:
This is exactly what I experienced. I guess I'll just have to start from scratch.

Sent from my Moto X
[Moto X Android Development] stastnysnipes26:
Not sure why you would flash over the stock slot...that is supposed to be your safety net. Should have installed to ROM slot 1....you probably have to rsd back to slot

Sent from my XT1060
[Moto X Android Development] freak4dell:
I'd rather have the space. If I have to RSD, I have to RSD. It's not a big deal.
[Moto X Android Development] mercado79:
I just restored my backup. No problems. Why should I lose a few gigs for no reason? My safety net is the back up.

Sent from my Moto X

---------- Post added at 11:53 PM ---------- Previous post was at 11:19 PM ----------

Curious if there's anything to be aware of in regards to the SafeStrap app. Did you just reinstall or restore from Titanium Backup?

Sent from my Moto X
[Moto X Android Development] codygs83:
What he said ^

Backed up my slot 1 ROM and restored it on stock slot with GREAT SUCCESS. Its very nice
[Moto X Android Development] freak4dell:
Yeah, you can just simply reinstall the app. I didn't even bother until right before typing this reply, because the recovery still works without the app installed. Just make sure to root by flashing SU first, because I think if the SS app doesn't detect root, it will just gray out all the buttons.
[Moto X Android Development] jayboyyyy:
over on the rootzwiki thread people have been reporting problems when installing safestrap on rom slots. it is not necessary as you just said and some people have been going through bootloops because of installing it in rom slots so I personally would avoid doing so. But its your call. I thought i would just mention it.
[Moto X Android Development] mercado79:
point taken, but freak4dell and i (i think) are both talking about installing it on a clean stock slot.
[Moto X Android Development] yamaha83:
im going to have to do some more reading before i try this. i thought on the safestrap thread on Wiki it said not to flash anything to the stock slot because it was untested. but makes sense that you should be able to just backup the slot and flash to it... i would rather do that since the memory space on these 16gig phones fills up fast...
[Moto X Android Development] jayboyyyy:
if when you say stock slot you mean the nonsafe slot then I don't think anyone was having problems with that. It was just installing SS on a safe/rom slot that people ran into problems.

---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------

basically that is more of a disclaimer. What I believe HC is trying to say there is he wrote the code and tried to get all of the bugs out of flashing stuff on rom slots. When you flash on the stock slot, things may change or get weird and he did not run tests for flashing on that stock. He isn't saying it won't work, he is just say he doesn't do that when testing the SS so do it at your own risk.
[Moto X Android Development] mercado79:
well, not that this says much, but... i'm on day two. no problems so far.

backed up the stock slot. tested it on a rom slot. wiped the stock slot (just a regular wipe, not advanced). flashed the OP's ROM which wipes /system. booted up like it was a new phone, though the safestrap boot screen was still there. set everything up normally and then restored some settings from titanium backup. if only this could be flashed over top of the stock rom so that you could keep your settings and data, but you do need to wipe or else the phone won't boot.

so far, so good...
[Moto X Android Development] freak4dell:
Yeah, I've been flashed over the stock slot for more than a week now. No problems. I have no idea how this wizardry works (I would have thought wiping system would also wipe out SS), but I'm glad it does. I just basically treat SS as a regular custom recovery, instead of a way to dual, triple, or quadruple boot. I've got no reason to run 2 ROMs, so if flashing to the stock slot works, why wouldn't I do that and use the phone will full storage intact?

For what it's worth, I made a backup of the stock setup in SS. Then I tried restoring data and apps from that to this ROM using Nandroid Manager, but it didn't work. The apps kept crashing. I never tried TiBu, and Helium refuses to see my backups for some reason, so I'm not sure if there's any way to flash this on the stock slot without have to start all over with data. SMS and Call Logs did get restored properly through Nandroid Manager, though. That's all I really care about, but if you are really determined to not lose your Angry Birds score, maybe a ROM slot is a better solution for you.
[Moto X Android Development] doobie711:
bad news gang... I underestimated how easy this was with a galaxy nexus. I have virtually zero access to anything useful on the hardware side. Our best bet is to somehow use the vzw ota zip to patch the radio images. This might only work with stock recovery though. I'm not totally clear on what safestrap's limitations are with the radio partitions. This might end up with a linux/osx script to overwrite the radio partitions. I'm pretty sure they're at /dev/block/mmcblk0p21 and /dev/block/mmcblk0p22. I'm not convinced it's two seperate files or if it's just split the way that fastboot files are split on motorola.
[Moto X Android Development] jayboyyyy:
have you considered sending hashcode a pm over on rootzwiki. I'm sure he can shed light on everything and probably save you a lot of time... I'd help if i could.
[Moto X Android Development] mercado79:
Really appreciate the time and effort you're putting into this. Just thought I'd point out that in the OP on Rootzwiki, Hashcode mentions that he's almost always on IRC. Freenode.net #safestrap

Sent from my Moto X
[Moto X Android Development] wtfmate913:
i see that a few of you are using the stock slot to flash the rom. I would like to do the same to preserve all possible storage space, but I just have a question first. Can anyone confirm, if i backup the stock slot, then save the backup on an external drive, wipe stock slot then flash this rom on the stock rom slot, if anything goes funky, can I still RSD lite back to stock ? I just want a daily driver which i can utilize all the storage space with, but don't want to be stuck with a paperweight if anything goes wrong
[Moto X Android Development] freak4dell:
Yes, you can RSD back to stock if needed, and then if you root and install SS again, you can restore the backup you made.
[Moto X Android Development] wtfmate913:
thanks. So I wiped stock slot in safestrap, installed the zip and supersu, but WiFi doesn't work for me. Tried RSDing back to stock to make sure wifi was off before trying again, but after I got the rom installed still no wifi.
[Moto X Android Development] freak4dell:
Are you sure you used the latest version of SS?
[Moto X Android Development] remicks:
The following post assumes you are rooted and have already installed the newest SafeStrap recovery to your device.

This works best off of a fresh RSD install to stock.

Mini guide to installing the SafeStrap ROM in stock slot

1: Boot into safestrap recovery

2: Make a nandroid of your stock slot and copy that nandroid to a PC or external drive

3: Boot into safestrap recovery (unless you just used ADB pull to retrieve the nandroid, in which case you never left recovery.)

4: Create a rom slot in slot 1 with the default size options

5: Flash the VZW SafeStrap ROM from the OP and the SuperSU install zip

6: Boot into the ROM, enable usb debugging and use adb to reboot to recovery (or just install some app to do it from the market.)

7: Create a nandroid of the rom slot

8: Switch to stock slot

9: Restore rom slot nandroid to stock slot

10: Factory reset stock slot via TWRP

11: Delete rom slot 1

12: Reboot to stock slot

13: Rejoice

Hope that helps anyone who was curious, sorry it seems a bit drawn out but I tried to make it idiot-proof (although I probably failed...).
[Moto X Android Development] spiral777:
Is there a video walk-through for this? And which device did you do this on? Was it the droid mini?
[Moto X Android Development] freak4dell:
I'm not trying to be an ass, but is there really a need for a video walk-through? There's already a video for how to do it on a ROM slot, and the process is 95% the same. In fact, half the steps remicks wrote down aren't even needed. I see no reason to install this on a ROM slot first, then back that up, then restore that backup to the stock slot. If you want to flash to the stock slot, just backup your stock ROM (optional), flash this ROM, and then do a wipe of data and cache (and I always do Dalvik cache out of habit). Don't use the format data option unless you want to lose your files on internal storage. Boot up, restore apps or whatever from TiBu, Helium, etc. if you want, and get on with using the phone.
[Moto X Android Development] codygs83:
I'm just happy remicks 13th step was rejoice instead of that gay "profit" bs everyone else thinks is cool and witty.

His guide is pretty straight forward for users who aren't familiar with ss.
[Moto X Android Development] wtfmate913:
I got the ROM working on stock slot I was stupid and accidentally downloaded an older safestrap version and that was why WiFi didn't work. Just had a brain fart
[Moto X Android Development] remicks:
Motorola X (Verizon)

Agreed, a video would be redundant. The only reason I put in the steps about making the nandroid and restoring it to the stock slot is because I personally flashed to the stock slot and was unable to boot and ended up having to RSD to get my phone functional again. As with anything to do with flashing, YMMV.

:D

Sent from my peppy little Sero 7
[Moto X Android Development] doobie711:
Good News Everyone!!! Well actually some good new and a whole lot of bad news. The good news is that over the weekend I tried some tricks to get the modem to flash and successfully got the boot image update. Now the bad news. The modem failed to update and the recovery kicked the phone off. The phone I was using also lost root access. The good news is that I'm going to try to edit the update script to just flash the modem and see if that fails the same way or actually gets somewhere.

The Caveats:

In order to flash the file like I did you have to use RSD to go to stock, install pwnmymoto, then use rsd to flash only the recovery, then download and take the update. Now I need to figure out if RSD still needs to be done or if playing with the update will just do like I want it to and update the modem only without worrying about checking any system things.
[Moto X Android Development] freak4dell:
I may be wrong, but I believe flashing the recovery prevents you from downgrading later, so keep that in mind if you have a locked device.
[Moto X Android Development] jayboyyyy:
how are you running SS or testing it without a rooted device?
[Moto X Android Development] mpetruzz:
So I was planning on flashing this rom, but after the last few comments I'm a bit hesitant.

Is this ROM OK to flash and still allow me to root?? I'm just trying to get the update with keeping root and didn't want to try some of the other methods that aren't 100%.
[Moto X Android Development] jayboyyyy:
i just did everything on a vzw phone and it all worked perfectly. I didn't turn wifi off either or whatever because I think that was an issue with an earlier SS not as much the rom. But maybe not. My wifi works just fine though. I did wipe cache and dalvik after the install of the rom. then installed supersu. then maybe wiped it again then booted the phone.

I actually installed it twice because i FUBARed tibu on the first install. Ran some restores that I shouldn't have. All is well for me.

forgot to mention that I also used fastboot to flash the new baseband. This actually flashes the baseband for the entire device not just in the rom slot fyi. Not sure if restoring the backups i made on the stock slot without the baseband being udpated will be compatible but if i ever decide to go back to the stock slot firmware then Ill just flash the old baseband back on there before i restore my back up (or uninstall SS if i need to).
[Moto X Android Development] mpetruzz:
Thanks, I'm going to give it a shot now. just curious I know a few people flashed this on the stock rom slot to free up space. How did you install it??

I'm not really sure how to flash the new baseband so can I just flash the rom??
[Moto X Android Development] jayboyyyy:
yes you can just flash the rom but without the baseband the new fixes for call quality won't be in place. I put it on a rom slot because I don't need space on my phone. Not sure what others use that much space for but whatever. You can put it on the stock slot if you want no problem. I don't think anyone has been reporting problems with it.

I just use SS for what it was made for, using rom slots so when crap hits the poop chute, you can go back to stock slot and have a working phone until you sort out the problems. I don't want to spend a day without a phone because I screwed something up and don't have the time to fix it right then.

if you knowhow to use fastboot then flashing the new baseband i easy. If you want to do it and need help just let me know. Its not as difficult as it sounds. just command prompt stuff.
[Moto X Android Development] codygs83:
I'd kill for the new baseband. Just don't know where to get the files.

Any help would be appreciated!
[Moto X Android Development] mpetruzz:
Cool, I'll flash it now. Maybe I can hit you up tomorrow on hangouts or something if you can help me with flashing the new baseband.
[Moto X Android Development] jayboyyyy:
FXZs were released on sbf already. Just download the file. unzip it. flash NON-HLOS.bin then erase modemst1 and modemst2, then flash fsg.mbn then you are done. pretty simple. about 2 minutes total (not including download time)

send me a pm if you want some help and we can work something out. Everything is really simple and I have saved bookmarks for easy instructions on all of it.
[Moto X Android Development] mpetruzz:
What size slot are you all making for this rom??
[Moto X Android Development] jayboyyyy:
stock size for me. didn't touch any size settings because defaults were adequate.
[Moto X Android Development] mpetruzz:
pm sent
[Moto X Android Development] DiGi91:
Now correct me if I'm wrong but flashing this ROM with SS still means write protect is enabled unless booting into "recovery" right?
[Moto X Android Development] freak4dell:
Yes, you must boot into "recovery" to disable write protect.
[Moto X Android Development] DiGi91:
Yeah just found that out.. Oh well at least I'm finally on the OTA! xD setting up all my tweaks now
[Moto X Android Development] seh6183:
No matter how many times I flash this I get the same results. I have tried the stock rom slot, rom slot 1 and 2. Always the same thing. I flash the rom and then go to boot, no boot logo, just black screen. After 5 minutes I hold down power, the phone attempts to boot with the Moto logo and then bootloops over and over. No SS even attempting to come up. Been trying for 24 hours with the same results.

I am thinking I am doing something wrong and need to boot into write protection mode off first before flashing the rom, but I just cant figure it out. I am about to rsd back to stock for the 50th time right now. Someone please help me. Thank you.
[Moto X Android Development] jayboyyyy:
No one can help you until you give them details of exactly what you did. You didn't even explain why you think you screwed up write protect mode. Based on what you said, I'll take a shot in the dark and when I'm wrong I can continue to guess I guess. This football game sucks anyway. You installed the wrong version of ss?
[Moto X Android Development] freak4dell:
Wrong version of SS or corrupt download of the ROM would be my first guesses.
[Moto X Android Development] seh6183:
I have version 3.63a because I have a droid maxx. I did this:

FXZ

pwnmymoto

boot in write protect off

install SS

click reboot recovery

in SS create rom slot 1

install this rom

install superSU

reboot

fail

Hardware is exactly identical to a moto x. People have flashed moto x stuff on the ultra/maxx fyi. Also, i redownloaded the rom and superSU from the OP and tried again with same result.
[Moto X Android Development] freak4dell:
First thing I'd do is see what happens if you don't flash SU right away. Try and boot into the ROM first.
[Moto X Android Development] seh6183:
Trying now. Should I click "reboot to recovery" or "reboot to write protect off mode"?

ROM slot 1 creating... (I clicked write protect off)

flashing rom....
[Moto X Android Development] freak4dell:
Reboot to recovery, (which will get you into the SS recovery), then make a new ROM slot, flash this ROM, and reboot. On that reboot, make sure you hit continue when the SS prompt comes up. You might have to do that twice because there's a bug in SS that makes the prompt come up again for some reason.
[Moto X Android Development] seh6183:
Did exactly what you said. As soon as I click continue, I hear the connection sound come from my computer and then the phone screen stays blank and nothing happens just like always. It looks like im in for another FXZ LOL

Held down power and got back into SS. Activated stock rom slot and deleted rom slot 1. Phone booting now. At least I dont have to FXZ.
[Moto X Android Development] freak4dell:
Have you tried downloading the ROM again, to make sure the first download wasn't corrupt?