Database Info

[RESEARCH|MT8127] Bootloader hack ideas for LeapFrog Epic

I dunno, but I thought maybe I could make a separate thread about a possible way to poke into the LeapFrog Epic's preloader so it could accept unsigned images. LeapFrog won't spill the beans for us, as their staff (falsely) claims to know next to nothing about it, so unless we somehow managed to social-engineer them into giving us a signed ROM or an unlocked bootloader, our only chance is to patch it so it would ignore the lack of digital signatures.
What I've done so far is to run a strings check on the preloader and uboot binaries - fastboot seems watered down somehow as it lacked references to "oem unlock" and so on, but none of that Amazon Fire-style failsafe seems present from what I can tell.
Preloader: http://pastebin.com/H9QbzqC0
lk: http://pastebin.com/kSxRKYna
Boot files from the latest firmware revision are attached here, so if anyone is interested, please please please let me know so we can fix bricked units and finally port TWRP to this underrated kids' tablet.

blakegriplingph said:
I dunno, but I thought maybe I could make a separate thread about a possible way to poke into the LeapFrog Epic's preloader so it could accept unsigned images. LeapFrog won't spill the beans for us, as their staff (falsely) claims to know next to nothing about it, so unless we somehow managed to social-engineer them into giving us a signed ROM or an unlocked bootloader, our only chance is to patch it so it would ignore the lack of digital signatures.
Click to expand...
Click to collapse
Bumping the thread.
Would also like to know is this is possible
If I may ask, how did you extract the strings from preloader and lk? Did you use a hexeditor or there is another app?

Gibz97 said:
Bumping the thread.
Would also like to know is this is possible
If I may ask, how did you extract the strings from preloader and lk? Did you use a hexeditor or there is another app?
Click to expand...
Click to collapse
I used this utility to do a strings dump off an Epic ROM:
http://split-code.com/strings2.html
It did turn up some interesting stuff but I was wondering if a binwalk or perhaps an IDA disassembly analysis would do wonders so we can finally poke into this tablet.

blakegriplingph said:
I used this utility to do a strings dump off an Epic ROM:
http://split-code.com/strings2.html
It did turn up some interesting stuff but I was wondering if a binwalk or perhaps an IDA disassembly analysis would do wonders so we can finally poke into this tablet.
Click to expand...
Click to collapse
Thanks for the tool but I cannot seem find a way to use it.
 @gursewak.10 or @smartmanvartan please chime in to help us because they were able to hack the preloader of k4 note and lk of RCA Viking Pro respectively

I also know a friend who is willing to donate a spare Epic, if that helps.
As for using Strings2, the following batch script should work:
Code:
@echo off
strings2 %1 > test.txt
pause
Just drag a binary to be analysed into the batch file, and a resulting text file with strings and stuff should be generated.

Hello friend
You need to tweak lk to unlock bootloader . i am giving you my phone's both files(.you can easily compare them.
on unlocked bootloader u can flash unsigned images via write memory option of SP flash tool .
Try HxD hex editor

gursewak.10 said:
Hello friend
You need to tweak lk to unlock bootloader . i am giving you my phone's both files(.you can easily compare them.
on unlocked bootloader u can flash unsigned images via write memory option of SP flash tool .
Try HxD hex editor
Click to expand...
Click to collapse
Hmm, I can flash the preloader to my leapfrog via SPFT, but not anything else. Write memory works, and I can flash stuff one at a time to it, but I couldn't get the tablet to force itself out of flash/download mode and into normal mode. There's no reset button, and not even taking the battery off does the trick.

However, on my working Epic, I can alter the demo system image, flash it back using Write Memory and still end up with a working device, just as long as the preloader isn't messed with in any way. Right now I am at a loss as to how to revive my other Epic, short of taking it apart and shorting KCOLO and GND. It also didn't help that the testpoints aren't labeled at all. :/
Also, I did a quick logcat while running the FOTA utility, and I managed to get a few URLs off the said logs. Problem is that while the ZIPs may be of some use, they're incremental and there doesn't seem to be a full scatter/zip image to restore a faulty unit. There definitely needs to be a way to patch the bootloader so we can do whatever we want to it, but is there any one of you guys who are experts when it comes to MTK modding?

Any more ideas?

Anyone, please?

Bumping in case there's anyone interested in poking into this.

Now this is interesting let us see what we can do.

Warrior1988 said:
Now this is interesting let us see what we can do.
Click to expand...
Click to collapse
You happen to have an Epic with you? Please let me know if you need more than just the firmware images. I've tried contacting LeapFrog regarding this issue to no avail. They did give my friend and I the kernel sources, but it's no use as the bootloader has to be unlocked for custom boot or recovery images to be used.

Is anyone willing to test if SP Flash Tool 5.1532.00 works on the Epic? I managed to flash a complete system image to a bricked Epic but I was unable to revive it as it has been bricked prior due to a botched preloader flash. The ROM's on my main Epic discussion thread, but one should take note to flash just the boot, recovery and system images and see if the device still works.

im also poking around in this since my volume up button doesnt work in bootloader mode
i have a figo gravity x55l
i can also upload the stock rom files that can be checked if needed

SP6RK said:
im also poking around in this since my volume up button doesnt work in bootloader mode
i have a figo gravity x55l
i can also upload the stock rom files that can be checked if needed
Click to expand...
Click to collapse
Are you able to muck around with LK or sbchk using IDA Pro or some other tool? Makes me wonder if merely deleting /system/bin/sbchk would disable boot-time checks or if there's more to it than just that.

blakegriplingph said:
Are you able to muck around with LK or sbchk using IDA Pro or some other tool? Makes me wonder if merely deleting /system/bin/sbchk would disable boot-time checks or if there's more to it than just that.
Click to expand...
Click to collapse
well i tried hex editors but lk.bin isnt decoded for my rom so half of my lk file is not showing me anything exept weird characters but i can see some of the other half.
if you delete the file...will it brick?...will it even boot?

GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
What device are you referring to? Is this for an MT8127 tablet?

blakegriplingph said:
What device are you referring to? Is this for an MT8127 tablet?
Click to expand...
Click to collapse
i have a figo gravity x55l ? and it is not a tablet
it is a mt6753 great phone btw!
im a starting developer and got this phone so i can learn from my mistakes of course?
but this should work on any device that you can get a hold of its boot.img from its firmware

Current ROOT Progress for G950U/G955U Snapdragon

***if using XDA labs app, please stop, select the 3 dot menu button in the top right, and view this thread from browser because of formatting issues with the labs app. This is to help make the OP easier to follow along with. ***
**Please Read First**
This will be the main, and ONLY thread we will keep updated for the progress of root on the Snapdragon variants of these phones from here on out.
As the other few threads are multi topic and confusing for people anticipating root, as well as for us working on it trying to sift through comments to keep each other updated. Those will be cleaned up to avoid confusion as well. This will make it easier for everyone to check back to see any new progress as I will be updating the OP whenever we make movement
**First, and foremost, I would like to recognize and thank @STF_TimelessGoD for his work on the initial post R&D Carrier Switch/Root Snapdragon. Without his time and effort putting that thread together and maintaining it, there would still be a lot of unanswered questions and we probably would not be as far as we are**
That thread will still continue for the Carrier Switching and a full guide is available at this link
[HOW TO] Carrier Switch For S8 Snapdragon
---------------------------------------------------​
Current Root Progress
We are currently working on 2 main possible methods for this. Refer to each method in RED below the Key Notes.
Please, if you do not know what terms are, or what files are, Google search them to avoid filling the thread with easily answered questions​
*UPDATE* 1 - 6-19_2:34pm CST
We are looking for relevant files to properly flash from EDL Mode. IF anyone can get their hands on these 3 files, specific for our chipset, PLEASE let us know.
The first 2 are the main needed, as the provisioning can possibly be made from provisioning info already on the phone.
- prog_ufs_firehose_8998_ddr.elf
- prog_ufs_firehose_8998_lite.elf
- provision_samsung.xml
*UPDATE* 2 - 6-19_9:00pm CST
We have aquired the necessary Elf files from above. Now doing more research on proper ways to use them as they are qualcomm/device specific
*UPDATE* 3 - 6-22_1:34am CST
Much much time spent combing through code of these files and tools that are able to handle them. As well as the verification process andriod uses in conjunction with qualcomm between all 3 bootloaders and the Learned a lot tonight.
We learned enough to be able to begin some new tests tomorrow that is not the same as either of the methods below. However I cannot at this time divulge the method being used and for that I am sorry!
*UPDATE* 4 - 6-28_4:35pm CST
We studied up a lot on our selinux and the way that Nougat 7.0 has changed how security works and are currently working on adb permissive with *a debuggable user* kernel. Refer to Update in key notes for more info.
-METHODS UPDATED WITH METHOD 3
Key Notes
In general order of them happening/being found out.
- Pre Release Combo Firmware is only known Firm to contain Allow OEM Unlock and have SELinux set to permissive by default. However, @elliwigy went through this thoroughly and found that permissive did literally nothing to help elevate privileges as it should have, and that the OEM unlock check box didn't seem to have any effect on secureboot.
[*]- Received multiple ENG Boot files, none of them contained system write capabilities as they should have. So they were no help. Someone (leaving names out) said they had ENG Boot with full root access that he would share, but stopped all involvement in the thread and we never heard back from him. Generally, just about always, an ENG Boot has system write capabilities, as that's the point of an Engineering Kernel.
[*]- SELinux Permissive was acheived on Stock firmware by @STF_TimelessGoD but it caused the phone to not charge past 80%. Trying to get into su shell from adb says it is started as root, but doesn't actually enter root shell. @elliwigy tested this out as well with the same results. Otherwise same problems as above.
[*]- @elliwigy got ahold of an actual ENG Boot, however, trying to flash from Odin and phone returned "This is ENG binary. Please use USER binary! (boot.img)". Meaning 2 things. 1, it is a true ENG Boot with system access, and 2, Samsung really stepped up their security
[*]- Chainfire Auto root does NOT work on our devices. To be clear, Chainfire's website has a bot that auto-compiles for all new devices regardless of it being capable or not. He did take a look at our device, but decided he wasn't going to spend the mass amount of time on it that is needed, like we currently are!
[*]- Next we looked at multiple security vulnerabilities that would allow escalated privileges(access to the system) Ended up deciding against this as we do not have a dev on the project with exploit building knowledge.
[*]- I brought up EDL mode as a possibility. Which is not suppose to be supported on Samsung as it needs fastboot, normally. Without fastboot, you are suppose to use a proprietary edl cable(easily made) to force your phone into it. Which still was thought to be unaccessable on Samsung. After a lot of research on how it SHOULD be done, we had mixed results. Until @BotsOne by chance found you could get into EDL from adb command line with the phone on. So this is part of one of our methods below.
[*]- I'm looking at modifying a serial flash tool to know the partition table of our devices, to make EDL mode properly work for us. This is so we can flash individual partitions and not the whole system.
[*]*UPDATE* 2 - No need to modify a serial flash tool, as using the Elf files from earlier takes care of that work. Working with them now to fully understand and operate with them
[*]*UPDATE* 4 - With the help of a fellow dev , @akiraO1 that has much more selinux experience than us, we were able to get a foot in on changing things and making our selinux fully permissive. There is a prop setting that made it kind of tight. but changing persist.security.ams.enforcing *AND security.perf_harden* to 0 fixed most of this. But there is still much more as the fstab inside the boot.img has system set to ro. We are working on this, but things are looking up
METHOD 1
Flashing Modified Bootloader Via EDL Mode
Modify a current serial flashing tool (such as the Mi flash tool) to include our partition table and options to flash to certain partitions individually
Modifying the bootloader source code to to be unlocked, then flashing unlocked bootloader via EDL
At that point we could Odin Twrp and then flash whatever we wanted
METHOD 2
Flashing True ENG Boot Via EDL Mode
- As the first method, would need to modify a serial flashing tool for this.
- First check would be to flash the True ENG Boot to the device via EDL.
- Then check if it boots because you can't Odin the Eng Boot without it failing as stated in key notes above. Because EDL has elevated privileges, it will flash to the device, but we have to see upon starting, if it will still binary check and stop from booting.
- If it boots, we should then be able to access su shell, and run a batch to obtain system root as usual.
METHOD 3 - Update 4
Modifying Boot Parameters with SELinux
- Using the permissive boot that we figured out proper capabilities
- Gain access to proper partitions to make the phone load a custom selinux profile that allows rw to system
- Mount system r/w and install su binaries via adb
- Modify remaining parameters needed within boot.img and create a runnable script for everyone!
^^EVERYTHING ABOVE WILL BE UPDATED AS PROGRESS IS MADE, WITH EDIT DATES. JUST LOOK FOR THE WORD *UPDATE* NEAR RELEVANT AREAS.^^
All Relevant Files, Hosted Courtesy Of @Maltego
- CLICK HERE -
------------------------------------------------------------------------------------------​
Current Contributors
@elliwigy
@Maltego
@STF_TimelessGoD
@BotsOne
@mweinbach
+ @akira01
+ @Harry44
**If you would like to help or contribute in any way, please message me.**
It may take a bit to get back to you, and for that I apologize
---------------------------------------------------------------------------------------------​
**Please be patient with us as this is not a simple task and it is not a standard root method that has ever been used on Samsung as EDL was not previously available**
.

**reserved**
IF YOU ARE LOOKING AT THIS FROM THE XDA LABS APP, YOU WILL OF COURSE NOTICE THE LACK OF COLORS AND SLIGHTLY AWKWARD FORMATTING.
-This is an issue with the apps ability to parse bb code format. And I cannot fix that. So just try to look for the update tags or use web browser. Sorry for the inconvenience

We will keep working on root guys. Do not worry. We are as close as you will get to professionals.

Nice job claryfing where we are and seperating the 2 threads, I think this was greatly needed.

Nicely constructed thread showing our progress, good job!
Also this came to my mind, what about flashing those ENG files @elliwigy got through EDL mode?

Interceptor777 said:
Nicely constructed thread showing our progress, good job!
Also this came to my mind, what about flashing those ENG files @eliwigly got through EDL mode?
Click to expand...
Click to collapse
We thought of that. We are missing 3 files we need.

mweinbach said:
We thought of that. We are missing 3 files we need.
Click to expand...
Click to collapse
Ah, I'm assuming those are EDL programmer files?

Interceptor777 said:
Ah, I'm assuming those are EDL programmer files?
Click to expand...
Click to collapse
Correct!

Interceptor777 said:
Ah, I'm assuming those are EDL programmer files?
Click to expand...
Click to collapse
Yep. We need $3500 to get into Samsung GSPN. So we are working on alternative methods.

mweinbach said:
Yep. We need $3500 to get into Samsung GSPN. So we are working on alternative methods.
Click to expand...
Click to collapse
Not necessarily that was just that one person i got a reply from another last night waiting to see the price

STF_TimelessGoD said:
Not necessarily that was just that one person i got a reply from another last night waiting to see the price
Click to expand...
Click to collapse
well, for now. thats what we need.

Glad to know that brilliant brains are working on the root. This rooting procedure will only be for G950U/G955U, and not for the Canadian variant G950W?

sky66high said:
Glad to know that brilliant brains are working on the root. This rooting procedure will only be for G950U/G955U, and not for the Canadian variant G950W?
Click to expand...
Click to collapse
It should work for Canadian Varient. We will update everyone when we get root.

Interceptor777 said:
Ah, I'm assuming those are EDL programmer files?
Click to expand...
Click to collapse
STF_TimelessGoD said:
Correct!
Click to expand...
Click to collapse
Do EDL programmer files from same chipset is enough?

If you can get use edl programme files from msm8998 chipset we will be golden

Yay new post to follow. Thanks.

yxexy said:
Do EDL programmer files from same chipset is enough?
Click to expand...
Click to collapse
Do you have access to said files? If so please pm the op.

Interceptor777 said:
Ah, I'm assuming those are EDL programmer files?
Click to expand...
Click to collapse
I was going to add those to the OP. Spent like 4 hours on the OP because I had to scroll the original thread. And still work on everything at the same time. I got burnt out and slightly forgot. Will add those within the next few hours

sky66high said:
Glad to know that brilliant brains are working on the root. This rooting procedure will only be for G950U/G955U, and not for the Canadian variant G950W?
Click to expand...
Click to collapse
As stated above, this should theoretically be for all snapdragon variants. Minus the g9500 which is the Chinese "duo" version. As they aren't compatible with Google play *as far as I know*
Things may change and we may end up needing extra testers for verification

Acoustichayes said:
As stated above, this should theoretically be for all snapdragon variants. Minus the g9500 which is the Chinese "duo" version. As they aren't compatible with Google play *as far as I know*
Things may change and we may end up needing extra testers for verification
Click to expand...
Click to collapse
Wait what? You have something in the works that works?

rooting DigiLand DL7006 - how?

I have tried the one click solutions and I'm getting nowhere. Even the shady ones don't work. Is there any word on rooting this tablet?

I just got my DL7006 and haven't gotten rooting to work either with the mainstream one-click root systems. Am trying to go the ADB shell route now, but I need to find the TWRP image (whatever that is). I'm a LINUX/UNIX person and I find this Android stuff REALLY frustrating.

I'm also looking for TWRP for DL8006. Unlocking the bootloader was easy.

I've unlocked the boot loader and nothing works either. I have the firmware sent to me directly from Digiland, but even with SP flash and MTK tools I can't seem to get anywhere. I'm no pro, that's a fact, but I've managed to gain root privilege on many devices that mainstream one clicks won't work on. This sucker just won't give up the ghost! If anyone can do anything with the FW I'd be happy to share it. If u make any progress all I ask is share the hell out of it!!

looking to root my DL8006 as well...

lsr992 said:
I've unlocked the boot loader and nothing works either. I have the firmware sent to me directly from Digiland, but even with SP flash and MTK tools I can't seem to get anywhere. I'm no pro, that's a fact, but I've managed to gain root privilege on many devices that mainstream one clicks won't work on. This sucker just won't give up the ghost! If anyone can do anything with the FW I'd be happy to share it. If u make any progress all I ask is share the hell out of it!!
Click to expand...
Click to collapse
If you have the opportunity to send that my way I can give it a shot because this is the tipping point of purchasing to see if it had root, and it is something i really want

Firmware
https://drive.google.com/file/d/1NXzgtfMXj_a0jZ5yrIZyQCq0fyDGpW4O/view?usp=drives
https://drive.google.com/file/d/1IASKKK_Y2yrPCZpvNIShRLxOGotfuKKE/view?usp=drivesdk
See if those work. They are the 2 digiland sent. Keep me posted please!

So there is an unofficial TWRP for one of the 2 firmwares for the dl7006 on the TWRP builder page. I submitted both boot.img files. I can't get it to work. Maybe someone else can.

lsr992 said:
I've unlocked the boot loader and nothing works either. I have the firmware sent to me directly from Digiland, but even with SP flash and MTK tools I can't seem to get anywhere. I'm no pro, that's a fact, but I've managed to gain root privilege on many devices that mainstream one clicks won't work on. This sucker just won't give up the ghost! If anyone can do anything with the FW I'd be happy to share it. If u make any progress all I ask is share the hell out of it!!
Click to expand...
Click to collapse
I figured a way to install magisk, no custom recovery required, no firmware required. Just the tablet, sp flash tools and.... HMU if interested, or just scourge hovatek

JhinCuatro said:
I figured a way to install magisk, no custom recovery required, no firmware required. Just the tablet, sp flash tools and.... HMU if interested, or just scourge hovatek
Click to expand...
Click to collapse
Please share it here. I’m not the only one looking for an answer and others could benefit from such a hack on this abandoned tablet.

mentaluproar said:
Please share it here. I’m not the only one looking for an answer and others could benefit from such a hack on this abandoned tablet.
Click to expand...
Click to collapse
I'll share the relevant guides that has helped me.
If you want me, or a personalized "guide" for your process, I'll be okay with that, un;ess you wanna totally geek out.
(There are multiple guides, depending on what your encounter, and to use some aspects of the tools)
I can already tell you that this can be a 1-3 hour process to learn and perform, and that the guides will not 100% represent all that you need to do, but 90%.
Note that you just need Wwr_MTK tool, the template for it, SP Flash TOOL and the vcdrom drivers the guide links to! Oh and, an account. That's needed to download files from hovatek.
https://forum.hovatek.com/thread-21970.html
https://forum.hovatek.com/thread-22701.html (If in following the first guide, and you encounter "DRAM FLIP TEST"
https://forum.hovatek.com/thread-526.html (Skip to step 7-21, the first guide redirects here on how to use readback. Mediatek tools no longer works, which is why you should ignore that thread mostly.)
With this, you can eventually get the boot.img of your tablet, which should then be patched with the magisk app (doesn't matter where, just get the patched boot.img), then you can use SP flash tool to flash the boot.img and get root! This can also be used to help build your own custom rom, kernel, and even recovery, with a semi automatic process.

DL8006 TWRP/Magisk
endleesss said:
I'm also looking for TWRP for DL8006. Unlocking the bootloader was easy.
Click to expand...
Click to collapse
I have a DL8006 and I rooted it with Magisk and added a TWRP port. Need these?

Dl8006 twrp
osirisale786 said:
I have a DL8006 and I rooted it with Magisk and added a TWRP port. Need these?
Click to expand...
Click to collapse
Can you please share more info? I have been struggling with one myself

osirisale786 said:
I have a DL8006 and I rooted it with Magisk and added a TWRP port. Need these?
Click to expand...
Click to collapse
interested as well Have one of these sitting around gathering dust...

osirisale786 said:
DL8006 TWRP/Magisk
I have a DL8006 and I rooted it with Magisk and added a TWRP port. Need these?
Click to expand...
Click to collapse
This is an older thread, but we're talking about an older device. Do you still have these files?

ROOT- HELP Needed

Hi guys,
I tried looking for this info on different forums online, couldn't really get to it.
TL;DR version- Need help unrooting/rooting back properly after update.
Anyway, I rooted my phone using Mac, OP7(phone) and some YouTube guide, and it worked like a charm. (Magisk, TRWP, the iso image, etc)- the only hiccup was I lost app data, but story for another day.
However, everything stopped working after an UPDATE!!
Thus, now I am caught between two worlds, where my phone is rooted- fastboot, but I am not getting any advantage- my adblock app(which had inspired this quest), or magiskhide(banking apps) are not working.
I tried doing the process again, but I think I am missing the right .zip files or versions, searching for them online is becoming a rabbit-holey adventure to no avail.
Attaching what I think are relevant files, for version details.
Thanks kindly.

saurabh_op7 said:
Hi guys,
I tried looking for this info on different forums online, couldn't really get to it.
TL;DR version- Need help unrooting/rooting back properly after update.
Anyway, I rooted my phone using Mac, OP7(phone) and some YouTube guide, and it worked like a charm. (Magisk, TRWP, the iso image, etc)- the only hiccup was I lost app data, but story for another day.
However, everything stopped working after an UPDATE!!
Thus, now I am caught between two worlds, where my phone is rooted- fastboot, but I am not getting any advantage- my adblock app(which had inspired this quest), or magiskhide(banking apps) are not working.
I tried doing the process again, but I think I am missing the right .zip files or versions, searching for them online is becoming a rabbit-holey adventure to no avail.
Attaching what I think are relevant files, for version details.
Thanks kindly.
Click to expand...
Click to collapse
Hello,
please check out this guide at first, It covers the majority of questions and files needed for rooting

strongst said:
Hello,
please check out this guide at first, It covers the majority of questions and files needed for rooting
Click to expand...
Click to collapse
Thanks for pointing that out.
Just to be clear, I am to perform the whole flashing-and-rebooting exercise with the zip, and image files(of TWRP, magisk) given in the links on the post you mentioned?
I am asking specifically w.r.t. version-updates, since the post is a bit old.

saurabh_op7 said:
Thanks for pointing that out.
Just to be clear, I am to perform the whole flashing-and-rebooting exercise with the zip, and image files(of TWRP, magisk) given in the links on the post you mentioned?
I am asking specifically w.r.t. version-updates, since the post is a bit old.
Click to expand...
Click to collapse
The thread is updated recently by myself and I'm still using the OP7, now with Android 11 hence it should also work. Noone wrote that it's not working anymore at a specific step.
Your bootloader should be still unlocked hence you can skip this step.
TWRP 3.4.0-10 and latest magisk stable(not canary) should work.

strongst said:
The thread is updated recently by myself and I'm still using the OP7, now with Android 11 hence it should also work. Noone wrote that it's not working anymore at a specific step.
Your bootloader should be still unlocked hence you can skip this step.
TWRP 3.4.0-10 and latest magisk stable(not canary) should work.
Click to expand...
Click to collapse
Hey,
Thanks a lot for the prompt replies.
My TWRP got flashed properly. But I am having issues with the "Magisk.zip" file, little digging around has led me to the discovery that Magisk manager and Magisk have been combined. In any case, I am unable to find the "Magisk.zip" file link in the GitHub directory.
Further digging proposes a method where some "customrom.img" file has to be patched via the application.
In any case, my Ramdisk on Magisk app is now a yes- this seems important.
And, I want to "I -want-to-say" flash Magisk but lacking the lead.
P.S- yeah, I didn't realise the update date was mentioned below, thanks again. I apologise in advance for other "noob" questions, I think I posted the question also in the wrong place- I'll try and keep up. Cheers.

You can use this attached one if you don't find a zip. For the first rooting: You can patch img files with the app and flash it, that's new since magisk 22 but not so convenient in my opinion.
The update process remains the same as described in my guide(using the magisk app).

strongst said:
You can use this one if you don't find a zip.
Click to expand...
Click to collapse
I figured it out man. Thanks again.
The step I was missing is "magiskvxx.apk" has to be renamed as "magiskvxx.zip".
Cheers.

saurabh_op7 said:
I figured it out man. Thanks again.
The step I was missing is "magiskvxx.apk" has to be renamed as "magiskvxx.zip".
Cheers.
Click to expand...
Click to collapse
exactly, it is mentioned here(as reference for others): https://topjohnwu.github.io/Magisk/install.html

The struggle... (64 bit recovery porting)

I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.

finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.

lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse

The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?

finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.

Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?

As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.

Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.

What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.

finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.

jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.