about SDT
about SDT
(13-02-2020, 06:25 PM)Timmylog After I successfully re flash the ported TWRP into my device, can I reboot my phone or is there any process I need to go through to make the custom recovery permanent?
(17-02-2020, 10:43 AM)Timmylog Hi! I've flashed the ported twrp into my recovery partition on my device with adb, but my device is now stuck in a bootloop. I've tried pressing all buttons simultaneously but nothing works up entering recovery mode is impossible and even fastboot mode too.
So I didn't panic, my plan was to undo what I did by using sp flash tool to only flash my recovery back to stock since I can't access fastboot anymore but unfortunately, sp flash tool keeps asking for an authentication file. So I downloaded the custom DA file for my device but when I loaded the file the flash tool kept telling me i needed something like a library file or maybe it said incorrect library stuff, I didn't really put that part in my mind. But what I want you to know is that I don't think I made any mistake on my part, cause what I think may be the problem is below: ...
(17-02-2020, 10:43 AM)Timmylog ...1.using the android 9 pie option instead of the go version into the twrp porting tool.
but there was no pie go option and you said it was okay for me to use it...
(17-02-2020, 10:43 AM)Timmylog ...2.DM verity issue:in the tutorial video it was stated that if the porting tool shows no DM verity detected we shouldn't bother flasin the VB meta file or patching magisk to the boot partition and it didn't detect any DM verity in my stock recovery image so I didn't bother flashing the VB meta and boot. Or less if the app has a bug and says no DM verity for everyone's recovery images then that could hve Been the cause of my bootloop problem...
(17-02-2020, 10:43 AM)Timmylog ...3.My actual recovery img size was around 30 MB plus but after the twrp porter created its own it was only around 16mb so maybe it was incomplete but it still told me the porting process was complete....
(17-02-2020, 10:43 AM)Timmylog N.B: THESE ARE JUST WHAT I THINK MAY BE THE CAUSE, THEY AREN'T FACTS.
Any way my plan now is to use the techno after sales flash tool ( also known as software download tool) which doesn't need any authentication file or custom da files, but before I do so I need to ask u tis question once again cause u didn't answer it the first time I asked you: can I use the software download tool to flash only my recovery partition or I can only use it to flash a whole firmware file?
My device is tecno pouvoir three air LC6A by the way...
(18-02-2020, 10:12 PM)Timmylog Hey! thanks for the instructions you gave me yesterday. Disabling the lib option worked and I was able to use spft to revert back to stock recovery which stopped the bootloop. Turns out that dm verityfile was actually the culprit ,so this time around I patched the vbmeta partition and flashed the ported TWRP successfully.although my device didn't enter a bootloop but I think the Android system is overwriting the ported TWRP cause I entered recovery mode only to be welcomed by my stock recovery...
(18-02-2020, 10:12 PM)Timmylog ...2 there's also this issue about magisk being flashed to the recovery partition for Android devices that don't have ramdisk in their boot partitions, Like Android 9.0 which doesn't have in it's boots partition but only in the recovery cause I checked the Android open source project (AOSP) and read the partition area and saw that there was only ramdisk in the boot partition, just like Tojohnwu, the developer of magisk said on his magisk installation website. And mine is the Android 9.0 so it still safe to patch my boot partition with magisk?
P.S : I've already patched magisk to my recovery partition but it seems it's been overwritten like the same way the ported TWRP is but just to be safe I'm going to flash my stock recovery again and wait for your answer.