[GUIDE] root, unlock, kk and flash back to jb [READ OP!!!]

[GUIDE] root, unlock, kk and flash back to jb [READ OP!!!] - RAZR HD General

************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14
LOOK AT YOUR SYSTEM VERSION AND MAKE SURE YOU ARE NOT ON 183.46.14or15 BEFORE POSTING, if you are, THE BOOTLOADER UNLOCK AND ROOT WONT WORK, PERIOD, END OF DISCUSSION.
YOU HOSED YOURSELF BY NOT DOING THIS BEFORE UPDATING, THE TOOLS ARE NOT BROKEN.
if you are already unlocked, the relevant parts of this guide will still work as described.
So, you have a Droid Razr Maxx HD or HD, xt926, and want to root, unlock the bootloader, and go back to JB, possibly.
Well this is the guide for you!
***you should backup data before any flash or mod
***the current condition of your phone is irrelevant (root etc). the script will flash from any version, to KK (data wipe option recommended)
first, you need to be on KitKat to root and unlock the bootloader,
if you are not, flash version 1.4 or 1.41 of this in fastboot.
moto drivers if you need them.
to get into fastboot, power off the phone, hold both volume buttons and power until the pre-boot menu comes up then release and choose "fastboot"
alternatively, you can use @SamuriHL's method if that strikes your fancy.
(PLEASE DONT ASK QUESTIONS ABOUT @SamuriHL'S SCRIPT HERE, use his forum.)
after booted etc, put this app, this app, and SU zip on your storage or sd card.
open the "tr" app and follow the directions to root your phone.
when complete and rebooted,
open the Motopocalypse app and follow the directions to unlock your bootloader.
when complete and rebooted,
we are going to need a custom recovery (just because they are great )
go here or here to get the only recovery compatible with KK (they are also in a sub folder of the flash tool)
to flash these per the op's instructions, you will need adb and fastboot.
if you don't have it installed,
open the directory from my flash tool posted above, hold shift, right click, and choose "open command prompt here". this will use the adb and fasboot in my script to install the recovery, using the commands in @dhacker29's op. just make sure you moved the recoveries out of the sub folder and into the main one, or it will fail.
here is a more complete step by step i made for another user. just change the file name if you are flashing twrp.
if you aren't comfortable using the commands to install the new recovery, alternatively, you can put the recovery on your storage and use Flashify to install it.
after flashing your new recovery, (3 button trick from above, and select "recovery")
boot back into recovery, and flash the SU zip from above. this will give you a properly working root (towel is great but has some faults)
now you have a fully functional razr hd or maxx hd with root and an unlocked bootloader on KitKat.
for those of you who just wanted to unlock and want to go back to JB, or just want to go back to JB for any reason after unlocking.
flash this in rsd (many tutorials on how to use RSD can be found on Google)
i already edited the stock file so you dont have to do it
now you want root again?
now that you are unlocked, forget all of those old exploits, (yes, they still work if you choose to use them) from now on, you can just install a custom recovery and flash the SU zip i gave you in recovery.
i hope this helps you, i will be updating it as needed.

reserved

Is the boot loader on KitKat kernel or jb kernel
Sent from my DROID RAZR HD using XDA Free mobile app

derpyherp said:
Is the boot loader on KitKat kernel or jb kernel
Sent from my DROID RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Not sure what you mean, but it should be on whatever system version you have installed.
Sent from my LG-VS980 using XDA Premium 4 mobile app

I'm completely new to unrooting and unlocking, so, please bear with me. When kitkat came out, my battery life suffered, and I learned about this exploit, I decided it was time to learn how to unroot and unlock so I could go back to jellybean.
Long story short, I gained root access, unlocked the bootloader, and got status code 3. Last night, I downloaded RSD Lite, booted into fastboot AP mode, and I must have missed a step or screwed something up, because I got the following errors:
--RSD lite said: "3/23 flash partition "gpt_main0.bin" -> Phone returned FAIL".
--The phone's flashboot screen says: "flash failure, usb connected, downgraded security version, update gpt_main version failed, preflash validation failed for GPT."
My phone was stuck in fashbot ap mode for a little while, and I could not restore the recovery img file I had saved with flashify, because it was no longer in the sd card directory. Not sure what's going on there, but whatever. Fortunately, I was able to wipe all data, and reboot into normal mode after holding all three buttons, but it was pretty scary for a while. Now, however, if I power off now, the only way I can get the phone to reboot properly is using the three button method. If I try to power on normally, I just get the flashboot AP screen, and a flash failure.
As I read through everything again and again, I think that perhaps I skipped the adb step, though rsd still went through its motions. I initially tried to pull the zip/rar file thru flashify, but flashify gave me an error and wouldn't work with it.
All this being said, wondering if anyone advise a best course of action at this point? Can I just go back to the adb step and use rsd again? Or, should I somehow flash a recovery back to kitkat and start over, even though my copy apparently went kaput? I could possibly grab a flashify file from my wife's phone, which is also the XT907, but not sure if it really works that way...Sort of nervous about tinkering further since I'm so new to this and apparently have a lot to learn. Alternately, I could try house of moto.
Thank you!

You can't downgrade the GPT or TZ partitions. That's why my RSD Script Generator and House of Moto utils create a UNIVERSAL script for downgrading. It skips those partitions.

SamuriHL said:
You can't downgrade the GPT or TZ partitions. That's why my RSD Script Generator and House of Moto utils create a UNIVERSAL script for downgrading. It skips those partitions.
Click to expand...
Click to collapse
I think I get the jist of what you're saying, and while I understand what a partition is, I'm not sure what a GPT or TZ partition is, specifically. Regardless, it sounds like you're saying the best course of action now is to go the RSD script generator route?
My goal is just to get back to a stable OS, and eventually downgrade to JB, version 98.18.94.XT907, as any other version sent my phone into involuntary power offs. Whether that means I install KK first then go down, or go straight to JB doesn't matter too much.
Would another option be to use my wife's flashify recovery? We have the same phones...

No, you can't flash things from other phones. So we can just drop that idea.
Yes, my RSD Script Generator is the quickest way. Use it with the 9.30.1 FXZ (what you're calling 9.18.94 as they are the same version, but, the FXZ is 9.30.1), then flash the UNIVERSAL script that's generated with RSD. Done, and on JB as you wish.

Issues with script
I am having trouble with the rooting script. I am running into the error 'Preflash validation failed' in the Dan Rosenberg script, and then trying to boot the phone takes me to AP Fastboot with 'No valid PIV block in SP for system / piv validation failed (system)'.
My guess is that this is because I casually downloaded the 1.4 version of the script instead of the 1.41, so maybe that utility will work better. I will update this thread as I continue to troubleshoot.
---------- Post added at 07:05 PM ---------- Previous post was at 06:59 PM ----------
ModernZombie said:
I am having trouble with the rooting script. I am running into the error 'Preflash validation failed' in the Dan Rosenberg script, and then trying to boot the phone takes me to AP Fastboot with 'No valid PIV block in SP for system / piv validation failed (system)'.
My guess is that this is because I casually downloaded the 1.4 version of the script instead of the 1.41, so maybe that utility will work better. I will update this thread as I continue to troubleshoot.
Click to expand...
Click to collapse
When I run the script it seems to enter a loop where it runs 'writing system' and 'sending system' again and again...
---------- Post added at 07:09 PM ---------- Previous post was at 07:05 PM ----------
ModernZombie said:
I am having trouble with the rooting script. I am running into the error 'Preflash validation failed' in the Dan Rosenberg script, and then trying to boot the phone takes me to AP Fastboot with 'No valid PIV block in SP for system / piv validation failed (system)'.
My guess is that this is because I casually downloaded the 1.4 version of the script instead of the 1.41, so maybe that utility will work better. I will update this thread as I continue to troubleshoot.
---------- Post added at 07:05 PM ---------- Previous post was at 06:59 PM ----------
When I run the script it seems to enter a loop where it runs 'writing system' and 'sending system' again and again...
Click to expand...
Click to collapse
Nevertheless the script seems to have succeeded and my booting issues are over. Using the 1.41 version of the script fixed my issue. Hopefully that helps someone who has the same problem that I did.

I'm glad you were able to use Bwen Diord's updated util to fix it. Goes to show you should always make sure to use the latest version of whatever util you're using.

SamuriHL said:
You can't downgrade the GPT or TZ partitions. That's why my RSD Script Generator and House of Moto utils create a UNIVERSAL script for downgrading. It skips those partitions.
Click to expand...
Click to collapse
see what happens when i take a 3 hour drive to NJ lol i missed all the fun.
i did edit that file, i must have missed a line, ill fix it right away.

ModernZombie said:
I am having trouble with the rooting script. I am running into the error 'Preflash validation failed' in the Dan Rosenberg script, and then trying to boot the phone takes me to AP Fastboot with 'No valid PIV block in SP for system / piv validation failed (system)'.
My guess is that this is because I casually downloaded the 1.4 version of the script instead of the 1.41, so maybe that utility will work better. I will update this thread as I continue to troubleshoot.
---------- Post added at 07:05 PM ---------- Previous post was at 06:59 PM ----------
When I run the script it seems to enter a loop where it runs 'writing system' and 'sending system' again and again...
---------- Post added at 07:09 PM ---------- Previous post was at 07:05 PM ----------
Nevertheless the script seems to have succeeded and my booting issues are over. Using the 1.41 version of the script fixed my issue. Hopefully that helps someone who has the same problem that I did.
Click to expand...
Click to collapse
it is supposed to write the system over and over and over, it breaks it down into small blocks and send then writes a little at a time.
thats how it is supposed to work.

bweN diorD said:
see what happens when i take a 3 hour drive to NJ lol i missed all the fun.
i did edit that file, i must have missed a line, ill fix it right away.
Click to expand...
Click to collapse
It happens to the best of us. LOL.

SamuriHL said:
It happens to the best of us. LOL.
Click to expand...
Click to collapse
i just looked and the gpt and tz are removed from the copy on my pc, im dl the file to verify.
i didnt dump the files from the directory, but that shouldnt matter because there not called out in the xml right?

he must not have used my file
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VANQUISH_CFC_IFLASH" />
<software_version version="vanquish_vzw-user 4.1.2 9.8.1Q-94-1 57 release-keysVANQUISH_BP_100730.151.64.17P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="BB624DBDA3BE7B433AFC4D0123B33491" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="68CB15F37E13BBD8277EB3429FCC871D" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="86C984B56AE4EE83AB0AE2B7525CCF1E" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="F9F828A07EFF5ACA78C51E60EC6A0391" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="BB624DBDA3BE7B433AFC4D0123B33491" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="68CB15F37E13BBD8277EB3429FCC871D" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="86C984B56AE4EE83AB0AE2B7525CCF1E" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="F9F828A07EFF5ACA78C51E60EC6A0391" />
<step operation="flash" partition="boot" filename="boot.img" MD5="70A4C7CC93E3C2CBC37B6DAA6BDA2E74" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="9D7F66A977550FF3496EBDAD79511CDE" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="0B2F9307E348E9CA0A0B11A29BCA28C1" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="82BE40595235096DCE6E20796DD39444" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="01CCD38F085EBEFE1080223FC62A5415" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="E01BB8745EE1529BD1DB7289EE38B2E1" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="9E38AECE800CB17548D62D4457100AF8" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="tombstones" />
</steps>
</flashing>

Looks good to me. This is why I just released a new tool that's really, REALLY hard to screw up. It's painfully easy.

SamuriHL said:
Looks good to me. This is why I just released a new tool that's really, REALLY hard to screw up. It's painfully easy.
Click to expand...
Click to collapse
well if they would just use what i provided, its cut and dry.
short of completely redoing the script and adding in every function from jb to kk, unlocking, and back to jb with auto install of the recoveries and root. well im not doing all that. the steps are well laid out, if they cant follow the directions, that's not my fault.
it gets frustrating when you spend time making something for the sole benefit of others, and they cant take five minutes to read the directions, then come running for help like its not working properly....

LMAO....I may have run into that problem a "few times".

bweN diorD said:
well if they would just use what i provided, its cut and dry.
short of completely redoing the script and adding in every function from jb to kk, unlocking, and back to jb with auto install of the recoveries and root. well im not doing all that. the steps are well laid out, if they cant follow the directions, that's not my fault.
it gets frustrating when you spend time making something for the sole benefit of others, and they cant take five minutes to read the directions, then come running for help like its not working properly....
Click to expand...
Click to collapse
Get used to it if you want to do this....

cmh714 said:
Get used to it if you want to do this....
Click to expand...
Click to collapse
I'm not going to concede.
Ill just start posting links to the op instead of explaining again.
Sent from my LG-VS980 using XDA Free mobile app

Related

[GUIDE] Republic Wireless Moto X KitKat 4.4.2 Root, Safestrap, TWRP, and MotoWpNoMo

Alright, this is a convoluted and awful process, but it works, and it is the only one we have right now.
If you already got 4.4.2 from the OTA or SBF, without using the method below. STOP none of this will work on your phone.
It is a 7 step process. Outline is as follows:
1. Download the 4.2.2 zip for your Moto X.
A. Go to Here. http://sbf.droid-developers.org/phone.php?device=0B. Download Android 4.2.2 Blur_Version.139.4.17.ghost_row.RepublicWireless.en.USC. Extract it.D. Flash the files with fastboot. Flash them all. Including bootloader and recovery.E. This will restore your phone to STOCK 4.2.2, hope you had backups.2. Root using RockMyMoto
A. http://forum.xda-developers.com/moto-x/orig-development/root-rockmymoto-yes-ota-t25095903. Install the Tmobile XT1053 Safestrap
A. http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/4. [kill write protection] MotoWpNoMo
A. This is permanent. (Well... Mostly, someone more important than me can answer how/why) Do you own research here)B. http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113C. Here is a mirror of the MotoWpNoMo, since his windows zip link is broken https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit5. Download the 4.4.2 Safestrap flashable update.zip from one of the links below.
A. Mirror A: http://www.leetnet.net/update_SafeStrap_4.4.2_RW.zipB. Mirror B: TDBC. Mirror C: TDBD. Reboot into SafeStrap TWRPE. Delete any Slots you may have. They won't work anymore after this.F. Flash the update zip into the "Stock" slot.6. Download the 4.4.2 zip for your Moto X.
A. Go to Here. http://sbf.droid-developers.org/phone.php?device=0B. Download Android 4.4.2 Blur_Version.165.44.12.ghost_row.RepublicWireless.en.USC. Extract it.D. STOP EVERYTHING AND READ THE NEXT PART CAREFULLY. YOU DON'T WANT TO SCREW THIS PART UP.E. LIKE SERIOUSLY, YOU WILL BRICK IT.F.
Code:
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
G. NOTHING ELSE. DO NOT TOUCH THE OTHER FILES. ESPECIALLY LEAVE RECOVERY UNTOUCHED. The reason for this is that you won't be able to flash the 4.2.2 ever again without the 4.2.2
recovery, which means you would lose the ability to root, disable WP, or install safestrap.7. Download the SuperSU zip (or if you are Rashed97 and then you can do some CM crap )
A. http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zipB. Flash this from TWRP, and it will "re-root" your 4.4.2
Thanks: jbrukardt, jcase, iKrYpToNiTe, glarepate, Rashed97, and my wife's phone for being a "test platform"
No Warranty. No Hating. No Killing my Dog.

RESERVED.

I can't thank you! Literally!
Bcuz: Sorry, you are limited to 8 thanks per day
So maybe I will thank you tomorrow. (X-D
---------- Post added at 04:11 PM ---------- Previous post was at 04:11 PM ----------
I can't thank you! Literally!
Bcuz: Sorry, you are limited to 8 thanks per day
So maybe I will thank you tomorrow. (X-D

glarepate said:
I can't thank you! Literally!
Bcuz: Sorry, you are limited to 8 thanks per day
So maybe I will thank you tomorrow.
Click to expand...
Click to collapse
Thank me by reading through it and making sure everything is sane and works. This is my first "Guide"

malcolmputer said:
Thank me by reading through it and making sure everything is sane and works. This is my first "Guide"
Click to expand...
Click to collapse
Ok. You have a typo in the section about downloading the KK SBF. It says:
6. Download the 4.4.2 zip for your Moto X.
A. Go to Here. http://sbf.droid-developers.org/phone.php?device=0
B. Download Android 4.2.2 Blur_Version.139.4.17.ghost_row.RepublicWireless.e n.US
It should say -- Blur_Version.165.44.12.ghost_row.RepublicWireless.en.US
So, thank you twice!!

Great new guide. ?
The only thing I think should be added, directly at the top of the OP...and in bold capital letters... ..is if you're already on 4.4.2.....stop reading.....and don't do any of this.. Lol
Unless something has changed, if they are already running 4 4.2.....and do step one, they could be on the road to trouble.
Please tho.....correct me if I'm wrong.
Great job tho!!!! I don't think many know of this relatively new method.
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
BTW....if this method leaves you with root AND write protection disabled on 4.4.2....shouldn't the person that figured this out be receiving the healthy bounty?????

Adding to this. MotoWpNoMo is dead link in the op of the original thread.
Here's a live link
https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit
---------- Post added at 11:58 PM ---------- Previous post was at 11:48 PM ----------
kj2112 said:
Great new guide. ?
The only thing I think should be added, directly at the top of the OP...and in bold capital letters... ..is if you're already on 4.4.2.....stop reading.....and don't do any of this.. Lol
Unless something has changed, if they are already running 4 4.2.....and do step one, they could be on the road to trouble.
Please tho.....correct me if I'm wrong.
Great job tho!!!! I don't think many know of this relatively new method.
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
BTW....if this method leaves you with root AND write protection disabled on 4.4.2....shouldn't the person that figured this out be receiving the healthy bounty?????
Click to expand...
Click to collapse
correct, if you've already taken the ota, you're right and proper borked.

Well, I couldn't wait for reports of success, requests for clarification, etc. So I just kind of bulled my way through and now I am up and running165.44.12.ghost_row.RepublicWireless.en.US and my phone is downloading stuff wildly as it syncs with Google's servers and restores all my old apps and settings and such-like.
Haven't switched to ART yet. But it's early days yet. Certainly too early to start whining when I have this lovely new OS to play with.
---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------
Well, I couldn't wait for reports of success, requests for clarification, etc. So I just kind of bulled my way through and now I am up and running165.44.12.ghost_row.RepublicWireless.en.US and my phone is downloading stuff wildly as it syncs with Google's servers and restores all my old apps and settings and such-like.
Haven't switched to ART yet. But it's early days yet. Certainly too early to start whining when I have this lovely new OS to play with.

OK, so I used the update.zip to update to 4.4.2. If I use RSD Lite to go back to 4.2.2, why wouldn't this guide work?

ScipioWarrior said:
OK, so I used the update.zip to update to 4.4.2. If I use RSD Lite to go back to 4.2.2, why wouldn't this guide work?
Click to expand...
Click to collapse
Cause once you're on the 4.4.2 boot loader....trying or successfully downgrading it can lead to a bricked device. Just something about that 4.4.2 boot loader.

kj2112 said:
Cause once you're on the 4.4.2 boot loader....trying or successfully downgrading it can lead to a bricked device. Just something about that 4.4.2 boot loader.
Click to expand...
Click to collapse
OK, so what step can't you do on the 4.4.2 bootloader?

Yep. If you use any other method to update than mine, you lose the ability to downgrade back to 4.2.2, which means no more disable WP, and in RW's case, without 4.4, no more root.

ScipioWarrior said:
OK, so what step can't you do on the 4.4.2 bootloader?
Click to expand...
Click to collapse
You can't downgrade it, period. And if your on a locked boot loader, you can't root it.
All you can do is sell it, and put the money towards one that can be unlocked and works on your provider.
Sorry.

kj2112 said:
Cause once you're on the 4.4.2 boot loader....trying or successfully downgrading it can lead to a bricked device. Just something about that 4.4.2 boot loader.
Click to expand...
Click to collapse
that something specifically is the recovery. the 4.4.2 recovery patches the bug that allows us to exploit and run MotoWpNoMo

So let's say that I somehow screwed up Step 1. I downloaded 4.2.2, verified md5, extracted, and ran the included .bat to flash everything. I've now booted up into a sick android logo with an exclamation point. How exactly have I screwed up and can it be fixed?
edit: Weird. After that happened, it rebooted on its own and now its fine.

teh_lorax said:
So let's say that I somehow screwed up Step 1. I downloaded 4.2.2, verified md5, extracted, and ran the included .bat to flash everything. I've now booted up into a sick android logo with an exclamation point. How exactly have I screwed up and can it be fixed?
edit: Weird. After that happened, it rebooted on its own and now its fine.
Click to expand...
Click to collapse
this wording looks awfully similiar.

A little bit more feedback on the process.
NOTE: I was 97% in Debian Wheezy but WPNoMo requires 32 bit Linux so for that I had to boot into Slackware. Also watch your phone's screen and grant permission when Su asks for it. I spaced that part out and had to -- shudder -- run the 'wpbegone' script a second time for it to succeed.
I was able to use the Android version of fastboot to set oem mode but for most everything else only the motofastboot program worked. My advice is just use the Motorola version for everything since there doesn't seem to be anything that it _can't_ do, it just has some things that it __can__ do that are needed. If you see the "variable not supported" diagnostic message then go back and re-do that step over again with motofastboot. When the step to configure the carrier for Sprint failed my heart dropped into the apartment down on the first floor. But re-doing the erasing and flashing steps, with no reboot, no re-running the 'fastboot oem set_fb_mode' command line or anything else, and it succeeded ; bullet dodged. Whew!
It would be nice if there were excruciating detail on things like every little step of wiping/factory setting the Stock slot in SafeStrap. Maybe it's just because I am out of practice that it seemed a little bit lacking in specificity and left me wondering a bit about what I was going to do next in light of what the instructions conveyed to me. Or maybe it's just my anxiety, after all I did get through it successfully.

glarepate said:
A little bit more feedback on the process.
NOTE: I was 97% in Debian Wheezy but WPNoMo requires 32 bit Linux so for that I had to boot into Slackware. Also watch your phone's screen and grant permission when Su asks for it. I spaced that part out and had to -- shudder -- run the 'wpbegone' script a second time for it to succeed.
I was able to use the Android version of fastboot to set oem mode but for most everything else only the motofastboot program worked. My advice is just use the Motorola version for everything since there doesn't seem to be anything that it _can't_ do, it just has some things that it __can__ do that are needed. If you see the "variable not supported" diagnostic message then go back and re-do that step over again with motofastboot. When the step to configure the carrier for Sprint failed my heart dropped into the apartment down on the first floor. But re-doing the erasing and flashing steps, with no reboot, no re-running the 'fastboot oem set_fb_mode' command line or anything else, and it succeeded ; bullet dodged. Whew!
It would be nice if there were excruciating detail on things like every little step of wiping/factory setting the Stock slot in SafeStrap. Maybe it's just because I am out of practice that it seemed a little bit lacking in specificity and left me wondering a bit about what I was going to do next in light of what the instructions conveyed to me. Or maybe it's just my anxiety, after all I did get through it successfully.
Click to expand...
Click to collapse
Flesh it out into a "noob guide" then that includes every detail

Fastboot Flash Errors
First of all, thanks so much!
So, when I try to flash the .img files through fastboot, boot.img always goes through successfully, but if i try to flash in motoboot.img, recovery.img, or system.img, I get this:
"Variable not supported!
target reported max download size of (whatever size it was) bytes
sending 'boot' <whatever size the file was kb>...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: however long it took s"
I have no idea what's going wrong, could you please help? I am able to restore my phone by selecting recovery in fastboot so there's no permanent damage done, but I want to get out of 4.2.2.

Will try to work on some noob-friendly verbiage this weekend. (-
---------- Post added at 12:25 AM ---------- Previous post was at 12:15 AM ----------
Victor Czar said:
First of all, thanks so much!
So, when I try to flash the .img files through fastboot, boot.img always goes through successfully, but if i try to flash in motoboot.img, recovery.img, or system.img, I get this:
"Variable not supported!
target reported max download size of (whatever size it was) bytes
sending 'boot' <whatever size the file was kb>...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: however long it took s"
I have no idea what's going wrong, could you please help? I am able to restore my phone by selecting recovery in fastboot so there's no permanent damage done, but I want to get out of 4.2.2.
Click to expand...
Click to collapse
For every step where you see "Variable not supported!" you will need to use the Motorola version of fastboot because the Android SDK version isn't capable of performing the task.
The Moto version is contained in this Zip archive:
http://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280

How to reload OTA update after clearing cache?

I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?

Dave_Ro said:
I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?
Click to expand...
Click to collapse
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?

wantabe said:
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?
Click to expand...
Click to collapse
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.

Dave_Ro said:
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.
Click to expand...
Click to collapse
Sorry! I should have received a notification email that you had responded. For whatever reason, lately, the notification works some of the time but not always. I had no idea the bootloaders had gotten so effing screwed up! I bought my daughter a 2012 N7 for Christmas and no wonder I had to let it do an OTA before it would let me flash a factory image. I vaguely remember getting a bootloader invalid state error. My brothers bone stock 2012 N7 is on 4.4.4 with no issues, he would have called me otherwise. ; )
If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor you use (I use editpad lite or notepad) and remove the -w from the text it won't wipe your device. You will keep your settings, installed apps and storage. Extract the factory image into the same folder as your adb.exe and fastboot.exe, you should see these files if you have the 3G version;
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-krt16s.zip
radio-tilapia-1231_0.18.0_0409.img
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.

wantabe said:
...I had no idea the bootloaders had gotten so effing screwed up!
Click to expand...
Click to collapse
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
]If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor...
Click to expand...
Click to collapse
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.
Click to expand...
Click to collapse
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?

Dave_Ro said:
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
Out of curiosity I looked at the bootloaders and even though they say v4.23 a crap load of them are different sizes. Just as an example jwr66v is 2,150,992 bytes and ktu84p is 2,151,068 bytes. Don't have a clue what is going on. I can tell you that the bootloaders on the N5 and 2013 N7 are the exact same size across os versions that state the same bootloader version number.
---------- Post added at 02:19 AM ---------- Previous post was at 02:00 AM ----------
The vast majority of the time I also fastboot flash the images separately, I make a few too may changes in the system files to be able to use an OTA unless it's a very small one. I would flash the images for krt16s, bootloader, boot, system, recovery and radio. Then let it do a couple OTA's. 4.4.2 has a different size bootloader (4,005,632 bytes) and 4.3, 4.4.3 and 4.4.4 have the same size (2,151,068 bytes).
---------- Post added at 02:26 AM ---------- Previous post was at 02:19 AM ----------
Dave_Ro said:
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
I would think flashing the system image would clear it out but I guess not. If you were rooted you could run SDMaid and I think that would clear it. If you were rooted you could sideload the OTA and put it in /cache and see it that works. Sorry, I don't have a lot of experience running OTA updates, I usually have to fastboot flash images.

Well, in the end I successfully reflashed it to 4.4 (KRT16S), erasing user data. It then did 3 OTAs to 4.4.4 in quick succession.
Along the way it said:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
tos? ISTR that was on the Atari ST
Thanks for the suggestion. I don't need half these apps anyway - it's good to have a clearout!
Dave

Easily Apply OTA Update To Rooted Nexus 6

I had a hard time finding this information, so thought I would post a new thread!
After you root your phone, even if using standard recovery, the OTA updates will no longer install. You may get the notifications, but after it reboots to install, you will get a failed notification. Even if you uninstall root. This is because if there is any change to the system image at all, the OTA update will fail.
To install it is actually easy, just requires some legwork. I assume you understand what the bootloader is, and what adb and fastboot tools are since your phone is already rooted. If you used a toolkit, there are plenty of guides on XDA on how to install these tools manually.
Step 1 - Collect Needed Files:
Visit the Google System Images page and download the image for your existing ROM. Check your About Device page to get the exact ID, it should say something like LVY48E.
Extract the system.img file so you can flash it later.
Download the OTA image. All OTA images are listed on the Nexus 6 OTA Images thread. Find the file which upgrades "From" your current ROM id. It will only work if from matches your current image version. It will be named something like 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip, and this file in particular flashes to the new LVY48F version from LVY48E version.
Step 2 - Flash Stock System Image:
This step replaces your system image with the stock system image. This will not delete your apps or other personal data, only the information stored on the system partition. The only exception is if you rooted and stored any data on this partition. Plug your phone into your computer. There is no way to do this without a PC.
Reboot into bootloader mode either from booting with POWER+VOLDOWN or via adb:
Code:
adb reboot bootloader
and flash the image
Code:
fastboot erase system
fastboot flash system system.img
At this point your system is stock again (unrooted).
Step 3 - Flash Update Image:
Enter the recovery mode. You can also do this via TWRP but I will cover with stock recovery. Press Volume Up/Down until you see RECOVERY and press power to choose. You are now in recovery.
Press and hold Power and tap Volume Up once to get the recovery menu. Then use Volume Up/Down to select "apply update from ADB" and then Power to select
I had to unplug and plug my phone back in at this point to get it to show up to adb. You can confirm it is visible with the command adb devices.
Apply the OTA update file using the following command, replacing the file name with your own:
Code:
adb sideload 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
After a few minutes the sideload will complete, the phone will reboot and optimize apps, and you can verify the update worked by checking your about system page again.
To root your device again, re-install SuperSU and you're good to go.

I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.

hayzooos said:
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
Click to expand...
Click to collapse
Nope, system.img was all that I flashed, verified it worked fine with just that.

So you just have to re-root after right?

JTheAppMerchant said:
So you just have to re-root after right?
Click to expand...
Click to collapse
Correct

Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
adb sideload 4458964f84d2e44ecd2c1c31c301d47eec4b080e.signed-shamu-LMY48M-from-LMY48I.4458964f
Click to expand...
Click to collapse
it gets to about 50%, then gives a Error message,
E:Error in /sideload/package.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
Any suggestions?

falconfox said:
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
it gets to about 50%, then gives a Error message,
Any suggestions?
Click to expand...
Click to collapse
First try a different USB cable and port.

Thanks for the guide. Does it wipe all the data and files in internal storage?

I did this successfully
torecdude said:
Thanks for the guide. Does it wipe all the data and files in internal storage?
Click to expand...
Click to collapse
I wanted to say thanks first of all for putting this up. It helps those rooted users out there that do actually want security patches applied to the system image. To answer the question above, No it does not wipe data or storage if you follow the instructions to only modify /system partition.
A note about the LMY48M update file and the above comments in the OP : This update changes the kernel (in other words), the boot.img file as well. So if you have flashed a non-stock kernel, you will need to go back to stock during the update (and I suggest just leaving it). That is the partition called boot where boot.img lives. It mainly is the kernel. The way to go back to stock (say if you flashed franco with the FKupdate tool and did not do it manually) is to simply do like above and flash it from the factory image he mentions above for 48I file.
You reboot to the bootloader (*I assume you know how*) with power and vol down button. And then the following command after flashing system.img:
fastboot flash boot boot.img
This takes you to stock LMY48I and should allow you to update now to 48M. I learned this by watching the update failure messages as well as noticed it has boot.img changed in the zip file. Hope this helps others. :good:

bitpushr said:
First try a different USB cable and port.
Click to expand...
Click to collapse
I'm having the exact same issue/error. Already tried new USB ports and cables.

falconfox said:
When I do the command:
it gets to about 50%, then gives a Error message, Any suggestions?
Click to expand...
Click to collapse
confused2much said:
I'm having the exact same issue/error. Already tried new USB ports and cables.
Click to expand...
Click to collapse
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.

jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I'll try this now, thanks for the response!

Honest question: why would you flash a system image and an ota when you could just flash the new system image?

jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.

jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I do not have the text "assert" anywhere in that file....

jase33 said:
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
Click to expand...
Click to collapse
Easier to just flash the new system image that gets you to the same place as the OTA.

jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.

Hi, I have the LNX07M, and I don't find it in the google page. Can you help me? please!

hayzooos said:
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Click to expand...
Click to collapse
I think the only reason to do both steps is to apply the update ASAP. If you are ok waiting, then only flash the new system.img. That's definitely what I always do. I don't mind waiting. I have Google Play Services notifications hidden now anyway, so those update notifications don't show up and bug me.
Thanks for the walk through though, @bitpushr, I'm sure many can make use of it.

confused2much said:
I do not have the text "assert" anywhere in that file....
Click to expand...
Click to collapse
Honestly, you shouldn't edit those files as that can be dangerous, and disabling the filesystem check can be dangerous, and it probably won't work because then the zip would fail signing verification.
If you followed all of the instructions in OP and still get error 7, try, on top of erasing and flashing the stock system.img, also extract and erase then flash boot.img and recovery.img. You will get error 7 if your recovery and kernel (boot.img) aren't stock.

After OTA 3.0 update, TWRP screen shows up after reboot?

So, I just downloaded the OTA 3.0 update and it said to reboot to continue? So, I let it reboot but after rebooting, it loaded up the TWRP screen?
What should I do?

Neo3D said:
So, I just downloaded the OTA 3.0 update and it said to reboot to continue? So, I let it reboot but after rebooting, it loaded up the TWRP screen?
What should I do?
Click to expand...
Click to collapse
Navigate to /data/user/0/com.nvidia.ota/app_download
There should be your downloaded ota zip and install manually through twrp. If that would be native stock recovery the process of installation would be automatic
Izsūtīts no manas Nokia 3310 используя бесплатную xda app

visitor29 said:
Navigate to /data/user/0/com.nvidia.ota/app_download
There should be your downloaded ota zip and install manually through twrp. If that would be native stock recovery the process of installation would be automatic
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
Thank you! But, my machine doesn't have a subfolder called, "0" after /data/user/?

Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/

unvaluablespace said:
Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/
Click to expand...
Click to collapse
(little bit browsing for appropriate folder then walk through factory reset procedure for automatic upgrade ??? !!!!) yes u can do that if you already on 2.1, but if you on 3.0 vulkan without stock recovery? and my way bit faster is (just navigate to appropriate folder for ota) ---- after upgrading 3.0 you can do factory reset through twrp or through system it self.
---------- Post added at 06:26 PM ---------- Previous post was at 06:09 PM ----------
Neo3D said:
Thanks!
I just started looking in all the folders and found the ota.zip file. Mine was located in:
Code:
/data/data/com.nvidia.ota/cache/
However, I have a new problem now. I keep getting this error:
Code:
This package is for "foster" devices; this is a "shieldtablet"
E:Error executing updater library in zip '@/cache/recovery/block.map'
E:Error installing zip file '@/cache/recovery/block.map'
I don't want to do a stock reset because that means I'll have to reinstall Kodi again. I don't want to lose all my preferences and settings in Kodi.
Click to expand...
Click to collapse
start downloading ota....when its over dont restart just press home button on remote and go to es file explore (first enable root exlorer) ---- navigate device/data/data/com.nvida.ota/app_download/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.zip
copy that long name file with ending with .zip to somewhere like download folder ------------reboot to recovery and reflash
p.s. ota location path is from 16gb i have 500gb i have same path, should be on yours tooo. try
p.s. sorry for gave you wrong path first, didnt check personally my self

Thanks, I just had to flash the recovery image again for the update to work.

Nice. glad to hear thats all you needed to do. I had a feeling that might be the case, but i didn't want to suggest that in case it was wrong. lol

Nougat OTA update for Moto X Pure Build (MPH24.49-18_18) required

Hello All,
My phone is currently 6.0 Android n phone model is Moto X Pure (XT1575).
The system version is 24.11.18.clark_retus.retus.en.US
The build number is MPH24.49-18. To be exact is MPH24.49-18_18.
My problem is that when i try to update my phone via sideloading the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip it gives me an error that my build number is MPH24.49-18_18 and my phone should be on MPH24.49-18_16 etc.
I know i can flash the stock Nougat rom but i have too much data n stuff on the phone currently and can't afford to erase it by flashing it. Can someone help me out to update my current build MPH24.49-18_18 to Nougat 7.0 OTA. I don't want to erase my current data and settings.
Thanks in advance.

Are you sure MPH24.49-18_18[/B] is CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml?
You should upgrade to 18-3, 18-4, 18-8 one by one, otherwise you couldn't update this package of 24.231.16 (18-16)
Or you can flash the stock Nougat rom but don't run these commands:
Code:
<step MD5="c9f43220863841663626358351b2f53b" operation="flash" partition="partition" filename="gpt.bin"/>
<step MD5="de64b3b22ee81f5e3d0eea330bf8e216" operation="flash" partition="bootloader" filename="bootloader.img"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
via rsd
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
via fastboot
and don't upgrade via ota in later use

zi_mo said:
Are you sure MPH24.49-18_18[/B] is CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml?
You should upgrade to 18-3, 18-4, 18-8 one by one, otherwise you couldn't update this package of 24.231.16 (18-16)
Or you can flash the stock Nougat rom but don't run these commands:
Code:
<step MD5="c9f43220863841663626358351b2f53b" operation="flash" partition="partition" filename="gpt.bin"/>
<step MD5="de64b3b22ee81f5e3d0eea330bf8e216" operation="flash" partition="bootloader" filename="bootloader.img"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
via rsd
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
via fastboot
and don't upgrade via ota in later use
Click to expand...
Click to collapse
for those steps i would need to downgrade my phone firmware.
is there a way i won't have to downgrade my firmware from MPH24.49-18_18??
i just need to apply OTA without losing data n current settings.

zi_mo said:
Are you sure MPH24.49-18_18[/B] is CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml?
You should upgrade to 18-3, 18-4, 18-8 one by one, otherwise you couldn't update this package of 24.231.16 (18-16)
Or you can flash the stock Nougat rom but don't run these commands:
Code:
<step MD5="c9f43220863841663626358351b2f53b" operation="flash" partition="partition" filename="gpt.bin"/>
<step MD5="de64b3b22ee81f5e3d0eea330bf8e216" operation="flash" partition="bootloader" filename="bootloader.img"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
via rsd
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
via fastboot
and don't upgrade via ota in later use
Click to expand...
Click to collapse
thank you. i misunderstood it at 1st. downloaded all the OTAs in the order you said and now i am on the last one. Downloading Nougat OTA
thank you very much again

Correct, you don't need to do the step with "erase userdata". This way you get to keep your apps.
Add at the end clearing the cache though:
Code:
fastboot erase cache
fastboot reboot

You are on the the "18_18" release? So you used the "official" image from Moto's website that is both incorrectly dated and versioned? Hmmm...
You actually have MPH24.49-18 (no subversion, we don't know why it has a _18 tacked on the file from Moto), it is the original Marshmallow released in December of 2015. To OTA from this, you would need about 5 or 6 steps if they are not offered to you by the Moto update server, first to 18-3, then 18-4, then 18-8, then 18-16, etc.
From this thread:
18 or 18_18 - The initial (shipped) Marshmallow release for Moto X Pure, November 2015 (release via OTA in late-December 2015, incorrectly dated on Moto's official website as 01-SEP-16 in the "official" recovery images section, it is NOT the newest or recommended image to use)
18-3 - February 2016 (released for OTA in mid-March 2016)
18-4 - May 2016 (released for OTA in late-June 2016)
18-8 - September 2016 (released for OTA in early-November 2016)
18-16 - December 2016 (release for OTA in mid-February 2017) *** Not available as a factory image***
Click to expand...
Click to collapse
I would suggest flashing the full factory image of MPH24.49-18-8 or Nougat NPH25.200-22

acejavelin said:
You are on the the "18_18" release? So you used the "official" image from Moto's website that is both incorrectly dated and versioned? Hmmm...
You actually have MPH24.49-18 (no subversion, we don't know why it has a _18 tacked on the file from Moto), it is the original Marshmallow released in December of 2015. To OTA from this, you would need about 5 or 6 steps if they are not offered to you by the Moto update server, first to 18-3, then 18-4, then 18-8, then 18-16, etc.
From this thread:
I would suggest flashing the full factory image of MPH24.49-18-8 or Nougat NPH25.200-22
Click to expand...
Click to collapse
yes i started updating my Base Marshmallow from 18-3 upto 18-16. And BAM i got Nougat notification. downloaded it and installed. the only issue now is battery backup. i might have lost 8-10% battery backup after updating.
i suggest to make a thread for every one with all the OTA Packages so everyone who are not able to update their MXPE would pick up OTA packages from there

thank you everyone. had a hard time finding OTA update packages on internet, but i am glad it was done and all my apps and data is secured. no need to erase the phone and updated officially using the OTA packages to Nougat 7.0!
thanks again everyone!!

acejavelin said:
You are on the the "18_18" release? So you used the "official" image from Moto's website that is both incorrectly dated and versioned? Hmmm...
You actually have MPH24.49-18 (no subversion, we don't know why it has a _18 tacked on the file from Moto), it is the original Marshmallow released in December of 2015. To OTA from this, you would need about 5 or 6 steps if they are not offered to you by the Moto update server, first to 18-3, then 18-4, then 18-8, then 18-16, etc.
From this thread:
I would suggest flashing the full factory image of MPH24.49-18-8 or Nougat NPH25.200-22
Click to expand...
Click to collapse
no i did not use the official image from Moto website. it was updated automatically to that version after i purchased the phone. i had lollipop on it and got updated to MM in early 2016. But i am glad it's on Nougat 7.0

dartoo said:
yes i started updating my Base Marshmallow from 18-3 upto 18-16. And BAM i got Nougat notification. downloaded it and installed. the only issue now is battery backup. i might have lost 8-10% battery backup after updating.
i suggest to make a thread for every one with all the OTA Packages so everyone who are not able to update their MXPE would pick up OTA packages from there
Click to expand...
Click to collapse
Do a factory reset after all the OTAs... It seems cliche but I get you see that battery backup loss become a gain.

acejavelin said:
Do a factory reset after all the OTAs... It seems cliche but I get you see that battery backup loss become a gain.
Click to expand...
Click to collapse
i'll give it a few charge cycles before resetting it. will see if it improves in a week.

Database Users

welcome