[Recovery Release] Working TWRP for Sony L1 (G3311 Single SIM others to be confirmed) - Sony Xperia L1 ROMs, Kernels, Recoveries, & Other

Requirements:
1. Bootloader Must Be Unlocked.
2. Have a backup of your working Magisk Patched boot.img saved to your External SDcard.​A little INFO:
The Sony L1 recovery seems to be disabled by SONY for some unknown and Probably stupid reason.
I have tried all ways to get the TWRP and Stock recovery to boot up from the fotakernel partition (recovery) but TWRP and even the stock recovery refuse to boot.
Anyway to cut a very long story short I am releasing this TWRP which is 95% functional and needs to be flashed to the boot partition
Working Method/flow:
Make sure you have a Back up of your working Boot.img "You know the one you used to root the device in the first place".
For ease of use You can use this app by XDA dev @wanam (Thread here) app on playstore Here You can also use this app to flash the v5-twrp-l1.img to your "boot" partition or you can go old skool and use dd (Via adb shell) or use the Magisk patched_boot.img you first rooted with..
Make SURE to Copy this working boot.img to your External SDcard.
When you require TWRP flash the downloaded TWRP to your boot partition using Fastboot (cmd's below) or the above app then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
IMPORTANT:
Remember Just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
Things Not Working:
1. You will not be able to mount encrypted data therefore you would need to FORMAT your data and then leave it unencrypted.
SuperSU and Magisk will disable forceencrypt for you.
2. Does not Charge or show battery % so I don't know if it's actually charging. (Probably Qnovo battery module used by sony)
It will probably work on all variants but I am not able to test that.
It's use is for backups and restores wipes and installs for which it seems fully functional. :good:
Install Instructios.
Boot to the bootloader then
Code:
fastboot flash boot v5-twrp-l1.img
Then
Code:
fastboot reboot
Download HERE v5-twrp-l1.img

Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311

Chronic2k13 said:
Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311
Click to expand...
Click to collapse
:laugh:
Ok maybe I should update the OP as it seems it's not really clear enough that obviously the boot is replaced by the recovery.
Method would be make sure you have a Back up your working Boot.img You know the one you used to root the device in the first place.
You can also use dd (Via adb shell) or a app from the playstore or better still use the Magisk patched_boot.img .
Copy this working boot.img to your External SDcard.
When required flash the recovery to your boot partition using Fastboot then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
Then just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
OP Updated let me know if it's clearer to understand now.
Thanks for reporting back. :good:

I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?

Chronic2k13 said:
I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?
Click to expand...
Click to collapse
I don't think you have really read or understood the OP
You are only ever flashing the "boot partition".
When you need to use TWRP you flash the TWRP.img to the boot partition and when your done you flash back your boot.img again to the boot partition as in the OP.
BTW Have you ever been able to enter the STOCK recovery using Power and Volume Down or using any commands
My phone could not enter the STOCK recovery at all let alone a custom one and since no one ever replied to my question about this I assumed this was the case for everyone as many sony devices from 7.0 had the recovery disabled?

I'm unable to get into stock recovery too!

So,
If we don't have a Recovery partition maybe we can
Create one...
Tutorial in here
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
I'll try it if i have time.

I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?

alegatorul said:
I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?
Click to expand...
Click to collapse
Mate you really need to be careful unless you really know what your doing
You will likely brick the phone if you continue to blindly mess with re-partitioning and the like.
If you were in TWRP which was flashed to the boot partition as directed in the OP then flashing the supersu.zip will simply modify your TWRP.img not your boot.img since TWRP is living in the boot partition at the time you run the .zip hence your looping.
This device has bootloader issues since it will not allow the booting of another partition except "boot" recovery, fotakernel, rdimage, all tested all failed to boot the TWRP recovery and stock recovery.
There is another method used by some sony devices but this will need to be heavily modified for this MediaTek SoC and will require a lot of study and script re-writes.
Spending all this time on a device that's pretty much obsolete before it was launched since it's not planned to receive oreo and Sony 90% locked down the bootloader is kinda futile so use the phone for what it is then throw it in the bin when done in a year or two.

Mate, you are right

Hi, please make recovery for L1 G3312 i hope you can do it.

tweak8 said:
Hi, please make recovery for L1 G3312 i hope you can do it.
Click to expand...
Click to collapse
I think this one may very well work for the dual SIM also so please try it and then report back with some actual details.
eg: bootloader status, firmware version, your region, etc etc.
Thanks.

Works great on the G3113 model, thank you for developing this! Now hoping to find a custom rom to install via .zip.

This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.

Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?

dumb person said:
Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?
Click to expand...
Click to collapse
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.

This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...

bigrammy said:
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.
Click to expand...
Click to collapse
I downloaded the boot from the link you posted and flashed it. Now it phone works again. Many thanks!!

riadjblicd said:
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...
Click to expand...
Click to collapse
Yes but Sony Disabled the recovery partition (fotakernel) by design so you can not boot from it.
The OP is clear about the need to flash the TWRP to your boot partition and the reason I also give full instruction in the workflow/method but people simply don't read anymore it seems. :crying:
TWRP can be injected into the boot.img so you can boot normally or boot TWRP using the volume keys at boot time but I can't be bothered working on this since Sony are not going to update the Android Version.
While the phone is OK I have far better phones to spend my time on at the moment.

how to backup boot.img without root? if its impossible then how do i root this phone?

Related

Stuck in Fastboot

Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
also it says invalid "boot image header!" in red letters
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
P.Kosunen said:
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
Click to expand...
Click to collapse
Alright thankyou!
I got everything to work again but I still can't flash roms. They just bootloop :S
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
You do know flashing stock again removes root, so it has to be rerooted again ?
aradalien said:
You do know flashing stock again removes root, so it has to be rerooted again ?
Click to expand...
Click to collapse
Yes I am very aware and followed through with root with that outcome.
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
Click to expand...
Click to collapse
CWM doesn't work it. It boots up (Im used cyanogenmod) the cyanogenmod boot animation but just stays there.
P.Kosunen said:
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Click to expand...
Click to collapse
I've flashed twrp too and came out with the same outcome.
stuck in fastboot
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
Exactly i am also facing same problem....
mobile unable to instal firmware...
still i am searching for solution ...
guys plz help me
I thought I am the only one with this problem..After mailing the phone to SC and got it back after 2 months, the phone still looks the same, just like they did nothing to fix it.

bootloop after using twrp (can't start smartphone, please help!)

i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
TobiS137 said:
i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
Click to expand...
Click to collapse
Enter fastboot, flash official twrp.Flash magisk in twrp.
vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
can you help me further? as i said i am a huge newbie and i only understood a little of that. is there any other ways you can contact me?
vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
Can you explain what exactly were you doing ?!
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
I'm new to this while A/B partition. I went through all the steps and my phone is rooted, with Magisk and TWRP. All seems to be fine. My question is this. When I boot to the recovery (TWRP) and choose the reboot option it defaults to Current Slot: Partition B. If I reboot to partition B it goes back to TWRP. I have to select Partition A to get the device to boot to the system.
Is this normal? Do I need to set it up in a different way?
samteeee said:
Can you explain what exactly were you doing ?!
Click to expand...
Click to collapse
i was trying to root the phone (wich i did) and then the twrp app that was on my phone after i had tried to install it using the img. it then turned into an ap that told me to update it in google play
after that was done i tried to flash it but everytime i tried it just crashed. a little time later after trying some more times i found that i started it in the bootloader and it ended up with me stuck in a bootloop. again i might not have explained enough. i am huge noob so i really need help.
ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\ . Does it change anything that i use twrp enchilada or does that not matter?
ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\
discord
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
TobiS137 said:
i think i did fastboot boot twrp. still not sure tho :\
Click to expand...
Click to collapse
To keep TWRP as the phones recovery, you'd first need to do as you did "Fastboot boot twrp" but that command will only allow you to boot into TWRP through your pc or whatever you ran that command on. After you've entered that temporary recovery, you'll need the TWRP installer .zip file, and flash that inside of that temporary TWRP. Then you can reboot into recovery on your phone again since it has been installed to one of the partitions.
TobiS137 said:
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
Click to expand...
Click to collapse
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
phone open again
my phone is back up and running again. i changed the partitian slot from A( the broken one with no OS) to B(the unchanged one) and it is now working again. if anyone is having the same problem the try to change to the second slot. it happend in twrp enchilada 3.2.2-0 if it is important. thank you all for your support.
I may be mistaken but I believe all you need to do is flash magisk to get up and running again
hallo dare said:
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
Click to expand...
Click to collapse
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
RusherDude said:
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
Click to expand...
Click to collapse
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
iElvis said:
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
Click to expand...
Click to collapse
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
RusherDude said:
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
Click to expand...
Click to collapse
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
iElvis said:
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
Click to expand...
Click to collapse
I am not denying anything! just surprised because on TWRP website they clearly state that no post-twrp-flashing step is needed:
https://twrp.me/oneplus/oneplus6.html
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel.
Click to expand...
Click to collapse
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
RusherDude said:
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
Click to expand...
Click to collapse
I think most people have moved to the official version. If it doesn't need magisk to avoid a bootloop, that's news to me. Not saying it's not the case, but I haven't seen any mention of it.

Updated Working twrp and decrypt steps for hannah & nora

hey guys i finally got my twrp back up and running here it is and i fixed format issue it had also supports f2fs now which is what stock uses and added a couple extra parititons it mounts and backs up
use cmd to flash twrp:
fastboot flash recovery updated-hannah-twrp-2019.img
hannah twrp:
https://drive.google.com/file/d/1ahEDJRaW6ZbpF7EgokQtQ6TEJ8yBUa9d/view?usp=drivesdk
cmd for nora:
fastboot flash recovery nora-twrp.img
nora twrp:
https://drive.google.com/file/d/12IPnevc7si2sNpxChMtPo5JJgwY4DJXh/view?usp=drivesdk
Sry i went MIA had alot happen lately so anyways im back here u go
for decryption patch a backed up boot.img with magisk beta both preserve boxes unchecked then flash in twrp as boot.img and flash zip below thanks @whodat711 for zip
https://drive.google.com/file/d/1-C4-ktJmW_oeyP1f5SAPGy3CX90mDuts/view?usp=drivesdk
then format data not wipe but format data button then type yes and press back all the way to main menu then flash masgisk 18.0.zip then reboot and it will not encrypt and u will have to start over as if phone is brand new ie. setting up google but enjoy ur decrypted e5+......
1.boot twrp and backup boot.img
2.make patched boot.img with magisk all perserve boxes unchecked while making it with magisk manager
3.flash twrp
4.flash patched boot.img and decryption zip from third link in post
5.format button in wipe section
6.flash magisk
7.reboot
Stock ROM MetroPcs xT1927-4 Hannah_T running good
skullkid383 said:
First and foremost I want to thank everyone in the twrp building group on telegram and @TwrpBuilder for the amazing guide on how to build twrp and guidance they gave to build this twrp
https://github.com/TwrpBuilder/twrpbuilder_tree_generator/wiki
So here is the twrp I built
https://drive.google.com/file/d/1aNTE6iAQQ4Ty1Zr1oM9ADb7xX_slrTzt/view?usp=drivesdk
After u flash twrp u need to edit fstab to disable force encryption then wipe phone flash latest beta magisk and ur all set
Refer to this guide for
Force encryption fstab file and how to disable force encryption thanks for this @CodyF86
https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
Click to expand...
Click to collapse
just installed your Hannah-twrp.img and it booted just fine everything works thanks
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues. Thanks for your work.
Thank you so much for this!
jokono421 said:
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues. Thanks for your work.
Click to expand...
Click to collapse
Yes sir
jokono421 said:
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues.
Click to expand...
Click to collapse
So you can actually boot from device now yes awesome ...
Keeps trying to force encryption but fails when flashing a gsi.
Is there a way around this? No verity for this device?
JimmyJurner said:
Keeps trying to force encryption but fails when flashing a gsi.
Is there a way around this? No verity for this device?
Click to expand...
Click to collapse
Are u on stock with root I got easy solution for u to follow if fstab guide above is to hard
Hey skullkid383, thankyou for your work on this!! Twrp flashed and works NP. But I cannot decrypt. Following steps, the step you mount before pushing in twrp adb does not work, no such folder. The push goes thru fine although the mount did not. Format data worked, I can see internal storage and move things to and from PC through tether. But when I reboot its sticks on moto screen. When I flash back to patched boot for magisk the is boots to an "decryption unsuccessful" msg and asks me to reset the phone endlessly. Any help pls?
Project89Odin said:
Hey skullkid383, thankyou for your work on this!! Twrp flashed and works NP. But I cannot decrypt. Following steps, the step you mount before pushing in twrp adb does not work, no such folder. The push goes thru fine although the mount did not. Format data worked, I can see internal storage and move things to and from PC through tether. But when I reboot its sticks on moto screen. When I flash back to patched boot for magisk the is boots to an "decryption unsuccessful" msg and asks me to reset the phone endlessly. Any help pls?
Click to expand...
Click to collapse
I'm looking into how to flash fstab in a zip cause I don't think fstab worked for some reason try patched boot.img here see if it changes anything wipe after flash https://drive.google.com/file/d/1s-nS6rLk1tnO1JVFO1emTJdGcO6mNhBk/view?usp=drivesdk
With this boot and wiping after fastboot and twrp installs it boots past moto logo but hangs with the decryption unsuccessful msg
Project89Odin said:
With this boot and wiping after fastboot and twrp installs it boots past moto logo but hangs with the decryption unsuccessful msg
Click to expand...
Click to collapse
Ok so ur fstab is not edited for some reason so do u have a old stock backup I will have u change fstab manually in stock then boot to the twrp and wipe
I do not, I'll have to fastboot flash everything back to revert to stock. Was rockin with no SD tonight.
Project89Odin said:
I do not, I'll have to fastboot flash everything back to revert to stock. Was rockin with no SD tonight.
Click to expand...
Click to collapse
Grrr always make backup rule number one lol ok I'm looking into getting a flashable zip made but in mean Time revert stock tell me when booted
Back up fully stock, not even twrp lol. Metropcs variant btw
Project89Odin said:
Back up fully stock, not even twrp lol. Metropcs variant btw
Click to expand...
Click to collapse
1st make a backup just in case:
Ok here we go flash twrp and magisk beta then patched boot.img boot system get a file explorer with root permissions edit fstab.qcom find it here: /vendor/etc.
just replace current one with one I'm uploading
in guide to make easier to find wipe then u should be good of course flash magisk beta after u wipe as well
Hmm still decryption unsuccessful. About to reflash to stock. Sorry for the slow response. I have the next several hours free to test. I don't have an SD card, so i rooted the old way, using your patched boot, then used es file explorer to replace fstab, rebooted to confirm, and fstabs permissions had changed from rw r r to rw rw so it stuck. once I format data and internal becomes visible I move magisk over, flash then reboot and get dencryption unsuccessful. Also even flashing the recovery before formatting resulted in it being lost every reboot, only after format data it stuck.
Project89Odin said:
Hmm still decryption unsuccessful. About to reflash to stock. Sorry for the slow response. I have the next several hours free to test. I don't have an SD card, so i rooted the old way, using your patched boot, then used es file explorer to replace fstab, rebooted to confirm, and fstabs permissions had changed from rw r r to rw rw so it stuck. once I format data and internal becomes visible I move magisk over, flash then reboot and get dencryption unsuccessful. Also even flashing the recovery before formatting resulted in it being lost every reboot, only after format data it stuck.
Click to expand...
Click to collapse
Ok I am going to build new one in awhile my PC screen broke idk when but until then the link to Hannah twrp is down till I fix it
Ah man, so instead of fastboot flashing everything back to stock, I figured I'd just flash stock recovery back, after the decryption unsuccessful route. Flashed stock recovery, when it booted and asked me to reset the phone instead of going to twrp this time it went to the stock recovery image of a reset...phone booted, got to looking around and holy crap I'm decrypted! flashed your twrp and now I'm rooted with twrp and decrypted!! So maybe boot twrp the first time when formatting data and decrypting so when you boot and the device asks you to reset because of decryption failure it can use stock recovery to complete the process, then flash twrp for the finish? Your incredibly helpful man, again thankyou for all of your efforts and work on this!!
Still wanna fix twrp found a issue in formatting data I wanna fix but it shall take some time to get it done link is down til then cause it's something that needs fixed first before I put it back up

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.

Can't reboot to Recovery after upgrade to Android 10

Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John
Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.
Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John
Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.
Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.
firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.

Categories

Resources