Database Develop

[Q] What root path do I use?

I just got a Moto X (non-developer edition) and I'm looking to root to take advantage of Xposed and Gravitybox. I'm a little confused as to what path to take however. I'd like to be able to get to 4.4 and still retain OTA updates without losing root, if possible.
Here's my details:
VZW Moto X
Android 4.2.2
Baseband MSM8960PRO_BP2323.020.90.00R
System: 139.15.1.ghost_verizon.verizon.en.us
Build Number: 13.9.0Q2.X-116-MX-17-57-X-1

You will need to look at using the SlapMyMoto method.
But you will not be able to take the future OTAs until someone figures out how to root them (if it even can be done).

I thought that the Slapmymoto method was from the 4.4 OTA already? Should I take the OTA and follow from step 1 of the guide? Or can I just skip downgrading and follow all the way through?

pan2thada said:
I thought that the Slapmymoto method was from the 4.4 OTA already? Should I take the OTA and follow from step 1 of the guide? Or can I just skip downgrading and follow all the way through?
Click to expand...
Click to collapse
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.

KidJoe said:
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.
Click to expand...
Click to collapse
Thanks! I'm coming from first a HTC Incredible and then a GNex so I'm not used to not being able to unlock the bootloader... I'm a little confused about these steps however:
Wait for the bootlaoder screen to appear
Code:
fastboot flash recovery recovery.img
fastboot reboot
Once the device has rebooted, go ahead and take the OTA, once 4.4 is up and running continue.
Step 5)
Now we need to downgrade the bootloader using the 4.2.2 bootloaders and flash the normal kernel to the recovery partition:
Code:
adb reboot bootloader
Wait for the bootlaoder screen to appear
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot reboot
Step 6)
Once booted into 4.4,
Code:
adb push su /data/local/tmp/su
adb push install.sh /data/local/tmp/install.sh
adb push rec.sh /data/local/tmp/rec.sh
adb push install-recovery.sh /data/local/tmp/install-recovery.sh
adb push setup.sh /data/local/tmp/setup.sh
adb reboot
Click to expand...
Click to collapse
First, does the fastboot flash command make a backup of my bootloader? If not, where do I get the bootloader I'm re-downgrading to from? Also where do the recovery.img or motoboot.img files come from? I just want to make sure I fully understand the process before I accidentally brick my phone.

KidJoe said:
If you are on 4.2.2 currently, just start the slapmymoto process as if you have just freshly flashed back to 4.2.2.
The Slapmymoto process will take you up to 4.4 and be rooted.
What mjphillips1981 was saying is once you use Slapmymoto, you will not be able to take any future OTA updates. If Slapmymoto works anything like the previous generation roots, it replaces your stock recovery, and some other things that will make OTA updates fail, lose root, and possibly cause you to be stuck in a boot loop (which should be repairable).
Just like other phones, when future ROM updates come out, unless you have an unlocked bootloader, you need to wait for someone to find an exploit, take advantage of it, and bring out a repeatable root process. So once you root, if you want to keep root, do NOT take an OTA until a root exploit and process have been posted.
Click to expand...
Click to collapse
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.

detonation said:
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.
Click to expand...
Click to collapse
Yes.

detonation said:
But you can always SBF back to factory stock to be able to get OTA's again, right? Without root anymore of course.
Click to expand...
Click to collapse
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
pan2thada said:
First, does the fastboot flash command make a backup of my bootloader? If not, where do I get the bootloader I'm re-downgrading to from? Also where do the recovery.img or motoboot.img files come from? I just want to make sure I fully understand the process before I accidentally brick my phone.
Click to expand...
Click to collapse
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools

KidJoe said:
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
can i use this fastboot installer?
http://forum.xda-developers.com/showthread.php?p=42407269

pan2thada said:
can i use this fastboot installer?
http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
that is a minimal install of Android SDK/Platform tools. Yes you can start with that... BUT you still need to use the special motorola fastboot.exe that I linked to instead of the stock fastboot.exe part of the package in this thread you are linking to.

KidJoe said:
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
KidJoe said:
that is a minimal install of Android SDK/Platform tools. Yes you can start with that... BUT you still need to use the special motorola fastboot.exe that I linked to instead of the stock fastboot.exe part of the package in this thread you are linking to.
Click to expand...
Click to collapse
I used the Android SDK/Platform tools fastboot.exe without issue to root my VZW Moto X using SlapMyMoto. Knowing what I know now, I wouldn't recommend it. Just saying it can be done.

KidJoe said:
In the current state. Yes. That is one way to fix the "boot loop" issue I mentioned, and get back to stock.
i.e. if you are on KK and root, you can re-flash the same KK rom and get back to stock and take a future OTA, without root.
---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------
These questions are answered in the Slapmymoto thread but..
No, the fastboot flash command does NOT backup anything... it FLASHES the files stored on your PC onto your phone. For example: Fastboot flash recovery recover.img would flash the recovery.img on your PC to your phone's recovery "partition"
and looking at the steps, Step 1 tells you to flash back to 4.2.2, which you are on. BUT you still need to download and unzip the 4.2.2 rom for your phone (step 1 has links to the Verizon and ATT versions), as that is where you'll get the .IMG files, logo.bin and other files you'll need in step 4 and 5.
also, make sure you are using THIS Fastboot.exe -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 NOT the one that comes with the Android SDK/PlatformTools
Click to expand...
Click to collapse
Thanks, unfortunately the Slapmymoto thread is 80 pages long and growing, so it's hard to get anything useful out of it. This is what I thought I was supposed to do but I wasn't certain.

[Q] can't install t-mobile 4.4.2 with TWRP 2.6.3.1

can't install t-mobile 4.4.2 with TWRP 2.6.3.1, how can i do? where to get the stock recovery?

arsene28 said:
can't install t-mobile 4.4.2 with TWRP 2.6.3.1, how can i do? where to get the stock recovery?
Click to expand...
Click to collapse
you need the stock firmware package for your phone and when you extract it there will be a image file named recovery you need to flash it then take the OTA then reflash your custom recovery

thank you very much
dray_jr said:
you need the stock firmware package for your phone and when you extract it there will be a image file named recovery you need to flash it then take the OTA then reflash your custom recovery
Click to expand...
Click to collapse
Thank you very much! I followed your words, and upgrated success!

arsene28 said:
can't install t-mobile 4.4.2 with TWRP 2.6.3.1, how can i do? where to get the stock recovery?
Click to expand...
Click to collapse
yo, did you sign up for that forum member thing or whatever it's called in order to get the update before they roll it out to everyone??
I'm on T-Mobile too but haven't gotten the update yet.

campzalot said:
yo, did you sign up for that forum member thing or whatever it's called in order to get the update before they roll it out to everyone??
I'm on T-Mobile too but haven't gotten the update yet.
Click to expand...
Click to collapse
You should see the update very soon. I didn't sign up for anything and received it last night.

campzalot said:
yo, did you sign up for that forum member thing or whatever it's called in order to get the update before they roll it out to everyone??
I'm on T-Mobile too but haven't gotten the update yet.
Click to expand...
Click to collapse
I didn't receive the ota too, Someone shows that they received the upgrade by ota, so I download it from this forum for upgrading.
Sent from my XT1053 using xda app-developers app

campzalot said:
yo, did you sign up for that forum member thing or whatever it's called in order to get the update before they roll it out to everyone??
I'm on T-Mobile too but haven't gotten the update yet.
Click to expand...
Click to collapse
You can get from here make sure to read and your device is compatible http://androidfannetwork.com/2014/02/05/get-the-t-mobile-moto-x-android-4-4-2-kitkat-ota-here-now/
Sent from my Nexus 7 using XDA Premium 4 mobile app

arsene28 said:
Thank you very much! I followed your words, and upgrated success!
Click to expand...
Click to collapse
Could you explain the steps in some more detail? Where do i get the stock image, how to extract the recovery... Thanks!
---------- Post added at 11:59 AM ---------- Previous post was at 11:35 AM ----------
raoulteeuwen said:
Could you explain the steps in some more detail? Where do i get the stock image, how to extract the recovery... Thanks!
Click to expand...
Click to collapse
Is it: download ROM from http://sbf.droid-developers.org/phone.php?device=0 , unzip, and flash extracted recovery.img ?

raoulteeuwen said:
Could you explain the steps in some more detail? Where do i get the stock image, how to extract the recovery... Thanks!
Click to expand...
Click to collapse
here to find your match firmware and download it http://sbf.droid-developers.org/phone.php?device=0
unzip it, and you can find a file named "recovery.img", and copy it to your sdk folder. if you don't have this tool. you can from this website and install it: http://developer.android.com/sdk/index.html . copy the "recovery.img" to "D:\adt\sdk\platform-tools" folder.
after that,connect your phone, and reboot to fastboot, open ":\adt\sdk\platform-tools" in your pc, hold "shift" and click right key of mouse, then shoose "open command window here". then input "fastboot flash recovery recovery.img", and you can get your recovery back to your stock recovery.
after that, you can follow this: http://androidfannetwork.com/2014/02/05/get-the-t-mobile-moto-x-android-4-4-2-kitkat-ota-here-now/
hope you can get what you want, and apologize for my poor english, hope you can understand my answer.

Yes, just like what you said. I'm sorry i didn't see your addition reply.
Sent from my XT1053 using xda app-developers app

arsene28 said:
here to find your match firmware and download it http://sbf.droid-developers.org/phone.php?device=0
unzip it, and you can find a file named "recovery.img", and copy it to your sdk folder. if you don't have this tool. you can from this website and install it: http://developer.android.com/sdk/index.html . copy the "recovery.img" to "D:\adt\sdk\platform-tools" folder.
after that,connect your phone, and reboot to fastboot, open ":\adt\sdk\platform-tools" in your pc, hold "shift" and click right key of mouse, then shoose "open command window here". then input "fastboot flash recovery recovery.img", and you can get your recovery back to your stock recovery.
after that, you can follow this: http://androidfannetwork.com/2014/02/05/get-the-t-mobile-moto-x-android-4-4-2-kitkat-ota-here-now/
hope you can get what you want, and apologize for my poor english, hope you can understand my answer.
Click to expand...
Click to collapse
Thank you very much. Did as you describe (just before reading it, i found out you can't flash an img file through twrp, so googled and found had to do it from PC via the fastboot command ... did that, but when i now try to reboot into recovery i get the green droid and a red exclamation mark ... Haven't found out how to solve that. Right after initiating the command, the first output is "variable not supported!", but the phone did flash. I did try a second time, but get the same result. So i now can't get into a recovery and can't flash Android 4.2.2. Any suggestions ?

raoulteeuwen said:
Thank you very much. Did as you describe (just before reading it, i found out you can't flash an img file through twrp, so googled and found had to do it from PC via the fastboot command ... did that, but when i now try to reboot into recovery i get the green droid and a red exclamation mark ... Haven't found out how to solve that. Right after initiating the command, the first output is "variable not supported!", but the phone did flash. I did try a second time, but get the same result. So i now can't get into a recovery and can't flash Android 4.2.2. Any suggestions ?
Click to expand...
Click to collapse
Found it: while seeing the droid and red exclamation, i can press "Volume Down and Power" and get a menu, am flashing the 4.2.2. while i type this. Thanks!

Mine is press the up and power button. Do you success to flash 4.2.2? I heard that it can't flash down to the previouse system, may cause some trouble?
Sent from my XT1053 using xda app-developers app

if you are not 100% sure you want 4.4.2 i would not flash it because you can not flash back to 4.4.

[Q] Stock rooted with TWRP. Any way to OTA to 4.4.2 without losing data?

So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.

nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
As far as I can figure, the only way would to use an app to backup the data, flash back to factory, re-root and restore the data. The OTA update will remove root access. I would do a backup with CWM first if possible.

nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
if you know what you actually changed with root permissions then you can just flash stock recovery onto the phone then remove all things root and put everything back to normal stock (like unfreezing things out of tibu or whatever) then take the ota. if you are not sure what you changed, you can flash recovery and system then take the ota (assuming you didn't flash new kernals or anything else major).
And if you just want to keep data then you can flash stock ota with rsdlite and remove the two entries that erase data and cache in the xml file. Then take the ota. or flash the fxz and remove the same data erasing entries in the xml

If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X

Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.

robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands

Schaweet said:
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Click to expand...
Click to collapse
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app

robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
robwege said:
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.

Schaweet said:
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Click to expand...
Click to collapse
I kept the old boot animation file so I can just move it back.
Sent from my XT1060 using XDA Premium 4 mobile app

OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X

Schaweet said:
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
OK. I think I will do your method instead. I will unfreeze the apps, install old boot logo and disable xposed just to be safe. Then I will do your method. Wish me luck.
Sent from my XT1060 using XDA Premium 4 mobile app

If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X

Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
You don't even need an unlocked bootloader, you can still flash stock images on a locked bootloader. Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.

eksasol said:
Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
Click to expand...
Click to collapse
You are correct. You can only flash a custom recovery if your bootloader is unlocked. That is what unlocking your bootloader allows you to do - flash unsigned recovery files (i.e., custom recoveries) and obviously, TWRP is not signed by motorola. Then once you have a custom recovery, the custom recovery allows you to flash unsigned operating systems.
If your bootloader is locked, you cannot flash an unsigned recovery.

Schaweet said:
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I meant step 7.
Sent from my XT1060 using XDA Premium 4 mobile app

robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Click to expand...
Click to collapse
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.

NightThyme said:
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
Click to expand...
Click to collapse
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app

robwege said:
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Sent from my Dev Edition Moto X

Schaweet said:
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Click to expand...
Click to collapse
This.

If I wanted to go back to stock from an aosp based ROM could I use the mfastboot recovery and system method or do I ha e to rsd.... I'm unlocked btw
Sent from my Moto X using Tapatalk

ktu84m UpDater

Edit, your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://d-h.st/OEl Use 7-zip or winrar to extract the files.
Mirror https://mega.co.nz/#!EVQyiaSR!sUIKUSR40EQSbL2p6OaOZq2NBxrWs0opbc6IbgbGVvI
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the hammerhead-ktu85m-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.

Gonna give this a shot

So far, so good. I just flashed jd1639's modified factory image using the provided instructions. Please note, there is a bit of a pause during the process, in all, it took around 78 seconds to complete. My N5 now says Android is upgrading. I'm in ART mode, so this will take a while. I will edit this post once it is completely up and running.
Thanks jd1639!
UPDATE: Everything seems to work fine, however my signal levels are not reporting as high as they were with the .17 baseband on Sprint. So I guess I won't have LTE in my office at all!

Any chance of a zip file to flash from custom recovery
Code_Blue N5

i'm getting fastboot is not recognized as internal or external command:??? Any ideas?
---------- Post added at 05:46 PM ---------- Previous post was at 05:30 PM ----------
Not working!... typed flash-all
fastboot is not rfecogniczed as internal or external command

MandoH said:
i'm getting fastboot is not recognized as internal or external command:??? Any ideas?
Click to expand...
Click to collapse
You don't have fastboot set up.
Edit, just double click on flash-all.bat. See if that works
Sent from my Nexus 5 using XDA Free mobile app

Does it work for D821 ?
When tried downloading, it says not available for my country..(India)
Sent from my Nexus 5 using XDA Free mobile app

double clicked and still samething persist.. any suggestions?

Is it okay to flash this with a custom kernel installed?

MandoH said:
double clicked and still samething persist.. any suggestions?
Click to expand...
Click to collapse
Install minimal adb & fastboot from this thread http://forum.xda-developers.com/showthread.php?t=2317790
Extract the rar folder of the ktu84m image to the install folder containing fastboot.exe
Run the flash-all.bat. It should now work

This will flash the stock 4.4.3 kernel.
Sent from my Nexus 5 using Tapatalk

confirmed working on Mac OS X, thanks jd1639!

trd360 said:
Is it okay to flash this with a custom kernel installed?
Click to expand...
Click to collapse
It'll work but will replace your kernel

worked perfectly on first try...window 8...thanks for this brother

trd360 said:
Is it okay to flash this with a custom kernel installed?
Click to expand...
Click to collapse
Same question (more specifically with Franco Kernel)?

Creed0 said:
Same question (more specifically with Franco Kernel)?
Click to expand...
Click to collapse
Yes, but it'll put the stock kernel on

hikarugo said:
Install minimal adb & fastboot from this thread http://forum.xda-developers.com/showthread.php?t=2317790
Extract the rar folder of the ktu84m image to the install folder containing fastboot.exe
Run the flash-all.bat. It should now work
Click to expand...
Click to collapse
This method worked well!!!! thanks a lot!!!:good::cyclops:

Great work. Thank you

Is it possible to use flashify for this?
Sent from my Nexus 5 using XDA Free mobile app

vipinbp said:
Is it possible to use flashify for this?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No
Sent from my Nexus 5 using XDA Free mobile app

Can't flash 6.0 , TWRP recovery won't go into ADB. What can I do?

I rooted today because I can't wait much longer for an OTA update. I'm trying to flash though ADB but can't because TWRP won't load ADB mode. I have reflashed TWRP recovery but it still doesn't work.
So can I do now? Can I use an OTG cable or download the image right to the device? Should I restore my backup and re-root without adding a custom recovery?
I'm so lost, any help would be great.

asarousi said:
I rooted today because I can't wait much longer for an OTA update. I'm trying to flash though ADB but can't because TWRP won't load ADB mode. I have reflashed TWRP recovery but it still doesn't work.
So can I do now? Can I use an OTG cable or download the image right to the device? Should I restore my backup and re-root without adding a custom recovery?
I'm so lost, any help would be great.
Click to expand...
Click to collapse
what are tou trying to accomplish?
you have twrp, use it to flash. you download what you need to the phone, then use twrp to flash it. adb doesnt flash anything.
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
i think i understand, youre trying to flash stovk marshmallow. you use fastboot to flash the factory image, while you are in your bootloader.

Hey @simms22 I just built aosp_shamu , just haven't flashed it myself
Sent from my Nexus 6 using Tapatalk

Yes, I'm trying to flash Marshmallow. I'm trying to access the file on my laptop to be sent to recovery through adb. How else can I get the file to my phone without adb. All the instructions involve adb, but I can't get it to go beyond "starting adb service" and it just sits there spinning its wheels. I tried originally to flash through Nexus Root Toolkit, but that failed do to it not seeing system.img.

asarousi said:
Yes, I'm trying to flash Marshmallow. I'm trying to access the file on my laptop to be sent to recovery through adb. How else can I get the file to my phone without adb. All the instructions involve adb, but I can't get it to go beyond "starting adb service" and it just sits there spinning its wheels. I tried originally to flash through Nexus Root Toolkit, but that failed do to it not seeing system.img.
Click to expand...
Click to collapse
USB-OTG. Or. adb push "file name" /storage/emulated/0/
Sent from my Nexus 6 using Tapatalk
---------- Post added at 20:36 ---------- Previous post was at 20:32 ----------
asarousi said:
Yes, I'm trying to flash Marshmallow. I'm trying to access the file on my laptop to be sent to recovery through adb. How else can I get the file to my phone without adb. All the instructions involve adb, but I can't get it to go beyond "starting adb service" and it just sits there spinning its wheels. I tried originally to flash through Nexus Root Toolkit, but that failed do to it not seeing system.img.
Click to expand...
Click to collapse
You want pure stock? I just made a shamu mm aosp straight from the source, its flashable. You'll have to flash mm gapps and su if you want root.
Official Team Bliss Flo, Deb, v400, v410, vk810, shamu-odexed Maintainer
Sent from my Nexus 6 using Tapatalk

blueyes said:
Hey @simms22 I just built aosp_shamu , just haven't flashed it myself
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
share, and ill probably flash with you. i miss the aosp browser

The Nexus Root Toolkit says I should force flash the image if system.img is not found, and it's not. Is this a good idea or will this brick my devic? Also, where can I find your build, blueeyes?

simms22 said:
share, and ill probably flash with you. i miss the aosp browser
Click to expand...
Click to collapse
http://downloads.blissroms.com/BlissPop/blueyes/
In that folder. Also made flo, deb, flounder
Sent from my Nexus 6 using Tapatalk

asarousi said:
The Nexus Root Toolkit says I should force flash the image if system.img is not found, and it's not. Is this a good idea or will this brick my devic? Also, where can I find your build, blueeyes?
Click to expand...
Click to collapse
get imgs here https://developers.google.com/android/nexus/images and follow this guide http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
no tool kits just do it manually it easy its how i do all my updates

billycar11 said:
get imgs here https://developers.google.com/android/nexus/images and follow this guide http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
no tool kits just do it manually it easy its how i do all my updates
Click to expand...
Click to collapse
Link is just above your post. I agree. Toolkits are an emergency tool. Unless you fully understand what its doing, don't use it.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 20:58 ---------- Previous post was at 20:54 ----------
You want the factory image. Download it. Extract all zips. Install minimal adb and fastboot. Plug up to CPU , put device in bootloader mode. Simply start adb/fastboot, CD to where images are, type fastboot flash bootloader "name of BL", fastboot reboot bootloader, fastboot flash boot boot.img, system system.img, cache cache.img
Sent from my Nexus 6 using Tapatalk

simms22 said:
share, and ill probably flash with you. i miss the aosp browser
Click to expand...
Click to collapse
You try it Simms? Trying to build cm13 now, patched the forced encryption crap.. Had to operate on this branch but its finally building
Sent from my Nexus 6 using Tapatalk

blueyes said:
You try it Simms? Trying to build cm13 now, patched the forced encryption crap.. Had to operate on this branch but its finally building
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
nope. just saw it. im gonna download it, and flash tomorrow. now i need to find marshmallow gapps

simms22 said:
nope. just saw it. im gonna download it, and flash tomorrow. now i need to find marshmallow gapps
Click to expand...
Click to collapse
Ever used benzo gapps? http://renderserver.net/?dir=devs/xanaxdroid/benzo
Sent from my Nexus 6 using Tapatalk

blueyes said:
Ever used benzo gapps? http://renderserver.net/?dir=devs/xanaxdroid/benzo
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
:good: