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.
*
*/
Installation
Download version .tar when you haven't a TWRP installed and you are coming from stock ROM and flash it via Odin in download mode. NOTE: Un-check Auto-reboot option in Odin, install tar file (it has to be placed in AP section) and after reboot manually in recovery mode with vol+, home and power buttons. This because otherwise you'll come back to stock recovery.
Download version .img when you have a TWRP installed. Simply, from home, go in install -> install image -> select your .img file -> press recovery as partition where you want to install it -> swipe to flash -> reboot system.
Download version .zip if you have an old TWRP. (you can install a .img or .zip file, as you want)
Bugs/Issues
Encryption with password isn't supported, so don't set the secure boot or put a password at the boot of the device
Time/date is wrong when /data is wiped, since it takes the right time from /data/vendor/time/ats_2
On matissevewifi, reboot > recovery button reboots into system. To reboot in recovery, type reboot recovery in twrp terminal, or adb reboot recovery through PC
Download
matisse (SM-T530, SM-T530NU, SM-T531, SM-T532, SM-T533, SM-T535): https://www.androidfilehost.com/?w=files&flid=319803
millet (SM-T330, SM-T330NU, SM-T331, SM-T335, SM-T337T): https://www.androidfilehost.com/?w=files&flid=319808
rubenslte (SM-T365): https://www.androidfilehost.com/?w=files&flid=319827
Mirror for all models: https://t.me/tab4los
Source code
matisse: https://github.com/matteo0026/android_device_samsung_matisse
millet: https://github.com/matteo0026/android_device_samsung_millet
matisse-millet kernel: https://github.com/matteo0026/android_kernel_samsung_msm8226
matissevewifi: https://github.com/matteo0026/android_device_samsung_matissevewifi
matissevewifi kernel: https://github.com/matteo0026/android_kernel_samsung_matissevewifi
rubenslte: https://github.com/matteo0026/android_device_samsung_rubenslte
rubenslte kernel:https://github.com/matteo0026/android_kernel_samsung_rubenslte
Added milletltetmo (SM-T337T)
milletwifi SM-T330NU
milletwifi SM-T330NU recovery not working on my tablet. I get "could not do normal boot" after installing on fresh install android 5.1.1
I did get millet3g (SM-T331) recovery to install and works. Any help would be appreciated Thank you
TWRP Flash on SM-t330nu
I've had TWRP (various versions) on my SM-t330nu for quite a while and am thrilled that we have newer rom's and TWRP's for our devices. When Matteo0026 started building his newer TWRP's I had a few problems with the "unified" version he released, but he went back to the drawing board and corrected those problems. Several weeks ago I successfully flashed the 3.3.1-0 build through the TWRP that was previously on my tablet and have had no problems. I do have to say, however, that I am not certain I am using the absolutely newest TWRP version since the build name has not changed, but since I am having no problems I am leaving well enough alone!
I get the could not do normal boot error on my SM-T330NU, I've tried flashing through Odin, and installing through TWRP. I can't seem to make this work. I can flash 3.0.3.0 and it works fine, but won't let me user newer roms.
I did flash the 3g TWRP and that will work, but I don't wanna mess around with loading roms that aren't for my model.
Edit: Got it working, had to flash this https://androidfilehost.com/?w=files&flid=49346 Via Odin 3.09, rebooted, flashed it again inside of twrp, rebooted and installed this https://build.twrp.me/twrp-3.3.1-0-milletwifi.img
That twrp-3.3.1-0-milletwifi.img worked without error.
Thank you,
Your welcome
Hi.
There isn't a tar for milletltetmo in the download link.
Please advise.
Thank you.
donj001 said:
Hi.
There isn't a tar for milletltetmo in the download link.
Please advise.
Thank you.
Click to expand...
Click to collapse
It's there
milletltetmo t7337t tar
DJABHipHop said:
It's there
Click to expand...
Click to collapse
It's not, but I just used the T335 tar and then flashed the t337t img file over it for good measure.
donj001 said:
It's not, but I just used the T335 tar and then flashed the t337t img file over it for good measure.
Click to expand...
Click to collapse
Okay you wanted .tar file... I forgot to upload it... This morning I'll do it so
Thanks for the hint @TheDude1179!
(Edit: Got it working, had to flash this https://androidfilehost.com/?w=files&flid=49346 Via Odin 3.09, rebooted, flashed it again inside of twrp, rebooted and installed this https://build.twrp.me/twrp-3.3.1-0-milletwifi.img)
It was the only way to get working the twrp in my sm t330 tab 4 millet wifi. No luck with the provided tar or img to this model. I tryed to flash inside the twrp the new img, but not worked as well.
I installed lineage 16 and gapps, but now the tablet does not turn off. when I plug the usb power it turns on and start booting, no.matter the way to force power off... just when battery runs out. Any idea to fix?
juraci said:
Thanks for the hint @TheDude1179!
(Edit: Got it working, had to flash this https://androidfilehost.com/?w=files&flid=49346 Via Odin 3.09, rebooted, flashed it again inside of twrp, rebooted and installed this https://build.twrp.me/twrp-3.3.1-0-milletwifi.img)
It was the only way to get working the twrp in my sm t330 tab 4 millet wifi. No luck with the provided tar or img to this model. I tryed to flash inside the twrp the new img, but not worked as well.
I installed lineage 16 and gapps, but now the tablet does not turn off. when I plug the usb power it turns on and start booting, no.matter the way to force power off... just when battery runs out. Any idea to fix?
Click to expand...
Click to collapse
Try unplugging the charger and then turn off the tablet.
here's my question about first installing twrp 3 an then 3.3.1. i saw a youtube video on installing twrp 3.0 img file with flash fire an then that way the guy got twrp 3.0 installed then updated to 3.3.1. so i am wondering can that be done or not. We need to first install the twrp tar with odin 3.0.9. i would like to know best approach so that i can get this installed this weekend and then install the lineage rom to the device.i am very excited to se development on these sort of tablets where as the nexus 9 tablet does not have any more development past 14.1.
mrk2815 said:
here's my question about first installing twrp 3 an then 3.3.1. i saw a youtube video on installing twrp 3.0 img file with flash fire an then that way the guy got twrp 3.0 installed then updated to 3.3.1. so i am wondering can that be done or not. We need to first install the twrp tar with odin 3.0.9. i would like to know best approach so that i can get this installed this weekend and then install the lineage rom to the device.i am very excited to se development on these sort of tablets where as the nexus 9 tablet does not have any more development past 14.1.
Click to expand...
Click to collapse
You can go to 3.0 and after to 3.3.1-0 by flashing the img file in recovery. In this way, the old recovery is overwritten.
Ok, I uploaded milletltetmo .tar TWRP. Sorry to be late. Happy flashing!
is this an updated twrp 3.3.1 or the same one that was linked to a few posts back.
mrk2815 said:
is this an updated twrp 3.3.1 or the same one that was linked to a few posts back.
Click to expand...
Click to collapse
Same one.
Hi guys, I uploaded .zip file of the TWRP (it's the same last build of these last months) for who needs to flash it easier with another custom recovery, maybe coming from an old version of TWRP.
matissewifi
i tried to install matissewifi on my Galaxy Tab 4 10.1 Wifi but now it's not booting into recovery. Directly going to download mode when trying to boot to recovery. I had TWRP 3.0.0 installed. First tried from TWRP. Then 2nd time tried with odin with no luck.
Related
Hello! Here im gonna show you an answer for how to flash custom recovery, this is very easy and you only need a pc or some couple of apps and a file.
First things first make sure you're phone is supported, unofficial custom recoveries works fine! Download the tar/img file of the custom recovery and some couple of apps on second method or a program and usb cable on first method.
PC method: Tar file
This one's will work fine and it will have no chance of failing in flash (Depends if something happened on the phone while flashing)(make sure you have samsung usb drivers installed!)
1. Install ODIN3 and Samsung USB Drivers
2. Make sure you have the downloaded tar file of the custom recovery.
3. Turn off the phone and make sure it is in ODIN Mode or Download Mode (A useful feauture for Samsung Devices)
4. Connect the phone to PC via USB Cable
5. Select the AP/PDA button (depends on you're ODIN3 version)
6.Select the tar file
Follow additional instructions from the custom recovery installation instructions or you may fail. (cuztomizing the settings or removing something on the phone)
7.After that click start and wait for some few seconds.
8a. If it leaded you to lock screen, launch recovery to make sure it flashed perfectly and works fine. But if it doesnt work reflash the recovery again/flash it with another version of recovery or another recoveries like CWM/Philz/TWRP (if reflashing dont work). Maybe because the recovery flashed is bugged or corrupted.
8b. If it leaded you automatically to "recovery booting" and then turns into ODIN Mode or Download Mode. Reflash the recovery again/Flash it with another recovery version or another recoveries like CWM/Philz/TWRP. Maybe because the recovery flashed is bugged or corrupted.
Non-PC Method: IMG File
This second method have some chances or RARE chances you may fail and brick or get stuck on a certain point, somehow convenient if you're out of options on flashing.
1. Download and Install Flashify app
2. Select your custom recovery IMG file
3. Wait for it to say that the file is flashed
4. Reboot the device
At this point, this one is the confusing point because you maybe dont know what to do next when you reboot the phone
5a. After rebooting the device, and it leads you to lock screen. Launch recovery to make sure its perfectly flashed and working. If not and when you launch the recovery, it leads you to download mode (recovery only problem), it looks like you need reflash it again/flash another recovery version or another recoveries like CWM/Philz/TWRP(if reflashing dont work) . Maybe because the recovery flashed is bugged or corrupted.
5b. After rebooting the device, it leads you automatically to recovery and not to the lock screen. It shows as "recovery booting" and then turns into ODIN Mode or Download Mode, this is the point you have to reflash it again/flash it with another recovery version or another recoveries like CWM/Philz/TWRP(if reflashing dont work). Maybe because the recovery flashed is bugged or corrupted.
This is some recoveries which include the two recoveries I said in this thread: Credits to @aapav01 @ali.filth for this amazing recoveries!
TWRP 3.0.0 by @aapav01 : http://forum.xda-developers.com/gal...recovery-twrp-2-8-6-0-touch-recovery-t3107535
Philz Recovery by @ali.filth : http://forum.xda-developers.com/galaxy-grand-2/orig-development/sm-g7102-philz-touch-6-47-4-t2798020
Request!: Whenever you visit some threads like this please leave a big thanks to them for there hardwork. Thank you
HAPPY FLASHING AND HAVE A GREAT CHRISTMAS AHEAD OF YOU!
goood job mate
agriculture said:
goood job mate
Click to expand...
Click to collapse
Thank you sir! Merry christmas and happy new year
NYT_RootComm said:
Thank you sir! Merry christmas and happy new year
Click to expand...
Click to collapse
how do i install custom recovery
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.
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
DJABHipHop said:
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
Click to expand...
Click to collapse
I always disable screen timeout in the settings of TWRP so I haven't run into that issue. Im not sure why you would say its buggy as hell. I dont think a screen timeout bug qualifies it for all that. Just disable screen timeout in twrp settings and move on. Certainly not a reason to downgrade, but to each their own I guess.
some one please port it to t330nu ...
MTP
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Reshan Kariyawasam said:
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Click to expand...
Click to collapse
Let me know if the camera and mic work
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
mrdreamers said:
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
Click to expand...
Click to collapse
Thats really odd!
As of right now I've seccessfuly fixed the microphone but its still really quite witch requird more digging all soulutions are welcome at this time freas build comming today for t530&t530nu user new thread started by to posted all device fixes and rom tweaks to The Samsung Galaxy Tab 4 in general.
https://drive.google.com/drive/folders/1F3qVR2Gy-SCqFwg5El7-aeGn6UhX-_-_?usp=sharing
DJABHipHop said:
Thats really odd!
Click to expand...
Click to collapse
ya i just odin firmware and started over no root no recovery, its a x-mas gift to my sister and law anyway she don't need all that, she's not nerdy like us lol!!!!
How it look?
How's the recovery doing? Is it working fully?
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
PizzaG said:
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Click to expand...
Click to collapse
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
srialmaster said:
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
Click to expand...
Click to collapse
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
nico3dd said:
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
Click to expand...
Click to collapse
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
PizzaG said:
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
Click to expand...
Click to collapse
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
nico3dd said:
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
Click to expand...
Click to collapse
At this point I would probably start over from scratch and flash stock with Odin. How did you try installing updated TWRP?
If you want me to update the tar file with newer TWRP so it can be flashed with Odin, send me the tar file of old twrp and the newer twrp img file and i'll get that done for you.
can you please port the twrp to the t330nu?
zuhero said:
can you please port the twrp to the t330nu?
Click to expand...
Click to collapse
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
PizzaG said:
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
Click to expand...
Click to collapse
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Delete
---------- Post added at 06:12 AM ---------- Previous post was at 06:08 AM ----------
zuhero said:
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Click to expand...
Click to collapse
If you know how to get skype working on the tab 4 for matisse & milet device hit me up on tellgrem @DJABHipHop I can sure use the help with fixing all the little but anoying bugs.
Thenk in advance.
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.
HTML:
#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
* y
Let’s start with the installation process
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_disabled.tar then go into download mode on your device. Put vbmeta_disabled.tar to userdata 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). . In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
BOOT TO TWRP RECOVERY AND MAKE FORMAT DATA AND WIPE SYSTEM
Developers specific details
Sources
https://github.com/blacktox/r1q
https://github.com/Grarak/android_bootable_recovery-1
vbmeta_disabled
https://drive.google.com/file/d/1_Ws71h--Z7YBGfllsbt8qlJElXRxTB1p/view?usp=sharing
twrp based on A805FXXU4BTC3 so you must on firmware binary 4
https://drive.google.com/file/d/1FkYQY_O7daPFX6lWt66Bn-aXadRrDWez/view?usp=sharing
XDA:DevDB Information
twrp galaxy a80, Tool/Utility for the Samsung Galaxy A80
Contributors
blackbuga
Version Information
Status: Testing
Created 2019-11-09
Last Updated 2020-07-03
Awesome! Where do I get the vbmeta.tar file?
Nazato said:
Awesome! Where do I get the vbmeta.tar file?
Click to expand...
Click to collapse
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases/download/3.3.1-3/vbmeta.tar
Sent from my SM-A805F using XDA-Developers Legacy app
blackbuga said:
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases/download/3.3.1-3/vbmeta.tar
Sent from my SM-A805F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Just got it to boot and the touchscreen is unresponsive. Quite a bummer since twrp is the only way to root as far as I've concluded :crying:
Nazato said:
Just got it to boot and the touchscreen is unresponsive. Quite a bummer since twrp is the only way to root as far as I've concluded :crying:
Click to expand...
Click to collapse
Rename it to recovery.img then compress to tar file and flash it
Fixed touchscreen
When reboot twrp flash again this img as image in boot to complete rooting
https://www.mediafire.com/file/ccix57wmz61crzd/magisk_patched.img/file
Sent from my SM-A805F using XDA-Developers Legacy app
blackbuga said:
Rename it to recovery.img then compress to tar file and flash it
Fixed touchscreen
When reboot twrp flash again this img as image in boot to complete rooting
https://www.mediafire.com/file/ccix57wmz61crzd/magisk_patched.img/file
Sent from my SM-A805F using XDA-Developers Legacy app
Click to expand...
Click to collapse
I followed your steps to no avail. First try, twrp didn't even boot up completely as it was stuck in the twrp logo screen. My second attempt was wiping data first using the stock recovery, then flashing twrp. Twrp booted up and I was happy as heck, but the touchscreen was unresponsive. I've completely set up my phone again after giving up. I wouldn't mind losing all my data again just to gain root, but I don't want to lose it for nothing
Now it just doesn't load further than the logo! !(
UPLOAD NEW BUILD
FIX TOUCHSCREEN
https://github.com/blacktox/r1q/releases/download/TWRP/recovery.img
blackbuga said:
UPLOAD NEW BUILD
FIX TOUCHSCREEN
https://github.com/blacktox/r1q/releases/download/TWRP/recovery.img
Click to expand...
Click to collapse
Thanks for fixing the issues! Bummer that I can't root. It's just stuck on bootloop with the Samsung splash image.
You must as sg7 firmware
Then flash twrp recovery
Open magisk manager and patch this recovery.img
And reboot to twrp instal image seltect magisk patched and flash it at boot
Wipe all and reboot
Now you have twrp and rooted
For patching recovery with magisk use this custom source
https://github.com/blacktox/work/blob/master/ianmacd.json
For patching with magisk 19.4
Sent from my SM-A805F using Tapatalk
blackbuga said:
You must as sg7 firmware
Then flash twrp recovery
Open magisk manager and patch this recovery.img
And reboot to twrp instal image seltect magisk patched and flash it at boot
Wipe all and reboot
Now you have twrp and rooted
For patching recovery with magisk use this custom source
https://github.com/blacktox/work/blob/master/ianmacd.json
For patching with magisk 19.4
Sent from my SM-A805F using Tapatalk
Click to expand...
Click to collapse
Thanks, man! This finally worked. Any way I can donate to you or something like buy you a beer or what
Is anything working? Decryption? Back-up? Restore?
I have saw the a70 page and it included many custom roms. Is it easy to port it over to the a80? I really want lineage os on my phone. Thanks
(I have an SM-A8050)
@blackbuga ; how about detail explaining about sg7 firmware how can we get it? what about give us step by step way of unlocking until flash twrp within provided link donwload files we needed, & last could u gv us stock recovery img for emergency used while we faced some trouble like bootloop or something else we dont expected. so we dont needed to flash whole firmware stock & make us felt safety & shortcut the time of we got trouble. thx for great works
Hello blackbuga,
I recently installed your unofficial TWRP-build for the A80.
I want to let you know that it is impossible to flash ROMs successfully. I am a TouchWiz developer since 2016 and I wanted to continue with OneUI.
So, I was porting the A71 firmware, but it didn't let me install the zip. It ended with the Error 7.
Here's a part of the log:
" -- Setting ROM Permissions
ApplyParsedPerms: removexattr of /system/system/usr/srec/en-US/wordlist.syms to 0 failed: Operation not supported on transport endpoint
ApplyParsedPerms: removexattr of /system/system/usr/srec/en-US/wordlist.syms to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7 "
It seems like it's a problem of the recovery. I hope to get an answer from you.
Greetings
Soon i realase new build recovery
Im waiting samsung realase new source s4 or u4
blackbuga said:
Soon i realase new build recovery
Im waiting samsung realase new source s4 or u4
Click to expand...
Click to collapse
Will this solve the above mentioned problem, or don't you know what the problem might be?
n0tavailable said:
Will this solve the above mentioned problem, or don't you know what the problem might be?
Click to expand...
Click to collapse
probelme related to your port not from recovery
edit the permission
Is it possible to installieren android 10 GSI i allways in bootloop and restart in recovery
Nazato said:
Thanks, man! This finally worked. Any way I can donate to you or something like buy you a beer or what
Click to expand...
Click to collapse
Bro @Nazato, could you write steps by steps to root A80 please...
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.
#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/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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
The best thing ever happened for realme ui 2. Great work mate..!
Finally, a proper working Recovery for our device
Wow...Finally Working TWRP for RMX1931 on RUI2.
Thanks alot bro.
Can I flash this, when I'm on Lineage-18.1?
zheka99 said:
Can I flash this, when I'm on Lineage-18.1
Click to expand...
Click to collapse
Technically its possible...but you should do it after roms released based on rui2 firmware. If not , you will endup with broken OS. For now dont flash custom roms with this recovery.
can i flash magysk to optine root, wich version?
Isavar said:
can i flash magysk to optine root, wich version?
Click to expand...
Click to collapse
Magisk-92546e8a(23016) from CANARY all Ok!
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Leozgz85 said:
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Click to expand...
Click to collapse
Hi
was the same for me, had to reinstall everything, only started in TWRP. Would like to install the recovery but I don't feel like this error anymore.
Thanks. It's working.
Doesnt work for me, i cant boot to realme ui after flashing the vbmeta, i got stuck on recovery. (f.14)
This recovery is broken for me, it gives me no space left on sdcard even after a full data reformat, ozip extraction stops after 500mb.
It's just not working as it should 3.4 works best
arnodorian-r said:
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.
#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/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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
Click to expand...
Click to collapse
I followed this guide and many others in the past 48 hours, with no success. Every time I flash TWRP and the VBMETA, I get stuck in TWRP bootloop.
I started unblocking the bootloader, rolling back to RUI1 - Android 9 and using the Deep-Test App.
After the roll back, I got the phone unblocked right, but then first soft-brick, with only bootloader available and no way to flash a working ROM. After some searches, I've finally managed to unbrick, using OPPO flash tool, and installing stock rom RMX1931_11_F.14_2021102817443142.
This gives me a working phone, RUI.2 - Android 11. Standard recovery.
I tried to flash TWRP and got the phone soft bricked again, in TWRP recovery bootloop.
I'd like to install TWRP and from there going to OrangeFox and finally install Lineage 19.1...
How can i first have a working TWRP recovery??? If you can support also following steps, would be amazing. Thank you!!!
I went few step further... but still I am not able to install a working custom recovery for my realme X2 pro.
I have now also rooted my device with magisk.
I just need a custom recovery to perform 2 actions:
- make a NANDroid backup;
- install a custom ROM.
Any advice? Thank you for your time!
Installed. Working like a charm with lineage 19.1. Only problem: can't access files in storage. Digging into the matter, it seems to be an issue with android 12's new encryption method, which can't be overriden by this version of the recovery. There's a brand new TWRP 3.7.0_9.0 in the official TWRP website which boasts to overcome this problem but, whenever I try to install it (with or without the vbmeta.img provided for version 3.6.0_11), the recovery won't start. Guess a new vbmeta.img is needed as everything goes ok reinstalling TWRP 3.6.0_11 and its corresponding vbmeta. Tried to extract and install vbmeta.img from the lineage zip file without success. Shall we have to patch vbmeta.img? How can we do that? Through Magisk? I've come across some "vbmeta patcher" apk... Am I pointing the right way?
can any one help me to unlock bootloader in realme x2 pro . i am on RUI 10 . i installed in depth tool it said seccesful but no bootloader just keep rebooting and showing fast boot for a moment .. help please i search every where for fix but no way to yet
I'm using the CN variant device, which I understand does not yet have confirmed support, nonetheless sharing the error I'm encountering in case it's a simple or obvious fix I'm missing.
Having followed all above steps, I'm able to flash and get into TWRP recovery, but decryption always failed (even after a dozen tries) with the following:
"Attempting to decrypt FBE for user 0...
Failed to decrypt user 0"
Much obliged for any insight on this. I'm attempting to get back on OF after successfully installing Lineage 19.1, which broke the OF recovery, and since OF needs to be installed as a ZIP, I need to get some version of TWRP working as an intermediary. Specifically this is because I didn't install GAPPS along with Lineage 19.1 (I misread the opening post, which seemed to imply that GAPPS was included in that particular ROM). So alternatively, if there's another way to get GAPPS onto the device without recovery (sideload won't work since I can't decrypt...) then that would be helpful too.
Thanks in advance for any insight on this!