Database Develop

[Recovery][EMUI 8.x][Mate 9][Unofficial]TWRP 3.2.1-0 [28/04/2018]

Disclaimer​This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation​
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_mate9_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features​
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** @Tecalote - He was the main tester for this version and also he was the one that convinced me to open this thread in first place
**** @Blackball
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_mate9_0.1.img - initial release

Thank you for such a great project!

I am very happy with this TWRP. Everything is working so far on EMUI, Android 8.
Data wipe is possible, cause OEM Path is excluded.
Vendor.img and System.img and recovery_ramdisk can be flashed by choosing img to the related img.
Backup, restore of all shown Partitions working perfectly.
Decryption of storage if using Fingerprint /PIN is working. Full encryption support for data..
Many thanks to @Pretoriano80 for this awesome and first most complete TWRP for Mate 9 :good::good:
BTW: @Blackball had tested this TWRP for P10 Plus and it is also working on this Device (so it will run also on P10).
Many thanks for testing too :good:

This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?

Wirmpolter said:
This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?
Click to expand...
Click to collapse
Format data is only necessary if installing AOSP based Roms which require this (in installation guide)
But for Stock Firmware you don't need to decrypt (format) anything because encryption is fully supported
Of course, you can't install older Stock based Custom Rom which mount data in the updater-script without /dev/block/dm-0

I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.

osk4rin said:
I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.
Click to expand...
Click to collapse
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.

Tecalote said:
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.
Click to expand...
Click to collapse
Oh right, thanks.

Seems to work perfectly, in my case the rom doesn't even seem to be overwrite twrp upon normal boot
Thanks a lot!

osk4rin said:
Oh right, thanks.
Click to expand...
Click to collapse
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.

i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password

Caguayote said:
i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password
Click to expand...
Click to collapse
If it's ask for password, then insert the same passwords/pin/pattern that you are using in Android, so TWRP can decrypt the internal storage.
That's the whole purpose of having a TWRP with decryption support.

10-4
Thank you for the clarification

Pretoriano80 said:
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.
Click to expand...
Click to collapse
how can I get them?

osk4rin said:
how can I get them?
Click to expand...
Click to collapse
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop

Work this nougat .. ??

Tecalote said:
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop
Click to expand...
Click to collapse
I just attached the build.pro files .Using RR remix treble project

Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!

_Nostromo_ said:
Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!
Click to expand...
Click to collapse
No, it's designed to work like this!

Pretoriano80 said:
No, it's designed to work like this!
Click to expand...
Click to collapse
Ok, thought so, it definitely makes sense, just being a bit lazy... Thanks a lot for your prompt response, Pretoriano80! :good:

[RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A70

Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/[/I]
I’d recommend to read everything in this post, if you care about your expensive phone.
Let’s start with the installation process
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
If you already installed a previous version of TWRP, start with step 4.
If you already have TWRP installed and just want to root, start with step 5.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Now you need to overwrite vbmeta partition, so you can flash third party partitions. Download vbmeta.tar then go into download mode on your device. Put vbmeta.tar to AP in Odin, click start. This should finish pretty quickly, so pay attention when your device reboots, because you need to boot into recovery (Hold power and volume up after the screen turns black). When booted into recovery, wipe your data and reboot normally into system. Now you can setup your phone as usual and make sure oem unlocking is still greyed out and enabled!
Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
(Optional) You might have lost root access by flash TWRP if you followed this standard guide for rooting. If you did lose it and want to gain root access again (you can also root your device with this method, even when you never rooted your device), download the latest Magisk Manager from the canary channel and install the apk to your phone.
If you are on stock:
Push the recovery.img file you just download for TWRP to your phone. Open Magisk Manager and hit install and patch a file. Select recovery.img and Magisk should start the patching process. Once Magisk is done, boot into TWRP. Backup your boot partition first and afterwards go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
If you are on an AOSP based rom:
Reboot to TWRP. Create a backup with boot partition. Reboot back to system, then open Magisk and hit install and patch a file. Locate the TWRP backup folder and look up your backup you just created. Select boot.emmc.win for patching. Once Magisk is done, reboot back to TWRP. Go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
So that was the easy part. The hard part is to completely read these following points!
Encryption/Decryption
Decryption works on this TWRP release, but only partially. That means you have to open the Settings Application first on your phone and disable a feature called strong protection. You can find it in Settings->Biometrics and security>Other security settings. It doesn’t matter when you disable it. Flash TWRP first and disable it, fine. Disable it and flash TWRP afterwards, fine. Never disable it, also fine, TWRP just fails to decrypt your data, but won’t do any harm. When this feature gets turned off, the device will generate a key which doesn't require any authentication for decryption, currently only this allows TWRP to decrypt the data partition successfully. This only applies to stock roms though, if you are using an AOSP based rom, then you don't have to do any of this.
Disabling decryption
Disabling decryption will create many problems. First TWRP will refuse to unmount system partition and thus you might run into problems flashing various zips. So I advise you to not disable decryption. If you still want to disable it you have to open terminal in TWRP and type in "stop servicemanager" everytime you want to unmount the system partition.
Backup and Restore
Because of encryption it's more complicated to backup your data partition.
If you want to backup data you have to make sure TWRP successfully decrypted your internal storage, otherwise you will run into problems backing up.
Restoring is even more complicated. Every time you set up a rom, new crypto keys will be generated and you can't backup these. That means if you want to restore data you have to restore the whole rom first excluding data. Format data partition completely, boot it up, then go back to TWRP and restore data. You will lose your internal storage, so I'd recommend you move important stuff to external storage.
Developers specific details
Sources
https://github.com/Grarak/android_device_samsung_a70q-twrp
https://github.com/Grarak/android_device_samsung_a70q
https://github.com/Grarak/android_bootable_recovery-1
Recovery image size
For some reason the ramdisk has a size limit, so I used LZMA compression to get its size down as much as possible.
During kernel compilation you will run into a DTC error. Apparently Samsung didn’t bother to update their DTC source in the kernel and you have to use their precompiled binary. I edited my kernel sources to automatically use their dtc binary.
Credits
Device tree of Redmi Note 7 Pro (https://github.com/TeamWin/android_device_xiaomi_violet). Helped a lot!
Topjohnwu for the detailed installation guide (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
TWRP Galaxy S10 thread for describing System-as-root pretty well
(https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
Downloads
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases (Also changelog)
Note The download is a zip file, unpack it and you will get the recovery image. To flash it in Odin pack it as tar with 7zip or a compression tool of your liking.

reserved

nice work, I'll buy the phone in this 2 days to start some works.

Thanks bro ?
Screenshot please

thanks alot ! development can start on this phone ! (i confirm twrp work)

BK☑️ said:
thanks alot ! development can start on this phone ! (i confirm twrp work)
Click to expand...
Click to collapse
Which version do you have?

devilhunter47 said:
Which version do you have?
Click to expand...
Click to collapse
TWRP version is 3.3.1
actual firmware is A705FNXXU3ASG6_A705FNOXM3ASG6_BTU (july security patch) (United kingdom)
prev. firmware was A705FNXXU1ASE4_A705FNOXM1ASE4_XEF (may security patch) (France)
edit 1 : the ui freeze completly when phone is booted up , had to flash all back
i'm going to flash A705FNXXU1ASD1_A705FNOXM1ASD1_BTU (april security patch) (United kingdom) and see if it boot correctly...
edit 2 : cant flash previous firmware due to 'security reasons' ,i flashed back stock recovery, it doesnt freeze anymore, i guess we will have to wait for a custom kernel

cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?

MTP
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
MTP doesnt work in this build
edit: it work in this build thanks
---------- Post added at 09:38 PM ---------- Previous post was at 09:30 PM ----------
kristiansja said:
cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?
Click to expand...
Click to collapse
i dont think this build is made for treble roms, so probably not

BK said:
MTP doesnt work in this build
Click to expand...
Click to collapse
Uploaded the wrong version. Fixed

Grarak said:
Uploaded the wrong version. Fixed
Click to expand...
Click to collapse
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
BK said:
lemme check
Click to expand...
Click to collapse
edit : it work now thanks!

Thanks dev! Astonished at the progress you've made despite Sammy's carelessness

BK☑️ said:
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
edit : it work now thanks!
Click to expand...
Click to collapse
With July security patch?

Okay, so can anybody else see if system or system images backup crashes TWRP?

FriendlyNeighborhoodShane said:
Okay, so can anybody else see if system or system images backup crashes TWRP?
Click to expand...
Click to collapse
yep , i tried backups yesterday but twrp crash when backing up system.img
---------- Post added at 09:04 AM ---------- Previous post was at 09:01 AM ----------
devilhunter47 said:
With July security patch?
Click to expand...
Click to collapse
i was refering to MTP , the link been fixed, MTP work now , but phone crash after boot up , or just wont boot at all, i were also stuck in prenormal RMM, thats why it wouldnt boot

Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse

Kernel source A70Q
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?

BK said:
Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse
Seems to be a kernel problem. Probably have to wait for Samsung to update their sources.
BK said:
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?
Click to expand...
Click to collapse
No
Click to expand...
Click to collapse

Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i contacted the guys from Samsung Opensource Center for kernel and platform source release, ill see what they say...

How to install TWRP can anyone tell step by step....

[RECOVERY][RMX1971][UNOFFICIAL] TWRP 3.3.x for Realme 5 Pro / Realme Q

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works( in android 10 & 9)
- Flashing Ozip works
- Flashing RealmeUi works
- Otg works
- Backups works
- Flash Rom works
- Sdcard works
Download:
TWRP
To Flash the TWRP:
Code:
Code:
fastboot flash recovery twrp_RMX1971-20200228.img
Then reboot in TWRP manually.
Source code: https://github.com/omnirom/android_bootable_recovery
Kernel source: https://github.com/bablusss/kernel_realme_sdm710
Credits:
Thanks to @mauronofrio and testers​

Reserved

Thanks for Updated TWRP ^_^
Everything works fine af, using from the last few weeks.

Thank you so so much!!!
Finally managed to decrypt the internal storage

Can anyone guide me for bootloader unlocking in Realme UI?

Twrp disappeared after reboot. Tried flashing twrp again, reboot, and next time i go twrp it's always replaced back to stock recovery. How to fix?

nickycarlo69 said:
Twrp disappeared after reboot. Tried flashing twrp again, reboot, and next time i go twrp it's always replaced back to stock recovery. How to fix?
Click to expand...
Click to collapse
Did you find any solution to this? Same happens here - once you've bootet to system (Realme UI) recovery is reverted back to stock.

nickycarlo69 said:
Twrp disappeared after reboot. Tried flashing twrp again, reboot, and next time i go twrp it's always replaced back to stock recovery. How to fix?
Click to expand...
Click to collapse
Have the same problem, but it seems this forum is dead. Shame, before updating it all worked just fine, now, its all gone an TWRP doesnt stick.
For now the phone seems unrootable.

Marduk666 said:
Have the same problem, but it seems this forum is dead. Shame, before updating it all worked just fine, now, its all gone an TWRP doesnt stick.
For now the phone seems unrootable.
Click to expand...
Click to collapse
I already gave guide for flashing realmeui follow this link u get ur answer. https://t.me/Realme5Pro_Downloads/581

BabluS said:
I already gave guide for flashing realmeui follow this link u get ur answer. https://t.me/Realme5Pro_Downloads/581
Click to expand...
Click to collapse
Oh! Didnt saw this! Thank you!
---------- Post added at 12:13 PM ---------- Previous post was at 11:28 AM ----------
BabluS said:
I already gave guide for flashing realmeui follow this link u get ur answer. https://t.me/Realme5Pro_Downloads/581
Click to expand...
Click to collapse
Is it safe to flash Magisk on RealmeUI?

cant flash recovery , i always get one of these errors , tried booting it too, still no luck tried different usb cables ,different ports 2.0 and 3.0
flashing on top of realme ui
need help , please

Thanks
BabluS said:
{Mod edit: Quote shortened for better reading experience!}
Click to expand...
Click to collapse
thanks for the recovery

Updating 11/07/2020 package via updater in settings..after updating showing No sim card in both sim..please help shortly

jeetubhatreja said:
Updating 11/07/2020 package via updater in settings..after updating showing No sim card in both sim..please help shortly
Click to expand...
Click to collapse
Wrong thread mate and if u were asking about pe do clean flash and use full package

BabluS said:
Wrong thread mate and if u were asking about pe do clean flash and use full package
Click to expand...
Click to collapse
Can i use dirty flash ?

I am stuck in twrp loop, can't boot to system after attempt to flash Aex rom. Any solution to make it boot? Atleast back to stock?
Edit: stock rom I used before twrp was Latest RUI, Android 10.

Does vbmeta have to be flashed if i want to update twrp also? And can i flash from within existing twrp?

hi i need stock recovery urgently
i cand extract from ozip firmware
please help me

Can't restore data from any ROM backup, always give fork error. Ideas?

metalgold2301 said:
hi i need stock recovery urgently
i cand extract from ozip firmware
please help me
Click to expand...
Click to collapse
Rename the ozip to zip and try reflashing the same again, you'll succeed. Hope this helps!

[Unofficial][Recovery][X505X] TWRP for Lenovo Tab M10 - X505X

Code:
**Disclaimer
*I am not be responsible for any bricked devices, data loss or thermonuclear wars.
*You are using this at your own risk.
Introduction
Welcome to TWRP for Lenovo Tab M10 X505X. Make sure you read the entire post carefully before you proceed with installation.
Pre-installation
Install ADB and Fastboot. Refer to this link if you need help installing ADB and Fastboot.
Unlock the bootloader. Refer to this link if you need help unlocking the bootloader.
Installation
Flash the TWRP image from bootloader.
Code:
fastboot flash recovery twrp.img
Warning:
Do not reboot the system yet. Remove the connection from the device. Hold the power button until it turns off. Then turn it on again with the recovery combo: Power button + Volume Up + Volume Down.
Once booted into the TWRP recovery mode, if you want to flash it permanently(otherwise it will be replaced with stock recovery after a reboot), install Magisk from recovery.
You can goto advanced option in TWRP and use the "ADB Sideload" option to sideload the Magisk zip file. In case sideload doesnt work, use adb to push the Magisk zip file to /tmp and then install the zip normally.
Warning:
Do not push the zip file to /data. The data partition is encrypted and any damage done messing with the data partition will not be my responsibility. You have been warned.
Downloads
TWRP image for X505X
Magisk
Known Issues
From android 9.0 onwards, the data partition is force encrypted and is not available to the TWRP. This is not much of an issue because update zips and ROM flashes usually dont use the data partition. So the data partition is encrypted.
Changelog
Code:
This is the first version
Upcoming Features
Support for decryption of data partition permanently/temporarily.
Upcoming Project
A custom rom for this device if I get enough support.
Donations
I have spent a lot of time on this project. Consider buying me a coffee or donating. It will be great support.
Google Pay
Feel free to ask me if you encounter any problems.
Device Tree
For those who are curious. This is the device tree I ported for X505X.
If this helped you, hit the thanks button.
It would mean a lot to me if you could follow me on :-
Github
Instagram
Special Thanks
Code:
Yahoo Mike - For his great support
XDA:DevDB Information
Custom Recovery for Lenovo Tab M10 X505X, Tool/Utility for the Lenovo Thinkpad Tablet
Contributors
Shamil Niyas, Yahoo Mike
Version Information
Status: Beta
Current Beta Version: 2.84
Beta Release Date: 2020-11-12
Created 2020-11-13
Last Updated 2020-11-13

Reserved

Hi, Useful thread here, I flashed this recovery to X505F and it's working fine except MTP and data partition does not unencrypt.
Can it be fixed somehow?
looking for a custom rom for this device as well.
Please help!

Hi, i dont have a pc currently with me, how can i do it using a mobile.

zubair1836 said:
Hi, Useful thread here, I flashed this recovery to X505F and it's working fine except MTP and data partition does not unencrypt.
Can it be fixed somehow?
looking for a custom rom for this device as well.
Please help!
Click to expand...
Click to collapse
I'm still working on the data encryption. I will update as soon as possible.
Look forward to the custom rom..

cYBER~VeTeRaN said:
Hi, i dont have a pc currently with me, how can i do it using a mobile.
Click to expand...
Click to collapse
Unfortunately you cannot flash it without pc. Or if you can access fastboot using your mobile and termux you might be able to flash, though I cannot guarantee it.

Pls update twrp to latest verison 3.5

cYBER~VeTeRaN said:
Pls update twrp to latest verison 3.5
Click to expand...
Click to collapse
Thanks...I will update asap...

Sir, i would like to know which rom u r planning to port, expecting a gaming rom, also i would like to know the current progress , thanks in advance

I have a lenovo m10 tablet as well but it's said to be a X306F instead? Will it work you think?

Ooo_64 said:
I have a lenovo m10 tablet as well but it's said to be a X306F instead? Will it work you think?
Click to expand...
Click to collapse
Do try booting thr recovery without flashing and post the result.
For booting without flashing run :
fastboot boot recovery.img

cYBER~VeTeRaN said:
Sir, i would like to know which rom u r planning to port, expecting a gaming rom, also i would like to know the current progress , thanks in advance
Click to expand...
Click to collapse
I'm still working out the device tree for the rom. Will update as soon as possible.

Forgive me for wondering, but I'm looking at buying a tablet, and I wonder a few things, first of which would be, what is everyone's experiences with this tablet??? The next thing I wonder is if you only plan on doing a single rom??? Say for instance, you started out with a CM rom, then did my personal favorite, ressurrection remix... Or maybe do remix first
Either way, I love android, but am missing ressurrection remix since back when I had a phone that supported it... The ressurrection remix rom has so many options it could take a 30$ device and make it feel like a 300$ device, but that's also a problem, because with lots of extra features and settings comes the greater possibility of bugs

Wiebenor said:
Forgive me for wondering, but I'm looking at buying a tablet, and I wonder a few things, first of which would be, what is everyone's experiences with this tablet??? The next thing I wonder is if you only plan on doing a single rom??? Say for instance, you started out with a CM rom, then did my personal favorite, ressurrection remix... Or maybe do remix first
Either way, I love android, but am missing ressurrection remix since back when I had a phone that supported it... The ressurrection remix rom has so many options it could take a 30$ device and make it feel like a 300$ device, but that's also a problem, because with lots of extra features and settings comes the greater possibility of bugs
Click to expand...
Click to collapse
RR is available on Project Treble as a GSI. You could try that.

So, I flashed recovery, tried rebooting by holding down power button and the volume buttons and now it's stuck in an infinite boot loop. Screen shows lenovo logo, and then it goes blank, vibrates, and then restarts to lenovo logo again. Holding down the power button won't even shut it off. Please help.

TWRP flashed successfully but sadly the data partition didn't work.
so to make it work, I first formatted the data partition and through the adb sideload I flashed disable-dm-verity (attached) and it now works, data-partition is not encrypted anymore.
I also compiled an orange fox recovery for it and the data partition is also working on it.

Yahoo Mike said:
RR is available on Project Treble as a GSI. You could try that.
Click to expand...
Click to collapse
Is the GSI Booted?

One update guys.
I accidently wiped system of TB-X505X and flashed Android 12 Beta 2 GSI and it worked.
only Bluetooth is dead.
and when plugging aux getting grounds from both system speakers and earphone

Wiebenor said:
Forgive me for wondering, but I'm looking at buying a tablet, and I wonder a few things, first of which would be, what is everyone's experiences with this tablet??? The next thing I wonder is if you only plan on doing a single rom??? Say for instance, you started out with a CM rom, then did my personal favorite, ressurrection remix... Or maybe do remix first
Either way, I love android, but am missing ressurrection remix since back when I had a phone that supported it... The ressurrection remix rom has so many options it could take a 30$ device and make it feel like a 300$ device, but that's also a problem, because with lots of extra features and settings comes the greater possibility of bugs
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...top-style-tb-x505x-lenovo-tab-m10-hd.4306713/.
You can go here for RROS for lenovo tab M10 Hd x505x

cYBER~VeTeRaN said:
Hi, i dont have a pc currently with me, how can i do it using a mobile.
Click to expand...
Click to collapse
Use Termux in other device

I tried rooting my lenevo tab M10 hd and flashed a incorrect boot img as I am new to rooting and bricked up my device then from some where I got the correct boot img and recovered my device but now I am unable to use its internal storage , its shows some random letters when I open the file manager can you guys help me out resolving this issue.

[RECOVERY][UNOFFICIAL] TWRP 3.5.2_10 for Moto G 5G (kiev)

DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff.
What has been tested and works:
- Touchscreen
- Installing flashable zips
- Flashing images
- Flashing the recovery itself
- Creating backups (to internal storage, sdcard or OTG)
- Restoring from backups
- Terminal
- adb
- Rebooting to system, recovery, bootloader, ...
That doesn't mean that other things don't work. It just means they weren't tested yet. As I proceed with testing I will update the above list.
Usage (without flashing)
Bash:
# boot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
If you want to flash you have 2 options
Bash:
# boot to bootloader
adb reboot bootloader
# ********* OPTION 1 *********
# Flash to active slot (replace <slot> with either a or b, depending on the current active slot).
# Of course, you can flash to both by first specifying a and then b.
fastboot flash recovery_<slot> twrp-3.5.2_10-kiev.img
# ********* OPTION 2 *********
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
# Once in the recovery, copy the twrp image file to your internal storage
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
# Then go to Install, then Install image, select the twrp image you pushed before.
# Then select the Recovery partition and swipe to confirm.
# Before swiping you will have the option to decide if you want to flash to both slots.
Download: google drive
Sources will be posted in due time and this post will be updated accordingly.
Built for: Motorola Moto G 5G (Motorla One 5G Ace)
My model: XT2113-3 (kiev)
Credits
To the guys over here for the device tree, especially to SyberHexen for providing me with useful information.

reserved

reserved

Great!

Tested on my Moto G 5G XT2113-3. Seems to work properly. Good job. Awaiting to flash it.

It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??

clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
It won't brick. I used it. (only once)

clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.

h3xmind said:
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
Click to expand...
Click to collapse
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.

PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.

Tomspector said:
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Click to expand...
Click to collapse
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me.

I will do it now,
I would help
h3xmind said:
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me
Click to expand...
Click to collapse
I will do it now

Tomspector said:
I will do it now,
I would help
I will do it now
Click to expand...
Click to collapse
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace

Tomspector said:
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Click to expand...
Click to collapse
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.

h3xmind said:
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
Click to expand...
Click to collapse
I did not clear my data, I did not feel like redoing my phone today,
It may be that

Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet

Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Ok, thanks for your help. I won't be testing anything tomorrow. I have a day off with my family

Tomspector said:
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Click to expand...
Click to collapse
Should be here: https://mirrors.lolinet.com/firmware/moto/kiev/official/

Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Anyway, I flashed it by doing the following:
Bash:
# boot to bootloader
adb reboot bootloader
# boot to twrp
fastboot boot twrp-3.5.2_10-kiev.img
# push the recovery image to the Download folder
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
Once inside the recovery I went to Install, then Install image, once I selected the twrp-3.5.2_10-kiev.img file that I previously pushed, twrp asked me on which partition I would like to flash it. I selected the Recovery partition. (Although I ask myself why does the phone have a separate recovery partition if it is an A/B device. I still have to figure this out. Normally in these devices one would have to pack the recovery into the boot imate and than flash the whole thing to the boot partition.)
Then I rebooted to recovery and it took me directly to twrp. The problem, however, is that the touch screen didn't work anymore. So, I guess I got myself some extra work But it'll be fun. I can't wait to put my hands on it.
Did you manage to find the rom for your phone?

PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
I tried Hexen's recovery. It's easily fixable to make the touch work. It took me two minutes. I'll let the guys working on it know how to do it. But first I have to figure out why does the touch screen stop working once you flash the recovery.