yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Guides, News, & Discussion] sic0048:
If you can download and install the OTA directly to the phone using the phone's update manager, then you can reroot the phone using Magisk's app. However, you must not allow the phone to reboot after the update before you open the Magisk manager and install Magisk. If you let it reboot, you will have to go through the longer root method of modifying the boot.img file.

Here is a basic set of instructions on how to take an OTA with the phone and retain root.

Step 1 - In the Magisk manager app: Click “Uninstall” then “restore images”. DO NOT REBOOT or press the reboot button.

Step 2 - Download and install OTA (in your phone's Settings/System/System Update). DO NOT REBOOT or press the reboot button.

Step 3 - Open the Magisk manager app and click “Install” next to Magisk (usually it says "Magisk is up to date") then “Install to second/inactive slot (After OTA)”

Step 4 - Press the Reboot button in Magisk.

That's it.

---------- Post added at 01:20 PM ---------- Previous post was at 01:13 PM ----------

It's much easier to side-load the OTA image instead of flashing the full factory image. The end result is the same, but side-loading does not require modifying any file to prevent a full wipe, and it doesn't even require an unlocked bootloader.

https://developers.google.com/android/ota

Here is a quick step by step on how to side-load.

Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find that you cannot boot into recovery while rooted, you will have to restore the stock boot.img. I've had this problem on some Android 10 images, but not all.

Step 2 - Download to your computer the correct OTA image from here.

Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".

Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").

Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.

Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.

Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.

Step 8 - Once the update finishes, reboot the phone to complete the update process. Please note that this initial boot may take an extended period of time. It is optimizing the apps behind the scenes without the normal progress indicator that you get when taking an normal OTA update through the phone. Please be patient and let the boot process complete. I've had it take 20+ minutes before. Be patient.

Step 9 - Reroot your phone using the standard Magisk "boot image patching" method.
[Google Pixel 4 XL Guides, News, & Discussion] krabman:
I was discussing rooted phones, if you're not rooted you can just take the OTA or if impatient sideloading will always work unlike when you are rooted where it will occasionally fail and you have to flash the boot or go dirty to get out of a softbrick. That's the problem with the OTA method also, while it's seemingly 100% on OnePlus devices where I would absolutely recommend that method it will occasionally fail with Pixel devices and you end up in a softbrick that requires flashing the boot or dirty flashing the full to get out of which means you're still downloading the full anyways. Same if you're rooted and you want to sideload the OTA. You're still going to download the full to get the boot to patch and having done that you're already ready to flash the full outside of removing the wipe which I think you know based on your post takes literally seconds.

The dirty flash is fool proof and done correctly is quite quick, comparable to the time it takes to sideload and then root. The Magisk OTA is the best method for time but is not fool-proof depending on the device, magisk version, etc. I have my reasons to recommend the dirty flash and they're based on experience. I suppose it comes down to how adverse you are to sorting out the occasional soft-brick versus spending a little more time for the no-fail method.
[Google Pixel 4 XL Guides, News, & Discussion] sic0048:
It's failing because Magisk never made a backup of the boot.img file for some reason. Perhaps you used a pre-modified boot.img file initially.

You have two options. One is to go through the traditional Magisk root directions where you download the stock boot.img from the full factory image and use Magisk to modify it and then flash it using your computer. This will create the backup needed to then uninstall Magisk. This seems like a lot of work just to turn around and uninstall it however.

The second option is to simply skip step 1. To be honest, step one is pretty optional it seems. So skip it and see if the OTA will download and install. Just be aware that it routinely will fail, especially on a rooted phone. This is why step 1 is written in, but I haven't seen it make a huge difference in the success rate either way. Be sure to do this on a decent wifi connection. I seem to get more failures when using cellular to download the OTA.

If it consistently fails (you can retry it as much as you like, but eventually you may have to "throw in the towel") you will have to move forward with either side-loading the OTA (what I would recommend) or flashing the full factory image in order to update. You will then have to follow the normal Magisk boot image modification method to root the phone.

---------- Post added at 02:26 PM ---------- Previous post was at 02:12 PM ----------

Obviously there is no right or wrong way of doing it. You are correct that by side-loading the OTA, I still have to download the full factory image to extract the boot.img file. However, side-loading the OTA takes a fraction of the time to actually flash than the full factory image does. This is why I lean towards the side-load option. It is much quicker. Normally factory images take 30-40 minutes to flash while a side-load OTA rarely takes more than 5 minutes. At least that has been my experience.

I'll download the OTA image and start the sideload process. While that is executing, I download the full factory image and extract the boot.img. Both of these events tend to finish up at the same time and I can then root the phone using the regular Magisk instructions.

I guess if I was on a metered internet connection, then taking the full factory image would use less data. But my home internet is not metered, so I'd rather save time than data.
[Google Pixel 4 XL Guides, News, & Discussion] krabman:
Huh, usually takes me 5ish or so minutes to flash the full image and boot will occur in a minute or two. I've never seen it take anything close to the time you describe.As the OTA can often be the entire image sent as an OTA it can take anywhere from the same time to just a minute or two if it's very small like this months image. The boot time for me is the same either way and seldom varies. The dirty flash will always work, the sideload will usually work with an occasional softbrick. With these phones I go dirty, with OnePlus I go magisk after OTA. Back when the roms were big time flashing was a hobby for me, first with windows phone and then with android when it came along. Nowadays the roms aren't what they used to be and I just want to go in and get it done without any issues and move on. Just a philosophy thing; it's business nowadays.
[Google Pixel 4 XL Guides, News, & Discussion] niko26:
That worked pretty well and flawlessly. :) Thanks for the hint!

Oh, and the OTA update took about 15 minutes IIRC. Be patient :)
[Google Pixel 4 XL Guides, News, & Discussion] Jiggs82:
Glad it worked for you;)
[Google Pixel 4 XL Guides, News, & Discussion] madgooner2810:
This is what I assumed. Back during the Nexus days I would get an OTA notification but installation would fail due to not being stock.

I still haven't gotten the OTA though - I really wanted to do it via the magisk method but seems like I'll be dirty flashing.

Does the updated clear cache on Google framework still work? Saw a thread where the old method would break push notifications but the new method wouldn't?
[Google Pixel 4 XL Guides, News, & Discussion] hrdc69:
Thanks to everyone for their suggestions of different methods to flash but to me it seems dirtyflashing is the safest method even though it may take a bit longer than sideloading. After reading all the various suggestions in the different posts this is how I think the exact sequence of steps should be to dirty flash. If I am wrong or have missed a step please let me know.

After downloading the November update I would edit the flash all.bat file and going into fastboot mode do the following:

fastboot update image-coral-qd1a.190821.007.a3.zip

Then I would let the Pixel boot up, put a copy of the November boot,img on the internal storage then patch it with Magisk.

Then fastboot the patched boot,img, then reboot and I should be updated?
[Google Pixel 4 XL Guides, News, & Discussion] Cilraaz:
I went in the reverse order and patched the new boot.img before flashing the November update.

Download the image

Extract boot.img from the image zip

adb push boot.img to the already rooted phone

Patch the new boot.img

adb reboot-bootloader

Flash bootloader

Reboot to bootloader

Flash radio

Reboot to bootloader

fastboot update <image zip>

Flash magisk patched boot image

Boot phone

Seemed to work for me. If it bootloops:

Reboot to the bootloader

Flash the November boot.img

Boot the phone normally

Reboot to the bootloader

Flash the magisk patched boot image

Boot phone
[Google Pixel 4 XL Guides, News, & Discussion] krabman:
Just mingle the files as shown on the developers page and execute the flash-all, it will take care of the rest. Up front make sure you have the correct image and do not forget to save the flash.all after you edit it so you don't get wiped. As you're not wiping you can move the boot.img over before or after the flash. Either way just use your already up to date and existing magisk app to patch it and then transfer it back and flash per usual. One other thing to be aware of is you need an A to C cable to flash the factory images, a lot of people have trouble using the C to C so you'll want one in hand before you start. Don't ask me why but it's a thing.

To the fellow above... I hadn't done mine yet, been busy. Decided to go ahead and do it just to catch the actual time: Ended up being 259 seconds for the full image flash. Still not sure where the 30 to 40 minute thing came from, I'v e genuinely never seen it take anything like that.
[Google Pixel 4 XL Guides, News, & Discussion] paulomario77:
Fastboot only recognizes my phone (I.e. fastboot devices) if connected to a USB C port. When connected to USB A, it doesn't show up on fastboot devices. I don't think my A to C cable is at fault, because I can run ADB commands using it.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Try switching the A to C cable to another USB port that is a non-charging USB port.
[Google Pixel 4 XL Guides, News, & Discussion] sic0048:
Using Magisk to modify the boot.img prior to flashing the update creates a usable patched boot.img, but the update will overwrite the backup that Magisk created of the stock boot.img. This means you cannot "uninstall" Magisk and restore the stock images to take an OTA update. Magisk will throw an error saying there is no backup.

Luckily it's a simple fix. Simply open the Magisk manger app, press install Magisk (even though it says it is up to date) and choose the ""Select and Patch a File" method, and choose the sotck boot.img that you already moved to the phone the first time you did this. This will recreate the patched file (that we really don't care about) but Magisk will also recreate the backup of the stock boot.img file. Once that is done, simply stop. You don't have to reflash the patched img since Magisk is already installed.

There is a rhyme and reason for the steps to install Magisk. Changing those steps can cause issues like this. In the future you will want to use Magisk to modify the boot image after you flash the update.
[Google Pixel 4 XL Guides, News, & Discussion] Cilraaz:
Ah, I've never had need to uninstall Magisk, as I flash full factory images every month instead of dealing with OTAs. Good to know, though. Thanks!
[Google Pixel 4 XL Guides, News, & Discussion] krabman:
I would carefully consider whether you want to use the dirty flash if you have only a C to C connection unless you've done it before and know it works. I can use the supplied C to C for everything except flashing the full factory images without issue but it will fail for me every time on the full. I'm not the only one, this happens to many people and has been going on since the P2. It will come up in every thread about flash failures with these devices and the first thing people are going to say is to switch to an A to C.
[Google Pixel 4 XL Guides, News, & Discussion] paulomario77:
Yes, that's exactly my case: I did a flash-all through a C to C cable, and now it won't boot. I can't even enter recovery mode. I did this because my A to C cable wasn't working for fastboot. When I get home, I'll try a different USB A port and flash-all again.
[Google Pixel 4 XL Guides, News, & Discussion] krabman:
You should be ok if you flash the works again on a working port with the A to C.
[Google Pixel 4 XL Guides, News, & Discussion] tonyreimer:
hi. im having problems flashing factory images. i previously had magisk installed and tried doin a factory data reset without uninstalling.
[Google Pixel 4 XL Guides, News, & Discussion] eg1122:
I've seen this happening to a lot of people. First, update your adb/fastboot files and try again. If that doesn't work grab your current (October?) Boot.img and flash it via fastboot using the following commands

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

After that try updating again
[Google Pixel 4 XL Guides, News, & Discussion] tonyreimer:
Thanks. I did manage to get it to boot by flashing boot_a and boot_b with the stock boot.img But i still cant update. throwing same errors. im kinda illiterate tho so ill keep foolin around.
[Google Pixel 4 XL Guides, News, & Discussion] eg1122:
Grab latest platform tools from here.

https://developer.android.com/studio/releases/platform-tools

Try using the included fastboot to update
[Google Pixel 4 XL Guides, News, & Discussion] 5m4r7ph0n36uru:
[MENTION=3804281]tonyreimer[/MENTION] could also download the latest fastboot right away without the need to download the full platform tools. Links are the following.

adb/fastboot Windows:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

adb/fastboot Linux:

https://dl.google.com/android/repository/platform-tools-latest-linux.zip
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
And don't forget this little gem of a possible cause to your dilema :eek:

https://xdaforums.com/pixel-4-xl/how-to/usb-cables-info-t3992691
[Google Pixel 4 XL Guides, News, & Discussion] krabman:
Yeah, been saying it, you need to use an A to C to flash the full factory images or your can run into a flash failure and you softbrick, this affected my 3, 3a, and this device so it's definitely a thing. Wont hit everyone every time but enough to make the A to C part of the process or one should at least be on hand to fall back on when you flash until you know you're good.. As to Magisk I leave it every time without running into issues, you may want to disable modules depending on what you have, if you don't know if they're going to be an issue just disable them all and reenable after you flash the boot.img. What you should see after flashing the factory image is the phone coming up fine but root is lost. Anything that was working on root that can screw you up will be doing so, that's why you disable those modules before you flash. Otherwise you'll be up just find and can patch the boot, send it over to the pc and flash it and you'll be rooted again. It takes more time to talk about it than it actually takes to do it, it's very simple once you've made the rounds once or twice.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Funny how this issue that started with the P2XL is still around. Who says google doesn't have a sense of humor! ??
[Google Pixel 4 XL Guides, News, & Discussion] mrjaydee82:
Has anyone gotten the update on their own? I was being lazy just waiting for the update and still notta...I suppose tomorrow I'll be manually doing it
[Google Pixel 4 XL Guides, News, & Discussion] wgrant:
I still haven't had it show up for me. I'm not all that concerned with it, I'm sure it'll show up eventually. I do check twice a day though.
[Google Pixel 4 XL Guides, News, & Discussion] wgrant:
Finally have the update as an opting through OTA. Had to manually check, never got the notification.

---------- Post added at 01:13 AM ---------- Previous post was at 12:27 AM ----------

Tried this and unfortunately didn't work. Keeps telling me the same. I checked root/data and I have a stock boot image there too. It's weird.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Well...you know what to do bruh if you have to! :good::cool:
[Google Pixel 4 XL Guides, News, & Discussion] wgrant:
Yeah, I know... Sucks cause I waited so I wouldn't have to use a computer lol. Oh well
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Damn first world problems! ??
[Google Pixel 4 XL Guides, News, & Discussion] wgrant:
I work on computers all day. I'm entitled to be lazy at home! I just wanted try something different in reality. I'll get around to it this week.
[Google Pixel 4 XL Guides, News, & Discussion] pdfruth:
See this Github issue
[Google Pixel 4 XL Guides, News, & Discussion] wgrant:
Just gave that a whirl too and no go. It's weird since there is a file there. If I remove the file the uninstall fails immediately for the same thing but if the file is there it takes longer but still fails. I know it's the correct boot.img, I pulled it fresh last night. Oh well, guess it's flashing or side loading time.

Thank you, I appreciate the suggestion. Plus it was nice information to have. Hopefully John will add that feature.

Edit: now up to November after doing it through fastboot. Had to redo my face for face unlock to work. Rooted also. Good to go.
[Google Pixel 4 XL Guides, News, & Discussion] pdfruth:
If it's any consolation... while the proposed change in that Git issue is ultimately about adding a new feature to Magisk, the hints about how to manually configure the system to support a successful Magisk "Uninstall - Restore Images" do indeed work.

After spending some quality time studying the code in the restore_imgs() function of the utils.sh script [*1], it's become quite clear what needs to be done in order to get things to work.

Basically, in order for the Magisk Manager app's "Uninstall - Restore Images" to work, there needs to be two files in place (well, three if you consider the /sbin/.magisk/config file). There needs to be gzip'd copies of the original boot.img and dtbo.img files in /data

So, since I've already flashed the November OTA, I retrieved the boot.img and dtbo.img files from the November factory image [*2].

Then, using a Linux system, I gzip'd each of them. Their files names became boot.img.gz and dtbo.img.gz

Then, I renamed the files;

from boot.img.gz to -> stock_boot_<SHA1>.img.gz

from dtbo.img.gz to -> stock_dtbo.img.gz

Where <SHA1> is the value from the SHA1= line in the /sbin/.magisk/config file. In my case that was b7d5567f57a7de3a3d83e7693069e8d11bad2bb7 (interestingly, the shasum from the Oct image). Your's may well be different.

Finally, I simply moved those two files to the /data directory on the phone.

Upon completing the above, the Magisk Manager app's "Uninstall - Restore Images" works as expected. Thus, I'm able to uninstall Magisk in preparation for the application of an OTA (when one comes along again). Note, this same series of steps will need to be followed after the application of each OTA going forward (or until the enhancement proposed in that Git issue is implemented, of course).

[*1] - https://github.com/topjohnwu/Magisk/blob/master/app/src/main/res/raw/utils.sh

[*2] - https://developers.google.com/android/images
[Google Pixel 4 XL Guides, News, & Discussion] wgrant:
Very informative, thank you. It looks like I was/am missing the dtbo file. When December comes around I'll see if I can do the OTA with a successful magisk uninstall following these instructions. Appreciate the effort put into this. I hope it helps someone else get up to November easier.
[Google Pixel 4 XL Guides, News, & Discussion] doomwithdon:
Tried these instruction to the letter, still didnt work for me. Gave me the same toast message. Can it be anything to do with the rename magisk package function? I have given a random name to the magisk package to hide it from my banking apps.
[Google Pixel 4 XL Guides, News, & Discussion] bobziuchkovski:
It looks like Recent Magisk versions are using a different file/directory structure for the backups. It now looks in /data/magisk_backup_${SHA1} directory for boot.img.gz and dtbo.img.gz (not stock_* files).

If that doesn't work, check the current git version of utils.sh to see if anything has changed again since posting this.
[General Questions and Answers] Gustavvo:
Hello,

I decided to have a shot and try to ask for help here. After many hours of trying and googling I could not find the proper solution how to backup my media files. Whenever I go to recovery mode and connect my phone via usb, using SDK tools I write "adb devices" and it tells me that my Samsung Galaxy S6 is connected via "sideload"?. Is there any way to backup my media using sideload? I am not able to pull data from the phone using "adb pull", but maybe there is some sort of script that I could push that would make my phone do a backup. Hopefully there is a chance to recover my files before I do a full wipe. Photos and memories gathered in 4 years. Would suck to loose all of that.
[General Questions and Answers] Droidriven:
Sideload is a one way street, you can only use sideload to transfer data from PC to your device, not device to PC.

Try booting into recovery and only wipe the cache partition(DO NOT FACTORY RESET), this will not delete your media files, it only deletes temporary files, if your cached files are causing your bootloop, wiping cache will fix it.

If you can't get the device to boot into system, you might be screwed.

One other option is, if your bootloader is unlocked, you can flash TWRP custom recovery for your specific model number then you have a couple of options, you can connect to adb while booted into TWRP and use adb commands to pull copies of your media files, or, you can use the Backup option in TWRP then extract the backup to retreive your files, extracting TWRP backups is kinda tricky though.
[Samsung Galaxy J2 Questions & Answers] PRemBh0i:
Can someone please let me know that which rom is the best for the J200G and is currently being updated or in Support?

Like EnigmaNL By ShaDisNX255. If there's any other then please let me know.
[Samsung Galaxy J2 Questions & Answers] TBM 13:
EnigmaNL by ShaDisNX255 is for the J2 Prime, not for the J2 2015 (J200).

I think that eXcustom is a good ROM.
[Samsung Galaxy J2 Questions & Answers] PRemBh0i:
Thanks for replying, yeah i figured EnigmaNL By ShaDisNX255 is for Prime after a while.So i searched around and i couldn't find the ExCustom Rom then i found the Final version which is sadly Trashed, and then the V2.

But i wanted to try the others, well i guess i'm gonna go one by one. Thanks again.
[Windows Mobile Development and Hacking General] ^^rac:
Hey guys!

Does anyone know, where one can get proper alarm notifications is .wav format?

The default PPC notfifications for alarms, is the same as the sms/ email notifications. I would like to have something ordinary, that sounds like an alarm......

Any ideas?

Thanks peeps!
[Windows Mobile Development and Hacking General] master athlon:
you could always make your own, just cut peice from some song or somthing that you like and save it as a .wav file.