Related
Hi,
My friend gave me this phone to update the rom, but I'm facing a problem. Device was rooted, recovery is installed, but some really old one - it doesn't even say what kind of recovery it is. So I read that I need to update to TWRP 2.8.4.0 rev.2. Tried flashing it with TWRP apk, but after choosing it and hitting install, it reboots and goes into old recovery and I can't install new TWRP. Then I tried installing it with this guide: http://rootoreviews.com/root-Lenovo-P780-install-twrp-custom-recovery , but I'm getting error: partition 'recovery' not support flash.
Lastly I tried with SP Flash Tools, but I can't install drivers. After holding red button 2 seconds and plugging cable there is no device unknown to install drivers or any kind of device looking like this phone.
Can anyone help ?
Thanks
gunlok said:
Hi,
My friend gave me this phone to update the rom, but I'm facing a problem. Device was rooted, recovery is installed, but some really old one - it doesn't even say what kind of recovery it is. So I read that I need to update to TWRP 2.8.4.0 rev.2. Tried flashing it with TWRP apk, but after choosing it and hitting install, it reboots and goes into old recovery and I can't install new TWRP. Then I tried installing it with this guide: http://rootoreviews.com/root-Lenovo-P780-install-twrp-custom-recovery , but I'm getting error: partition 'recovery' not support flash.
Lastly I tried with SP Flash Tools, but I can't install drivers. After holding red button 2 seconds and plugging cable there is no device unknown to install drivers or any kind of device looking like this phone.
Can anyone help ?
Thanks
Click to expand...
Click to collapse
Hi. I have read your message and you have to do this:
First Tutorial.
I see that you have installed allready one custom recovery.
1. Download TWRP from here: http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605
2. After download putt the zip file to your root of your internal memory
3. Reboot to your current recovery and install twrp
4. After install power down your phone.
5. Start your phone again with all buttons pressed: Power + Volume up and Volume down.
6. Go to TWRP and do a full backup of your current firmware.
7. After full backup you can install any custom firmware you want.
8. I reccomend latest MIUI from AndreyZO, Mirror 9.
9. Good luck. If you have other questions write here.
Seccond Tutorial
1. Look in this post: http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605
2. Download TWRP_v2.8.4.0 rev2 and read twice that tutorial
3. Go to this post and download SP Flash Tool: https://drive.google.com/drive/folders/0B_B98oK4DpK1S1l2bXRkTGxhVFk
4. Go to this post and download latest stock KITKAT and drivers: http://forum.xda-developers.com/lenovo-p780/development/p780-row-s226-flash-flashtool-t2909202
5. When you install the drivers in windows 8,10 you must disable driver signing. Look on youtube.
6. Now you must flash new system.
7. Unpack stock Kitkat firmware.
8. Unpack TWRP.
9. Go to firmware folder and delete recovery.img and replace with TWRP
10. Flash the firmware.
11. After flash boot at least once. If by any chance your phone is Lenovo P780 speed edition, after this flash will not start. This means that you need the latest preloader. Download it from here: http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161
12. After flash reboot in recovery by powering off the phone and start with all buttons pressed: Power + Volume up and Volume down.
13. Now you have last stock firmware with custom recovery installed. Go to TWRP and do a full backup of your current firmware.
14. After full backup you can install any custom firmware you want.
15. I reccomend latest MIUI from AndreyZO, Mirror 9.
16. Good luck. If you have other questions write here.
Tried to flash from this weird recovery, but I get error - look at pic.
I didnt flash this recovery, it must've been flashed by seller in my country. It looks like he way buying chinese versions and then flashing modified rom with polish language (very poorly translated).
Problem with sp flash tools is, I cant install usb driver. When Im in download mode I get the sound that usb device has been plugged in and after 1 second i get the unplugging sound. There is no unknown device in Device Manager, do I am not able to update the driver :/
gunlok said:
Tried to flash from this weird recovery, but I get error - look at pic.
I didnt flash this recovery, it must've been flashed by seller in my country. It looks like he way buying chinese versions and then flashing modified rom with polish language (very poorly translated).
Problem with sp flash tools is, I cant install usb driver. When Im in download mode I get the sound that usb device has been plugged in and after 1 second i get the unplugging sound. There is no unknown device in Device Manager, do I am not able to update the driver :/
Click to expand...
Click to collapse
That one is stock recovery. Proceed with the seccond tutorial.
One more question before I try to flash, I got CN verision, u answered to me in different thread:
stympy said:
Hi. Your layout is CN.
Look if you have custom recovery TWRP Installed.
If you have TWRP installed you can go to this post and install latest MIUI MINOVO.
Good luck.
Click to expand...
Click to collapse
So is that ROW Kit Kat ok for me ?
Yes it is ok as base firmware.
After you flash and install TWRP, you can install any custom firmware.
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
Ehh now in SP flash tool I get this error... I followed all steps :/
gunlok said:
Ehh now in SP flash tool I get this error... I followed all steps :/
Click to expand...
Click to collapse
Try version 5 and see what happens.
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
gunlok said:
Ehh now in SP flash tool I get this error... I followed all steps :/
Click to expand...
Click to collapse
Did you have any success with SP Flash tool v5?
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
Hi,
Sorry for delay, wasn't at home during weekend. Im flashing right now, but I had to use "Format all + download", cause only download showed error: "PMT changed for the ROM it must be download". Now I can flash the ROW version of custom rom or CN ?
Hmm I have still stock recovery not TWRP, although I replaced it with TWRP. File size matches perfectly...
Ok, worked but I flashed it with ROW version of recovery, making backup at the moment.
Got an error installing minovo_NOTE_6.12.1_ROW.zip, couldn't boot into recovery after so I decided to flash via SP Flash Tools one more time. After that booted into recovery and once more I have stock recovery xD I'm in serious WTF mode right now
Hmm I think I screwed something. After booting Kit Kat it says "Invalid imei" :/ I guess I will have to restore with MTK droid tools ? Can you guide me through that ?
gunlok said:
Hi,
Sorry for delay, wasn't at home during weekend. Im flashing right now, but I had to use "Format all + download", cause only download showed error: "PMT changed for the ROM it must be download". Now I can flash the ROW version of custom rom or CN ?
Hmm I have still stock recovery not TWRP, although I replaced it with TWRP. File size matches perfectly...
Ok, worked but I flashed it with ROW version of recovery, making backup at the moment.
Got an error installing minovo_NOTE_6.12.1_ROW.zip, couldn't boot into recovery after so I decided to flash via SP Flash Tools one more time. After that booted into recovery and once more I have stock recovery xD I'm in serious WTF mode right now
Hmm I think I screwed something. After booting Kit Kat it says "Invalid imei" :/ I guess I will have to restore with MTK droid tools ? Can you guide me through that ?
Click to expand...
Click to collapse
Hi. Look on this location:
http://forum.xda-developers.com/showthread.php?t=3174563
Send from my Lenovo P1 Vibe Pro with 3 Gb of RAM and 32 Gb of Internal Storage.
Sorry for annoying you once again. When I try to flash anything in TWRP I get error "unable to mount /system". I read that it could mean that system partition might have incorrect file system. What is the standard one for p780?
It happens when I flash the stock KK with TWRP recovery, then I want to flash Superuser. I need superuser to use MTKdroidtools to restore IMEI.
My biggest problem is when I boot the Stock KK after flashing and power OFF, I can't boot to TWRP recovery. Instead it's booting stock recovery. Only way to to boot to TWRP or any custom recovery (tried CWM) is only after fresh flashing with SPflashtools, but I can't flash superuser. If I format /system I can install superuser (no error unable to mount /system), but I have no system to boot to use MTKdroidtools.
This phone is driving me crazy....
UPDATE:
Ok i managed to restore everything, thanks for help. Can't flash custorm rom still but im making different thread.
Guide to rooting infocus Epic 1 (for windows) for build 00.
This method is only tested on build 00IN_1_360 only. If you are on the older build, first update your phone to build 00IN_1_360 then proceed. Check Build number in settings->about phone.
Proceed at your own risk, I will not be help responsible if your phone bricks, Your warranty will be void after this. Also all phone data will be lost including data on internal memory like photos, etc after these steps so take necessary backups.
Prepare your system
1. Extract and Install MTK Driver Auto Installer v5.1632 (google it)
2. Install Phone F Driver (from phone CD-emulation/driver folder upon connecting your phone)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
4. Download latest SuperSU flashable zip file from here
5. Download twrp-3.0.3-0-epic1-noveritynoencrypt.zip from here, extract in the folder where you have installed adb and fastboot
6. Download noencryptnoverty_boot.zip from attachments and extract to folder where you have installed adb and fastboot
Steps to root:
1. Enable Developer options in phone settings (goto phone settings -> about phone -> tap build number 7 times)
1a. Enable OEM unlock
1b. Enable USB Debugging
2. Connect phone to computer, wait for hardware to auto install
3. open cmd as administrator
3a. goto the directory where adb and fastboot is installed
4. type command:
4a.
adb reboot bootloader
(Wait for phone to come in fastboot)
4b.
fastboot OEM unlock
(press vol up key on phone)
4c.
fastboot flash boot noveritynoencrypt.img
4d.
fastboot flash recovery recovery.img
4e.
fastboot reboot
You will get an phone orange state prompt, do not worry its normal. Phone may reboot once or twice. Wait for phone to normal bootup.
5. open cmd and type command
5e.
adb reboot recovery
Phone will reboot in recovery i.e. TWRP
6. Tap on Keep system read-only. Do not swipe to allow modifications. If TWRP asks for password, don't enter any press back.
7a. Tap Wipe -> Format Data. Come out to main menu, then click reboot and then recovery to restart recovery.
7b. Tap Wipe -> Advanced Wipe -> Select Dalvik /ART, Cache, Data and Internal Storage. This is important step, as these partitions are encrypted at the moment, so if you flash anything the phone rom may corrupt.
8. Come out and then Tap Reboot -> System
9. Once the phone is back, turn off the phone. Then power on with vol up key pressed to boot into TWRP
10. Tap Backup, select all partitions, select phone storage (SD card preferred) and take backup (optional step but highly recommended )
11. Now tap install, goto the location where you had copied SuperSU zip file, flash it.
Congratulations your Phone is rooted. Reboot, see SuperSU icon in app drawer.
Many thanks to @mujammil786 for providing stock files and @Bornstud for testing twrp builds
Special thanks to our devs @DespairFactor for modifying boot.img to disable Encryption and Verity and @kirito9 for creating TWRP for our device. Without their help, it wouldn’t have been possible.
MODS
(Take backup of your ROM/Data before applying any mods)
Viper4Android (Advanced Sound Enhancement)
Hugely Customizable and better than MaxxAudio or Dolby Atmos IMHO
Now working on our device Infocus Epic 1
Need to flash the 2 attached files via TWRP before installing the official app from HERE. Although latest version v2.5.0.5 also works, but i personally prefer v2.4.0.1 (busybox required)
(Note the attached files are not my work, they are picked from here and here. Say thanks to original contributors.)
Good V4A profile: HERE
Extract it to ViPER4Android Directory in internal Storage
Xposed
Needs no introduction. Every android enthusiast should know what it is. Anyway if you are new, xposed opens limitless ROM customization(s) and useful features via 100s of its modules.
Installation:
1. Flash framework xposed-v87-sdk23-arm64.zip from HERE via TWRP. Reboot after installation will take long time (~10 - 15 minutes)
2. Install app XposedInstaller_3.1.1.apk from HERE
Restoring phone back through SUT
If you are stuck somewhere or want to restore the phone factory state (like for when giving to repair), you can restore the phone back via SUT
Link for build 1280: https://firmwarefile.com/infocus-epic-1
Also dont turn off your phone as suggested in sut readme file. It only works when your phone is on. Check below vid for more instructions
https://m.youtube.com/watch?v=eV_cId5fC9E
Reduce battery consumption & phone temperature
Found an interesting thread, mod works on our device also
https://forum.xda-developers.com/red...tings-t3687897
I have tried both flavor 1 and flavor 2 over the past week. Results with flavor 1 were positive in the beginning but for some reason standby drain shot up after 3-4 days, not sure what the reason was.
On flavor 2, I have just disabled MTK perfservice by setting
ro.mtk_perfservice_support = 0 in build.prop
Yes this limits the a72 core to 1.5ghz, but i have noticed phone is heating less and need for charging the phone has reduced. I haven't noticed much drop in performance either, but that might be as I don't use intensive apps.
Mafioso said:
I've managed to unpack nb0 file through a688 tool, however its only successful in unpacking few files before it crashes with some array size error, but the good thing is I was able to extract the scatter file for this phone before it happened.
Anyway, I was hopeful that I would be able to make backup of Stock ROM and Recovery through it via spflash tools however as it turns out, spflash tool is giving me error while doing readback BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
Not sure how to fix it, i've updated my drivers as well as i'm using latest version of spflash tool (SP_Flash_Tool_v5.1628_Win)
Attaching scatter file.
Click to expand...
Click to collapse
From where uve downloaded the stock firmware
Romeotamizh said:
From where uve downloaded the stock firmware
Click to expand...
Click to collapse
http://firmwarefile.com/infocus-epic-1
Mafioso said:
http://firmwarefile.com/infocus-epic-1
Click to expand...
Click to collapse
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Romeotamizh said:
Oh
Click to expand...
Click to collapse
Look in other sites bro for img files
Romeotamizh said:
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Look in other sites bro for img files
Click to expand...
Click to collapse
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Mafioso said:
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Click to expand...
Click to collapse
Ooh bro I'm happy to help but seriously i Duno about these kind of extensions hope u understand
Mafioso said:
I'm trying to root Infocus Epic 1, its a good budget phone with decent specs. Availability is only in India, not sure other regions. Anyway I'm having hard time to root it, since not much support is available. But so far, I have tried below things:
1. Tried to root with Kingroot, doesn't work .Probably because it is very new version of Marshmallow with Oct'16 patch level and kernel dated in dec 16.
2. Tried to generate scatter file via MTK Droid tool v2.5.3, after enable USB debugging in phone. The phone get detected in the tool, however create scatter file option in block map is disabled I've read somewhere, it might be due to MTK6797 (Helios x20) is quite new and is not yet fully supported by tool yet. Not sure if its true though. But if I can generate scatter file, I can extract phone's stock recovery via SPFlash tool readback to try a hand at porting twrp/cwm with some help..
3. Downloaded stock Infocus Epic 1 firmware in hope for recovering stock recovery.img or MTK scatter file, however on unpacking the firmware package, I found it contains unknown image file of nb0 extension which is it to be flashed via SUT Tool. Not sure how to unpack this file
Any more ideas, how can i atleast start with my quest to root/put custom recovery on this phone ? @Romeotamizh Pls help.
Click to expand...
Click to collapse
I can give u stock recovery of epic 1..
mujammil786 said:
I can give u stock recovery of epic 1..
Click to expand...
Click to collapse
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Mafioso said:
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Click to expand...
Click to collapse
I was able to extract it from last update zip
---------- Post added at 04:45 PM ---------- Previous post was at 04:33 PM ----------
Epic 1 stock recovery
https://drive.google.com/file/d/0B4FNo4vddleCNmpwcS1hS3FLam8/view?usp=drivesdk
mujammil786 said:
I was able to extract it from last update zip
Click to expand...
Click to collapse
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Mafioso said:
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Click to expand...
Click to collapse
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
mujammil786 said:
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
Click to expand...
Click to collapse
thanks, updated first post.
Mafioso said:
thanks, updated first post.
Click to expand...
Click to collapse
Thanks let's hope for best
I like this phone and the only thing lacking is Root, Hope someone will do it
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Mafioso said:
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Click to expand...
Click to collapse
My device does not get detect in fastboot can u show me screen shot of command u are trying....
mujammil786 said:
My device does not get detect in fastboot can u show me screen shot of command u are trying....
Click to expand...
Click to collapse
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Mafioso said:
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Click to expand...
Click to collapse
Ok will try thanx
bootloder get unlocked and locked too
ok so phone get detected in fastboot mode:victory: .was able to lock and unlock boot loader but without custom recovery it is no useful for us.
unlocked bootloader.
tried flashing Vernee_Apollo_Lite_P6(same spec. as epic 1) twrp recovery.
flashing done but after flashing phone refused to boot.
flashed stock recovery from update zip.
locked bootloader.
phone booted but erased internal memory after boot.
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
do you know any guide for making twrp and i think phone will not boot if it detect any change in system partition i think
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Fran Montero said:
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Click to expand...
Click to collapse
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Ruben Craveiro said:
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Click to expand...
Click to collapse
Have you installed it already?
Many thanks!
Fran Montero said:
Have you installed it already?
Many thanks!
Click to expand...
Click to collapse
Im using latest twrp with updated preloader and LOS13
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Maybe you have a sd card formatted as internal storage?
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
1. load scatter.txt in earlier post.
2. select preloader, lk and boot imgs, location of these from the stock 20160810 ROM.
3. select recovery, location of TWRP img.
4. unselect everything else.
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
If your device already rooted, you can also install flashyfi and flash the .img file.
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
a bit late (did came to it to test your solution earlier) but it worked indeed. perfect, very much appreciated.
Can u upload 20171201 again?! Link is not working... Thx
opss said:
Can u upload 20171201 again?! Link is not working... Thx
Click to expand...
Click to collapse
You'll find a link here: https://forum.xda-developers.com/el...t/rom-stock-rom-android-6-0-12-01-17-t3542463
Thx dude
jotei66 said:
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
Click to expand...
Click to collapse
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
Click to expand...
Click to collapse
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
Click to expand...
Click to collapse
Have you tried pressing power and then keep finger pressed on vol up to go straight to TWRP recovery and then flashing a new ROM in TWRP ?
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
thecrazyfarang said:
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
Click to expand...
Click to collapse
No worries, just glad you got it sorted out.
Btw (although I know you dont really wanna risk trying it) my son uses my P9000 and has TWRP installed with no issues at all and root with Magisk.
But great yous sorted out
Root twrp Step by step for newbeee-
Ok,so I've installed TWRP 3.0.2-8 and when I start the phone it goes into the recovery... what to do next? Can I find a tutorial somewhere how to do this? And wich image can I use or is the best for the moment?
thx for helping...
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
hey did you get it fixed and can you please send the link to the stock rom
yayjk said:
hey did you get it fixed and can you please send the link to the stock rom
Click to expand...
Click to collapse
TRY ASKING THE QUESTION ON THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
---------- Post added at 05:00 PM ---------- Previous post was at 05:00 PM ----------
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
TRY ASKING IN THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
How to Unbrick Lenovo K8 Plus 4GB
Hi All
I tried many stock roms and many versions of SP flash tool but none helped me to unbrick my lenovo k8 plus (4gb ram).
I was trying to downgrade it to Naugat from Oreo but it shows same error every time.
Error is (SP Flash tool version latest 5.18)
" Error_Status_Sec_Insufficient_Buffer( 0xC002004B)
[Hint]:
Verified boot is enabled.
Please download signed image (md1img-verified.img) or disable verified boot."
Plzzz help same problem
Enabled verified boot ...how to disabled
Same problem my lenovo k8plus
Enabled verified boot ...how to disabled
You need to use "Lenovo Moto Smart Assistant" instead of SPFlash tool to flash and you will be good to go. You can get the tool from the Lenovo official website.
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
Try with Lenovo Moto Smart Assistant. I too have bricked my phone... but I've successfully started my phone using this tool. you will get official signed ROM from here.
you can use LMSA tool to rescue,90% sucessfully ,don't use splashtool beacause it's many error if you choose wrong version
Had the same problem. Can confirm Lenovo's tool sucessfully recovers ohone from bricked state. A lifesaver!
Downloaded from https://lenovomobilesupport.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
then updated to version 5.9.2.4 from inside the app itself
i downloaded the custom recovery for t20 (TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02) from gethub "i cant attach the link because of the forums rules"
then flashed it using fastboot , but then the tablet didn't boot into normal mode but i was getting the boot mode selection when i hold the (power + volume up) which gave me access to recovery mode and fastboot mode
the problem is that this custom recovery had issues with the touch screen and was basically not usable .
so i switched the phone into fastboot and i flashed the patched boot image that was working before but the tablet still didn't boot into normal mode , then i flashed the stock recovery image and now every thing gone .
the tablet has no options to boot into fastboot or recovery anymore.
basically the tablets boots and i get the teclast logo then the image of the broken android with a "no command" on screen and nothing else
i tried holding the volume up and plug in the usb-c cable but i got the same broken droid
holding volume up and power doesn't give the options for boot modes anymore
i would appreciate any help a this moment , thanks
hany20006 said:
i would appreciate any help a this moment , thanks
Click to expand...
Click to collapse
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
ViAlexSt said:
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
Click to expand...
Click to collapse
thanks for the reply my version is E2
i tried flashing the stock but i keep getting an error that the preloader file is not valid . can u upload yours so i can try with it
hany20006 said:
my version is E2
Click to expand...
Click to collapse
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2: Chinese storage or my Y.Disk
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
ViAlexSt said:
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2:
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
Click to expand...
Click to collapse
thank you very much for providing the y.disk link , i spent the whole yesterday searching for a way to download from baidu without luck.
i managed to flash the stock software (using format all +download) and it worked and now the tablet is up and running (unfortunately its chines ) i changed the language but there is bits here and there with chines still i cant complain.
there is no recovery image with this tablet , do u think i should flash the twrp recovery even if it has touch issues.
i cant thank u enough for your help
have a nice day
hany20006 said:
do u think i should flash the twrp recovery even if it has touch issues
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
ViAlexSt said:
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
Click to expand...
Click to collapse
yeah i just rooted the device and then flashed the recovery using the Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek (TWRP 3.2.1-0)
the touch screen is till having issues , but i guess i have to use mouse as you said
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Draiter said:
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Click to expand...
Click to collapse
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
hany20006 said:
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
Click to expand...
Click to collapse
Hey thanks for the quick reply, I will give it a go
Sent from my SM-G935F using Tapatalk
Got the boot.img flashed and recovery flashed (Phil's), but cannot do a full backup in recovery, cannot Mount data.
Have you been able to do a full backup?
Sent from my SM-G935F using Tapatalk
Draiter said:
cannot Mount data
Click to expand...
Click to collapse
Standard phenomenon for Nougat/Oreo: to mount a partition /date, must first format it. With loss of user data!
Some TWRP editions don't require this, /data mounted.
Hello.
Thanks ViAlexSt for the help, but I´m still having problems with root
, I try with (MTK) Auto TWRP recovery porter and with MTK Auto Philz recovery porter, with success only with TWRP.
Wiith Philz only get into recovery, when go to the OS the screen freeze with Teclast Logo in red.
With TRWP have an error, not able to mound device.
Is no possible install zip or create a backup.
Any idea??
I have a T20 T2E1
Thanks
I format with SPFlashtool with format+flash option, but not work, no backup, no any wipe.
Still with message Unable to mount parition.
I will try with an older version OF TWRP.
Some screenshots.
Thanks
https://photos.app.goo.gl/qwmLqnhxVk8vRmWA8
https://photos.app.goo.gl/VP5vJCDC7HaDpgaB8
AWLanzarote said:
Still with message Unable to mount parition.
Click to expand...
Click to collapse
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
ViAlexSt said:
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
Click to expand...
Click to collapse
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
AWLanzarote said:
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
Click to expand...
Click to collapse
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
toxstoxs said:
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
Click to expand...
Click to collapse
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
AWLanzarote said:
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
Click to expand...
Click to collapse
I went troght that step by step guide but :
1) into Pre requirement steps, i made a NVRAM backup with SP Tool.
step 2 is not so interesting to me as the tablet is new so no personal data are saved.
point 3 : How suppose to make a nandroid backup if no TWRP is intalled???
then.. i suppose that it mean to INSTALL a TWRP and just after make a nandroid backup right?
but...
just after ulock the bootloader and reaching step by step the point 7 and 8 of the guide,
after the command "fastboot boot recovery.img" the device reboot and go in permanent loop.
No way to access the recovery.
is there something that i may check? just once i been able to enter the twrp and the main problem were the impossibilty to access and format the /data partition so, no factory reset were possible and obviously no bbot as well (permanent boot loop).
Im not use adb tools, im only use sp fash tool.
I do it like this.
1 flash the downloaded Rom from Teclast with SP flash tool, to get all fresh.
2 Enable usb debug and oem unlock
3 copy in your device the stock boot.img from the folder firmware from the zip downloaded from Teclast,
4 in your device install the app Majisk manager and use it to patch your original boot.img
5 copy into sd the files magisk.zip, No verity opt encrypt.zip,
6 with sp flash tool flash the patched boot.img and the downloaded TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02"]twrp renamed to recovery.img ”this was the only one trwp which works on my T20”https://github.com/TwrpBuilderTests/android_device_teclast_t20/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02
7 reboot in recovery with TWRP and install magisk.zip and no verity opt encrypt.zip