Database Info

[Q] Anything missing to update to Kit Kat?

I'm rooted with rock my moto, stock recovery is reflashed, & I have write protection permanently off. Uninstalling safestrap is a no-brainer. I'm guessing the OTA will kill root and write protection? I presume slap my moto will work once I'm in Kit Kat, but is there anything I can do while on 4.2.2 to prepare for a rootable update into KitKat?
fat-fingered and Maxx-ed out.

I second this, want to be fully prepared and make no mistakes

I fxz'd back to stock a few days ago. I was under the impression that our root method altered the system partition and would cause updates to fail

Root method only removes stock recovery (used for write protection off). Flash recovery back on in ADB, good as new. My stress is permanent write protection off causing a problem after pre-KK FXZ, or OTA in restoring root (if SuperSU Survival Mode can't maintain root).
Edit: WP will survive FXZ, but not likely OTA. Soooo...FXZ, OTA, Slap, WPoff (again) looks like.
fat-fingered and Maxx-ed out.

From what I can tell you need to fxz back to stock and run slapmymoto frist, since slapmymoto work like rockmymoto except installs a "backdoor" instead of root. Keep in mind by taking the 4.4 update you are risking preminate loss of root, because slapmymoto works on the idea that you can roll back to 4.2.2 after KitKat and moto has had a month since the moto x's update rolled to prevent this on the droids. Also I know that anyone has used the motowpnomo mod have has issues getting root back. There is a fix out but I haven't used it and am not sure how it will effect the moto slapping process

Please let us know if anyone gets a successful or unsuccessful method. Then we can verify what does/doesn't work. I have a backup running and the update downloading at the moment. I will post back if I get some time to give it a try.

l337h4cker said:
Please let us know if anyone gets a successful or unsuccessful method. Then we can verify what does/doesn't work. I have a backup running and the update downloading at the moment. I will post back if I get some time to give it a try.
Click to expand...
Click to collapse
Plz pull the update from /cashe with root explorer (or w/r you use) and post a link I'm happy to try but it hasn't been pushed to me yet.

Can anyone pull the install-recovery.sh from system/img for the 4.2.2? I need it for my update.

I just used House of Moto in "Keep Data" mode. Stock recovery is back, along with the annoying bootup sound. Still waiting for the update to push to my phone.
http://forum.xda-developers.com/showthread.php?t=2450702&highlight=houseofmoto

rlmesq said:
I just used House of Moto in "Keep Data" mode. Stock recovery is back, along with the annoying bootup sound. Still waiting for the update to push to my phone.
http://forum.xda-developers.com/showthread.php?t=2450702&highlight=houseofmoto
Click to expand...
Click to collapse
Recommended you look over SlapMyMoto 1.0 before taking the OTA! If you still have root, you could run the MotoWPoff exploit now, if you want.
fat-fingered and Maxx-ed out.

Einsteindks said:
Recommended you look over SlapMyMoto 1.0 before taking the OTA! If you still have root, you could run the MotoWPoff exploit now, if you want.
Click to expand...
Click to collapse
Will MotoWPoff survive the OTA? The thread says
This exploit is permanent in the sense it will survive factory resets, reflashing the device, etc. However, like with any exploit, you should not expect it to survive OTA's or other updates.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2551113

rlmesq said:
Will MotoWPoff survive the OTA? The thread says
http://forum.xda-developers.com/showthread.php?t=2551113
Click to expand...
Click to collapse
Either it did, or KK allows WP toggle for rooted users. Not quite smart to know why. I can tell you what I did, but I can't tell you what happened or why it works.
fat-fingered and Maxx-ed out.

I have an unlocked bootloader. I haven't gotten update yet. Losing patience. I got the email last night saying it would push this morning. Still waiting
Sent from my XT1080 Developer Edition using Tapatalk

Einsteindks said:
I'm rooted with rock my moto, stock recovery is reflashed, & I have write protection permanently off. Uninstalling safestrap is a no-brainer. I'm guessing the OTA will kill root and write protection? I presume slap my moto will work once I'm in Kit Kat, but is there anything I can do while on 4.2.2 to prepare for a rootable update into KitKat?
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
I am in the same situation, very curious on where to go from here to achieve root on 4.4. I have yet to get the update, but would like to be prepared.
Thank you.
Sent from my XT1080 using Tapatalk

[Q] XT1030 Rooted, 4.4 update keeps rebooting

Hi guys.
So I purchased 2 of the Droid Minis for my kids. They are both on 12.15.15 (camera update) 4.2.2 and started bugging them to take the update to 4.4
Before letting them take the update, I wanted to root them both so I could install tracking software on them, so I followed the thread here: http://forum.xda-developers.com/showthread.php?t=2509590
(for RockMyMoto)
PwnMyMoto never did anything but error, so I figured it was because of the camera update.
I successfully rooted BOTH XT1030 phones following the RockMyMoto OP, verified by installing SuperSU and double verified by installing TiBU from my license. Both phones are truly rooted as both asked me to grant or deny root access, and I've even checked via RootManager and it does indeed allow access.
So after following the link above and successfully rooting both phones, I started the 4.4 update on the first one and waited for it, but it just rebooted over and over, which made me stop in my tracks on the second phone.
Right now, the phone that was supposed to be taking the 4.4 update will boot all the way to a usable homescreen, but it reboots after about 20 seconds of having hit the homescreen. It's been doing this for about an hour now.
I've gotten enough time to get into Settings > About and check, and it's still on 4.2.2 (12.15.15), and even allows to check for updates before rebooting again (if I'm quick, I can even push the button to check for updates, but the device only lasts for 20 seconds before it automatically reboots.
I've tried booting into Recovery, but it just reboots into normal mode, lasts 20 seconds and reboots again.
I'm stuck, and would appreciate some help here. I'm not new to flashing, having been a crackflasher since the OG D1. Although, I have to say that these Droid Mini's are significantly harder to work with than my Note3, S4 and any of my previous phones...
help PLEASE?!
Obviously, my daughter has a bunch of games on her phone after having it since Christmas, and I'd definitely prefer not to lose her data. I had the foresight to make a TiBU backup before moving forward with the 4.4 update, but in it's current state of rebooting, it won't stay on long enough for me to copy the TiBU folder to my computer.
If I knew how to fastboot, perhaps I could fastboot the files for 4.2.2 back to the phone without losing her data - at least so I could transfer the TiBU folder over in case the phone has to be RSD'd back to stock...
If this is an option, please help me out with the exact commands that I might need. Thanks in advance!!
EDIT: I read how to fastboot (hadn't done it for a couple years) and found the correct files for the xt1030 here: http://sbf.droid-developers.org/phone.php?device=2
I downloaded and unzipped the 12.15.15 file.
I then used fastboot to push boot.img, motoimg.img, recovery.img successfully (although there is NO recovery no matter how I try to boot into it)
BUT, when I fastboot flash system.img, it comes up with several errors and fails, so I'm sure that the problem actually exists in the system image on the phone.
*** I DID NOT erase anything, only dirty flashed. I did this because I need to back up the user data before anything happens to it.
If I do erase system on the phone, will I lose her data? What about the other images that are still on the phone??
**EDIT: I found that I needed to use mfastboot instead of the standard fastboot to flash the system.img because it's apparently too big - mfastboot breaks it into smaller chunks and pushes them correctly, however, the phone still reboots.
This isn't considered a bootloop, it will boot all the way into the homescreen, stay active and live for around 20 seconds and then reboot.
I'm already going to be in trouble when she finds out she can't use her phone in the morning... PLEASE help a brother out!
Hope that info helps someone to help me better!

Unfortunately the Droid Mini and Max has yet to get their own device forums. So, I have moved the post to this forum in hopes some folks can help as the Ultra may share some characteristics as it's a relatively new device getting the 4.4 update as well.
MD

Moscow Desire said:
Unfortunately the Droid Mini and Max has yet to get their own device forums. So, I have moved the post to this forum in hopes some folks can help as the Ultra may share some characteristics as it's a relatively new device getting the 4.4 update as well.
MD
Click to expand...
Click to collapse
Thanks MD.
I just now figured it out on my own.
I hope that this thread will serve to help anyone that may stumble across a similar problem on their XT1030 device - perhaps even other Moto devices.
WHAT I FOUND:
While fastbooting and mfastbooting files to the phone, I realized that it wasn't working because I was missing something somewhere, so I opened the XML file in the original 12.15.15 zip and went through it line by line.
The one thing that I had neglected to do while in fastboot was to ERASE CACHE.
Once I had erased cache via fastboot (and obviously after pushing all the proper img files), it all worked correctly after reboot - the phone no longer reboots on it's own and immediately started the download of the OTA 4.4.
I hope that this post helps anyone else that happens across this problem.

Psychlone said:
Thanks MD.
I just now figured it out on my own.
I hope that this thread will serve to help anyone that may stumble across a similar problem on their XT1030 device - perhaps even other Moto devices.
WHAT I FOUND:
While fastbooting and mfastbooting files to the phone, I realized that it wasn't working because I was missing something somewhere, so I opened the XML file in the original 12.15.15 zip and went through it line by line.
The one thing that I had neglected to do while in fastboot was to ERASE CACHE.
Once I had erased cache via fastboot (and obviously after pushing all the proper img files), it all worked correctly after reboot - the phone no longer reboots on it's own and immediately started the download of the OTA 4.4.
I hope that this post helps anyone else that happens across this problem.
Click to expand...
Click to collapse
Glad you solved it. Yeah, cleaning cache is always a good thing.. Sure your daughters will be happy now!

You have to follow this guide here http://forum.xda-developers.com/showthread.php?t=2603358 to gain root after 4.4 Update.

Hatary said:
You have to follow this guide here http://forum.xda-developers.com/showthread.php?t=2603358 to gain root after 4.4 Update.
Click to expand...
Click to collapse
Incorrect. That will not work for his device.

Topsnake said:
Incorrect. That will not work for his device.
Click to expand...
Click to collapse
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
If he is already on Kitkat, then you are right of course!He forgot to disable write-protection (http://forum.xda-developers.com/showthread.php?t=2551113) and flashing back to the camera update (12.5.5) and using SlapMyMoto (http://forum.xda-developers.com/showthread.php?t=2538896) before the Kitkat update.

Hatary said:
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
Click to expand...
Click to collapse
I don't see how, seeing as we cannot downgrade from 4.4 to 4.2.2
Maxx'd out Kit Kat

Topsnake said:
I don't see how, seeing as we cannot downgrade from 4.4 to 4.2.2
Maxx'd out Kit Kat
Click to expand...
Click to collapse
Sorry i edited my post before! Of course it doesn't work when he updated already to 4.4

Hatary said:
Sorry i edited my post before! Of course it doesn't work when he updated already to 4.4
Click to expand...
Click to collapse
I see. At any rate, ive streamlined the process for our phones here
http://forum.xda-developers.com/showthread.php?t=2616104
Maxx'd out Kit Kat

Never take a ota update while rooted
Same thing happened to me but i learned the hard way that you should never take a OTA update while rooted because it screws things up and the phone is not stable enough to run Android OS without crashing and rebooting again. So what i did is i used RSD lite to reset to stock and after making sure root was gone i took the OTA update and now my DROID ultra is working fine . and FYI if you still want root when running KitKat use slapmymoto to keep root it requires you to have 4.2.2 already installed and then follow some steps so you can keep root in KitKat hope it helps!

What version of RSD Lite for XT1030?
droidusr2014 said:
Same thing happened to me but i learned the hard way that you should never take a OTA update while rooted because it screws things up and the phone is not stable enough to run Android OS without crashing and rebooting again. So what i did is i used RSD lite to reset to stock and after making sure root was gone i took the OTA update and now my DROID ultra is working fine . and FYI if you still want root when running KitKat use slapmymoto to keep root it requires you to have 4.2.2 already installed and then follow some steps so you can keep root in KitKat hope it helps!
Click to expand...
Click to collapse
What version of RSD Lite did you use? I've tried 5.6, 6.4, 6.5, with different USB cables including the one that comes with the phone but I cannot get RSD Lite to recognize my device. I tried fastboot as well but it keeps giving me an error about missing XML files when I try to flash.

MINI root
Hatary said:
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
If he is already on Kitkat, then you are right of course!He forgot to disable write-protection (http://forum.xda-developers.com/showthread.php?t=2551113) and flashing back to the camera update (12.5.5) and using SlapMyMoto (http://forum.xda-developers.com/showthread.php?t=2538896) before the Kitkat update.
Click to expand...
Click to collapse
Hi, I have MINI with factory 4.4
How can I root it and have custom recovery ( TWRP )
I cannot find guide for XT1030...
THANKS

zsebob said:
Hi, I have MINI with factory 4.4
How can I root it and have custom recovery ( TWRP )
I cannot find guide for XT1030...
THANKS
Click to expand...
Click to collapse
you can't root 4.4. You are stuck until (hopefully) someone releases a root exploit for 4.4
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
mschwartz33 said:
What version of RSD Lite did you use? I've tried 5.6, 6.4, 6.5, with different USB cables including the one that comes with the phone but I cannot get RSD Lite to recognize my device. I tried fastboot as well but it keeps giving me an error about missing XML files when I try to flash.
Click to expand...
Click to collapse
can you post a screen shot/picture of the error you are getting and also the cmd window where you are entering the fastboot commands?

BladeRunner said:
you can't root 4.4. You are stuck until (hopefully) someone releases a root exploit for 4.4
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
can you post a screen shot/picture of the error you are getting and also the cmd window where you are entering the fastboot commands?
Click to expand...
Click to collapse
Thanks! The downgrade to JB and root and update to 4.4 not working on Mini?

zsebob said:
Thanks! The downgrade to JB and root and update to 4.4 not working on Mini?
Click to expand...
Click to collapse
downgrading isn't possible

Confused about if there's root for 4.4 etc

Ok so I got my XT1080 few days or whatever and it had the first 4.4 ota, you know the one with the transparent status bar but still that blue jelly bean hue on the status bar etc.... So not thinking of it I just decided to see if there was another ota and there was so I got it and now I want root.... Here's what I want to know please.. Without telling me to go read 30 pages on another post can someone just tell me
Is there root for me
If so do I have to have boot loader unlocked, I've had phones with locked boot loaders and still flashed Roms
Can I flash Roms on this device with a locked boot loader via twrp
I mainly read that you have to downgrade to a certain version use jcase method it something? I got lost in that bounty post..

Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.

bluebloomers said:
Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.
Click to expand...
Click to collapse
Wow I love you!

alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!

kdm212 said:
alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!
Click to expand...
Click to collapse
What build of 4.4 are you one? 19.5.3 or 19.6.3?

Topsnake said:
What build of 4.4 are you one? 19.5.3 or 19.6.3?
Click to expand...
Click to collapse
19.5.3 it should be made known i plan on using the phone with t-mobile and the outside hope that i can have a fully functional phone with lte...

Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?

Topsnake said:
Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?
Click to expand...
Click to collapse
Boot loader is not unlocked. However if I do the update I won't be able to get root. Correct?

Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off

Topsnake said:
Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off
Click to expand...
Click to collapse
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!

kdm212 said:
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!
Click to expand...
Click to collapse
Link to what specifically? You dont need to downgrade on your version

Topsnake said:
Link to what specifically? You dont need to downgrade on your version
Click to expand...
Click to collapse
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?

kdm212 said:
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?
Click to expand...
Click to collapse
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4

Topsnake said:
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4
Click to expand...
Click to collapse
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!

kdm212 said:
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!
Click to expand...
Click to collapse
No problem

any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?

kdm212 said:
any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?
Click to expand...
Click to collapse
Run motowpnomo to gain wp off then safe strap can install su to system

Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.

TheDroidURLookinFor said:
Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.
Click to expand...
Click to collapse
What version is it on?

Topsnake said:
What version is it on?
Click to expand...
Click to collapse
19.5.3

A little help, please...

XT1080M Dev Ed currently running 4.4 / 19.6.3 rooted with native tether exploit.
If anyone is willing to spare a few minutes and point me in the right direction, I want to be rooted with native tether exploit on 4.4.4 ideally without having to backup then restore all my data and apps, however, I'm willing to do that if it gets me the most stable setup to start over from scratch instead of some patch upgrade path.
Any help greatly appreciated -- I have been searching threads almost three hours but am not quite sure the best path and I am seeing conflicting info or am not understanding some info correclty.
Thanks for your time..!

reyxlp said:
XT1080M Dev Ed currently running 4.4 / 19.6.3 rooted with native tether exploit.
If anyone is willing to spare a few minutes and point me in the right direction, I want to be rooted with native tether exploit on 4.4.4 ideally without having to backup then restore all my data and apps, however, I'm willing to do that if it gets me the most stable setup to start over from scratch instead of some patch upgrade path.
Any help greatly appreciated -- I have been searching threads almost three hours but am not quite sure the best path and I am seeing conflicting info or am not understanding some info correclty.
Thanks for your time..!
Click to expand...
Click to collapse
The smartest thing would be to wait for this: http://forum.xda-developers.com/droid-ultra/general/request-help-exploit-moto-bl-bootloader-t2829042
Then you can update to ANY android version with no fear of losing root.

samwathegreat said:
The smartest thing would be to wait for this: http://forum.xda-developers.com/droid-ultra/general/request-help-exploit-moto-bl-bootloader-t2829042
Then you can update to ANY android version with no fear of losing root.
Click to expand...
Click to collapse
Thanks for the quick reply!
I'm on a Dev Ed with unlocked BL so I thought I didn't have to worry about losing root or not being able to regain it if I lost it?
Or is there no root method available yet for 4.4.4, even for unlocked BL Dev Ed phones?

reyxlp said:
Thanks for the quick reply!
I'm on a Dev Ed with unlocked BL so I thought I didn't have to worry about losing root or not being able to regain it if I lost it?
Or is there no root method available yet for 4.4.4, even for unlocked BL Dev Ed phones?
Click to expand...
Click to collapse
AH! Ok didn't realize you were on an unlocked DEV edition. This is EASY!
Download the entire 4.4.4 SBF for your specific device.
Two ways of doing it:
1. RSD Lite: Extract the SBF, find the XML file. Edit it with Notepad. Find the line "getvar max-download-size" and erase that entire line. Find the line "erase userdata" and erase that entire line. Flash the SBF with RSD Lite (DON'T SELECT THE ZIP! Select the XML file you modified).
You will be updated to 4.4.4 without losing your data/apps.
2. Manual method: Extract the SBF and follow the instructions for manual flashing. SKIP THE COMMAND "fastboot erase userdata".
You will be updated to 4.4.4 without losing your data/apps.
Easy peasy! Full instructions are here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Also there are links to all tools you will need and the firmware files themselves. **BE SURE TO DELETE / SKIP THE ERASE USERDATA COMMAND - otherwise EVERYTHING will be erased. This is NOT included in the linked guide - the guide assumes you WANT to erase everything**
Afterwards, you can re-flash TWRP and re-root. This WILL cause you to lose root (because su is stored in /system) and you will also need to reinstall Xposed if you are using that. But all apps / settings / files will be intact.

samwathegreat said:
AH! Ok didn't realize you were on an unlocked DEV edition. This is EASY!
Download the entire 4.4.4 SBF for your carrier.
Two ways of doing it:
1. RSD Lite: Extract the SBF, find the XML file. Edit it with Notepad. Find the line "getvar max-download-size" and erase that entire line. Find the line "erase userdata" and erase that entire line. Flash the SBF with RSD Lite (DON'T SELECT THE ZIP! Select the XML file you modified).
You will be updated to 4.4.4 without losing your data/apps.
2. Manual method: Extract the SBF and follow the instructions for manual flashing. SKIP THE COMMAND "fastboot erase userdata".
You will be updated to 4.4.4 without losing your data/apps.
Easy peasy! Full instructions are here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Also there are links to all tools you will need and the firmware files themselves. **BE SURE TO DELETE / SKIP THE ERASE USERDATA COMMAND - otherwise EVERYTHING will be erased. This is NOT included in the linked guide - the guide assumes you WANT to erase everything**
Afterwards, you can re-flash TWRP and re-root. This WILL cause you to lose root (because su is stored in /system) and you will also need to reinstall Xposed if you are using that. But all apps / settings / files will be intact.
Click to expand...
Click to collapse
Do I need to restore to stock before doing any of this?
Also:
I currently have the native tether hack going (19.6.3 version) and I don't want to lose it. Do you know if it will survive either of these processes? Or do you know if there a native tether hack already available for 4.4.4 that I can fall back on in case upgrading kills my existing hack?
Thanks again for the help...

reyxlp said:
Do I need to restore to stock before doing any of this?
Also:
I currently have the native tether hack going (19.6.3 version) and I don't want to lose it. Do you know if it will survive either of these processes? Or do you know if there a native tether hack already available for 4.4.4 that I can fall back on in case upgrading kills my existing hack?
Thanks again for the help...
Click to expand...
Click to collapse
This WILL return you to stock -- stock 4.4.4. No reason to flash 4.4 first....this will take you STRAIGHT to 4.4.4.
Yes, the native tether will be lost. You can use THIS instead: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
It works like a dream to enable native tether and bypass the entitlement. Just install it afterwards (after you have flashed twrp and re-rooted), and it will enable native tether for you. Click the "apply on reboot" and it will enable tether after every reboot - no system modifications made

samwathegreat said:
This WILL return you to stock -- stock 4.4.4. No reason to flash 4.4 first....this will take you STRAIGHT to 4.4.4.
Yes, the native tether will be lost. You can use THIS instead: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
It works like a dream to enable native tether and bypass the entitlement. Just install it afterwards (after you have flashed twrp and re-rooted), and it will enable native tether for you. Click the "apply on reboot" and it will enable tether after every reboot - no system modifications made
Click to expand...
Click to collapse
Ah, yes, sorry I missed that, re: returning to stock.
Thanks for all the help!

reyxlp said:
Ah, yes, sorry I missed that, re: returning to stock.
Thanks for all the help!
Click to expand...
Click to collapse
Seeing as you have a XT1080 make sure you flash the 1080 software. Not the Moto X FXZ. Looks like @samwathegreat linked to moto X thread.
Next run my port, guaranteed you'll like it better and comes pre-built with hotspot. Also comes with google dialer/gmail email client/T-Mobile fix etc. All the goodies from the X ported the the Maxx. Link below. Also both the stock XT1080 4.4.4
If you decide to run my port, you dont need to update to 4.4.4 first. You can simply flash my port and be on 4.4.4. Doing it this way will enable you to downgrade to 4.4 19.6.3 if you later choose. If you update to 4.4.4 21.11.21, you cannot downgrade later.
My port below.
http://forum.xda-developers.com/showthread.php?t=2828366
If you choose to use stock XT1080 4.4.4 you can use the tether bypass linked below as well. Same endpoint as the one samwa linked, just doesnt need to be reset each boot and is now twrp flashable.
Link
http://forum.xda-developers.com/showthread.php?t=2811810

Topsnake said:
Seeing as you have a XT1080 make sure you flash the 1080 software. Not the Moto X FXZ. Looks like @samwathegreat linked to moto X thread.
Click to expand...
Click to collapse
I linked him to the guide in the Moto X thread because it is much more concise than anything in the Ultra section. The instructions are identical. In my second reply, I stated to use the correct 4.4.4 firmware for *his device*.
Granted....in hindsight (considering some of the "spoon-feed me" attitudes we see all too often on XDA), I probably should have been more specific. The point is though, that the procedure is identical....

samwathegreat said:
I linked him to the guide in the Moto X thread because it is much more concise than anything in the Ultra section. The instructions are identical. In my second reply, I stated to use the correct 4.4.4 firmware for *his device*.
Granted....in hindsight (considering some of the "spoon-feed me" attitudes we see all too often on XDA), I probably should have been more specific. The point is though, that the procedure is identical....
Click to expand...
Click to collapse
Agreed. You know we can no longer assume anything here.

samwathegreat said:
This WILL return you to stock -- stock 4.4.4. No reason to flash 4.4 first....this will take you STRAIGHT to 4.4.4.
Yes, the native tether will be lost. You can use THIS instead: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
It works like a dream to enable native tether and bypass the entitlement. Just install it afterwards (after you have flashed twrp and re-rooted), and it will enable native tether for you. Click the "apply on reboot" and it will enable tether after every reboot - no system modifications made
Click to expand...
Click to collapse
I am on a Droid Maxx (Not DE) running 4.4.4 on 21.11.21. Locked bootloader, but Rooted ever since JB 4.2.2, followed by SlapMyMoto/MotoWpNoMo and SuperSU survival....I have always updated with OTAs, ever since 4.2........ 21.11.21 turned Wp back on, so I have been using the referenced entitlement bypass v1.2 for tether.
Will the entitlement bypass app continue to work if I take the 23.3.24 OTA
@iKrYpToNiTe -any thoughts?
Thanks in advance for any help. Greatly appreciated.
Donated to @jcase ( sent as friend instead of donate)
Donated to @Topsnake ( pp Confirmation: 98U78263NX3684739)

I think you will lose root if you proceed with the latest OTA.

Sounds like you might be one of those for whom the Sunshine app will work.
Worth a try, you'll be unlocked and never have to worry about losing root again.
Sent from my XT1080 using XDA Free mobile app

If your on 4.2.2 just unlock with sunshine. Best 25 bucks you will ever spend.
sent from "my kungfu is stronger then yours" XT1080

bigv5150 said:
If your on 4.2.2 just unlock with sunshine. Best 25 bucks you will ever spend.
sent from "my kungfu is stronger then yours" XT1080
Click to expand...
Click to collapse
I second that 100%, I love my Maxx now.

kenryan said:
Sounds like you might be one of those for whom the Sunshine app will work.
Worth a try, you'll be unlocked and never have to worry about losing root again.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the idea......and Sunshine worked on my Droid Maxx running 4.4.4 on 21.11.21.
So I went with sunshine, and BINGO! worked on Maxx.
After unfreezing bloat, and undoing previous mods to the /system/ folder, I then took the 23.3.24 OTA and all is good. Entitlement Bypass v1.2, still works (Now that I have an unlocked BL and write protection is back off, there are other options for tether, but I love the fact that entitlement bypass doesnt change system folder, making it that much easier to revert to stock and take OTAs).
From what I can see, even if I still had the locked BL and WP on, taking the 23.3.24 OTA would have still been ok, by keeping root with SuperSU survival, and bypass entitlement still would work. The update went flawless. But like I said, I wanted more options if this had not been the case, so thats why I "sunshined".
-Droide Maxx 4.4.4, 23.3.24 with Root and Unlocked BL......Rooted (RockMyMoto done back on 12.15.1.5, SlapMyMoto on 19.5.3), Unlocked BL (Sunshine ran on 21.11.21), Stock ROM & Stock Recovery

sunshine and 24.3.7
have you taken 24.3.7 OTA without issue? I'm same -- xt1080 after sunshine and counting on entitlement bypass. can you confirm no problems after taking OTA?

kdavidb said:
have you taken 24.3.7 OTA without issue? I'm same -- xt1080 after sunshine and counting on entitlement bypass. can you confirm no problems after taking OTA?
Click to expand...
Click to collapse
I did and entitlement bypass works fine.
sent from "my kungfu is stronger then yours" XT1080

bigv5150 said:
I did and entitlement bypass works fine.
sent from "my kungfu is stronger then yours" XT1080
Click to expand...
Click to collapse
thanks much. I had the same result -- no changes to root or bootloader.
anyone know of a convenient "safe to remove" bloatware list?

[Q] Unable to get back to stock

I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse

TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks

I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.

nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.

dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.

nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?

dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.

nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?

dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM

back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks

empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.

unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?

empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845

not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?

Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.

empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...

nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.

jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?