Database Users

New Factory Image and Custom Recovery

So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?

geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.

bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr

Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.

geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.

MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.

I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img

Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?

rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.

In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.

mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.

How to update firmware if you've already flashed TWRP

I figured out how to update after flashing twrp. Maybe obvious to some but I've seen questions about it.
The zip in the "Convert CA to WW" thread has the stock rom in a zip file. Open it and inside is a recovery.img file in it, extract it to your adb folder on your PC.
Download the firmware update from ASUS official site and save to the root of your sd card or internal storage (it will recognize both.)
Reboot into fastboot on your device.
fastboot flash recovery recovery.img
When that finishes reboot and your phone should find the update and ask if you want to install. Do so. You may need to power cycle first.
When you're done you can reflash TWRP.
Once you have TWRP you can flash Magisk or SuperSU as you see fit.
It's painless.

An old post from you, but thank you. This was really easy. I've spent 2 days trying to figure out how to upgrade without restore stock rom, boot etc. and lose all data. I was about to give up when I saw this post, I didn't expect it to work - to easy. But I could give it a try.
This was painless.
Then it took me 3 hours to figure out how to reinstall twrp again, it wasn't just to flash and reboot I had to boot directly into recovery after flash. But that is another story.

Thanks, you just saved me some time!

Kasdarack said:
I figured out how to update after flashing twrp. Maybe obvious to some but I've seen questions about it.
The zip in the "Convert CA to WW" thread has the stock rom in a zip file. Open it and inside is a recovery.img file in it, extract it to your adb folder on your PC.
Download the firmware update from ASUS official site and save to the root of your sd card or internal storage (it will recognize both.)
Reboot into fastboot on your device.
fastboot flash recovery recovery.img
When that finishes reboot and your phone should find the update and ask if you want to install. Do so. You may need to power cycle first.
When you're done you can reflash TWRP.
Once you have TWRP you can flash Magisk or SuperSU as you see fit.
It's painless.
Click to expand...
Click to collapse
Will this recovery work for upgrading nougat to oreo?

Em Kay said:
Will this recovery work for upgrading nougat to oreo?
Click to expand...
Click to collapse
You need to upgrade to latest N - ...14.2020.1712.85, once you do that you should get Oreo as FOTA after reboot

DanFreed said:
You need to upgrade to latest N - ...14.2020.1712.85, once you do that you should get Oreo as FOTA after reboot
Click to expand...
Click to collapse
Thanks, man.
Can I manually update with the recovery by downloading the rom?
I think, the FOTA won't arrive as I've rooted my phone.

Em Kay said:
Thanks, man.
Can I manually update with the recovery by downloading the rom?
I think, the FOTA won't arrive as I've rooted my phone.
Click to expand...
Click to collapse
When you flash stock recovery and update you unroot, so you will get FOTA. Just update to Oreo and then flash twrp and Magisk (or whatever you use) again.
I am rooted and updated to Oreo then chose updates involving battery improvement and/or system stability (downloaded to external sd), after installed the last update I flashed twrp and rooted again.
You need to flash stock recovery before update. The phone will find the updated with custom recovery but update will fail.
The site I downloaded stock recovery from is down so you have to search for it, or download RAW stock rom and extract the recovery from it

DanFreed said:
You need to flash stock recovery before update. The phone will find the updated with custom recovery but update will fail.
The site I downloaded stock recovery from is down so you have to search for it, or download RAW stock rom and extract the recovery from it
Click to expand...
Click to collapse
Anyone know where I can get stock recovery or how to extract from stock image from the ASUS site?

derbend said:
Anyone know where I can get stock recovery or how to extract from stock image from the ASUS site?
Click to expand...
Click to collapse
Seems like Mega is up again. You should find stock recovery here
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB

DanFreed said:
Seems like Mega is up again. You should find stock recovery here
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB
Click to expand...
Click to collapse
Thanks! I ended up having to use the 11.41.87.2 recovery in order to flash a Nougat update - it wouldn't work with the older recoveries.

Do I have to flash no verity?

I really just want to root stock. I have the Boost Mobile Perry.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).

I really don't care about encryption.

guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.

Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.

guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.

Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img

i have the moto e4 mkt which no verity version do i have to flash ?

Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.

madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome

Problem flashing stock image

I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?

You already took the November OTA or are you still on October?

ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November

Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.

I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.

Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks

Yes.... fastboot flash boot boot.img

ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?

I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.

ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?

TWRP doesn't work with Q. Just use stock recovery to sideload.

ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.

The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk

Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?

How to update to 11.0.8.8IN11AA on pre rooted device

Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.

paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.

MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?

Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.

MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.

paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.

Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.

Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...

datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?

Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches

What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.

It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.

Could someone post boot img I can't find this 11.8.8 to download.
Thanks.

Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.

If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.

h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541