[DarshWins404]

Sorry i am just curious why do i have to rename the boot img ans also i can flash this boot img with SP flash tool right???

[hovatek]

Sorry i am just curious why do i have to rename the boot img ans also i can flash this boot img with SP flash tool right???

You are porting TWRP using boot.img instead of recovery.img from your firmware (recovery is giving black screen so its unreliable to port with). You have to rename boot.img to recovery.img when using in our tool because the tool looks for a file name recovery.img when porting TWRP

You can flash the ported TWRP however you wish, just ensure to flash it to the recovery partition

[DarshWins404]

The thing you suggested didn't work

I took the stock boot img and pasted in in stock recovery folder of recovery tool
Then i ran the tool and used sp flash tool to flash the recovery img from output folder

But still the same problem
When i try to boot in recovery the iball logo blinks and then screen goes black then device restart
Any other fix?

[hovatek]

The thing you suggested didn't work

I took the stock boot img and pasted in in stock recovery folder of recovery tool
Then i ran the tool and used sp flash tool to flash the recovery img from output folder

But still the same problem
When i try to boot in recovery the iball logo blinks and then screen goes black then device restart
Any other fix?

Patch your boot.img using magisk and flash. Confirm you have root.
Then retry each version of our TWRP porters with your boot.img (renamed to recovery.img). Lets see if any works.

[DarshWins404]

So what you are trying to say is
Root using magisk
And use the same magisk_patched.img(renamed to recovery.img then use the TWRP porter and flash the recovery from output folder using sp flash tool ??

[DarshWins404]

Sorry it didn't work

[hovatek]

Sorry it didn't work

What didn't work?
1. You didn't have root?
2. You had root but ported TWRP didn't work

If 2 then its down to a manual port

[DarshWins404]

Actually both and recovery is still black screening.
I want to share 1 more thing
I tried flashing Validus Os actually i used mtk extractor to make system.img after flashing it my device didn't boot in validus but my recovery turned on it was stock recovery i dont know how
After that i reflashed the stock firm ware but i cannot access recovery but my device is on and i reflashed magisk boot img and i have root

Waiting for more fixes

[hovatek]

Actually both and recovery is still black screening.
I want to share 1 more thing
I tried flashing Validus Os actually i used mtk extractor to make system.img after flashing it my device didn't boot in validus but my recovery turned on it was stock recovery i dont know how
After that i reflashed the stock firm ware but i cannot access recovery but my device is on and i reflashed magisk boot img and i have root

Waiting for more fixes

The problem seems to be the stock firmware. Search for a different one

[DarshWins404]

I am very happy to tell you that my device has philz recovery you were right the problem was firmware i changed it to android 5.1 but now the thing is i cannot boot up my device i can only boot it in recovery mode otherwise i am stuck in logo

Therefore i cannot unlock bootloader and the recovery has something like
E:Cant mount cache/recovery/last_log
And 3 line after that

What should I do??