It’s not worth it.
Edit: Feel free to try it out, but there’s nothing there over vs code that you want to use.
I dont think so. I was only able to get some devices details using adb (useless) I searched on banana hackers, Gemini, nothing. And I tried other Kaios phones only 1 old kaios Alcatel phone was detected by adb
2 devices identical (?) hardware, purchased about one year apart (no, not f21 pro).
Same boot, lk, recovery, system, vendor.
Flashing boot to recovery partition (or erasing, formatting) causes the device to boot straight into system when an attempt is made to boot into recovery.
But only on one of the two. The other somehow stops booting to recovery for ONE boot, then recreates the recovery partition.
Preloader? Where’s this coming from?
What’s the risk of flashing the preloader from the one with the expected behavior to the other? (I mean, I kinda know, brick, I’d add it to the growing collection).
Any other low level partitions can recreate recovery?
Is my best bet just to remove the location from boot? Remove key combos from lk? Any other ideas?
I have quite a bit of ddr4 desktop ram. Couple hundred gb. Mostly 16gb modules.
Some 3200 some 2666v.
Got any interesting tech items you don’t use? Let’s make a trade
Help me get rid of these so I can hoard new things 
Problem solved, I just removed all items but reboot from the recovery menu.
And… Factory reset from system booted still works!
Edit- annnnd it came back
Figured it out. Never seen this before but the system itself flashes stock recovery if it doesn’t match.
For anyone curious:
#system/bin/install-recovery.sh
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery:12657568:ae1d7d362c74691d37099e5143a81e1ca8415fb3; then
applypatch EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot:7437216:189bd4a6af957747ccecc14e9ba5edf1b637502f EMMC:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery ae1d7d362c74691d37099e5143a81e1ca8415fb3 12657568 189bd4a6af957747ccecc14e9ba5edf1b637502f:/system/recovery-from-boot.p && log -t recovery “Installing new recovery image: succeeded” || log -t recovery “Installing new recovery image: failed”
else
log -t recovery “Recovery image already installed”
fi
Script uses /system/recovery-from-boot.p
2 Likes
heres the egate Reseller portal tps://app.offlinesoftware.solutions:5000/user-licenses/176
hum that actually ingenious way to prevent flashin custom recoveries
1 Like
Sorta, only when the system boots will it replace it
1 Like
ahh never mind - missed that
is there a way to block spotify pictures and videos i know theres a thread avout that but no solution there. any updated info
Did it with xposed never tried with hosts
do you have the domain names that you used. can you share the xposed files.
Didn’t use hosts
I’ll have to find them, it was a kinda just for laughs project
did it work well
Needed alott of refining but yeah pretty much. Grayed out any images
Just letting you know in advance I most probably won’t find it
no problem - its kind of “just for laughs” for me too
1 Like
Whaddya think of a device like this?
- need auth to flash in fastboot
- recovery menu limited to “reboot” in the menu
- mtkclient known to brick device if you flash with it
- all the classic removals in system (+ many modifications to system apps eg. settings and system ui)
Any holes?
What’s the easiest way to remove system apps permanently with root without causing problems?
adb shell
su
mount -o remount,rw / # or /vendor, /product, sometimes /system
pm path name.of.application # package name, can do pm list packages "name" to find
rm -rf /path/to/apk/folder
reboot
1 Like