Database Info

HTC One Verizon TWRP issue

hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.

kpitao said:
hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.
Click to expand...
Click to collapse
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1

andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery

kpitao said:
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery
Click to expand...
Click to collapse
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.

andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
andybones said:
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.
Click to expand...
Click to collapse
the first couples times I did, I choose the firmware "m8vzw_AllInOne_Firmware" and " 4.17.605.9 Modified Firmware ".... both did not work in my case but then I did again with full wipe firmware "4.17.605.9 Full Firmware" and did work.... I didn't have nothing on my phone anyway so, the full firmware which wiped worked..
Thanks

Cannot start ROM / permanent reboot into recovery

Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy

jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it

thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS

jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?

Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy

jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.

zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.

jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.

Sorry, what exaclty is a fastboot rom and where do i get it?

zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)

Maybe my phone has a problem with flahing recoverys in general I don't know.

jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz

What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...

Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....

guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy

[SOLVED] TWRP 3.0.2 bootloop

Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.

After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?

audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.

Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.

audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!

I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.

TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?

I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...

download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck

hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...

kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda

audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.

kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/

Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...

[Solved][C2105]Can't install custom recovery with anything contanining FOTAKernel way

Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?

qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety

Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!

Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.

qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!

Teclast M89 problem installing TWRP

Hi folks. As the title suggest I'm having problems installing TWRP recovery on teclast M89 tablet. I've tried a few different tutorials with no success. When I do it with fastboot it says that its installed, after that when I try to reboot the device, I'm stuck in bootloop. I've tried to do it a few times and its always the same problem. Does anyone have a solution? Thanks.

Hello, the same for me with my M89, I'm going crazy.... Help us please!!!! Thanks!!!

Teclast M89 TWRP 3.3.1
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
My small Teclast M89 website: https://teclast-m89.neocities.org/

M89 TWRP Worked!
ValdikSS said:
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
Click to expand...
Click to collapse
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!

Jmlanner said:
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!
Click to expand...
Click to collapse
Make sure to backup nvram, nvdata, private partitions.

ValdikSS said:
Make sure to backup nvram, nvdata, private partitions.
Click to expand...
Click to collapse
Will do. I did bkk nvdata, will double check if I bkk privdata. again TK!

stuck
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks

voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
Hi
I think you are going to have to reflash the original Rom using SPFlahtool. Then you must install Magisk Manage on tabletr. Copy the boot image from the ROM files to Your phone. Then use Magisk Manager to Patch the copied boot image. Transfer modified boot image to PC. Use fastboot to flash modified boot image back onto the tablet. The long and the short of it is - you need to find a way to patch the boot image with Magisk before any TWRP will work.

Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though

voland34 said:
Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though
Click to expand...
Click to collapse
I am glad you got your tablet running again. I had originally started out with just Magisk as root also. I do like to have a working TWRP for backing up though. You should be able now to flash the above mentioned TWRP now via SpFlashtool or fastboot.

voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para

ValdikSS said:
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para
Click to expand...
Click to collapse
Ok, i'll try. Thanks!

Does anybody know if this guide also works for the new Teclast M89 PRO-model???

gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No, most probably it won't. PRO model has different SoC/CPU.

gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.

Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!

w1nst0n sm1th said:
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.
Click to expand...
Click to collapse
The bootloop is not because you've unlocked the bootloader, but most probably because the firmware is designed to perform userdata partition setup in the recovery upon first boot, and you don't have stock recovery, that's why it can't finish formatting procedure.
This could be fixed by flashing stock recovery and booting once.
You can ask for a firmware from Teclast (I used to ask them on vkontakte because they didn't respond my mails), they will provide it.
OR you can write zeros to "para" partition using fastboot, it should do the trick too.
---------- Post added at 16:58 ---------- Previous post was at 16:56 ----------
Edgaralanmx said:
Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!
Click to expand...
Click to collapse
Try to unplug/plug again HDMI cable several times. It seems that the HDMI controller or drivers are buggy.
To change the resolution I use "SecondScreen" software (requires root).

Hi guys,
I´m looking for a working rooting method for my Teclast M89 Pro model ??
Any idea ?? What about the "One Click Root" Program ???
Thank´s a lot

The device was trying to root.
I get the following information when restarting:
orange state
the device has been unlocked and can't be trusted
your device will boot in 5 seconds
Click to expand...
Click to collapse
When I try TWRP via sideload or recovery menu I get the following:
Supported API:3
-- Install /sdcard/teclast_m89_twrp_311.zip ...
Finding update packacke ...
Opening update package ...
Verifying update package ...
Update package verification took 0.5 s (result 0).
Installing update ...
E:Failed to find META-INF/com/android/metadata in update package.
Installing Teclast M89 TWRP Recovery
script succeeded: result was [1.000000]
Install from SD Card complete.
Click to expand...
Click to collapse
But TWRP is not installed.
Where is the problem?

kumpi said:
But TWRP is not installed.
Where is the problem?
Click to expand...
Click to collapse
Are you trying to enter recovery right after flashing it, without booting the OS first? I think you need do enter TWRP right after flashing it.