Database Users

[GUIDE] Sideload NOF27B/C on Stock, TWRP, Custom Kernel, Mods, Root - Updated 3/6/17

Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.

This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed

bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...

Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse

I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.

Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?

can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.

thank you! worked great!

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:

I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay

rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?

spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.

spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.

Is something up with the OP or is it just my XDA app causing it to show like this..

aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.

rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.

spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update

Where can I find my stock boot.img? (I'm running stock rom on gt-i9515)

Hello,
Where can I find this file?
My main goal is to install magisk on an un-rooted galaxy s4 gt-i9515 device, and one of the steps is patching the boot.img.
Where can I find this file? Should I copy it and patch the copied file? Or should I patch the original one (I have full TWRP backup from before root & system files editing)?
edit:
I've seen this on youtube and it seems too easy, is this a legit way to get your boot.img? https://www.youtube.com/watch?v=i-Cyxemi25g

Magisk the patching itself.

Pwnycorn said:
Magisk the patching itself.
Click to expand...
Click to collapse
That's not it. I told I am trying to do it on an UN-ROOTED device. Magisk asks me to choose my boot.img file so it can patch it.
In order to do that, I need to get that boot.img file first...

FurySh0ck said:
That's not it. I told I am trying to do it on an UN-ROOTED device. Magisk asks me to choose my boot.img file so it can patch it.
In order to do that, I need to get that boot.img file first...
Click to expand...
Click to collapse
Dude, Magisk has to be flashed from recovery. I don't know What you are doing right now, but I'm pretty sure you're overcomplicating things.

Pwnycorn said:
Dude, Magisk has to be flashed from recovery. I don't know What you are doing right now, but I'm pretty sure you're overcomplicating things.
Click to expand...
Click to collapse
I am posting a new thread about the whole process I've done. Please read it and help me install Magisk.
Btw I have a TWRP backup of the state before flashing / installing anyhting, so I am constantly recovering my system back to a state which passes safetynet.

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

Root working

I just wanted to say that root is possible with the magisk/patch boot.img method. I am currently running the latest Oct. 011.C4 image with root. Titanium Backup is restoring as we speak...

dethknite said:
I just wanted to say that root is possible with the magisk/patch boot.img method. I am currently running the latest Oct. 011.C1 image with root. Titanium Backup is restoring as we speak...
Click to expand...
Click to collapse
Mind sharing your extracted boot.img?

dethknite said:
I just wanted to say that root is possible with the magisk/patch boot.img method. I am currently running the latest Oct. 011.C1 image with root. Titanium Backup is restoring as we speak...
Click to expand...
Click to collapse
I can confirm, root working on my Pixel 4. Used the same method as with the Pixel 3 on Android 10, Magisk patched the boot img, then fastboot flash. I used the canary channel of magisk.
(Link for the factory images)
https://developers.google.com/android/images
---------- Post added at 09:14 PM ---------- Previous post was at 09:03 PM ----------
Shponglized said:
Mind sharing your extracted boot.img?
Click to expand...
Click to collapse
PM sent.

dethknite said:
I just wanted to say that root is possible with the magisk/patch boot.img method. I am currently running the latest Oct. 011.C1 image with root. Titanium Backup is restoring as we speak...
Click to expand...
Click to collapse
Have you got any magisk modules working? If so, which ones?

I tried to root my Pixel 4 using the Pixel 3 method but no luck. Pulled the boot.img from "10.0.0 (QD1A.190821.011.C4, Oct 2019)" for "flame" for Pixel 4. I used the Canary Magisk Manager and patched the boot imaged.
Got this error when trying to flash from ABD.
FAIL (remote: Failed to write to partition Not Found)
Anyone one else successful?

inclusive said:
I tried to root my Pixel 4 using the Pixel 3 method but no luck. Pulled the boot.img from "10.0.0 (QD1A.190821.011.C4, Oct 2019)" for "flame" for Pixel 4. I used the Canary Magisk Manager and patched the boot imaged.
Got this error when trying to flash from ABD.
FAIL (remote: Failed to write to partition Not Found)
Anyone one else successful?
Click to expand...
Click to collapse
You have to flash with fastboot, not adb
Sent from my Pixel 4 using Tapatalk

ajrty33 said:
You have to flash with fastboot, not adb
Sent from my Pixel 4 using Tapatalk
Click to expand...
Click to collapse
I was using ABD with fastboot but was getting that error. Redownloaded to a newer version and was able to root successfully. Now, just to get adaway to work. Thank you

How do I know which system image I should download?

Thanks dude! I just succeed to root my Pixel 4, too!

marc.ientilucci said:
How do I know which system image I should download?
Click to expand...
Click to collapse
Check your current build number under About Phone.

Oh yes..... Best news I've heard so far today.
I'm doing this right now!

cntryby429 said:
Check your current build number under About Phone.
Click to expand...
Click to collapse
What about for future updates?

marc.ientilucci said:
What about for future updates?
Click to expand...
Click to collapse
I'm not entirely sure. I came from the Pixel 2 and, as I recall, anytime there were multiple releases of a monthly patch they would have one generic image and one or more labeled for specific carriers. For example:
9.0.0 (PPR1.180610.009, Aug 2018)
9.0.0 (PPR1.180610.011, Aug 2018, Telstra)
I wonder if this will get corrected or if future patches will be named more clearly.

marc.ientilucci said:
How do I know which system image I should download?
Click to expand...
Click to collapse
I recommend flashing the updated Oct. image (without -w) and then subsequently using its boot image... that is what I am on.
10.0.0 (QD1A.190821.011.C4, Oct 2019)

KHANrad_SIN said:
Have you got any magisk modules working? If so, which ones?
Click to expand...
Click to collapse
I have several modules running--all of the same as my P3 (except edxposed). Even have Viper4Android running using the same AML hack for Android 10.

Noob question, but if I unlock the bootloader and root the device. Do I still get the lastest updates from google?

Vedrick said:
Noob question, but if I unlock the bootloader and root the device. Do I still get the lastest updates from google?
Click to expand...
Click to collapse
Yes. An unlocked bootloader itself won't break OTAs. Being rooted (requiring an unlocked bootloader) requires re-rooting after an OTA since the boot.img is overwritten. Having a custom recovery (not yet available for the Pixel 4) will preclude you from taking an OTA (from within the os, see below).
You can always flash the flashall.bat from the system image using fastboot for a clean install or an edited version of flashall.bat (removing the "-w") to effectively OTA and preserve your data.

what does it exactly mean to patch the bootimage, i want to root my phone because there a few google apps that I really have no need for. Especially considering the limited space on my 64gb model, wanna get rid of all the crap

KHANrad_SIN said:
Have you got any magisk modules working? If so, which ones?
Click to expand...
Click to collapse
KHANrad_SIN said:
Have you got any magisk modules working? If so, which ones?
Click to expand...
Click to collapse
For anyone who is curious, I went ahead and tried some modules myself. I'll list the ones I tried and whether they worked or not.
Viper4Android FX (working)
- so I got this to work, but in order to do so I believe you need to also install AML (Audio Modification Library) and reboot a few times after opening the V4A app and installing the driver, I don't know the exact method I just played around with it until it worked.
Ainur Sauron (working)
- I installed this along with V4A and it seems to be working
AML (Audio modification Library) (working)
- This needs to be installed in order to allow Ainur Sauron and V4A to work in conjunction
- It also needs to be installed for V4A to work in general on Android 10
Youtube Vanced (not the black themed one) (working)
- this was also kind of finicky, I had to install the module, then reboot, go to the settings app --> apps & notifications --> see all apps --> youtube --> disable/uninstall --> re-enable it, then reboot, then uninstall the youtube vanced module, reboot again, then go back to settings and uninstall the youtube app, now finally reinstall the youtube vanced module and reboot
- not entirely sure if all these steps need to be done to get it to work but that's what I did
Active Edge Mod for Pixel devices (was not working before, but is now currently working)
- the official changelog says support was added for the Pixel 4 XL so I figured I would give it a shot out of curiosity
- I tried it and it soft bricked my pixel 4, it got stuck on the "pixel is starting" animation and then I tried to reboot but every time it did it would just go to a black screen after the G logo
- Even doing a clean flash of the factory image didn't get rid of it
- I manged to fix it by relocking and then unlocking the bootloader again
- I have provided the developer with the necessary files to support our devices though and he said he is working on it
- UPDATE: As of October 25th 4:31AM PST he has now updated the module to be compatible with the smaller Pixel 4 and I can confirm it is working
Substratum Lite (some working)
- I only installed the Swift Dark substratum theme
- I also only tried it on a few apps like instagram, snapchat, maps, google play music, and google home
- I have not tried it on the other apps/elements like system UI or any other app so I can't really confirm if those work or not, but I can at least say some apps can be overlayed
Remember YMMV, and I am not responsible for your device getting bricked lol

ahsank128 said:
what does it exactly mean to patch the bootimage, i want to root my phone because there a few google apps that I really have no need for. Especially considering the limited space on my 64gb model, wanna get rid of all the crap
Click to expand...
Click to collapse
Magisk is the current root method. You download Magisk Manager and from within its UI you provide it the stock boot.img and it'll spit out a patched version that you can then flash to the boot partition using fastboot.
Magisk Manager + flashing the Magisk-patched boot.img = root access

HELP PLEASE!!PHONE not working after update

Guys help me please! After the last OTA update, I tried rooting as I always do through boot_a.img patching via magisk etc, and now the phone is not working appropriately. No network and no wifi, and after a while touchscreen stops working. I can't reflash the latest firmware I find on the official site as it's from February 15th and it says it's older than the one I have, so it doesn't allow me.
What can I do to fix my phone?

lowrider82 said:
Guys help me please! After the last OTA update, I tried rooting as I always do through boot_a.img patching via magisk etc, and now the phone is not working appropriately. No network and no wifi, and after a while touchscreen stops working. I can't reflash the latest firmware I find on the official site as it's from February 15th and it says it's older than the one I have, so it doesn't allow me.
What can I do to fix my phone?
Click to expand...
Click to collapse
Use the MSM tool and restore your phone to older firmware that way.
I don't know about the boot_a.img process you've been following, but that is not how I would recommend rooting.
Using fastboot, boot (DO NOT FLASH) TWRP, and then use a dd command to pull the boot.img
Boot into Android, install Magisk, inject root into the boot.img you pulled in the last step
Boot into fastboot, boot (DO NOT FLASH) the boot.img you just injected root into
Using Magisk Manager, Direct Install the kernel you booted from, then reboot and you are rooted

edit

NotATreoFan said:
Use the MSM tool and restore your phone to older firmware that way.
I don't know about the boot_a.img process you've been following, but that is not how I would recommend rooting.
Using fastboot, boot (DO NOT FLASH) TWRP, and then use a dd command to pull the boot.img
Boot into Android, install Magisk, inject root into the boot.img you pulled in the last step
Boot into fastboot, boot (DO NOT FLASH) the boot.img you just injected root into
Using Magisk Manager, Direct Install the kernel you booted from, then reboot and you are rooted
Click to expand...
Click to collapse
Thanks man, I managed to recover and boot again..now all I need is to reinstall magisk. Is there some guide you can point me to, that details the process you mention, mine is international unbranded and NOT-5G phone? I am not an expert so some of the things you say I am unsure how they are done...thanks again and very grateful for your time

lowrider82 said:
Thanks man, I managed to recover and boot again..now all I need is to reinstall magisk. Is there some guide you can point me to, that details the process you mention, mine is international unbranded and NOT-5G phone? I am not an expert so some of the things you say I am unsure how they are done...thanks again and very grateful for your time
Click to expand...
Click to collapse
The rooting process is the same, regardless of 5G or not. Check this thread, and follow the steps that begin with booting from TWRP (Step 5):
https://forum.xda-developers.com/7t-pro-mclaren/how-to/how-to-guide-root-oneplus-7t-pro-t4021325
You should not need the final step of setting A or B active, so disregard that one.

NotATreoFan said:
The rooting process is the same, regardless of 5G or not. Check this thread, and follow the steps that begin with booting from TWRP (Step 5):
https://forum.xda-developers.com/7t-pro-mclaren/how-to/how-to-guide-root-oneplus-7t-pro-t4021325
You should not need the final step of setting A or B active, so disregard that one.
Click to expand...
Click to collapse
Thank you I am so grateful... you helped me and it worked!
I have one last question for you in case you found a possible alternative. I noticed the camera app is quite poor, it doesn't even allow to select video/photo resolution/megapixels. Is there any modded version of the camera app you'd recommend, that will allow me to keep the same quality and full triple camera utilization that the stock camera app offers, while adding some nifty extra options?

lowrider82 said:
Thank you I am so grateful... you helped me and it worked!
I have one last question for you in case you found a possible alternative. I noticed the camera app is quite poor, it doesn't even allow to select video/photo resolution/megapixels. Is there any modded version of the camera app you'd recommend, that will allow me to keep the same quality and full triple camera utilization that the stock camera app offers, while adding some nifty extra options?
Click to expand...
Click to collapse
I haven't used it myself, but with root access, GCam ports are able to access all the cameras.