Database Users

[Q] Failure to update 4.2.2

after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks

williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
you probably need stock recovery to complete the update... I would just wait for someone to root the update and then flash it that way

williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.

phonic said:
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
Click to expand...
Click to collapse
is this problem caused by flashed kernel ??

williamlaw said:
is this problem caused by flashed kernel ??
Click to expand...
Click to collapse
Did you not bother to read anything I wrote?

I had the same problem. If you have a TWRP backup from a previous android version that allowed the ota to work just flash that and you'll still receive the ota for 4.2.2
Sent from my Nexus 7 using Tapatalk HD

This happened to me too, though I have the wifi-only version. So it's not just the radio.

I got the same problem with my Wifi version. Is there any fix yet? I only rooted the device but the rest is still stock. How come the update failed?

the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?

rexxxxx said:
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
Click to expand...
Click to collapse
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.

spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
finally flashed back to stock 4.2.1 then OTA update 4.2.2

spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
how ? I indeed have the mount stick installed for the OTG cable !

rexxxxx said:
how ? I indeed have the mount stick installed for the OTG cable !
Click to expand...
Click to collapse
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer

I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
So, is there any way of doing this without doing a wipe ? Or losing any of your data ?
What about putting the update, downloaded from google, on a USB stick and booting into twrp then flashing from there ?
I don't mind losing root, although I have rootkeeper installed, and I don't mind losing custom recovery, all of this can be fixed.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
What I don't want to do is lose my data. I have plenty of full twrp backups done, but then these are 4.2.1 backups. Backing up my apps isn't really feasible at the moment because of their sheer size. Horn, NOVA 3, the GTA games, bards tale, all gigs and gigs of data. Infact, I only have 1 gig left on a 32Gb N7, and I just don't have anywhere left to put a full backup of apps on to. I also don't want to download them all again, NOVA 3, for example, took me 6 hours to download on wi-fi.
I have read a lot of advice and help on here, plenty of googling which simply sends you back here anyway, and most advice centers around losing your data in some way. So, any help without losing data would be most appreciated,

spiou said:
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
Click to expand...
Click to collapse
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app

After reading many threads and articles, I finally upgraded to 4.2.2 with stock recovery. Your mileage may vary.
Based on the discussions on http://forum.xda-developers.com/showthread.php?t=2148456, the failure may be caused by an app you installed
that corrupted some system files. Therefore, you have to flash 4.2.1 stock system and boot images back. The nice thing is your data and settings remain intact.
Although you lost root, it can be easily re-rooted using nexus root toolkit.
Now you're back to 4.2.1 which is allowed to upgrade, use OTA RootKeeper to keep su and then upgrade thru OTA. If you can not longer get OTA, you can clean data/stop/start Google Framework service, Google play service, and Google play store, and then re-check update. The last tip I read it somewhere but I forgot where I read it. Sorry.
Good luck. :laugh:
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse

JohnRM said:
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
Click to expand...
Click to collapse
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....

rexxxxx said:
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You must clear the data of the Google framework (in the list of apps) and reboot immediately the tablet. Then the update will be proposed again.
One more thing : when you replace the file, check that the permissions are identical.

khaytsus said:
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
Click to expand...
Click to collapse
Exactly. I don't understand why we need to see posts like that over and over and over again. Hell, the OTA update will even tell the user what failed, and yet people still complain and ask what's wrong.
Also, while in most cases a custom recovery is OK (though the update will overwrite it), with the N73G unit, you need to use the stock recovery, otherwise it will fail without warning ahead of time.

spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
Can you elaborate? E.g., where do you get the original debuggerd from, how do you replace it (adb push?), etc.

[Q] Fail Updating to 4.2.2

Unlocked Bootloader.
CWM.
Root.
Fail in updating, with message something like assert fail apply_update_check status 7.
Revert to Stock Recovery and Unroot (bootloader is still unlock), update again, result in error with the android robot and red exclamation.
Happen to my Nexus 7 and Galaxy Nexus as well (same unlock bootloader cwm root, same revert method, same error).
Has anyone face this and any solution to make OTA works?

Get back to stock, then try again
Sent from my Nexus 4 using xda premium

Had the same problem. This will answer all your questions
http://forum.xda-developers.com/showthread.php?t=2145848

thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.

raijinshou said:
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
Click to expand...
Click to collapse
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.

Guzanni said:
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Click to expand...
Click to collapse
boot.img and system.img can be founded in the STOCK ROM, here is the link for STOCK 4.2.1 for Nexus 4:
https://docs.google.com/open?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU
(Source: http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ )
Extract the file, you can find boot.img and system.img inside it.
To flash these 2 files, since I am not familiar with fastboot, I am using Nexus 4 Toolkit to help with it.
You can download Nexus 4 Toolkit: http://goo.im/devs/mskip/toolkit/google_nexus4/Google_Nexus_4_ToolKit_v1.3.0.exe
(Source: http://forum.xda-developers.com/showthread.php?t=1995688 )
Copy boot.img and system.img to Nexus 4 Toolkit folder of "put_img_files_to_flash_here"
then using "11. Boot or Flash .img Files to Device option", flash the file to the correct partition
(when flashing boot.img, to boot partition | when flashing system.img, to system partition).

Rooted 5.0.... how to upgrade to 5.1.1

Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

WiFivomFranMan said:
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I'm on the same boat, but I think our answer will come soon. Today I found out that WugFresh will be updating the NRT Toolkit to support the Nexus Player. See this post.

Why not just download the image and flash it? Plenty of guides on how to do this

lafester said:
Why not just download the image and flash it? Plenty of guides on how to do this
Click to expand...
Click to collapse
I didn't know that there were difficulties with 5.1.1. I used Wugfresh's tool to install 5.1.1 with the "no wipe" option and I had 5.1.1 just fine - but can't figure out how to get root back!! And I need root to expand the storage!! Right now I have a fresh, clean, 5.1.1 install on my NP.
I tried Wugfresh's tool, I sure wish it told me that it didn't work with the firmware that it had already detected!!
I also tried the Chainfire root.img that I used back on 5.0 and it seems to work until I tell SuperSU to update the binaries. At that point it basically times out and asks me to reboot.
What next?! Wait for Wugfresh? Is there another way to root?

I flashed the cm recovery from dhacker and used it to flash the newest beta of supersu. After that the app didn't show up until I installed it from the store but now it works fine

I just want to upgrade it without losing all my stuff (Saved games for my NES ROM, etc...)

Why don't you locate the save data in es file explorer and copy it to the cloud. Reimage nexus player and set up es file explorer, cloud and copy the saved data back to where you stored it.

would anyone be so kind to point me to one of the guides on how to use factory image/OTA to update from 5.0 rooted to 5.1.1? I don't care about keeping my settings, and I don't care about root. just want the latest and greatest.
thanks in advance

The Nexus Player is a Nexus device, and you can always upgrade to the latest version by using the factory images found here: https://developers.google.com/android/nexus/images. The procedure to flash a factory image on any Nexus device has not changed since the Nexus One was released, so you can look at any of the guides for Nexus devices.
Essentially it boils down to this: The factory image contains a few files in an archive format. There are a few images within that you need: bootloader (I can't remember what the name of the file is but it's something like xxxxbootloaderxxx.img), system.img, boot.img, recovery.img). Extract those images from within the archive and flash them. You do this by booting into the bootloader, opening a command prompt in the same folder that you downloaded the image files) on your PC and type the following commands:
fastboot flash bootloader bootloader.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
If you also want to start fresh and wipe all your data, execute the following command: fastboot format userdata
Then execute: fastboot reboot
Done.
Notes:
1) You need to extract these files in the same directory as where you downloaded the images before proceeding.
2) if you are using Windows, you need to install the the driver (found here: http://developer.android.com/sdk/win-usb.html)
3) The procedure above assumes your bootloader is unlocked. If not, you will need to unlock it (using: fastboot oem unlock) and it will wipe all your data.

efrant said:
1) There is currently no way to get root on 5.1.1 without modifying the kernel (so that it boots SELinux in permissive mode).
Click to expand...
Click to collapse
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053

etnpnys said:
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
Click to expand...
Click to collapse
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.

efrant said:
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
Click to expand...
Click to collapse
Ok - whew! I know that I went through the process but I couldn't be 100% sure because I have tried so many things to get expanded storage working to no avail that I've kinda given up for the time being...

It's a nexus - use custom recovery to flash supersu and your rooted.... Done

Toneman07 said:
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Click to expand...
Click to collapse
Not necessarily... You still need a modified boot.img to get the whole thing working...

etnpnys said:
Not necessarily... You still need a modified boot.img to get the whole thing working...
Click to expand...
Click to collapse
Thats interesting considering both my nexus phone and samsung tablet are running stock kernels (boot.img) and rooted just fine using the above method.

Latest OTA update - Help needed

Hi all,
I have a bit of an issue with the latest OTA update currently being pushed out and looking for help how best to proceed.
I have unlocked and rooted the phone previously and recovery is TWRP. My phone is encrypted.
When I accepted the updated the phone rebooted and showed the TWRP splash screen which flashes on and off endlessly. If I turn the phone off and on again it restarts fine but after a few seconds the update process starts again. I am currently stuck in this loop.
Any advice as to how I can get out of this without wiping my phone?
I am wondering if I could flash the standard recovery to remove TWRP if this would work. Could it and if so, where can i get the standard recovery image.
Thanks and sorry of this is already covered, I searched but couldn't find it.

For XT1575.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

If you want to update be on stock rom i.e. unrooted and no xposed,nothing added or removed from system and also flash stock recovery.
After successful update flash twrp.

So, if I want to install the lastest update it's enough to unroot, remove xposed and flash stock recovery? Or it's better to flash full stock through fastboot?

So I managed to find a link to the full image for my device (XT1572 so the above link wouldn't work to the best of my knowledge - but thanks anyway @Hitti2)
I flashed the standard recovery and rebooted which stopped the endless loop. The update still fails to install but I can live with that for now.
I'll investigate further what I need to do to get the update to take properly but for now I have a functioning phone which is a good start to the day.
Thanks all.
Sent from my XT1572 using Tapatalk

Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]

There is a whole thread dedicated to this update in general.

lafester said:
There is a whole thread dedicated to this update in general.
Click to expand...
Click to collapse
Maybe there is but as I stated in the OP, I couldn't find the right information at the time of posting. Maybe helpful would be to also link the thread as it may help others.

@lafester could you link thread please.
Sent from my XT1572 using Tapatalk

Boot image?
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
user7743 said:
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
Click to expand...
Click to collapse

nathlynn22 said:
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
This one possibly?
http://forum.xda-developers.com/moto-x-style/general/xt1575-february-2016-security-update-t3323126
---------- Post added at 10:42 PM ---------- Previous post was at 09:50 PM ----------
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.

chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
evandena said:
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
Click to expand...
Click to collapse
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software

Thanks so much for trying to help. I went ahead and flashed the boot and recovery files for my model. I did the Boot image first, no luck. then i did the recovery, and this time andy thought a bit longer before giving me the Error! message. And then instead of my phone doing an autoreboot, it was stuck on the dead Andy and I needed to do hold down the power button to get it to shut down.
Anyone have any additional thoughts?
user7743 said:
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Click to expand...
Click to collapse

I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.

This phone has never been able to take OTAs for some reason. I wish I understood why. I tried to leave the thing stock to keep things simple, but it wasn't to be... anyway...
Thanks for the advice. Any idea where to get a download of the .zip files (is it really more than one zip file, or was that a typo)? I tried searching, but can't seem to find the right things to search for.
Also, once i have the zip file(s):
1) Do I just install it via TWRP like any other zip file?
2) to get rid of the OTA prompt, do i wipe the cache and reboot before or after i install the update via the zip?
Many thanks!
InFamousD147 said:
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
Click to expand...
Click to collapse

I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.

Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse

chuck-fu said:
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Click to expand...
Click to collapse
I have the 1572 RETEU, but you can find the stock firmware here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If it's like the stock firmware that I have for the 1572 it should have all the img files and the system chunks. You just need to flash all the chunks like this:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
This has to be done because Marshmallow doesn't allow any modification in the system or the boot image, and will not proceed with the OTA if the ROM is not full stock.
EDIT: You will not loose any data, but any modification to the system partition will be undone.

Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?

chuck-fu said:
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
Click to expand...
Click to collapse
I just let the normal OTA install after flashing system, boot and recovery, without wiping any partition. Maybe you can try a flash all the zip to make sure it's full stock and see if the OTA install. Just make a backup before in case nothing change.

Help to get N preview 3 installed from a custom rom with no pc just TWrp

Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk

iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.

messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.

superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?

flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!

I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk

So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app

GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.

x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?

I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...