Trying to alter a stock ROM and resign with my own custom key just for myself. This process will allow me to use a device with custom changes (NOT root), but still allow me to use Android Pay.
This process involves using the "make_ext4fs" tool. However, this tool (as far as I can tell) requires using the old plaintext version of "file_contexts". Android 7+ uses a new binary version of this file instead ("file_contexts.bin").
So if anyone can solve either of these questions, I would be very grateful:
1) Is there a tool to convert my device's binary "file_contexts.bin" to the old plaintext "file_contexts"? -OR-
2) Is there a build of "make_ext4fs" that accepts the new binary format "file_contexts.bin"? I tried to build the new nougat version myself from AOSP, but after a successful build of the tool, I can't get the thing to read files on either 64-bit or 32-bit systems. It yields an error "No such file or directory" when trying to point to file_contexts. I am not a great C developer, so I don't know if I built it wrong. For reference, no, I am not missing the lib32stdc++6 libraries. I have attached the binary if you want to see if you can get it to work. -OR-
3) If anyone has the file_contexts text file for the OnePlus 3, ROM version 7.X Nougat, that would work too!
Any help anyone can offer in any way would be fantastic! Thank you so much for your time to look at this!
A good question
1) yes, see my signature
munjeni said:
1) yes, see my signature
Click to expand...
Click to collapse
I'm trying to do the same with a 7.1.1. rom. I convert the file_contexts.bin to file_contexts, unpack the rom, do the modifications to the rom, repack the rom then replace the original system.new.dat and system.transfer.list with the newly packed ones (original file_contexts.bin is still in the original zip) and when I go to flash it in TWRP it doesn't flash the system and I get a No OS installed Is there something I have to do to the file_contexts.bin after I repack the system.new.dat?
"file_contexts.bin" to the old plaintext "file_contexts" tool: http://blog.cofface.com/archives/2255.html
puargs said:
I tried to build the new nougat version myself from AOSP, but after a successful build of the tool, I can't get the thing to read files on either 64-bit or 32-bit systems. It yields an error "No such file or directory" when trying to point to file_contexts. I am not a great C developer, so I don't know if I built it wrong. For reference, no, I am not missing the lib32stdc++6 libraries.
Click to expand...
Click to collapse
Try building with the pie (Position Independent Executable) flag. Had this exact same problem when trying to compile a CVE for android.
Hopefully this should work for you and sorry for the Necro post
So there's threads about how to unpack UPDATE.APP on windows/PC/OS X so i decided why not do it on android too, this apps requires some additional tools to be downloaded just as OS X/Windows and linux needs as well. but process is otherwise similar. this tutorial doesn't need root!
NOTE THIS TUTORIAL isn't fully working on OREO on Huawei devices, it has some issues and i haven't found a workaround for it yet!
Needed apps
Termux https://play.google.com/store/apps/details?id=com.termux
Recommended apps
Hacker keyboard
Needed files
https://github.com/atarii/split_updata.pl/blob/master/splitupdate
@Atarii 's modification of splitupdate to manually enter the partitions you want to unpack
The desired FW you wan't to unpack
Unpack process:
Download Termux
Open termux and type
termux-setup-storage This will allow termux to access your /sdcard
pkg install perl (this will install perl which the update.app process is using) once asked press y and enter.
copy the downloaded files to root of your SDCARD *We keep this simple*
Once copied type: cd storage
perl splitupdate UPDATE.APP partitionyouwanttoextract if everything goes well you should be good to go and having the selected files in a folder called output where selected files should be stored.
The unpack tutorial is done. But wait! If you want to browse the files you need to do one more thing or two.
Download android image kitchen
https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
This will allow you to *unpack boot/recovery and convert system image (also vendor, product, cust and version)
*in order to unpack a boot or recovery file you'll need to remove all code using a hex edit file until you see ANDROID text. Else it won't unpack. You can unpack aosp images easily with this tool and modify what you want and repack to flash it on your device tested with twrp image for honor 8.
I would suggest to not unpack/repack boot using this tool since it'll cause problem.
There's a python script that works to unpack boot and recovery which can be found https://github.com/liudongmiao/bootimg/blob/master/bootimg.py
For this you'll need to install python.
pkg install python and hit y and enter
Now you just do as the splitupdate part where you extract the file.
Command to unpack
python bootimg.py --unpack-bootimg similar is for ramdisk but you replace bootimg with ramdisk.
To repack just simply python bootimg.py --repack-bootimg
Please note if you repack ramdisk the boot might not work (it's a while since I tested this) now this covers up how you unpack boot and extract update.app from phone.
Credits to @Atarii for telling how to unpack boot on phone and for his custom splipupdate script
Sent from my FRD-L09 using Tapatalk
Known Issues:
If you get Killed when trying to extract system.img this is most likely because the image size is too big, this isn't due to small space available i guess its due to all ram is being taken yet i can't tell.
i get permission issues. yeah this can happen sometimes try chmod +x or chmod 0777 with root, it might help.
when typing termux-setup-storage i get lots of errors and i'm on 8.0 EMUI
This is not your fault it's a bug caused by android i'd guess, or app isn't adopted completely for 8.0
Hello, I think I found what is the issue with WiFi - Vendor configs don't change WiFi Country code but they do change region and that causes the WiFi error. I was able to unpack the .RAW file to a normal folder and then the system.ISO where I was able to edit the build.prop and vendor props.
I prepared a few methods on how to edit the ROM to make WiFi work:
A) Changed the country code in the build.prop to a chosen country [you won't be able to use WiFi abroad of that country].
B) Edited all the vendor props to change WiFi country code to according countries [should work everywhere].
C) Removed the country code line from build.prop files [may work everywhere or nowhere]. -checked more files in the system and came to conclusion that this method won't work
The edited ROM will have to be flashed using Qualcomm flashing tool as there's no way to repack it to .RAW file.
For testers:
Before flashing copy all your files as they will be removed. Also mind the fact that I don't know if this will work or brick your device [if it does brick it then you can flash an unedited ROM to fix it].
Tutorial how to build your ROM:
1. Go to: https://drive.google.com/open?id=1Iph9eTL6dU_x_LAOt7Z9PN7KbwCAHACn
2. Download V570KL.rar
3. Go to Done2 folder and download system folder and IMG_EXTRACTOR_3.1 software from there. [For extractor software you'll have to download Java and Python]
4. Go to main folder and then go to Patch folder and go to Method C folder and download the folder with your country name [if it's not there contact me].
5. Locate your downloaded files and place them into one folder for easier work on them.
6. Unpack V570KL.rar
7. Copy build.prop file from country name folder and replace the build.prop in system folder with it.
PATCHING system.IMG
8. Open Img_Extractor [you need Python and Java for it to work], choose system.IMG and select Repack option. Now locate the edited system file. When it's selected check the byte number if it's the same as the one that system.IMG in V570KL folder has. If it's the same click Repack and wait till it does it's thing. [If the number is not the same edit it to the same number].
9. Replace the system.IMG in V570KL folder with our patched .IMG file.
PATCHING recovery.IMG
10. Reopen Img_Extractor software and choose recovery.IMG option.
11. Locate recovery.img [it's in V570KL folder].
12. Unpack the file, after unpacking locate the unpacked folder and go to initrd folder that's inside of it and there replace default.prop with default.prop located in country patch folder.
13. Go back to Img_Extractor and repack recovery.IMG
PATCHING ROM
14. Prepare edited system.IMG and recovery.IMG
15. Open V570KL folder and paste our patched IMGs in there [replace the old ones or remove them].
16. Our ROM is now ready.
*note - Img_Extractor has to be run with Admin rights to properly unpack/repack the files.
Flashing Tutorial:
QFIL flashing won't be possible as I couldn't get the needed Firehose file for it to work. There is however a Firehose file for V520KL [Asus Zenfone V] which might work but it's pretty risky to do.
A much safer method then will be to flash V570KL ENG rom first with Asus Flashing tool and on this rom we'll be able to unlock bootloader [open path to flashing edited roms].
There's also the VZW Repair Tool that could help us flash the phone, after the phone is detected the software will download OG Verizon ROM that can be replaced [in our case with the ENG ROM], after it's installed we will be able to flash the edited one.
Flashing tutorial downloads:
Asus Flashing Tool - https://www.asusflashtool.com/ [download version 2.0.1 and put your phone into recovery before connecting it to PC]
VZW Repair Tool - https://drive.google.com/drive/folders/15KAGi4XeKf8lwuJ46XO5LZ1mZLM7f5V1
V570KL ENG ROM - https://drive.google.com/open?id=1cizBJWHG1oDduMcImWAE_jSsbfQ5TJi6
Built ROM downloads:
MethodA - UA + camera2api + removed verizon features - https://drive.google.com/drive/folders/1g7jbq2UxQC1XFzqCUjfCa1XIVq23Vs14
MethodB - universal* + camera2api + removed verizon features - https://drive.google.com/drive/folders/1OYNjKjV8H2mhRpdyROgLCM7AeIxj0emw
MethodC - universal - not releasing
MethodC2 - universal + camera2api + removed verizon apps and features - not releasing
universal* - may not work in Ukraine and Russia as there were no vendor files for those countries in the system, however there was a file called EUCommon that may make it work
Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*
Hi friend, I have this phone. I will be glad to work together, I could not do everything according to your instructions. I guess I don't understand English well. I will be happy to work with you with the help of a team viewer. Please contact me
I edited the ROM but I don't know how to flash it, previous flashing methods for this model don't work anymore because of Asus disabling the only flashing tool with V570KL model, V2 doesn't support this model. I also thought of replacing the .RAW files in Verizon repair tool but I don't know if that would work, can't check that.
Anyway I added ENG rom link.
Hello!
So I just bought this phone online so my son could use Daydream. I'm not on Verizon and the plan was to just use WiFi. Well... I have the WiFi problem. I have worked though multiple other methods to try and find a fix and nothing has worked. I'm at the point where I'm about to try OP's method. Because of the possibility of bricking the device, wanted to check in first to see if anyone has continued to work on the problem or if there are any new developments. Once I make the decision to attempt, I will check in and after to let you know what happens.
Thanks!
Rk
Anyone know how to fix wifi issue on my v570kl without breaking it? I'm from ukraine.
Hi! I need your help solving WiFi problem for V570KL for country "UA". I downloaded your rar file from Google Drive along the path "Asus/Patch/Full_MethodA [Ukraine]/UA [Ukraine]/V570KL_edited.rar".
What do I do next? As I understand it, I need to launch the Asus Flash Tool, enter the phone in the recovery and connect the cable to the computer, then select the V570KL_edited.rar file and start flashing. I am asking for your help.
Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.
SlenderPL said:
Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*
Click to expand...
Click to collapse
After giving up for today, I decided to try this path, and...at least using standard unlocking methods, phone doesn't seem to understand what's happening, haha
ASUS guys really wanted to make this the most impossible, don't they?
Pedreo1997 said:
Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.
Click to expand...
Click to collapse
Update 5 - 16:40 VET / 2023-01-07
I took a break for a couple days for returning to this hell, and... let's see the progress so far:
* ASUS Zenfone Flash Tool V2.0.1.0 is doing nothing to help.
* I investigated there is a way to flash manually (using fastboot) the whole system, so it should be helpful, I think.
* Using a tool our friend SlenderPL left in the GDrive folder 'Asus Tool (RC4)', I unpacked the whole .RAW file. That was at first thinking into creating a .zip file to attempt another way to flash the ROM, but then I did found apparently it has more success chances trying to flash the stock rom, file by file, using 'fastboot flash' command, file by file. However, of course I need the tree, the .xml, the .bat file that tells me the order of how flashing it. It doesn't exist.
Right now I have a folder with the whole .RAW totally unpacked.
* I tried to force flashing, entering into Recovery, and then using sideload, writing:
adb sideload V570KL_all_WW_eng_T3.0.3.raw
Click to expand...
Click to collapse
of course, after placing the .raw file in the same folder of platform-tools on the computer. The phone did read the file, but again I got an error 'E:signature verification failed'.
Let's see whay newer idea I get...
Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?
wivelt said:
Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?
Click to expand...
Click to collapse
I think it's on the edge of fantasy. Try to do it, and if it works, write a detailed guide. I will be extremely grateful!
First, to clarify, the last time I rooted anything was a Galaxy S3 back in the day. I'm by no means an expert, I just figured I'd help out folks like me that haven't touched all these new tools, well, ever.
Just did this myself earlier today attempted to get Magisk root, but alas, I got stuck in a boot loop. Luckily I had muddled through getting the image first, otherwise I'd still be stuck in said boot loop. I figured I'd post this for anyone else trying to root these things just to make sure you have a backup you can trust (I generally don't trust rando images that folks post online). All of the instructions below are assuming you're on Windows 10 and using PowerShell just because that's the default these days. Without further adieu.
Download ADB/fastboot (on your Windows machine)
I downloaded adb/fastboot from google directly: https://developer.android.com/studio/releases/platform-tools
Just extract and browse to the platform-tools directory in Windows Explorer until you can see adb.exe and a bunch of other tools
Download the latest SP Flash Tool
I just grabbed it from here: https://spflashtools.com/
Please let me know if there's an "official" place to find SP Flash Tool, cause everything surrounding all the download sites seems a bit sus...
Enable USB Debugging (on the tablet)
Go to settings -> About tablet
Tap the Build number 10 times (until debugging mode unlocks)
Hit back and go to System
Click Advanced and then Developer Options
Enable USB Debugger
I also enabled OEM unlocking because the whole point of this is for me to run either AOSP or Lineage someday. I honestly don't know if unlocking the bootloader is needed for dumping your own images, but I highly suspect it's not.
Plug the tablet into your computer
You'll likely see a prompt on your tablet about allowing your computer to debug your tablet. I just checked the box and hit accept so I wouldn't see it again.
Get your scatter file (on your Windows machine)
I tried several things to get the scatter file (I guess this is like a partition table based on the contents I saw) but in the end, by far the easiest way was to just download the scatter file from the file system.
In the Windows Explorer window from before (platform-tools), hold down shift while left clicking and click on Open PowerShell window here
Now type the following to get a shell on your:
.\adb.exe shell
This will get you into the shell environment. Now type the following to verify your scatter file is there:
ls -al /system/data/misc/
In here you should see something like:
-rw-r--r-- 1 root root 13893 2008-12-31 19:00 MT8168_Android_scatter.txt
Now that we have the name, just type exit to get out of the shell
Download the scatter file
.\adb.exe pull /system/data/misc/MT8168_Android_scatter.txt
Open up the scatter file in your favorite text editor (for me, Notepad++)
Now you can see the partition layout, offsets, etc, etc
Dump your image(s) (on your Windows machine)
Now open SP Flash Tool (flash_tool.exe)
On the Download tab, make sure the Download-Agent is MTK_AllInOne_DA.bin
Now click Choose for the Scatter-loading file and browse to the scatter file you just downloaded
This should be in your platform-tools folder unless you moved it
Once the scatter file is loaded, the partition table should fill up with a bunch of partitions
Click on the Readback tab
Click Add
Double-click on the new entry
Navigate to where you want to save your image, and give it a name (in this case I'm starting with boot.img)
Remember how you opened the scatter file in a text editor? Search in the scatter file for boot.img
Make sure the region matches (should be EMMC_USER) between the scatter file and SP Flash Tool
Copy/paste the value for start_addr in the scatter file to Start Address in SP Flash Tool
Copy/paste the value for partition_size in the scatter file to Length in SP Flash Tool
Now do the same thing for recovery.img and any other images you'd like
If you want a full ROM backup, name the file something like ROM_0, then use Start Address of 0x0 and length as the start_addr for the second-to-last entry in the scatter file (in my case, it was 0xc1a80000, just make sure it doesn't start with f's)
Note: I don't know for sure if this is accurate or not, I'm still playing with it, but so far it appears to be. Probably?
Poking around in WwR MTK 2.51, it looks like for this particular device (100011885) I wanted a total dump of 0x73A000000. It looks like this number is derived from the first 8Mb of the EMMC_USER dump, so I'm not sure of an easier way than throwing WwR MTK at it for the moment.
Once you've got all the entries for what you'd like to dump, make sure to disconnect the tablet from your computer and power it off
Now click on Download in SP Flash tool
Once things grey out, then plug the tablet in. After a few seconds, you'll see the images start dumping.
Congrats, you have a boot.img (and whatever other images you wanted). Like I said, from here I tried using Magisk to patch the boot file, but when I flashed it in fastboot, after enabling OEM unlocking in Developer Options, it just kept popping up the initial Onn graphic along with the Orange State warning without getting to the "fancy" Onn graphic and the rest of the boot process. I was able to flash the original boot.img back and it once again booted properly again.
Also, for anyone interested, I've posted my dumped files for the 100011885 in my google drive: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
Maybe someone will have pity on me and figure out why Magisk isn't working?
Whenever I get a moment, I'll dump my 100003562 as well.
First, thanks a ton for this. I have been trying to pull a full system dump since I bought the tablet and had resorted to single pulls by name(very long and involved) I don't know if this will work for you, but on both of my 7 inch Gen 2 tablets, I just sideloaded Magisk Manager and then opened it (this was after unlocking the tablet) When I first opened MM it just said it needed to download some additional files for my environment. I clicked okay, it downloaded and installed the additional files. Once it rebooted, I open MM again and clicked install Magisk. On the next screen, I clicked direct install and let it do it's thing. After rebooting, root checker showed I had root, but I still can't get it to pass safetyNet. Root access does work as I have installed a few modules and busy box.