D
Deleted member 11961949
Guest
- That's all Bkeler's genius glory, and I'm hoping for us this will give a real start !
Yes
Don't know about this, I still have imei numbers and other things seems ok for nowIMHO. mtk client is a mixture of SPFT and TWRP for Linux.
But you have to be careful, the "debuging mode" inscription says that you ruined the NVRAM
No problem!
No problem!
We must try different options. I am a research engineer by training. We were lectured for two semesters on the design of an experiment (task - not sure what to do - result). It is necessary to choose the most optimal algorithm of our actions. I think it makes no sense to fight Gogle, but go around. In the beginning, we need to understand where the manufacturer has put his protection and try to get rid of it. Next will be easier...
About debuging mode. Yes, I can be wrong about nvram, but this suggests that some partitions are overwritten and oukitel now knows about it...
I wanted to be an entomologist since childhood, but worked with radiation for 10 years.Landscaper & Photographer was my great choices since the beginning.
I wanted to be an entomologist since childhood, but worked with radiation for 10 years.
But then crashed Oukitel wp5 Pro...
aheuaheuah ... not really ...Hi!
Since we have problems with the sim card when doing a read-write system partition, our friend suggested doing this search
"Did you guys check in one of your init*.rc scripts why sim card makes problems when phone is booted as RW with fstab? Maybe sim card itself is mounted as ro or something? and this causes conflicts with rw in fstab? It must be something simple like that.
To search your init scripts for certain keyword you can try this code:
Bash:
adb shell
su
for a in /etc/init/ \
/etc/init/hw/ \
/system/etc/init/hw/ \
/system/etc/init/ \
/product/etc/init/ \
/product/etc/init/hw/ \
/vendor/etc/init/ \
/vendor/etc/init/hw/; do cd $a; printf "\n\nChecking all files from %s\n\n" $a; grep -nr "sim" $a; done;
also manually check the init scripts in /, /product and /vendor and maybe /odm or whatever. If you check those paths with script it will crash or take forever..."
Does anyone want to do this?
python3 mtk w boot,vbmeta boot.patched,vbmeta.img.empty
I don't know how it happens in mtk client, but in spft you read the first megabyte of the EMMC_BOOT_1
and the first megabyte of the EMMC_USER. In the first - is the preloader, in the second - is the Table of sections (RPT).
Maybe the RPT is wrong?
I posted two files with ota updates. If you look at the checkroot file, it looks like the Chinese just check the checksums...
There is a possibility that their defense is built on this
Project TrebleHow can SPFT or MTKclient have at one given moment write access during process ?
Oh well.. even with that oukitel won't work on updates, they are quiet in late for this phone.
Of couse.Oh well.. even with that oukitel won't work on updates, they are quiet in late for this phone.
adb shell 'pm list packages -f' | sed -e 's/.*=//' | sort
adb shell pm list packages
adb shell pm uninstall -k --user 0 com.ssui.chdmodel
adb shell pm uninstall -k --user 0 com.android.companiondevicemanager
adb shell pm uninstall -k --user 0 com.android.dynsystem
adb shell pm uninstall -k --user 0 com.android.wallpaper.livepicker
adb shell pm uninstall -k --user 0 com.google.android.apps.tachyon
adb shell pm uninstall -k --user 0 com.google.android.apps.docs
adb shell pm uninstall -k --user 0 com.google.android.apps.googleassistant
adb shell pm uninstall -k --user 0 com.google.android.apps.wellbeing
adb shell pm uninstall -k --user 0 com.google.android.apps.youtube.music
adb shell pm uninstall -k --user 0 com.elephanttek.faceunlock
adb shell pm uninstall -k --user 0 com.android.emergency
adb shell pm uninstall -k --user 0 com.android.nfc
adb shell pm uninstall -k --user 0 com.elephanttek.faceunlock
adb shell pm uninstall -k --user 0 com.adups.privacypolicy
adb shell pm uninstall -k --user 0 com.android.backupconfirm
adb shell pm uninstall -k --user 0 com.adups.fota
adb shell pm uninstall -k --user 0 com.android.bips
adb shell pm uninstall -k --user 0 com.android.cts.ctsshim
adb shell pm uninstall -k --user 0 com.android.cts.priv.ctsshim
adb shell pm uninstall -k --user 0 com.android.localtransport
adb shell pm uninstall -k --user 0 com.android.partnerbrowsercustomizations.example
adb shell pm uninstall -k --user 0 com.android.printspooler
adb shell pm uninstall -k --user 0 com.android.sharedstoragebackup
adb shell pm uninstall -k --user 0 com.android.wallpaperbackup
adb shell pm uninstall -k --user 0 com.debug.loggerui
adb shell pm uninstall -k --user 0 com.android.traceur
adb shell pm uninstall -k --user 0 com.android.htmlviewer
adb shell pm uninstall -k --user 0 com.google.android.apps.restore
adb shell pm uninstall -k --user 0 com.google.android.apps.restore
adb shell pm uninstall -k --user 0 com.google.android.feedback
adb shell pm uninstall -k --user 0 com.google.android.onetimeinitializer
adb shell pm uninstall -k --user 0 com.google.android.gms.location.history
adb shell pm uninstall -k --user 0 com.google.android.videos
adb shell pm uninstall -k --user 0 com.mediatek.atmwifimeta
adb shell pm uninstall -k --user 0 com.android.calllogbackup
adb shell pm uninstall -k --user 0 com.ssui.setupwizard
adb shell pm uninstall -k --user 0 com.ssui.sos
adb shell cmd package install-existing com.app name
You can also use some 3rd party app manager, which shows installed package names or check it via Google store. It does not matter.
{packageName='com.ssui.keyguard', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=0, cornerSwitch=2, userOptSwitch=1, listType=1, status=1, userOperated=0}
{packageName='com.ssui.launcher3', mainSwitch=0, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=0, cornerSwitch=2, userOptSwitch=1, listType=1, status=1, userOperated=0}
{packageName='com.android.music', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=0, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
*
*
*
{packageName='com.twitter.android', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
{packageName='com.android.email', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
{packageName='com.linkedin.android', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
and past it on the bottom with changed package name:{packageName='com.facebook.orca', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
This is example for Signal messenger:{packageName='YOUR.APP.PACKAGE.NAME', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
Repeat this for all apps with disappearing notifications and save the file.{packageName='org.thoughtcrime.securesms', mainSwitch=1, lockScreenSwitch=0, showDetailSwitch=0, handsupSwitch=1, cornerSwitch=1, userOptSwitch=1, listType=1, status=1, userOperated=0}
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
fastboot -w
fastboot reboot fastboot
fastboot erase system
fastboot delete-logical-partition product
fastboot --disable-verity --disable-verification flash system Havoc-OS-v3.12-20201230-Official-GApps-arm64-ab.img
fastboot -w
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot
fastboot flash boot magisk_patched_boot.img
fastboot --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
su
props