Search results

Thx ... I'm going ahead to get this phone!

Thx! And, yeah, I did a quick look at the Amazon version ... and ran the opposite direction. ;)

Thanks! Appreciate this info ... its something I used to check into but being so rusty on stock phones, didn't even think about the various bands. Glad to have those links!

Yes, I searched. And yes, I realize this may be a trivial question. But I've done no tinkering on my past 2 phones so real rusty on anything other than VZW purchased phones. First, I live in a VZW-only area, so different carriers is not an option. And its time for me to do a phone upgrade...

Quick question ... I'm stock/rooted MOB30D (previous updated via WugFresh's tool). Can I just flash this over my current set-up?

As mentioned in the OP, I can confirm this works. Thanks for posting this app!

es25 gave me play store problems ... reverted to es24 and all its well on cm11.

Recently saw both stock odexed and stock deodexed rooted 4.2.2 for unlocked VZW XT1060 posted over on DroidRzr.com

+1 I tried appending hosts (just pasting in blocked to end block portion) on pc as admin but then could not connect to anything on internet ... not able to open my Gmail on Chrome, Feedly, etc etc etc. After undo and save, could connect to internet fine. So guess some editing needs to be done...

Cool ... flashed 2.7 with recovery tools ... first time for me and so convenient to do it right on the phone.

For me 005m is working better and getting more deep sleep than on 005u for VZW XT1060DE. Only thing I'm seeing on both though is that Intelliplug Hotplug Driver and Eco Mode does not stick (after later going back to check settings in FauxClock ... no reboot done) ... unless they don't/won't...

Watching to see how this pans out....

Watching to see how this pans out....

Watching to see how this pans out....

Watching to see how this pans out....

Watching to see how this pans out....

I don't want to get this thread off-topic ... but is there a good 'guide' as to when to mount which when doing what in recovery? Generally I've never mounted anything in recovery and never had an issue ... except found the Razr M finicky on that point.

I think that sums it up best. Right now Googorola is a mess, at least in my view. They hugely botched up the first sale, crashing their website. When I later got a discount on the Valentine's Day deal, they shipped me a pre-damaged phone. Super hassle to replace ... took rattling cages on social...

Apex Launcher is "4.0+" compatible so in theory should not cause a crash/bootloop issue. When I have a whole lot more time to kill, might try this again later.

Well ... that didn't go so good. Though I could downgrade to 4.2.2, I bootlooped unless doing data wipe. After that, booted up alright and started to selectively restore a few things. However, when restoring Apex launcher ... crashed and went into bootloop. So ... fastboot files back to 4.2.2...

Perfect ... really appreciate those insights!

I followed your input, quasi-updating to 4.4.2 flashing just the portions you suggested. From what I've seen so far, wasn't impressed with 4.4 battery life (compared to 4.2.2). And I'm not seeing any improvement on 4.4.2 after several days ... getting about the same battery life while using...

I'm sure I've used your work a couple of times, definitely on my Razr Maxx and also on Razr M. Glad you're still tinkering with the Motorola devices! The 'unofficial' update to 4.4.2 sans motoboot/gpt was easy and was up and running again faster than I'd anticipated. Thanks for putting together...

Thanks! After having bitten and flashed a "leak" back on my Razr Maxx ... then shortly after that we who flashed it learned we could not go back, I just want to be quadriple sure before I paint myself into a corner with paint that don't dry. :silly:

In other words, when you flashed back to 4.4 (from 4.4.2), you didn't flash these portions of the 4.4 fxz: fastboot flash partition gpt.bin fastboot flash motoboot motoboot.img This may not be relevant, but here's what I'm wondering. I'm still on 4.4 with update files frozen via TiBu...

I'm thinking to do the same. Just want to confirm that Active Display/Notifications working fine this way ... as I'd like to check out 4.4.2 before commiting to it by flashing OTA.

For the win (as I plan do with my Dev Edition newly rec'd): Buy a Dev Edition (sale price @ Motorola ends today I think) so you can easily root and retain root when update to 4.2.2; update phone on VZW online account; unlock bootloader; allow OTA to install while on stock recovery, install TWRP...

You might want to check this thread: http://forum.xda-developers.com/showthread.php?t=2629057

Thanks for developing this app. Though I previously bought Tasker and usually pride myself on learning things quickly, I'm a Tasker-flunky. SwiP has been easy to understand and use. Thanks!

I got my issue resolved after some serious head banging ... before I knew about Wendy. But right after my situation got fixed via Matt, I came across a guy having a similar replacement issue on a Dev Edition, got him in touch with Wendy ... on the SAME afternoon she fixed the issue for him that...

If this the one @ full size that you were looking for?

I believe you can find that wallpaper and a few other of the customer moto-maker wallpapers for download in this thread: http://forum.xda-developers.com/showthread.php?t=2478065

^^ Thx, appreciate that feedback.

Will this zip work on 4.4 as well, since VZW hasn't updated to 4.4.2 yet?

I have to agree with that. Just today I joined a G+ community for a Dev's beta app ... but after several hours, just plain got tired of the flood of posts with "Please add this and that 'n that ..." or "I have high standards and would like to see ....". "Pleeeeese add this right away....", etc...

Same here. My locked retail phone will soon become my wife's ... after I receive my Dev Edition. I tried to go straight to a Dev Edition during the first discount code fiasco, had one in my cart, entered shipping & billing ... poof, it was gone. Didn't want to pass up second chance since I may...

You and I both seem to understand that would be the sensible and customer-friendly way to resolve the issue. However after getting spun in circles and re-circles, Motorola finally offered to do an advanced exchange ... but then within minutes the Motorola Customer Service agent sent me this: "I...

+1 on which forum. I got my brand new Dev Edition with multiple screen scratches. Customer service seems not to care when this phone should never have been shipped ... now it's like oh "I'm sorry about that" and I'm supposed to lose the $100 discount to boot. No way to treat a customer. Woodside...

Be sure to check your phones carefully. Received mine with a pre-scratched screen (several top to bottom)... and have spent hours trying to get this resolved, so far to no avail. Hope none of you have to go thru this....

Thank you for this root tool. Worked perfect on my wife's old creaky Bionic, allowing me to root it, backup with TiBu, transfer that all over to my unused Razr M, and move on from there ... made life simpler. THANKS!

I'm coming from a little different angle. I had the VZW Dev Edition in my cart on CyberMonday, but "thanks" to Motorola's mess-up, lost it in the process. So, no way I'd pay full price for one after they excluded the DE from follow-up deals. Decided to take a peek at the retail version to see if...

I want to thank each of you for your helpful input before I decided to grab a $150 off "X". Finally got it Friday and after rooting and getting it set-up, find I really like the Active Notifications / "breathing", along with Handcent notification customizations, Xposed/Gravity .... and keeping...

After unboxing and activating my X, right away I could see the OTA was starting to download, so quickly began the root process. Hit roadblocks at first so had to turn off Windows (7) Firewall & disable Microsoft Security Essentials in order for Cydia to connect. After that, it was 'just follow...

I'll second the FAQs. In my case, option 1 of the above FAQ (No Wipe Mode) hit an AutoIt Error, option 2 (side load) hit some kind of Korean IME mismatch error ... ended up with an option 3 solution that took all of a couple minutes.

Flashed over stock KRT16S, only wiping dalvik & cache. After re enabling xposed and gravitybox, all seems good.

Uninstalled NRT, downloaded and re-installed NRT. Same error. HOWEVER, this error popping up may be due to one NRT change I made ... enabling "No Wipe Mode"? I don't have time at the moment to re-try without "No Wipe Mode" enabled, but will do so later when I have enough time to restore data.

Previously used NRT when I updated my Nexus 7 Wifi (2012) to KRT16S (4.4) without a hitch. Was doing the same thing for KOT49H (4.4.2) but get an AutoIt Error as follows" Line 14368 (File 'C:\....\NexusRootToolkit.exe'): Error: Variable used without being declared. I reloaded NRT making sure...

Just a quick question. I will be getting my retail Verizon "X" in a day or so, when FedEx decides to stop sitting on my package. From what I understand, it would should arrive with 4.2 pre-camera update. I'm weighing my options at this point: 1.) Root with your Kit (PwnMyMoto option), freeze...

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"...

If I'm understanding correctly, I could still update to 4.4 and root my Moto X (Verizon consumer/retail) that I'll receive via FedEx today, since write protection hasn't been touched as of yet? If that's the case, then I'd only be partially-rooted ... due to write protection limitations...