Database Info

Trouble relocking

Maybe someone can help with the problem I am running into.
I rooted the Xoom after the 3.01 update using the one click method and had no trouble flashing BRD's kernals. After thr news of the 3.1 update. I ran the SBF files to return everything back to bone stock. I had no problem installing the OTA update.
Here is where I ran inro the problems. I tried to play a video thru Google Video app and received error 49. My device was SBF'd and unrooted so wtf could the problem be? I just installed the OTA so why won't my video app work?
I started tinkering and thought maybe. the sbf didn't relock my Xoom so I ran the fastboot commands to relock and I got the dreaded LNX 0x0004 error at the boot screen. After about an hour of freaking out I managed to get my Xoom to fastboot protocol support and unlocked and it rebooted and works properly but I still can't watch videos and I now also have the movie studio app back when it had disappeared after the OTA.
Baseband Version
N_02.0F.00R
Kernal
2.6.36.3-gc2bee64
android [email protected] #1
Build
HMJ37
Anyone can help?

Booted Recovery and got this...
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/misc
(No such file or directory)
E:failed to mount /cache (No such file or directory)
E:can't mount /cache/recovery/command
-- Wiping data...
Performing BP clear. . .
E:finished indispensable
Epen mdm-ctrl OK
E: Finished boot BP to normal mode
E:from flash to normal mode
Epen dev
E:engine init finished
E:Successfully wrote 13 bytes
E:Transfered 13 byte(s) CMD opcode = 0x0012 to aux engine succeeded
E:write finished
E:Attempted to read 12 bytes and read 12 bytes
E:Successfully read 12 bytes
BP clear complete successfully.
Formatting /data. . .

Did you try this? http://www.xoomforums.com/forum/mot...s/2788-how-restore-3g-4g-system-boot-img.html
You will be stock and locked on 3.0.1. Then wait for ota.

Brenardo said:
Maybe someone can help with the problem I am running into.
I rooted the Xoom after the 3.01 update using the one click method and had no trouble flashing BRD's kernals. After thr news of the 3.1 update. I ran the SBF files to return everything back to bone stock. I had no problem installing the OTA update.
Here is where I ran inro the problems. I tried to play a video thru Google Video app and received error 49. My device was SBF'd and unrooted so wtf could the problem be? I just installed the OTA so why won't my video app work?
I started tinkering and thought maybe. the sbf didn't relock my Xoom so I ran the fastboot commands to relock and I got the dreaded LNX 0x0004 error at the boot screen. After about an hour of freaking out I managed to get my Xoom to fastboot protocol support and unlocked and it rebooted and works properly but I still can't watch videos and I now also have the movie studio app back when it had disappeared after the OTA.
Baseband Version
N_02.0F.00R
Kernal
2.6.36.3-gc2bee64
android [email protected] #1
Build
HMJ37
Anyone can help?
Click to expand...
Click to collapse
Suggest you use link above to flash all stock images again, and fastboot oem lock it and apply update then see if it works.
Good luck!

[Q] Help...Another spinning wheel

Hi Folks,
Noob here and I think I'm about to brick my tab...appreciate the help...
My previously runs on JB 4.2.1 and bootloader 10.6.1.14.8 and it is stuck at spinning wheel after flashing with TF700t to CleanROM 3.4.7 Inheritance DEODEX v2 with TWRP 2.4.40
The installation went well without any problems but after cleaning cache and dalvik cache and rebooting it... it is stuck at spinning wheel screen and I don't know what to do.
I have tried reinstalling several times through TWRP but with same result.
I tried to look at the partitions.. Looks good to me.. but what do you think?
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
[email protected]:/ # hexdump -C -n 512 /dev/block/mmcblk0p3
hexdump -C -n 512 /dev/block/mmcblk0p3
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000200
I plug the tab usb to my laptop and laptop no longer detects it as a media/storage.
I tried fastboot but fastboot doesn't seem to be able to detect it
I am not sure what to do next... can someone please help me?
Thank you...:crying:

You are on the JB 4.2 bootloader and you are trying to run an JB 4.1 based rom on it, plus - and more importantly - you have an outdated recovery installed with that bootloader.
Go to this thread: http://forum.xda-developers.com/showthread.php?t=2425383
CROMi-X is the successor to CROMI. Go to the OP, follow the instructions in Scenario Two, flashing the latest bootloader/recovery package, TO THE LETTER, most importantly to boot to system after you flashed that package.
Boot back into TWRP (which should be v2.6.1 at this point) and before you flash CROMi-X 5.0.2 do a Factory Reset in TWRP.
That should get you going...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

ddguy said:
My previously runs on JB 4.2.1 and bootloader 10.6.1.14.8 and it is stuck at spinning wheel after flashing with TF700t to CleanROM 3.4.7 Inheritance DEODEX v2 with TWRP 2.4.40
Click to expand...
Click to collapse
This is a downgrade from Android 4.2 to 4.1 - in such cases you must delete all your data via recovery because Android downgrades are not supported. Or, like berndblb already explained, better install the latest version of CROMI-X instead of that outdated 3.4.7.

berndblb said:
You are on the JB 4.2 bootloader and you are trying to run an JB 4.1 based rom on it, plus - and more importantly - you have an outdated recovery installed with that bootloader.
Go to this thread: http://forum.xda-developers.com/showthread.php?t=2425383
CROMi-X is the successor to CROMI. Go to the OP, follow the instructions in Scenario Two, flashing the latest bootloader/recovery package, TO THE LETTER, most importantly to boot to system after you flashed that package.
Boot back into TWRP (which should be v2.6.1 at this point) and before you flash CROMi-X 5.0.2 do a Factory Reset in TWRP.
That should get you going...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the respond. Truly appreciate it.
Please don't mind me if I am asking the wrong questions but I'm just trying real hard not to permanently mess this up.
Starting with flashing bootloader and custom recovery
What is the best way to flash bootloader? I found this article http://androidroot.mobi/pages/tegra3-guide-nvflash/
I tried to see my device adb shell but could not detect
however I am able to in Fastboot
>fastboot devices
015d2bbcc00c2007 fastboot
Also I do not see the USB icon in the tab on fastboot. Is that a concern?
Thanks again...

_that said:
This is a downgrade from Android 4.2 to 4.1 - in such cases you must delete all your data via recovery because Android downgrades are not supported. Or, like berndblb already explained, better install the latest version of CROMI-X instead of that outdated 3.4.7.
Click to expand...
Click to collapse
Thanks!
Is that by using TWRP (I'm on 2.4.40)-> Wipe-> Factory Reset? or Format Data?
Or I should update the bootloader and TWRP first?
Thanks

ddguy said:
Thanks!
Is that by using TWRP (I'm on 2.4.40)-> Wipe-> Factory Reset? or Format Data?
Or I should update the bootloader and TWRP first?
Click to expand...
Click to collapse
Why do you want to install an outdated version of CROMI?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

_that said:
Why do you want to install an outdated version of CROMI?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Sorry I was coming from your suggestion to delete all the data before I install with an updated version.
Or should I just follow on what berndblb mentioned?
Thanks

ddguy said:
Sorry I was coming from your suggestion to delete all the data before I install with an updated version.
Or should I just follow on what berndblb mentioned?
Thanks
Click to expand...
Click to collapse
Hi All,
I'm most glad to share that this problem is solved. Many thanks for the guidance. I like to share what I did in the process to repair but credit goes to those that has spent countless hours in the development.
1) I downloaded the 10.6.1.14.10 bootloader with TWRP 2.6.1.0
2) Copied that to a microSD (no need to unzip) and insert into the tab
3) Boot into recovery which I have TWRP 2.4.40 installed
4) Click Install and flashing will begin.
5) Take a while to complete but once done, tab will reboot
6) Go to recovery mode again and you will see the updated bootloader
7) Go into recovery mode and TWRP shows 2.6.1
8) Perform a factory reset but I added a step to perform a backup and reboot
9) Copy Cromi-X into microSD without unpacking the zip.
10)boot into recovery mode with microSD inserted
11) Install!
12) Problem fixed and proceed to jump with joy
Thank you berndblb, _that and sbdbags

[Q] How can I update my rooted Moto G to 4.4.4 ?

Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !

JayZeus said:
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
Click to expand...
Click to collapse
If you made some modification to the 4.4.2 rom you'll have to restore the stock before upgrading to 4.4.4.
Bootloader can be unlocked, Recovery can be custom but any mod/root to the room will cause the error.
To restore to stock follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219

Thanks a lot, it worked!
By the way is the part where you erase you data mandatory ? In case I have to do this again.

Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app

mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ! Thank you.

mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) [emoji481]
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This way I'll keep my installed applications?
Thanks.

4.4.2 > 4.4.4. just rolled out in UK (o2 moto g).
right after i get my phone rooted and started setting it up...
Thanks for this thread.. what's the minimum we have to restore, basically the system partition so it's unrooted?
If we have stock 4.4.2 (rooted) can we flash JUST these 3 files?
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
and skip the rest? I want to save redo-ing as much as possible..

I got the 4.4.4 OTA today (210.12.40.en.GB) and I have unlocked bootloader + Philz recovery - Philz worked fine for the 4.4.2 OTA update, but when I downloaded the 4.4.4 OTA and rebooted Philz would abort with "a status 7" mismatch error and then the phone would boot to Android, then 20 seconds later shutdown and reboot to Philz again, continuously. After some playing, I did the following:
1. Flashed stock recovery (taken from Mototool AIO's 4.4.2 stock.img) from fastboot - re-downloaded the 4.4.4 OTA but that failed with "Error!"
2. Flashed stock kernel (I was running faux123) - same issue, 4.4.4 OTA failed still.
3. Flashed latest Philz recovery again (philz_touch_6.50.6-falcon.zip) then
4. Flashed stock 4.4.2 GB kernel (to match my OTA version) - kernel from here http://forum.xda-developers.com/showthread.php?t=2649763 - success... OTA downloaded and this time installed.
SO, conclusion is you don't need stock recovery to flash OTA, BUT you do need the correct kernel for your update and having a custom kernel causes the mismatch error.
Hope this helps someone!

So the UPDATE-SuperSU-v1.91.zip in MotoG-Tools.zip still works to root 4.4.4 right?
i found it here
http://www.swedroid.se/forum/showthread.php?t=106595
and this is what i used for 4.4.2
Most of the old guides around no longer worked in 4.4.2, i dunno if they closed any other holes in 4.4.4?
edit: version typo sorry

just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning

JayZeus said:
I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error.
Click to expand...
Click to collapse
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.

agoodhi said:
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
Click to expand...
Click to collapse
I figured it out... I simply did a delete cache from CWM recovery and now no more boot loop.

fatechand said:
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
Click to expand...
Click to collapse
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729

Smiff2 said:
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Click to expand...
Click to collapse
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.

fatechand said:
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
Click to expand...
Click to collapse
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
---------- Post added at 06:32 AM ---------- Previous post was at 06:14 AM ----------
agoodhi said:
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
Click to expand...
Click to collapse
CWM message:
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
assert failed: getprop("ro.product.device) == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma"
E: Error in /cache/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
(Status 7)
Installation aborted.
Rebooting...

fatechand said he had CWM 6047 installed and OTA update was ok. he just had to re-root? perhaps difference between 6046 and 6047 CWM, or some difference in way you rooted?
I have same recovery, rooted, 4.4.2, so should work... ?

1.4 update for shield tabletk1,

New update arrive to me, unfortunately i can't flash cause my system partition was modified, anybody tried and flashed it for those on stock?
Edit: a little dismayed, july 1 security patch? Its almost the middle of September now

Same situation here. Can flash the ota.
I rooted and changed to twrp.
I think it's because of the recovery. Don't you?
Is there a way to flash back to the stock recovery without a complete flash to stock?

zagzag99 said:
Same situation here. Can flash the ota.
I rooted and changed to twrp.
I think it's because of the recovery. Don't you?
Is there a way to flash back to the stock recovery without a complete flash to stock?
Click to expand...
Click to collapse
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only

thirdzcee said:
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
Click to expand...
Click to collapse
I had OTAs until 1.3
Then flashed TWRP
Now it fails claiming of fingerprints mismatch.
It expects sub reversion 726.6502 and somehow I'm on 700.6952
Is that how it fails at your end?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Is there a easy twrp flashable stock?

zagzag99 said:
Is there a easy twrp flashable stock?
Click to expand...
Click to collapse
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.

zagzag99 said:
I had OTAs until 1.3
Then flashed TWRP
Now it fails claiming of fingerprints mismatch.
It expects sub reversion 726.6502 and somehow I'm on 700.6952
Is that how it fails at your end?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Is there a easy twrp flashable stock?
Click to expand...
Click to collapse
Mine is a little different
Verifying update package...
I:comment is 1547 bytes; signature 1529 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
sysutil: mmapped 4 ranges
Source: nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K/40827_726.6502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K/49349_766.5399:user/release-keys
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" has unexpected contents.
"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I:Saving locale "en_US"

thirdzcee said:
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
Click to expand...
Click to collapse
I suspect it has to do with the fact that systemless root modifies the bootloader and the delta OTA checks that. Try uninstalling root from SuperSU (it does say uninstallation is required for OTA to proceed) and see if OTA proceeds.

Isira said:
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
Click to expand...
Click to collapse
Thanks, i just did the full ota flash... Waiting for the art pre compile of all my apps now.

Isira said:
I suspect it has to do with the fact that systemless root modifies the bootloader and the delta OTA checks that. Try uninstalling root from SuperSU (it does say uninstallation is required for OTA to proceed) and see if OTA proceeds.
Click to expand...
Click to collapse
Thank you, uninstalled magisk OTA went fine for me, now ill have to wait to go back home to root again, systemlessly

where is the OTA file located? I tried data/data/com.nvidia.ota/files/rom but it's not there.
*edit nvm, found it, under app_download folder and not the files/rom folder

Full OTA k1 1.4 for recovery
https://mega.nz/#!Q1VUVBrR!v40m3Q4s-rqcfCYQmEqIw0MzEJTI897Sd7ZousmhcKU

Hi folks, I'm having an issue with the update; I have rooted my Shield K1, have attempted to update to 1.4 using FlashFire app on Stock recovery, I have a 64GB Samsung EVO SD card and my storage was on adoptive. The update/flash started fine, but on reboot the error message "Unfortunately, Setup Wizard has stopped" comes up, I click OK and nothing happens. Does anyone know how I can rectify this issue please?

I found that by downloading the full image (which you can do via the built in updater on the tablet via Settings), I could use Flashfire to install and root it, no data lost. Didn't work with the smaller OTA file, but the full file worked flawless.

Thanks, but I can't get past the error message. I have seen another way to flash the update and have found out I did one of the steps wrong, if I can get it working again I'll post.

chewdiggy said:
Thanks, but I can't get past the error message. I have seen another way to flash the update and have found out I did one of the steps wrong, if I can get it working again I'll post.
Click to expand...
Click to collapse
You tried wiping cache?

Isira said:
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
Click to expand...
Click to collapse
Hey mate what is the best version of supersu to flash?
Sent from my SHIELD Tablet K1 using Tapatalk

thirdzcee said:
You tried wiping cache?
Click to expand...
Click to collapse
I have now wiped the cache and it is back to defaults. Thank you thirdzcee. Will not make that mistake again, I assure you.

robgee789 said:
Hey mate what is the best version of supersu to flash?
Click to expand...
Click to collapse
Use Flashfire, it'll do it all for you. (although it does appears to come with 2.76 instead of 2.78 of SuperSU, but updates itself anyway).

I have been having issues on my k1 since the 1.4 firmware I tried doing the toggle able system-less root and xposed but i lose touch and the tablet just doesn't work and i end up having to reinstall the 1.4 update at this point i'm sitting at fresh wiped tablet i dont yet.
I have narrowed my issues down to bad SD card as adopted storage.

i just downloaded the update by accident but i dont want to flash it because i have root and twrp so i moved the ota and restarted my tablet, but the notification is still there, any ideas on how to remove the notification?

UPDATE TO 7.0 Nougat XT1650-03 Retus US Version

After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it

This is really sad. They said it was going to be this week and a global roll out.
Nothing!
I can't wait until Samsung release the S8E.. Giving this phone to my 8 years old niece to have!

can u make some order here ?
what is your model ?
if u flashed 24.246-45 then u said it needs to be 40
then did u flash the 40 over 45 ?
thanks
hassanman1997 said:
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware,
Click to expand...
Click to collapse

This is really helpful. I hit the same snag when I tried to upgrade from -17 firmware.
Any chance you could upload the Canadian Rogers firmware (-45) to Mega? It's so painful waiting for 9 hours for it to fail a few minutes from the end.

Yeah I can try, but I won't be home until night, the only pain was waiting 9 hours, and the firmware is -45, I accidently wrote -40 , I don't think there is any firmware with-40

I tried all the above. Still fails for me.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
I think because the file has been replaced with a v2 so it's failing verification

I'm uploading the Rogers .45 firmware to mega right now. I'll update this post once its done uploading.
Link: https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Downloaded straight from FileFactory and uploaded directly to Mega

Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome

svetius said:
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
Click to expand...
Click to collapse
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?

Prfndhatrdofman said:
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Click to expand...
Click to collapse
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.

svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
You got further than me. ADB Sideload wouldnt even look at the Nougat OTA zip. tried multiple ADB versions too

svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
Sideload was successful for me, but still completely in a bootloop as well..

for me it worked fine with ADB sideload.

my bootloader is unlocked, i tried locking it back to get official OTA but failed to lock it again.
I tried every method that was mentioned but failed over and over
so here is what I did:
1) removed all the personal files from phone (pictures, videos, texts etc) so i don't lose em
2) flashed the rogers [XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml] firmware by using mfastboot, make sure you grab the mfastbootv2, you can google and download it, use mfastboot and flash the firmware by command lines
3)after flashing, rebooted, set up the device and skipping a few steps to get into homescreen, and then powered off the phone.
4)downloaded Blur_Version.24.21.46.griffin.retail.en.US.zip and placed it in the adb folder, make sure you download the latest adb tools, you can google and find them easily too
5) extract the adb folder and place the Blur_Version.24.21.46.griffin.retail.en.US.zip in side that folder
6) reboot the phone and press volume to navigate to recovery, you should boot into stock recovery as you flashed stock firmware
7) hold power button and press volume up and youll see the menu, select update by ota and connect to the phone
8) open command line in the adb tools and use command to flash ota via adb
9) mine failed at 95% because of system image error, so instead of rebooting it, i used the command again and flashed the ota via adb, it failed again, however when i rebooted i was presented by the new red moto boot animation, there i knew it was updated to android N

*Delete*

hassanman1997 said:
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
Click to expand...
Click to collapse
OK, so i got it working. But there were some difficulties.
I was on 24.246-45 already, but i installed TWRP and a custom kernel. I reflashed the recovery and boot from the BELL 24.246.45 firmware, and proceeded sideloading the update. It errored out, saying system was mounted r/w once (after I installed TWRP, but I never altered it beyond that).
So i flashed the system chunks from the firmware ( "mfastboot flash system system.img_sparsechunk.0" , "mfastboot flash system system.img_sparsechunk.1" etc.), then i retried the sideload, and it worked. The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.

gomisensei said:
... The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
Click to expand...
Click to collapse
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...

enetec said:
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
Click to expand...
Click to collapse
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...

gomisensei said:
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
Click to expand...
Click to collapse
:laugh:

Does that actually work for other software channels as well?
I'm from india, my software chanel is retin (retail India) can I still flash the one that came for retus?
Sent from my Moto Z using XDA Labs