Database Develop

[Q] Aw Crap. My phone wont factory data reset. Help

A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?

It looks like I need to reflash the stock recovery image. I believe I have that (as long as the stock recovery is the same for all moto x phones (verizon, sprint, tmo, att, etc).
The problem I am having now is that I don't know how to flash the stock recovery image. All the instructions that I find require the phone to be in fastboot mode, but I have a locked boot loader....so. ..wud am I supposed to do??

dzlvs8 said:
A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?
Click to expand...
Click to collapse
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.

_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.

_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?

dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Click to expand...
Click to collapse
Well your phone is technically rooted when you boot normally, but you don't have write capabilities to /system which is why nothing is sticking. You need to boot the phone into recovery mode to make those changes, and then reboot normally to use them. To boot into the recovery mode with write protection off you need to power your phone down, and power it back up while holding volume down. That gets you into the bootloader and from there you choose recovery and then your phone will reboot with write protection off. It's kind of annoying to have to do it this way but blame Motorola for locking the phone down as well as they did.
To flash the stock recovery back, you need to put the recovery file in your adb folder and then the command is "fastboot flash recovery recovery.img" without the quotes, but if you are unfamiliar with adb I don't recommend doing it. You can just flash the whole stock image with RSDLite and start from square one. I've not personally used RSDLite but here is a video tutorial for you- http://forum.xda-developers.com/showthread.php?t=2446515

dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?
Click to expand...
Click to collapse
also just a quick note:
"adb reboot recovery" will boot you into recovery/writeable system
"adb reboot bootloader" will boot you into fastboot for using rsdlite which is all described in the instructions given by metalhead

Moto X bricked after OTA UPDATE HELP

My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please

fellhound said:
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
Click to expand...
Click to collapse
Fastboot erase cache

shane1 said:
Fastboot erase cache
Click to expand...
Click to collapse
i tried to install stock but i can't with "adb reboot fastloader" beacuse it restarts every 10-20 seconds"
and according to http://forum.xda-developers.com/showthread.php?t=2444957
We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.
After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.
there is not a single drop of help with fastloader
edit: i managed to enable usb depuration by clicking several times on status/kernel version
i can run the command now, moto x responds and just Fast reboot, does not enter into fastloader
reached a dead end, now im desperated

Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X

flashallthetime said:
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
Click to expand...
Click to collapse
wow, finally, i was dying, now it does not reset itself.
How can i know if i have custom recovery? i though it was the normal one, wasn't aware pwnmymoto install custom recovery..
should i install stock rom anyways?
now i am downloading OTA again, now that i don't have root and pwnmymoto installed maybe it will work
will report results in 5 minutes
Thanks for the help guise
EDIT: lel no, after redownloading OTA update, it's still halfbricking with reboots.
I have recovered it again cleaning cache, but i wish to get OTA
Any ideas?
P.D all this trouble just to put 2 files into /system/ to enable Playstation mobile geez ;_;

fellhound said:
bump
Click to expand...
Click to collapse
I specifically know very little about pwnmymoto root method, my boot loader is unlocked, so I rooted the old fashion way. I know pwnmymoto hijacks the stick recovery. You may want to rsdlite back to stock, I believe there's a fxz with the latest update and root with jcases new method. Unless someone with more experience with pwnmymoto replies
Sent on my Moto X

You need to either flash the stock recovery and system through fastboot, or just RSD the whole thing (which deletes all your data). That's the only way you'll get it to accept the OTA update. Without the stock recovery, it will keep boot looping when you try to install the OTA.

Yes. Restore to stock. Threads galore. Once you boot you'll get an OTA prompt that'll work no problem.
Sent from my XT1060 using Tapatalk

http://forum.xda-developers.com/moto-x/general/moto-x-unbrick-ota-update-loader-v30-t3153725

[Q] Moto X stuck in a boot loop

Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE

darylbu said:
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
Click to expand...
Click to collapse
How did you fix it?

I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?

Recovery
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.

MikeNaples said:
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
Click to expand...
Click to collapse
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache

serophia said:
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
Click to expand...
Click to collapse
This process seems to work quite well.
I'd recommend to use MFastboot. With your phone off, you can boot into fastboot by holding power and volume down for a few seconds, release and it will boot into fastboot. Connect the usb cable, and first try "fastboot erase cache". If that doesn't work by itself, repeat the process but also use "fastboot erase userdata" (THIS WILL ERASE ALL YOUR DATA!) but at least there is a chance you might get it to boot normally. It´s like a factory reset, you will have to start from scratch.
I know my answer is out of date but it might be useful for someone coming for this same solution.

Moto x Stuck in TWRP loop
pls help me guys it just goes on restarting it dose not even goes in recovery mode

Guys.. I got struck at unlocked boot loader. Flashed TWRP on 5.1 ( GB retail rom). And its not booting now and not able to flash any rom.. kindly Help...!!!

[Q] Can't update to 5.1 (Previously unlocked & rooted, but re-locked)

I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?

if any files have changed in the system, any, and just one, then you can not update via ota.

simms22 said:
if any files have changed in the system, any, and just one, then you can not update via ota.
Click to expand...
Click to collapse
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...

RichCowell said:
I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?
Click to expand...
Click to collapse
Click the OTA link in my signature for some more information.

RichCowell said:
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...
Click to expand...
Click to collapse
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).

simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Agreed, factory image should get you back to Ota ready.

simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?

RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
for the future, if you are flashing a factory img, then yes.

RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Same thing. Everything has to be 100% stock.
No need to wipe if you don't relock your bootloader.

RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?

RichCowell said:
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?
Click to expand...
Click to collapse
if it booted fine, and your about phone says 5.1, then youre fine.

simms22 said:
if it booted fine, and your about phone says 5.1, then youre fine.
Click to expand...
Click to collapse
Awesome, thanks
Need to decide now whether to bother rooting to make future updates easier...

I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?

sarshadd said:
I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?
Click to expand...
Click to collapse
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.

rootSU said:
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.
Click to expand...
Click to collapse
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.

sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
What does it say when you sideload?

sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
After you put the boot loader in sideload mode, unplug and replug the USB cable, then run adb sideload.

Help, I can't get back to stock!!!

Hello my fellow friends in HTC Desire 626s Metro PCs land.
This is Isaiah speaking. I've run into a little misfortune here and I wanted to know if someone would be kind enough to help me out.
I have seemed to get myself in a little snag, were for some reason after I relock my phone, it won't reboot the system. What happens is, it boots right into download mode. So I unlocked it again and guess what. Everything booted normally.
Then I go to unlock it again, it jumps right back to download mode. I'm going bonkers over here, like Willy Wonka bonkers because i can't figure out why I can't relock my phone without it going right back to download mode. I flashed stock recovery through cmd, before I relocked it, that didn't work. All I did was root my phone. No debloated roms or anything. Just simply rooted my phone. I'm on Android 6.0.1. Somebody will you please help me get back to stock. Sigh, momma told there'd be days like this! Lol!!! I had to throw in a little humor.

I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.

Ace18o said:
I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.
Click to expand...
Click to collapse
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.

s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Ahh my bad, I was very tired last night.

s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.

Problem solved
IsaacGuti said:
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.
Click to expand...
Click to collapse
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:

s3llz said:
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:
Click to expand...
Click to collapse
By any chance, do you have the stock recovery link? I'm having the same issue :/

Sharkyzz said:
By any chance, do you have the stock recovery link? I'm having the same issue :/
Click to expand...
Click to collapse
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing

s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.

s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.