Database Develop

[Q] Rooted Moto X, OTA update today causing boot loop

Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA

I have froze the ota apk to try to prevent this

small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php

emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?

jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.

OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.

jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.

You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse

FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!

Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.

so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option

jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.

jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.

shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?

Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss

Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app

IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance

Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190

Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse

manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.

[Q] Stuck in safe mode

Hi,
I'm having an issue. The volume down button on my moto x seems to be stuck down, and if I power down or reboot, I am greeted by the fastboot screen. I cannot use the volume buttons to select a normal boot up, as volume down does nothing, and volumeup scrolls. If I plug my phone into a computer, I can use the adb to type "mfastboot continue" and resume startup. However, this places me in "Safe Mode." After soft rebooting (which bypasses the fastboot screen altogether), I still find myself in safe mode. I have the xt1058. Any help getting out of this mode would be appreciated as soon as possible.

themsftcpu said:
Hi,
I'm having an issue. The volume down button on my moto x seems to be stuck down, and if I power down or reboot, I am greeted by the fastboot screen. I cannot use the volume buttons to select a normal boot up, as volume down does nothing, and volumeup scrolls. If I plug my phone into a computer, I can use the adb to type "mfastboot continue" and resume startup. However, this places me in "Safe Mode." After soft rebooting (which bypasses the fastboot screen altogether), I still find myself in safe mode. I have the xt1058. Any help getting out of this mode would be appreciated as soon as possible.
Click to expand...
Click to collapse
When you type "fastboot reboot", does it also end up in bootloader mode?
I'm a little confused because you say that VOL DOWN does nothing, and VOL UP scrolls....it should be the opposite. VOL DOWN should scroll, while VOL UP should select. I'm curious if you could [carefully] remove the back and see if you can find something obstructing the buttons. Be careful and watch a youtube video on rear case removal if necessary.

samwathegreat said:
When you type "fastboot reboot", does it also end up in bootloader mode?
I'm a little confused because you say that VOL DOWN does nothing, and VOL UP scrolls....it should be the opposite. VOL DOWN should scroll, while VOL UP should select. I'm curious if you could [carefully] remove the back and see if you can find something obstructing the buttons. Be careful and watch a youtube video on rear case removal if necessary.
Click to expand...
Click to collapse
Yes, fastboot reboot still puts the device on the fastboot screen. I'll look into removing the case tommorow, also would doing so void my warranty in any way?
And yes, the volume up button is scrolling, and the volume down button does nothing.

themsftcpu said:
Yes, fastboot reboot still puts the device on the fastboot screen. I'll look into removing the case tommorow, also would doing so void my warranty in any way?
And yes, the volume up button is scrolling, and the volume down button does nothing.
Click to expand...
Click to collapse
If you haven't physically damaged your device (which will likely have voided your warranty already), you might consider requesting a warranty replacement.
Unless you do a bad job of disassembly, I doubt they will even know you did this.
Here is an excellent guide that will help you fix your buttons: http://forum.xda-developers.com/moto-x/moto-x-qa/motorola-moto-x-screen-replacement-t2449765
It is geared toward screen replacement, but you can just follow the disassembly to the part where the volume rocker is removed. Clean it and re-assemble.
Good Luck :good:
PS: Sent you a PM.

samwathegreat said:
If you haven't physically damaged your device (which will likely have voided your warranty already), you might consider requesting a warranty replacement.
Unless you do a bad job of disassembly, I doubt they will even know you did this.
Here is an excellent guide that will help you fix your buttons: http://forum.xda-developers.com/moto-x/moto-x-qa/motorola-moto-x-screen-replacement-t2449765
It is geared toward screen replacement, but you can just follow the disassembly to the part where the volume rocker is removed. Clean it and re-assemble.
Good Luck :good:
PS: Sent you a PM.
Click to expand...
Click to collapse
I figure what I will end up doing (painfully) is unrooting my device and restoring it to as close to factory as possible, and then contacting ATT\Motorola.
Any advice on the best way to sucessfully unroot and not have any evidence of a root in the first place? (Sorry, I've looked at previous posts, but I can't really afford to void my warranty and have to pay to replace this phone, and I'd like direct advice from somebody that does know. thanks for all your support so far)
Also, until I am able to contact ATT and get to a store, is there any way to run third-party apps in safe mode (e.g. nova launcher, twitch, etc.)

themsftcpu said:
I figure what I will end up doing (painfully) is unrooting my device and restoring it to as close to factory as possible, and then contacting ATT\Motorola.
Any advice on the best way to sucessfully unroot and not have any evidence of a root in the first place? (Sorry, I've looked at previous posts, but I can't really afford to void my warranty and have to pay to replace this phone, and I'd like direct advice from somebody that does know. thanks for all your support so far)
Also, until I am able to contact ATT and get to a store, is there any way to run third-party apps in safe mode (e.g. nova launcher, twitch, etc.)
Click to expand...
Click to collapse
First, I have no idea which method you used to root and whether or not you disabled WP, or if you unlocked. You never advised to any of this. In fact, you never even advised that you were rooted at all....
I have no idea how or if you can run 3rd party apps in safe mode.

themsftcpu said:
I figure what I will end up doing (painfully) is unrooting my device and restoring it to as close to factory as possible, and then contacting ATT\Motorola.
Any advice on the best way to sucessfully unroot and not have any evidence of a root in the first place? (Sorry, I've looked at previous posts, but I can't really afford to void my warranty and have to pay to replace this phone, and I'd like direct advice from somebody that does know. thanks for all your support so far)
Also, until I am able to contact ATT and get to a store, is there any way to run third-party apps in safe mode (e.g. nova launcher, twitch, etc.)
Click to expand...
Click to collapse
You will need to restore the fxz/XML with Rsd to unroot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
It is vol up which cancels the fast boot mode. Once you see the screen with the 4 options that is the same one Rsd uses. Unlike the older msm8960 phones the first screen is ap/fast boot & is Rsd ready.

aviwdoowks said:
You will need to restore the fxz/XML with Rsd to unroot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
It is vol up which cancels the fast boot mode. Once you see the screen with the 4 options that is the same one Rsd uses. Unlike the older msm8960 phones the first screen is ap/fast boot & is Rsd ready.
Click to expand...
Click to collapse
Actually, there are 5 options: Normal Powerup, Recovery, Factory, Barcodes, BP Tools.
Next, he has advised that his buttons are messed up, and that VOL UP scrolls and doesn't select (he even confirmed that after I questioned it).
And third, if he has unlocked, there is NO chance of "hiding" the fact that he unlocked. This is the reason I asked for clarification about about which method he used to root.

I just mean to say that: being in that Bootloader screen is AP/fastboot. No selection/action is needed. A Rsd restore will unroot the phone.

samwathegreat said:
Actually, there are 5 options: Normal Powerup, Recovery, Factory, Barcodes, BP Tools.
Next, he has advised that his buttons are messed up, and that VOL UP scrolls and doesn't select (he even confirmed that after I questioned it).
And third, if he has unlocked, there is NO chance of "hiding" the fact that he unlocked. This is the reason I asked for clarification about about which method he used to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/moto-x-qa/play-store-crashes-download-continues-t2724215 Root information in that post, sorry for not clarifying.
Also clarifying to the post involving RSD, do I just run RSD Lite on windows and flash a vanilla ROM to my phone? (also would I be able to flash cyanogenmod, or would that violate my warranty\tos)
(EDIT: Just did some googling, from what I can tell custom ROMs are against warranty... does the same apply to official ROMs, such as the 4.4 vanilla at&t rom. Only reason I am so concerned about voiding my warranty is that I'll have to take my phone into the store to get the buttons fixed, and I'm sure the first thing they'll do is run a bunch of checks on the phone software)

Rsd is only for a factory restore, just what you need.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515

aviwdoowks said:
Rsd is only for a factory restore, just what you need.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Thanks, I restored to stock. Unfortunately, I am still in safe mode which is a bit of a pain.

If you have superSU installed you can use that to unroot as there is an unroot option in there and it does work, after you unroot then uninstall superSU.

Transmissiontech said:
If you have superSU installed you can use that to unroot as there is an unroot option in there and it does work, after you unroot then uninstall superSU.
Click to expand...
Click to collapse
I had thought of that, except I couldn't actually access superSU because of recovery mode. I've already restored to stock, however. Thanks anyways!

Got the 5.0.1 notification but...

Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?

Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0

Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.

Anyone able to help?

If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.

It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update

Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop

Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.

Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....

I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!

StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky

I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app

Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.

ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.

gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.

capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.

No worries bud

capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app

Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B

Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..

Nexus 6 infinite bootloop

Just received the n6 today and there was a notification to update to 5.1. I downloaded and updated it and now it is in an infinite bootloop- keeps on saying optimising 125 apps. (BTW this was completely stock- I didn't even sign in to my Google account) . I tried recovery mode wipes and endless reboots but nothings working- help please?
Btw I am a complete noob who doesn't know anything about root etc so I really don't know what to do.

Anyone

Anyone here

Dry Bones said:
Did your phone die mid installation?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
heres a thread that could help you if factory resetting or wiping the dalvik/cache isnt working.
Click to expand...
Click to collapse
It didn't die,no. I want a way of fixing the bootloop- without voiding my warranty

Derp12340 said:
Anyone
Click to expand...
Click to collapse
Derp12340 said:
Anyone here
Click to expand...
Click to collapse
Greetings,
Please refrain from bumping a thread until at least 24 hours have passed. XDA Assist is a very busy forum and the Assist RC's have lives outside of XDA as well.
Regards,
The_Merovingian
Forum Moderator

look up how to flash a factory image.. because as i see it, you only have two choices, flashing a factory image, or getting an exchange from wherever you bought your n6.

Did you ever let it finish optimizing apps? Any time an OTA is installed the first boot takes what seems like forever aka 10+ mins depending on number of apps installed. If you interrupt the process I guess it's possible to corrupt something.
Otherwise like @simms22 said install the factory image to reset it entirely or take it back to in for repairs.
If you'd like to run the factory image install yourself follow Google's instructions and download 6.0.1 image for shamu (Nexus 6) at https://developers.google.com/android/nexus/images.

And also I did not enable developer settings nor did I root my device (it is completely stock) so my bootloader is locked and USB debugging is not enabled

Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.

Go ahead and enable usb debugging and unlock the bootloader.
Once you have everything updated and you don't plan to root or want to do manual installs or take back ups just relock the bootloader when you're done and turn off usb debugging.

janjanrex said:
Go ahead and enable usb debugging and unlock the bootloader.
Once you have everything updated and you don't plan to root or want to do manual installs or take back ups just relock the bootloader when you're done and turn off usb debugging.
Click to expand...
Click to collapse
I think you missed the point... The device is bootlooping = impossible to enable USB debugging and unlock the bootloader.
Derp12340 said:
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Click to expand...
Click to collapse
I think you need to go with option 3 - get a new phone under warranty, which shouldn't be a problem.
With your new phone, before doing anything else, unlock your bootloader. That will save you a lot of headache.
Edit: Did you try doing a factory reset in recovery? Check this link for instructions: http://www.digitaltrends.com/mobile/use-recovery-mode-android/

The Final Answer
If you aren't going to replace the phone under warranty, then this is your only option.
1. Download Nexus Toolkit. http://www.wugfresh.com/nrt/
2. Use the toolkit to download the latest factory image.
3. Boot into Bootloader
4. Flash factory image

pr0ndigy said:
If you aren't going to replace the phone under warranty, then this is your only option.
1. Download Nexus Toolkit. http://www.wugfresh.com/nrt/
2. Use the toolkit to download the latest factory image.
3. Boot into Bootloader
4. Flash factory image
Click to expand...
Click to collapse
well, he has multiple options to choose from.. the other option being flashing the factory image the right way :silly:

simms22 said:
well, he has multiple options to choose from.. the other option being flashing the factory image the right way :silly:
Click to expand...
Click to collapse
My way is the right way!
How do i know?
Because i've done it, and it works.
So take your **** talk somewhere else kid :good:

These little spats are what keep the community interesting, and I enjoy them when they happen. As Dame Edna Everage said: "I have the fortunate gift of being able to laugh at other people's misfortunes." But personally, I go with experience.
simms22 32,086 posts Thanks Meter: 25,801
pr0ndigy 79 posts Thanks Meter: 22
But hey, what do I know...?
As it happens, I'm a big fan of NRT, having praised, recommended and contributed to it a number of times, but I don't rely on it solely. And I would not go so far as to say "My way is the right way".
Just saying...

Its not a boot loop if you were able to get to the "optimizing apps" message. and the fact that it got to the "optimizing apps" message means your system partition is functioning properly.
Ive had optimization run for 35+ minutes before booting when i took my first official update. You may have messed the phone up if you forced Reboot/power off while it was optimizing.
try and let it boot, if you get the optimizing message then plug it up and let it sit overnight if you have to, i promise IT WILL BOOT.
worse comes to worse, just google "nexus 6 back to stock". your boot loader doesnt have to be unlocked, and usb debugging does not have to be enabled to return to stock

Derp12340 said:
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=0nDLvy8F5qk
Using ADB mode, you can flash latest factory images: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
https://developers.google.com/android/nexus/images?hl=en

pr0ndigy said:
My way is the right way!
How do i know?
Because i've done it, and it works.
So take your **** talk somewhere else kid :good:
Click to expand...
Click to collapse
LOL. you have no idea who you're taking to
Sent from my Nexus 6 using Tapatalk

Seems I solved the problem myself. I used the rootkit- I basically just unlocked the bootloader and then reset it and flashed marshamallow 6.0.1 and I'm gonna relock the bootloader tomorrow. It was easy enough even for a noob like me.

I wonder how you did it. I can't imagine that such toolkit is able to unlock a bootloader when "OEM unlocking" wasn't enabled in your rom. Or did you enable that before?

Locked bootloader after installing Magisk / boot problem, can't boot and can't unlock

Hey everyone!
First posting here, long time reader. So, I just f***** up big time. I tried to install the YT Vanced modules for my X4, realized I had to get rid of the stock YT app first, installed Terminal Debloater and at that point my device stuck during boot. To make things infinitely worse, I then proceeded to re-lock the bootloader cycling through the last commands issued. That was dumb, yeah.
Now I get the "device corrupt" message when I try to boot normally and fastboot won't let me flash again saying I need to enable USB debugging, which I can't because the system won't let me boot.
I have a severe feeling I'm screwed with nobody but myself to blame, but I'm also aware of the godlike knowledge in these boards so... can anyone point me in a direction here? Damn I like that phone and have zero funds for a new one right now :/
I can still get into the Power+Down menu, the stock recovery gets me nowhere though. Oh, and it's the Euro Model, Motorola Moto X4 XT1900-05, running the Oreo OTA update.
Cheers people,
grslbr

You need to flash the original official firmware that came loaded on your device but good luck trying to find a copy of that. With the bootloader locked, you're screwed.

Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/

FI stock roms seem to be located at https://firmware.center/firmware/Motorola/Moto X4/Stock/ Have not tried them myself and not sure you can flash with a locked bootloader.

You should be able to flash a stock ROM pretty easily. From what I've seen, you should be able to install any retail stock rom without unlocking the bootloader.

grslbr said:
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
Click to expand...
Click to collapse
Hold Vol+ and Power buttons. Phone will try to reboot several times and then boot normaly. Go to developer options and tick allow factory unlock and USB debugging. Then you just unlock bootloader as usual.
This procedure helped fix the same issue with my xt1900-7 reteu.