Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
Flashing Disabled vbmeta (To boot a modified system)
Spoiler: View
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Sources
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/DevZillion/android_device_samsung_gta7litewifixx/
Kernel Source - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx
Click to expand...
Click to collapse
Special thanks to:
TeamWin for the Recovery Project.
Zillion for doing the device tree & kernel.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Genial!!
Zillion said:
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite WiFi.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
Flashing Disabled vbmeta (To boot a modified system)
Sources
Special thanks to:
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Click to expand...
Click to collapse
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
dda7lite said:
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
Click to expand...
Click to collapse
Please, read the How To Install section.
Zillion said:
Please, read the How To Install section.
Click to expand...
Click to collapse
I did but the file that needs to be flashed is unavailable in that link
dda7lite said:
I did but the file that needs to be flashed is unavailable in that link
Click to expand...
Click to collapse
Thanks for reporting the issue, link fixed.
Zillion said:
Thanks for reporting the issue, link fixed.
Click to expand...
Click to collapse
i have other problem error "E:unable to open block device /dev/block/sda: No medium found"
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
chocovo said:
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
Click to expand...
Click to collapse
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
dda7lite said:
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
Click to expand...
Click to collapse
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
chocovo said:
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
Click to expand...
Click to collapse
I only did once and I didn't use the stock vbmeta I just searched "vbmeta disabled Samsung" it should show up with vbmeta disabled android 11 but works the same on 13 and I didn't use TWRP only fastboot so i don't know how to flash it there.
Btw your English is good don't worry.
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Yeah
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
Bootloop after
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
chocovo said:
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
Click to expand...
Click to collapse
If you really want to flash a gsi and can't get it to work use a fastboot enabled recovery that's what I did
dda7lite said:
Bootloop after
Click to expand...
Click to collapse
Disable vbmeta, it's the only thing I can see you missed.
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Gian-D said:
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Click to expand...
Click to collapse
Force restart and keep the usb cable connected to the PC and tablet then as soon as screen blinks hold volume +and-
Related
TWRP for C9LTECHN/SM-C9000 Galaxy C9 Pro
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
PLEASE BEFORE YOU FLASH ROMS MAKE A COMPLETE BACKUP OF YOUR SYSTEM INCLUDING EFS SO YOU DO NOT BRICK YOUR MOBILE
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to intall TWRP using ODIN
1) Go to Settings » About phone » and tap “Build number” seven times to enable “Developer options”.
2) Go back to the main Settings page, scroll to bottom and select“Developer options” from there.
3) Under Developer options, look for “Enable OEM unlock”checkbox/toggle and make sure you Check it or turn it ON.
4) Now Boot your Samsung Android device into Download mode.To Do So Follow the steps below
5) Switch off your device.
6) Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin will automatically detect the device and show an “Added!!” message. If not then your device is not connected properly
7) Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
8) Click the Start button on Odin to start Flashing and wait for it to finish the process.
Once it finished successfully, a pass message on the Odin screen will pop up
Your device will automatically reboot when Odin is done flashing. Now You can disconnect your device.
Done!!! TWRP is now installed on your device
NOTE: YOU MAY HAVE TO UNCHECK AUTO REBOOT IN THE OPTIONS TAB IN ODIN
TWRP source code: https://github.com/TeamWin
Source code device tree: https://github.com/travismills82/twrp_android_device_samsung_c9ltechn https://github.com/TeamWin/android_device_samsung_c9ltechn/
TWRP Nougat Download: https://www.androidfilehost.com/?fid=889964283620775437
TWRP Oreo Download: https://www.androidfilehost.com/?fid=1322778262903985796
no-verity-no-encrypt: https://www.androidfilehost.com/?fid=745425885120752506
ROOT OPTIONS:
SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Contributors @travis82 @k2wl @deadman96385
I can confirm this works. backup, mount data, restore, otg usb, install.
I am runnung it now
Does this work on a SM-C9000?
Flavio said:
Does this work on a SM-C9000?
Click to expand...
Click to collapse
That's already for C9000. Can't you see the c9ltechn article. That's c9 pro's code
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Flavio said:
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Click to expand...
Click to collapse
You can flash any file still that just an article but you can't mount data anymore or backup data
I can flash files but cannot mount Data. I presume it is still encrypted despite being formatted twice?
Format data and reboot to recovery
ivanox1972 said:
Format data and reboot to recovery
Click to expand...
Click to collapse
So in TWRP format Data and then reboot again in TWRP.
And then flash SuperSU and no_verity?
Ok, I formatted Data twice in TWRP. Mounting Data works.
I flashed SuperSU in TWRP. Mounting Data works.
I flashed no_verity. Mounting Data works.
I rebooted into TWRP. Mounting Data works.
I rebooted into system and then switched off and rebooted into TWRP. Mounting Data does not work.
What am I doing wrong?
Correction:
I have now used this no-verity-no-encrypt_ashyx file:
https://www.androidfilehost.com/?fid=24591000424951049
And now Data stays decrypted!
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
I tested it few days, it works perfect and it is perfectly debloated
Please share Travis. Thank you for your work.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
can you share it please ???
I presume you would have to flash GApps separately with this ROM?
Flavio said:
I presume you would have to flash GApps separately with this ROM?
Click to expand...
Click to collapse
no god no, HK firmware has gapps built in like normal. I'll tweak it up some more and release it today on a separate thread. Right now I'm trying to get kernels to boot-up since they compile fine.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
I am interested, currently I just using the package disabler to disable all bloat samsung app..
do you have flashable s8 systemui for c9pro.. thanks
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
travis82 said:
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
Click to expand...
Click to collapse
Awesome work buddy, ill try to make my own ROM for this device :highfive:
will be pushing f2fs and ntfs support soon too when TWRP becomes official.
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
install Magisk then official twrp app and flash twrp from the app to recovery
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
Click to expand...
Click to collapse
The only way it worked for me was to install official twrp app, and flash twrp-3.3.1-0-Armor_6.img from the app to recovery, then click on reboot to rrcovery also in the app.
Twrp will only be available one time after the reboot (so it is not really flashed)
(Adb flash recovery doesn't work for me)
In order to use official twrp app, i rooted with magisk
U welcome
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
PanRyba said:
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
Click to expand...
Click to collapse
Same as twrp
Install magisk app and do it from there:
Go to github website and download MagiskManager-v7.3.4.apk
https://github.com/topjohnwu/Magisk/releases
From the apk you will be able to flash your boot partition with magisk (it will save a boot image flashed with magisk on your phone)
The second step is simply to transfer that .img on your computer, install platform tools (in order to use adb command line)
Launch cmd.exe in platform tools folder
Connect your phone to computer via a usb cable and usb debug enabled
Type the command "adb devices" to check if your device is recognised (if a window appear on your phone to enable connection click ok)
Then type "adb reboot bootloader" (you are now in fastboot mode)
Then type "fastboot flash boot (then the name of your flashed with magisk boot image.img that you previously put in platforms tool folder in order to not search for the path)"
Then type "fastboot reboot"
Then from magisk manager app update magisk
That's it
No need for a recovery in the first place to root with magisk
finally works. thanks you dude. I really appreciate your help
PanRyba said:
finally works. thanks you dude. I really appreciate your help
Click to expand...
Click to collapse
You're welcome
Glad to help
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
Click to expand...
Click to collapse
I also used that guide and couldn't get TWRP or Magisk to install on my new Armor 6E. I was able to use "Method 2" and SP Tool to flash TWRP 3.3.1-0, then I was able to flash Magisk using TWRP recovery.
I flashed Magisk-v20. 0(20000).zip
MD5 checksum: 56f82549e9f3c659a11f1f459e56489f
Now I seem to be stuck with the "Orange State" message at boot.
When I attempt to use TWRP to flash "no-verity-opt-encrypt-6.0.zip" I get the following :
-----
Installing zip file '[file path]'
Checking for Digest file...
Verifying zip signature...
Zip signature verified successfully.
##dm-verity and forced encryption disabler by jcadduono version 6.0##
Unpacking the installer...
Updater process ended with ERROR: 1
Error installing zip file' no-verity-opt-encrypt-6.0.zip'
Updating partition details...
... done
-----
The file has this MD5 checksum:
caea927e96c755f3568e85dbded88923
When I attempt to use TWRP to flash "orange_state_disabler_MTK Only.zip" I get the following:
-----
Installing zip file '[pathname]'
Checking for Digest file...
Verifying zip signature...
Zip signature verification failed!
Error installing zip file 'orange_state_disabler_MTK Only.zip'
Updating partition details...
... done
-----
That file has this MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
I get nearly the same result when I attempt to install "ROMProvider.COM_orange_state_disabler 0.3.zip"
(Zip signature verification failed!)
That file also has the same MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
TWRP asks for a password when I first boot into recovery. I also tried to contact them at the unofficialtwrp.com website (where I downloaded the zip files), but their contact page seems to loop back on itself.
Has anyone else run into this (and stuck with Orange State warning at boot)?
ndt44 said:
Now I seem to be stuck with the "Orange State" message at boot.
Click to expand...
Click to collapse
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
Click to expand...
Click to collapse
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
mvyrmnd said:
The 6 and 6E are very similar devices. The TWRP listed here works on the 6E. Magisk also works as described.
I cannot confirm for the 6 (but is likely), but the 6E works with all phh-based GSI ROMs.
These phones use A/B images.
Click to expand...
Click to collapse
Can't post links even when quoting so you just have to google "treble project github"
I have gotten roms to work (use A/B even if treble check says its only A for somereason).
I wasn't able to get liniageOS to work (from the pie roms, i think everyting else seems to work) and android Q ones even thou it should be able to from what i have gathered.
IMPORTANT! It seems like every rom is missing basic features like gestures, i dont know if it has to do with the kernel maybe? Im nubie.
VERY IMPOTANT!! Lost my IMEI number from messing around with the phone so be careful! Im not responsible.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
Would it be possible to get an MD5 checksum and filename which worked for you so that I might compare them? Did you get that file from the unofficial twrp page linked above then? Also were the "system and data EXT4 partitions" on the phone Internal Storage or the USB OTG?
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
Click to expand...
Click to collapse
I obtained this file here:
https://www.google.com/amp/s/rompro...ange-state-fixer-fix-orange-state/amp/?espv=1
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
mrmazak said:
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
Click to expand...
Click to collapse
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
poohju said:
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
Click to expand...
Click to collapse
Thanks. Do you have links?
mrmazak said:
Thanks. Do you have links?
Click to expand...
Click to collapse
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
poohju said:
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
Click to expand...
Click to collapse
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
mrmazak said:
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
Click to expand...
Click to collapse
Good luck to you maybe you can share it when your done
poohju said:
Good luck to you maybe you can share it when your done
Click to expand...
Click to collapse
My phone is still not delivered. But I did compile twrp from source, using the September update files from ulefone site.
I started with the device tree from the armor 6, and made few changes that I have found to work for treble devices and system as root on other recent mtk phones I have.
But I can't confirm the build works. If you want to beta test it, let me know.
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 lite 5G
bugs:
backup/restore is unreliable
adb sideload and fastbootd
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Contributors:
@VladV1V , @TheMalachite
Tree:
GitHub - TeamWin/android_device_xiaomi_renoir
Contribute to TeamWin/android_device_xiaomi_renoir development by creating an account on GitHub.
github.com
Kernel:
https://github.com/VladV1V/kernel_xiaomi_renoir
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
Sorry, but the installation did not work for me... :-( What i have done:
- i renamend the downloaded file to "twrp.img"
- i copied this file to the internal storage
- i startet the phone in fastboot mode
- then i startet adb
- i used the command "fastboot boot twrp.img"
Then i saw the following:
downloading 'boot.img'...
OKAY [ 2.826s]
booting...
OKAY [ 0.201s]
finished. total time: 3.027s
But the phone only switched off and nothing happend. What's wrong?
EDIT: i solved the problem! I forgot to put the file "twrp.img" into the adb folder. After doing this, the installation worked! Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Hi, thank's for your work for our device...
I read somewhere, that if we have TWRP installed, that we cannot flash update with fastboot...I want to know if it's true and if yes, how can we flash update..we have to find recovery update, or we can extract from fastboot archive and flash it??
thanks for your answer
Rainman67 said:
Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Click to expand...
Click to collapse
certainly not available yet...you have to backup in internal storage and then copy to SD...
Another question: how to go back to stock recovery?
Rainman67 said:
Another question: how to go back to stock recovery?
Click to expand...
Click to collapse
I'm on Xiaomi EU ROM. After last update via fastboot Miui Recovery 5.0 comes back.
Great hopefully this leads to development of some easy to flash roms, cant wait to get rid of this buggy MIUI trash.
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
same with #8 boot into twrp and no touchscreen
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
Boot TWRP from fastboot and touch will work.
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
How did you flash it?
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Peterpaulmarie said:
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Click to expand...
Click to collapse
pm me on telegram if you can get logs and have adb access
dannejanne said:
Boot TWRP from fastboot and touch will work.
Click to expand...
Click to collapse
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
i just boot to try if it can boot in twrp lol, no need to flash it so far,if needed it i will use the method u guys said(real flash in)
Well then both of you make sure you're actually using the build from afh and only use it for fastboot boot, when you want to flash use flash current twrp don't flash it with fastboot
Touch works when using fastboot boot and when flashed, it Was already tested on multiple devices
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
doclucas said:
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
Click to expand...
Click to collapse
Touch already works normally without fastboot
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Yes, I can confirm. After start recovery wait 10-15sec touchscreen will work
With the test builds from telegram twrp was not able to recognize my SD card. Is this now fixed?
Is it possible to flash Xiaomi.eu weekly rom only by starting twrp from fastboot without installing it?
Note: Flash at your own risk. This Build still in Alpha Stage, and can be considered as non-stable yet, and still in the process of testing.
Build Product: macedonia
Build Asserts: RMX3301, RMX3300
Build Date: 03/05/23
Build Release: Unofficial Alpha
Build Branch: 12.1 (v3.7.0)[/B][/I]
[B][I]Compatibility: RUI 4.0 and 3.0
Release Notes
TWRP now boots, decryption is working fine but aren't tested in GSI.
Do not flash OTA firmware yet, it is not well-tested, could brick your device.
Realme GT2 Pro is Virtual A/B with dedicated Recovery Partition, no need to boot it like other A/Bs, just flash it.
Working Features
Internal Storage
FastbootD
ADB Commands and Terminal
Flashing .zip files like magisk and recovery.
Flashing non-logical .img files.
ADB Sideload
MTP
Backup/Restore
Issues and Bugs
External Storage
Flashing OTA.
Vibration/Haptics
How to FlashAssuming you already have unlocked bootloader, your PC has adb/fastboot installed, and platform tools. Let's begin.
Download the .img file from the release page.
Place the image file inside platform tools folder in your PC.
Now, open CMD inside platform tools folder.
Boot your device in bootloader/fastboot mode.
Type in CMD: fastboot flash recovery name-of-twrp.img. It'll flash in current active slot.
If you want to flash it in specific slot, add slot suffix _a or _b:
fastboot flash recovery_a name-of-twrp.img
fastboot flash recovery_b name-of-twrp.img
After flashing is done, type: fastboot reboot recovery.
Enjoy your new custom recovery—TWRP.
DOWNLOAD HERE: link
Source code: https://github.com/hoangzk9as/custom_recovery_tree_realme_macedonia
Contributors: cd-Crypton, xuanhoang1811
Excellent work
Hi, very great work!
I just wanted to confirm that OTG indeed does not currently. Tried with a couple of different USB Sticks, but "USB Storage" still shows as 0MB and pressing "mount" does nothing.
Fatal_Scythe said:
Hi, very great work!
I just wanted to confirm that OTG indeed does not currently. Tried with a couple of different USB Sticks, but "USB Storage" still shows as 0MB and pressing "mount" does nothing.
Click to expand...
Click to collapse
Oh, thanks for testing, i'll try to fix it
Fatal_Scythe said:
Hi, very great work!
I just wanted to confirm that OTG indeed does not currently. Tried with a couple of different USB Sticks, but "USB Storage" still shows as 0MB and pressing "mount" does nothing.
Click to expand...
Click to collapse
Excuse me, did you root your device?
Can you run this command for me in termux, while otg was plugged in?
cat /proc/partitions
Great.
xuanhoang1811 said:
Excuse me, did you root your device?
Can you run this command for me in termux, while otg was plugged in?
cat /proc/partitions
Click to expand...
Click to collapse
Yep, my Phone is rooted.
Here's a text file with the output of the command ^^
Fatal_Scythe said:
Yep, my Phone is rooted.
Here's a text file with the output of the command ^^
Click to expand...
Click to collapse
Hi, i made another twrp build, can you flash and check it with OTG again
DOWNLOAD HERE
xuanhoang1811 said:
Hi, i made another twrp build, can you flash and check it with OTG again
DOWNLOAD HERE
Click to expand...
Click to collapse
Hey, thanks!
Unfortunately, OTG still doesn't work. ^^''
OTG in Android works, but when rebooting to Recovery I can't mount "USB Storage"
Fatal_Scythe said:
Hey, thanks!
Unfortunately, OTG still doesn't work. ^^''
OTG in Android works, but when rebooting to Recovery I can't mount "USB Storage"
Click to expand...
Click to collapse
Thanks for testing, we're trying to fix this error
xuanhoang1811 said:
Thanks for testing, we're trying to fix this error
Click to expand...
Click to collapse
Your welcome.
Thanks for taking the time to build TWRP for our Device. ^^
Feel free to let me know when you need someone to test something
Thanks a lot! I will try it in few days.
First of all, thanks for your work. ADB Sideload is still not working in the second release. Here, I attach a log file.
Is the project dead ?
xuanhoang1811 said:
Note: Flash at your own risk. This Build still in Alpha Stage, and can be considered as non-stable yet, and still in the process of testing.
Build Product: macedonia
Build Asserts: RMX3301, RMX3300
Build Date: 03/05/23
Build Release: Unofficial Alpha
Build Branch: 12.1 (v3.7.0)[/B][/I]
[B][I]Compatibility: RUI 4.0 and 3.0
Release Notes
TWRP now boots, decryption is working fine but aren't tested in GSI.
Do not flash OTA firmware yet, it is not well-tested, could brick your device.
Realme GT2 Pro is Virtual A/B with dedicated Recovery Partition, no need to boot it like other A/Bs, just flash it.
Working Features
Internal Storage
FastbootD
ADB Commands and Terminal
Flashing .zip files like magisk and recovery.
Flashing non-logical .img files.
ADB Sideload
MTP
Backup/Restore
Issues and Bugs
External Storage
Flashing OTA.
Vibration/Haptics
How to FlashAssuming you already have unlocked bootloader, your PC has adb/fastboot installed, and platform tools. Let's begin.
Download the .img file from the release page.
Place the image file inside platform tools folder in your PC.
Now, open CMD inside platform tools folder.
Boot your device in bootloader/fastboot mode.
Type in CMD: fastboot flash recovery name-of-twrp.img. It'll flash in current active slot.
If you want to flash it in specific slot, add slot suffix _a or _b:
fastboot flash recovery_a name-of-twrp.img
fastboot flash recovery_b name-of-twrp.img
After flashing is done, type: fastboot reboot recovery.
Enjoy your new custom recovery—TWRP.
DOWNLOAD HERE: link
Source code: https://github.com/hoangzk9as/custom_recovery_tree_realme_macedonia
Contributors: cd-Crypton, xuanhoang1811
Click to expand...
Click to collapse
any possibilities that RMX3312 (GT2) might get a TWRP from your side?
Too bad there is no custom rom support.
Please has anyone been able to port TWRP recovery for an a/b partitioned device, I mean devices that contains the recovery ramdisk in the boot.img and doesn't have a separate recovery partition.
Thanks in advance.
Kelexine said:
Please has anyone been able to port TWRP recovery for an a/b partitioned device, I mean devices that contains the recovery ramdisk in the boot.img and doesn't have a separate recovery partition.
Thanks in advance.
Click to expand...
Click to collapse
What do you mean by "port"?
TWRP is supported on multiple A/B devices such as the Google Pixel. However, TWRP does not support the compression necessary to replace the stock recovery in the boot image, so TWRP may only be used "live", where the TWRP image is booted via command, instead of being flashed to /boot.
V0latyle said:
What do you mean by "port"?
TWRP is supported on multiple A/B devices such as the Google Pixel. However, TWRP does not support the compression necessary to replace the stock recovery in the boot image, so TWRP may only be used "live", where the TWRP image is booted via command, instead of being flashed to /boot.
Click to expand...
Click to collapse
By porting I mean changing some files, like copying the kernel and other device specific files to a prebuilt TWRP boot image for a related device.
For example I was able to do that for my android 8 based device and it worked flawlessly, but my problem is that I don't know how to do that for a/b partitioned devices cause my device is not officially supported and i can't seem to find any unofficial version for my device, plus my phone's kernel source and device are not published on GitHub or anywhere.
But some devices specially some Mediatek and Unisoc based devices don't support live boot and so it's necessary two flash it to the boot partition.
Finally built twrp for this device after so many attempts, here is the file for those that owns this device too.
NOTE: This file is for KG5j variant not KG5k or any other variant
Kelexine said:
Finally built twrp for this device after so many attempts, here is the file for those that owns this device too.
Click to expand...
Click to collapse
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
I don't understand, please explain your issues so I can know how to help
Follow this guide https://forum.xda-developers.com/t/...hat-does-not-have-recovery-partition.4572311/
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
You can use the updated version with crypto support and automatic data partition decryption.
Download from https://github.com/dextterblog/Twrp-builder/releases
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
After flashing run fastboot reboot, it will reboot directly to TWRP recovery enter your lock screen password to unecrypt data, then click on advanced install recovery ramdisk and select the twrp.img you downloaded or click on advanced then install current TWRP and let the recovery do the rest.
Check it out on hovatek forum
Kelexine said:
Here is a copy of you can't download from GitHub.
Click to expand...
Click to collapse
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This Guide will help you!
FiniteCode said:
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This Guide will help you!
Click to expand...
Click to collapse
Thanks but I already compiled for my device
Kelexine said:
Thanks but I already compiled for my device
Click to expand...
Click to collapse
Great! No Problem...
(*Sigh* Why Am I So Late At Everything?)
FiniteCode said:
Great! No Problem...
(*Sigh* Why Am I So Late At Everything?)
Click to expand...
Click to collapse
Just keep trying your best
New release: TWRP recovery for TECNO SPARK 8C
Link to files are here for latest build look here and for direct download click here