Database Info

Has anyone gotten the OTA URL or file for the Stagefright patch?

Hey I was wondering if anyone has managed to get their hands on the download URL for the patch. It'd be a small patch that you would be able to flash in the stock recovery since it's signed by Alcatel. It'd be much easier for people to put this on their sd cards and flash rather than reimaging their phones.

Someone had a link to the bin... maybe @famewolf

FBis251 said:
Hey I was wondering if anyone has managed to get their hands on the download URL for the patch. It'd be a small patch that you would be able to flash in the stock recovery since it's signed by Alcatel. It'd be much easier for people to put this on their sd cards and flash rather than reimaging their phones.
Click to expand...
Click to collapse
What exactly are you trying to do with it? The patch was specific to each different model of idol 3 (6045i, 6045Y, 6045K, 6039Y, 6039K, 6039i) and was generated at the time the system checker polled their server...it looked at what firmware level the user was already at and added all patches they didn't yet have installed..the urls last for a limited time so yes I did intercept it via a transparent squid proxy but I doubt the url will do you much good as it's probably expired by now...if you want the FILE this is not a patch that will sideload to well I don't believe since one of the things it does is check the checksum of recovery and if it doesn't match the system default recovery it overwrites it. If you try to install it on a device that has any of the previous patches applied that were not applied to MY device at the time of download the update will fail as patch will not apply to an already updated file. The update will then error out.
So to sum all of that up, what exactly are you trying to do with the file? Oh and the update is 302mb....not exactly "small".
..and no it's not "easier" as if you are rooted and don't fully unroot you risk putting yourself into boot loops that currently cannot be resolved since it wipes out your recovery at the same time. Factory recovery for 6045i and 6045Y does not have reboot to bootloader as an option so you basically have a paperweight. It's easier to deal with an image that is already updated and then just flash the supersu zip right after.

The neat thing is that since the updates are signed by alcatel they're basically the only type of file that will flash with the stock recovery.
It's a shame that they got generated on the fly but it makes sense since it'll be a single download every time for each phone, but that means that as you said it's not reusable.
I haven't messed with Android phones in a bit but I read that as of lollipop that patching mechanism changed to some sort of binary diff patcher instead unlike in the KitKat and older days that an OTA zip would contain the full file to be replaced.
Thanks for the information

FBis251 said:
The neat thing is that since the updates are signed by alcatel they're basically the only type of file that will flash with the stock recovery.
It's a shame that they got generated on the fly but it makes sense since it'll be a single download every time for each phone, but that means that as you said it's not reusable.
I haven't messed with Android phones in a bit but I read that as of lollipop that patching mechanism changed to some sort of binary diff patcher instead unlike in the KitKat and older days that an OTA zip would contain the full file to be replaced.
Thanks for the information
Click to expand...
Click to collapse
Add me to the list that can send you pm's and I'll drop you a link to look at.

root questions

Hey guys and gals, I'm new to the pixel and new to unlockable phones. I've always used AT&T brand phones with locked bootloaders so that being said I've never used Magisk or TWRP, although i used SafeStrap back on my S5 which is sortof like TWRP. I've rooted every device that I've had and installed SuperSu, roms etc but what I'm wondering is what is the difference in Magisk and SuperSu, which one is better in your opinion. I've read about making sure I'm on the latest image before doing certain things like installing roms and i believe TWRP, when yall say image, is that just saying the latest firmware. Sorry for my ignorance but I've always ran samsung phones. I just ordered my pixel 2 through Google so it's not carrier branded or locked down, it'll be away my house Friday so I'm just trying to do a little homework before it gets here so i can hit the ground running.
Thanks in advance

Magisk vs. SuperSU: Use Magisk as SuperSU was just announced as EOL.
Meaning of "image": In the context of "be on the latest image" it refers to the Factory Images (firmware) available from google. It's seems to be best to always flash the Factory Image (as opposed to an OTA image). If you must retain your data then you can edit the flash-all.bat (or flash-all.sh) file to remove the "-w" flag towards the end to keep the batch file from wiping data.
If you're new to pixel phones then you should beware of A/B partitions and their effect on the order of flashing/booting partitions. Also, know that the recovery is tucked inside of the boot image so flashing new ROMs will wipe out your TWRP installation so you can either reflash TWRP every time or get in the habit of just"fastboot boot"ing TWRP every time you need it. Last, be sure to update your fastboot/adb files regularly as several Pixel OS updates in the last 2 years have required the absolutely newest fastboot. Google now makes them available as a standalone direct download which is far more convenient than installing Android Studio if you only need the fastboot/adb files.

cntryby429 said:
Magisk vs. SuperSU: Use Magisk as SuperSU was just announced as EOL.
Meaning of "image": In the context of "be on the latest image" it refers to the Factory Images (firmware) available from google. It's seems to be best to always flash the Factory Image (as opposed to an OTA image). If you must retain your data then you can edit the flash-all.bat (or flash-all.sh) file to remove the "-w" flag towards the end to keep the batch file from wiping data.
If you're new to pixel phones then you should beware of A/B partitions and their effect on the order of flashing/booting partitions. Also, know that the recovery is tucked inside of the boot image so flashing new ROMs will wipe out your TWRP installation so you can either reflash TWRP every time or get in the habit of just"fastboot boot"ing TWRP every time you need it. Last, be sure to update your fastboot/adb files regularly as several Pixel OS updates in the last 2 years have required the absolutely newest fastboot. Google now makes them available as a standalone direct download which is far more convenient than installing Android Studio if you only need the fastboot/adb files.
Click to expand...
Click to collapse
Thanks for the info. I'll keep reading up on it all. The A/B partitons sounds like two different slots that you can boot from, is that correct. Like having stock backup on partition A and a rom on partition B. It i could be wrong all together. Lol. Anyhow thanks for the info. Can't wait to get it and play with it. It'll be my backup phone since whe I'm working AT&T don't pick up service i bought the pixel so i can put a prepaid sim in it to run on Verizon network.

FilthyFord said:
Thanks for the info. I'll keep reading up on it all. The A/B partitons sounds like two different slots that you can boot from, is that correct. Like having stock backup on partition A and a rom on partition B. It i could be wrong all together. Lol. Anyhow thanks for the info. Can't wait to get it and play with it. It'll be my backup phone since whe I'm working AT&T don't pick up service i bought the pixel so i can put a prepaid sim in it to run on Verizon network.
Click to expand...
Click to collapse
The A/B partition system was designed for seamless OTAs. Your device functions as usual, while the inactive slot updates. Once you reboot after an OTA, the slot changes to the updated slot, whether it be A or B, as if nothing happened. I know that you can switch between the two, but I don't believe that you can choose to occupy either of them with a custom ROM or a backup. Just follow the guide about updating to the latest Google software and you'll be golden.

DuckRuckus said:
The A/B partition system was designed for seamless OTAs. Your device functions as usual, while the inactive slot updates. Once you reboot after an OTA, the slot changes to the updated slot, whether it be A or B, as if nothing happened. I know that you can switch between the two, but I don't believe that you can choose to occupy either of them with a custom ROM or a backup. Just follow the guide about updating to the latest Google software and you'll be golden.
Click to expand...
Click to collapse
Thank you for clearing that up for me.

Getting root on the BNTV460 is a pain....

Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.

Articul8Madness said:
Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.
Click to expand...
Click to collapse
If it is close enough to 450, and you can get into fastboot, you can try and boot the linked boot.img
fastboot boot m19_ST16C7BNv205.img
Same modifications I had to use to get the first boot image I found to work with BNTV450.
avb, mtk type and signature removed.
Also patched with Magisk 19 (canary release)
For good measure.
https://drive.google.com/open?id=1LgtB2JKCKwLJ64mUlij5Cb_cJrBi8Av1
PS.
Tested above modified v2.0.5 boot.img on BNTV450 running v1.0.2, so it should work on BN v1.0.2 and up.
Good Luck.
Cheers.
PPS.
Just ordered one. (Should show up in 2-3 days.)

Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.

Articul8Madness said:
Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.
Click to expand...
Click to collapse
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304

turtleletortue said:
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304
Click to expand...
Click to collapse
I appreciate it, but I've since taken it back. Tell you what though, maybe I'll pick up a used one on ebay and try it

[OTA / UPDATE GUIDE WHILE MAGISK ROOTED] UPDATE FIRMWARE *WITHOUT LOSING DATA* (for stock Samsung ROM users)

** PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE POSTING AND/OR ATTEMPTING ANY MODIFICATIONS TO YOUR DEVICE. THIS GUIDE ASSUMES YOU ALREADY KNOW HOW TO OR HAVE ALREADY UNLOCKED YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, HOW TO FIX KG STATE ISSUES, HOW TO USE ODIN, 7-ZIP, LZ4 TOOL, ETC. THIS POST IS SIMPLY MY OBSERVATIONS AND STEPS TO UPDATE THE FIRMWARE WHILE ROOTED WITH MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE. MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY IF YOU LOSE YOUR DATA. THE STEPS I SHARE HAVE WORKED WITHOUT FAIL FOR ME, BUT THAT DOESN'T MEAN YOU MAY NOT RUN INTO PROBLEMS. BACKUP YOUR DATA.**
The reason I decided to write up this guide is because of the extremely large amount of misinformation, as well as general noob-ness (no offense to anyone, just my observations to be completely honest), that I seem to come across when it comes to the Samsung sub-forums around here. I've seen many people state that updating the firmware on this particular device (Galaxy Tab S6 LITE) will REQUIRE a data wipe, which is simply not true in my experience. However, I will admit that the procedure is extremely bass ackwards when it comes to this particular device, so maybe that's why people have been claiming this.
This guide only applies to stock Samsung firmware users.
Spoiler: Boring Backstory (click to read):
I ditched Samsung a long time ago, after the Galaxy S5 (not TAB, but the phone) days, when they really started locking up the bootloaders on the USA variants. Only T-Mobile was excluded on that particular model, but from what I understand, pretty much all Snapdragons since then have been completely locked down, across all carriers. So first of all, F*CK Samsung for being dickholes. Other than that, I recently decided I wanted to start using an Android tablet again, so at first I bought a Galaxy Tab S6 Lite several months ago. Eventually I got the Galaxy Tab S7 Plus, after hearing (and it's true) that the S7 series tablets actually kept Widevine L1 status after unlocking bootloader / rooting. Heck yeah.
Anyway, my Tab S6 Lite just gathered dust over the last few months, but now that I'm donating it to a friend of mine who's in school, I reloaded it with stock firmware, but rooted and heavily modified (he's an art student, so having all the stock Samsung / S-Pen integrations will be very useful for him). I finally decided to take some rough notes (written and mental, lol) about the process of updating the firmware WITHOUT losing data. As in updating your device as if like taking a standard OTA, but needing to do it manually because we're rooted and modified.
Unfortunately, like I said this device is freaking weird. Not sure if it's because it's Exynos (it's my first Exy device) or what, but it doesn't follow the same procedure as I've been used to back in the Galaxy phone days, other Tabs I've come across, nor with the Galaxy Tab S7 Plus I now own... Which is to literally follow the instructions as the creator of Magisk himself, @topjohnwu, published on his Github (see the Samsung section): https://topjohnwu.github.io/Magisk/install.html
But following those official Magisk instructions will result in this particular device not being able to boot, and you will need to wipe and start over. tl;dr - normally for sammy devices, you need to patch the full AP file in Magisk Manager and flash that in the AP slot in Odin because it also patches vbmeta to work around AVB. But for this device, this doesn't seem to be the case. At least in my experience.
Spoiler: Technical Rantings; Still Worth A Read IMO (click to read):
For some reason, on this particular device, you can't just patch the entire AP file. That will result in your device not booting, and eventually requiring a clean (wipe it all) Odin flash. Instead you need to flash the full, unmodified AP file (which normally would screw you over and is completely advised against), and then some extra steps... Anyway, I've outlined those steps below, as well as some preparation you'll need to do beforehand, which really just involves patching the boot image itself and placing in a .tar archive, which I would hope you already know how to do to be perfectly honest.
Not sure WTF is going on, as on other Samsung devices, you want to patch the entire AP file because Magisk will also automatically patch the vbmeta image thus working around AVB restrictions. It's really freaking weird to me because normally failing to patch vbmeta should normally result in inability to boot and subsequent SOL situation where you need to wipe... but with this device, it's ass backwards. And Magisk does indeed patch the vbmeta image when patching the full AP for this device... Why instead you need to skip patching the full AP file and flash just the patched boot image separately (thus skipping patching vbmeta) makes little sense to me. Not sure why this tablet is different, but again I'm not usually a huge fan of Samsung anyway so I really don't give AF. But they make the best Android tablets, so now that I've recently bought them (though I won't have this model S6 Lite for much longer), well I wanted to share with you guys; here are my working update instructions for the Galaxy Tab S6 Lite, without losing data. At least it works for me.
FOLLOW THIS GUIDE AT YOUR OWN RISK! AND BACKUP YOUR CRAP BEFORE ATTEMPTING, JUST IN CASE.
I'm not responsible for any problems you incur, etc. etc. blah blah.
(BTW, this is for the SM-P610 - WiFi USA version. Not tested on LTE, and if you try on LTE, you'll also have a CP file to flash, fyi. I have no experience with the LTE model either). This guide assumes you already have your bootloader unlocked, know how to use Odin, aren't a complete noob, and can at least restore back to stock if crap goes sideways.
Below are some bonus resources anyway, to hopefully clear up some silly questions before they come up.​
* Please thank the devs and OP's of these posts if you find them helpful and/or use their tools. It's the least you can do! *
[FRIJA] USE THIS TO DOWNLOAD THE LATEST FIRMWARE: https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910584/
[ODIN *PATCHED*] I RECOMMEND VERSION "Odin3 v3.14.1_3B_PatcheD": https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
[LZ4 TOOL] DECRYPTS LZ4 EXTENSION'D FILES: https://github.com/lz4/lz4/releases
[BL WARNING TEXT REMOVAL] TO REMOVE UGLY WARNING TEXT AT BOOT: https://forum.xda-developers.com/t/...tock-firmwares-modded-bl-warningtext.4195829/
* Please thank the devs and OP's of these posts if you find them helpful and/or use their tools. It's the least you can do! *
***************************** STEPS TO UPDATE FIRMWARE: *****************************​
Use Frija (download thread provided above), or download firmware from somewhere like samfw.com
Open / unzip the firmware, and then open the AP archive and pull boot.img.lz4.
Using LZ4 tool (download thread provided above), decrypt boot.img.lz4 to boot.img
* you can just simply drag and drop the boot.img.lz4 file over the lz4.exe binary in Windows explorer
Copy boot.img to your tablet. Open Magisk (Manager) and patch the file.
Copy the Magisk Patched boot file back to your PC. Rename it as boot.img
Create .tar file (tar file name doesn't matter) containing ONLY boot.img - do not use compression (if using 7-Zip, add the boot.img to archive, select archive format as "tar", and use compression level as "Store"). While the .tar file name doesn't matter, IT SHOULD ONLY CONTAIN A SINGLE FILE - boot.img
Reboot to download mode. Hook up your tablet to your PC.
**IT MAY GET SCARY HERE ON SOME STEPS, BUT CONTINUE FOLLOWING THIS EXACTLY**
(Use Odin3 v3.14.1_3B_PatcheD, link provided above)
Flash new stock firmware, using BL / AP / HOME_CSC (must use HOME_CSC to not wipe data, DO NOT USE THE REGULAR CSC FILE OR IT WILL AUTOMATICALLY WIPE). If you have LTE version, also flash the CP file in CP slot. WiFi version does not have CP file.
Using default Odin options is fine (F. Reset Time, Auto Reboot). In fact, I would recommend it for the sake of following this guide.
It'll be scary, but it will reboot a few times and eventually boot into recovery mode. Don't interrupt the process and let it eventually settle on its own into recovery mode (after a few seemingly failed boot attempts).
It'll make you think you're screwed and must factory wipe the device. DON'T FREAK OUT. Options will be:
Try again
Factory data reset
View recovery logs
While USB cable is still plugged into the tablet and computer, select Try again (tap power button, but don't hold the button down) and then immediately hold down volume up and down at the same time so that and until it goes back to download mode. As prompted, press volume up to continue.
Using Odin, flash ONLY the magisk patched boot image tar file (uncheck BL / CSC boxes if Odin is still open from before). Also you can flash the modified bootloader splash tar as well at this time, might as well kill 2 birds with 1 stone. Again, you can just leave default options enabled (F. Reset Time, Auto Reboot).
Again, this will be very scary. It won't boot to system, but rather bootloader again. Probably an error at the bottom, something like "failed to load locales from the resource files" / "failed to compare" / whatever. However, the normal recovery options should now be available.
YOU WILL ONLY WIPE CACHE PARTITION (scroll down to "Wipe cache partition", and then confirm yes. Then select "Reboot system now".
It will take a while to boot, but this time you should eventually get to the lone "SAMSUNG" boot logo (this is a great sign), and then eventually get the "Tablet is updating..." box which shows the progress as it re-optimizes all of your apps.
That's it, and once it finishes optimizing your apps, should continue to load to your lockscreen! If so, congratulations, you've now updated to the latest firmware while retaining root without losing your data!
**********************************************************​
Even with a heavily modified tablet, this has worked over several months, including the jump from A10 to A11. SafetyNet still passes (using kdrag0n's module), YouTube Vanced (my module), LSposed with Firefds kit and GravityBox R, and a bunch of other Magisk modules.
I'm very much aware you can save time by tweaking the above process, but this was the very safest exact procedure I could think of, so I recommend following it exactly as I wrote above.
Good luck, I hope it works for you, and enjoy your tablets!

just in case

and another

Damn, thanks dude. I'd just about given up clean flashing and thought I'll give your suggestion a go and it worked like a Boss! Im using the LTE version and not a single hiccup. Thank you for saving me a huge hassle. Only things i didn't follow was use frija, paid$2.99 and got the firmware. Everything else was exactly what you did. Worked man! Thank you so much again.
If anyone wants the latest. ACR firmware for SM-P615, lemme know and I'll share my drive link with you.
Cheers! Kudos. On latest may update now.

Didn't do the 2 birds one stone thing, was scared. I'm gonna do that later. Again, just to clarify, i run Magisk only for and root level file brousing, does it really matter if i don't pass the test? Everything runs as it should, just curious if there was a benefit to it.

Thanks a lot for this detailed guide!
It worked perfectly on my Galaxy tab S7, I updated it successfully with magisk already installed.

didnt work for me on the CUH2 update

sunmybun said:
didnt work for me on the CUH2 update
Click to expand...
Click to collapse
I actually just tried it and it does still work for CUH2. I am happy for this firmware as I was having a weird system reboot every time I unlock with PIN.

shattacrew said:
I actually just tried it and it does still work for CUH2. I am happy for this firmware as I was having a weird system reboot every time I unlock with PIN.
Click to expand...
Click to collapse
it mightve not worked for me because i decrypted my data partition by factory reset and disabling the system to encrypt and check the partition before booting.
one of the tablets is encrypted and is using the KOO firmware, and the updating steps doesnt work either.
Ive flashed the tablets that were originally XAR firmware to KOO firmware.
im giving my inputs with my situation.
if anyone can find a way for my situtation, let me know =)

So I haven't updated my rooted tablet since the September 2020 update. Can I still jump to the latest version and still root or do I need to do some additional steps first?

still hasnt worked for me. I even went back to the tablet being encrypted.
for people who updated to DUL9 and rooted. please tell me the steps because it doesnt work for me

Can you specify the process of creating the TAR file? I patched the boot file from AP in Magisk already.
I used WinRar to make a .zip containing boot.img, then renamed it from AP-SLOT.zip to AP-SLOT.tar. Don't know if that's acceptable. I also used the "Store" compression method.
Afterwards what slot in Odin do you upload the .tar file to? I tried the AP slot but it hangs at "File analysis.....". It seems like it want a .tar.md5 file

TheCoryGuy said:
Can you specify the process of creating the TAR file? I patched the boot file from AP in Magisk already.
I used WinRar to make a .zip containing boot.img, then renamed it from AP-SLOT.zip to AP-SLOT.tar. Don't know if that's acceptable. I also used the "Store" compression method.
Afterwards what slot in Odin do you upload the .tar file to? I tried the AP slot but it hangs at "File analysis.....". It seems like it want a .tar.md5 file
Click to expand...
Click to collapse
you cant just rename from zip to tar. you have to use a diff program like 7zip to make into .tar

Great instruction. Everything is up and running and that stupid splash screen is gone. Great job, @i5lee8bit.

Late for the party...
I've found a python utility to download Samsung firmware at full speed.
It's quite easy to use:
SamLoader
[Tool] Samloader (SamFirm / Frija replacement)
Hello, I recently wanted to download some firmware for my Samsung device, but I realized that there is no 100% open source program to do so. In fact, all the tools that claim to do so require a library that is packed by Themida (so it is...
forum.xda-developers.com

Thank you @i5lee8bit this worked like a charm.
One question though, using a patched Odin is a not a requirement, is it?
Thank you @eddiefive for samloader link.

I just completed this to upgrade to Android 13 on my Tab S6 Lite. It worked perfectly. Thanks so much. I'm always amazed at the community support here.

awtompson said:
I just completed this to upgrade to Android 13 on my Tab S6 Lite. It worked perfectly. Thanks so much. I'm always amazed at the community support here.
Click to expand...
Click to collapse
I had successfully used this method to update to Android 12 (SM-P610_2_20221024120141_tk8omuwosv_fac)
I just tried updating to Android 13 (SM-P610_3_20230118120131_f9h5nltlpa_fac) and after wiping the cache step and rebooting to system, it goes into bootloop.
I tried twice, and in fact I re-downloaded everything and did all the steps just in case there was any corruption in any step or I missed something. Same thing. bootloop.
Had to re-apply Android 12 to recover the tablet.
I used Odin3 v3.14.1_3B_PatcheD
Any ideas?

badabing2003 said:
I had successfully used this method to update to Android 12 (SM-P610_2_20221024120141_tk8omuwosv_fac)
I just tried updating to Android 13 (SM-P610_3_20230118120131_f9h5nltlpa_fac) and after wiping the cache step and rebooting to system, it goes into bootloop.
I tried twice, and in fact I re-downloaded everything and did all the steps just in case there was any corruption in any step or I missed something. Same thing. bootloop.
Had to re-apply Android 12 to recover the tablet.
I used Odin3 v3.14.1_3B_PatcheD
Any ideas?
Click to expand...
Click to collapse
Not really. I did not use the patched Odin but I don't think that'st the problem. The boot after wiping cache did take long time, but no boot loops. The trickiest part is getting it to reboot into download mode after the "Try again" step. Wish I could be more help.

awtompson said:
Not really. I did not use the patched Odin but I don't think that'st the problem. The boot after wiping cache did take long time, but no boot loops. The trickiest part is getting it to reboot into download mode after the "Try again" step. Wish I could be more help.
Click to expand...
Click to collapse
Thanks, rebooting to download was easy for me, but the damn thing almost immediately would go into bootloop after the wipe, no long wait.

Umidigi A7 Pro 128GB Global [Magisk Root Help?]

UPDATE: You can now get root on the Android 10 Umidigi A7 Pro using magisk.zip v25.2 (25200).
See post 10 for more info
----------
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!

[reserved]

earlier today i managed to find a link for magisk canary. i dont have the device near me atm, but i believe the manager is v7.5 and magisk itself is v19.X. the output patch file comes out named differently with the older version (newer version appends a unique string behind the name). however, same results as before. boot loop.
one positive note tho: the patched boot file completes with a big green check rather than the runtime error, or whatever it was previously.
i tried pushing the patched boot file over fastboot and via the flash tool. same results regardless.
re-flashed the stock boot image and phone is back up and running. still no root though.
still leaning strongly toward it being a magisk problem, but ive seen mention of disabling some security features dealing with individual partitions, but that was on other umidigi models, so ill have to research further if nothing else pans out

found this tut mentioning vbmeta. otherwise, same process that ive been using with no success. figure its worth a shot. ill post back with results
rooting the umidigi a7 pro (magisk)
rooting the umidigi a7 pro (magisk). GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This guide is for advince users only! better guide comming soon on XDA (I have test this on my own umidigi a7 pro )In order to root your umidigi a7 pro you need to: 1) download device FW --> https://community.umidigi.com/forum.php?mod=forumdisplay&fid=235 (DO NOT download the EEA verison if you are not in Europe!) 2) download sp flash tool in case you brick you phone. --> https://spflashtool.com/ 3) unlock your bootloader --> https://www.getdroidtips.com/unlock-bootloader-umidigi-a5-pro-2/ 2) flash this vbmeta.img file with fastboot in bootloader mode. --> https://mega.nz/file/dnAS3AhD#g5PnSg-0UKFvyhZSZ8Em6gKO2Do7avaUepPmsH75-Bg cmd: fastboot flash vbmeta vbmeta.img 3) extract the boot.img from fw.7z file and patch it with magisk 4) flash your patched_boot.img in bootloader mode cmd: fastboot flash boot boot.img enjoy your rooted phone!!!

nope, the vbmeta thing didnt help. bootloop. i tried using the patch from the latest magisk, and the patch from the older version of magisk. same across the board.

double b26 said:
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!
Click to expand...
Click to collapse
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.

[RESOURCES]
magisk download archive
Download Latest Magisk zip v23.0 and Magisk Manager 8.0.7 and Root your phone
On this page, we will share the full instructions to download and install Magisk zip on your Android Phone. This tutorial is also for the newbies/noobs
www.getdroidtips.com

19deke55 said:
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.
Click to expand...
Click to collapse
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.

double b26 said:
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
Click to expand...
Click to collapse
Thanks. The Mediatek side of things is interesting as I have at least one Lenovo tablet that uses them and the Kindle Fire tablet I have also. Such a pain that manufacturers have went down the road of locking bootloaders the way they have. It used to be so easy to install ROMs. Oh well. C'est la vie.
Thanks for the info. I can't see me touching the Umidigi now for a couple of years. It would be more than my life's worth, lol. I'll copy the contents of your post for future reference.
Have a nice day. Hope you have success with your efforts and that your satellite connection improves.

I GOT ROOT !!
Sorry, I forgot to update this thread...
Bottom line is that there was a bug in magisk. It has since been repaired, and root procedure works 'as advertised' using magisk.zip v25.2 (25200)
After having no luck, I gave up. A few months later I tried again after reading about how magisk had a recent bug fix that sounded like it might have been the problem for this Umidigi. So, I grabbed a new build of magisk .zip, followed the tutorial, and it worked as expected. Pretty simple, once you have the resources ready. Not to mention, a windows 10 pc is all you need to get it done.
---------
My Metro by T-Mobile plan is no-cap-LTE, but doesn't have a hotspot allotment. I'm using a 'hotspot unlocker' magisk module to give me access to the hotspot. I believe it stops reporting hotspot activity back to the ISP, but I'm not sure. Regardless, I use a lot of hotspot data every month, but not a peep from the provider.
In conjunction with that, I'm running "VPN Hotspot" to tunnel hotspot traffic thru my phone's VPN connection. Otherwise, tethered data bypasses the VPN. The app is on play store and requires root.
I'm using the phones hotspot to serve data across to an old dd wrt router I have set as a repeater bridge. It runs a virtual wifi network, and other devices sign into that network. From there, behind the router, it operates as a normal home wifi network. Smart TVs, Chromecast, and all your tablet apps work as expected.
----------
I'm also running a few other modules, like viper audio. So far, so good. Really can't complain for a cheap device. It even gets decent battery life when serving data. About 10% per hour, avg running, but can go further if not running a VPN and close background apps .
---------
I'll look on the PC and see if I can compile a list of software, drivers, etc that were needed.