Related
Helloo.. what's up guys...
I'm so sorry. Long time no post.. hehe
Today i'm gonna share custom recovery (again) for Samsung Galaxy V SM-G313HZ aka vivalto3gnvdx. This custom recovery called TWRP 3.0.
Quoted from official website :
Screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What’s new in 3.0.2-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
Link : Since our device officially supported by teamwin, then all updates can be downloaded directly to the official website TWRP on the vivalto section here
Old build :
What’s new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Link :
Odin version
Flashable version
Changelog :
Fix MTP
Thanks to Allah SWT
Credits :
Team win
Cleverior
corphish (for his clue to fix MTP)
And you...
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
PLEASE PUT THIS POST AS SOURCE. THANKS
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
doesntexits said:
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
Click to expand...
Click to collapse
Ok.. thanks for correction.
MTP is detected but can not mount. In adb, device is in recovery status. not in device status. is this same with you ?
screenshot of adb is attached.
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
doesntexits said:
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
Click to expand...
Click to collapse
There is no custom lun in my boardconfig. Maybe i can try to add it later. And the correct lun file location is in /sys/devices/virtual/android_usb/android0/f_mass_storage/lun .
I'm using TWRP source from omni source.
adb shell is working bro. Now your problem is MTP only.
doesntexits said:
adb shell is working bro. Now your problem is MTP only.
Click to expand...
Click to collapse
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
cleverior.ipul said:
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
Click to expand...
Click to collapse
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
doesntexits said:
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
Click to expand...
Click to collapse
Ya, even using custom lun but still not working.
Update with fix MTP
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
which version of firmware do u use ? have u try to install twrp using odin ?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
If you install TWRP from Odin, make sure you've choose .tar file as PDA, if not the recovery won't be installed
There's no way to install it through stock recovery, since it always gives "E: Signature verification failed".......
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Kazryu said:
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Click to expand...
Click to collapse
When install custom recovery using Odin, don't tick auto reboot. After install successfully, pull your battery out, seriously!
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
doesntexits said:
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
Click to expand...
Click to collapse
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
cleverior.ipul said:
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
Click to expand...
Click to collapse
It adds f2fs support for TWRP recovery, so we can flash other ROMs with f2fs partition support
I cannot use `adb shell`, can you use it?
---------- Post added at 14:33 ---------- Previous post was at 13:57 ----------
In TWRP 2, I remove all adbd control scripts in init.rc, just leave adbd service def, then in init.recovery.scx15.rc:
Code:
on init
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct D002
write /sys/class/android_usb/android0/functions [B]mtp,mass_storage,adb[/B]
# adb won't work in OSX without this
write /sys/class/android_usb/android0/bDeviceClass EF
write /sys/class/android_usb/android0/bDeviceSubClass 02
write /sys/class/android_usb/android0/bDeviceProtocol 01
[B] export PATH /sbin:/system/bin
export LD_LIBRARY_PATH .:/sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /external_sd
write /sys/class/android_usb/android0/enable 1
start adbd[/B]
So now I can use adb shell and MTP in TWRP 2.
Dude, on the TWRP Official Site I see it is in version 3.0.2-0, so it is safe to install that version and you will update this thread to the new version ?
Team Win Recovery Project 3.1.1
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#include <std_disclaimer.h>
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, European Union for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
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.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
Download:
Galaxy S8 (dreamlte - Exynos vaiants - G950F/FD/N/X)
https://twrp.me/devices/samsunggalaxys8.html
Galaxy S8+ (dream2lte - Exynos variants - G955F/FD/X/N)
https://twrp.me/devices/samsunggalaxys8plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - General Discussion
Join to get quick support (when you find my guide confusing or meet any unexpected problem).
You can also discuss about ROMs(this group is "neutral" so you can discuss about or review any ROM. Note: Devs: Do NOT aggressively advertise your work.), get latest updates from developers or report possible bugs.
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
XDA:DevDB Information
TWRP for Galaxy S8 and S8+, Tool/Utility for the Samsung Galaxy S8
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2017-04-24
Last Updated 2018-07-22
Changelog:
Aug. 02:
Merged AQG kernel updates from Samsung.
NOTE: AQG or later bootloader is supported and REQUIRED from this version.
May. 30:
Possible fix for I/O problems.
Backported latest F2FS from Linux 4.12.
Minor kernel updates.
Apr. 27:
Problems Solved:
1. MTP
2. ADB
3. External SD Mount
Features Added:
F2FS - Note: This change ONLY makes it possible to operate F2FS in TWRP. You still need a F2FS-compatible KERNEL to boot into system with F2FS.
Note: As MTP and ADB are available now, flashable zips will no longer be included. Please download them by yourself and transfer them from your computer to phone if you need them.
Useful Links:
Disable dm-verity and make encryption optional: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk: https://forum.xda-developers.com/apps/magisk
Apr. 24:
Initial Release
Guides:
Notice: It may wipe all your data including those in internal storage.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Awesome
Great work thank you very much
Sent from my SM-G955F using Tapatalk
if i wipe data partition in order to disable encryption - is that like erasing my phone and starting from scratch? will i lose all my data?
nk33 said:
if i wipe data partition in order to disable encryption - is that like erasing my phone and starting from scratch? will i lose all my data?
Click to expand...
Click to collapse
Yes you will, make sure you've backed-up as much as you can to your Google Cloud Storage. I promise, it's worth it.
Many Thanks
Kevin_R said:
Yes you will, make sure you've backed-up as much as you can to your Google Cloud Storage. I promise, it's worth it.
Click to expand...
Click to collapse
Thanks.
And if i just install TWRP, and then the root zip file to give me root will it all work ok? will i achieve root ok?
I spent ages getting this phone just like i want it and seriously cant be bothered to do it all again - will i be ok keeping encryption on if all i want to achieve is root?
what will i lose out on if i dont disable encryption?
nk33 said:
Thanks.
And if i just install TWRP, and then the root zip file to give me root will it all work ok? will i achieve root ok?
I spent ages getting this phone just like i want it and seriously cant be bothered to do it all again - will i be ok keeping encryption on if all i want to achieve is root?
what will i lose out on if i dont disable encryption?
Click to expand...
Click to collapse
I found that if I didn't disable the encryption, root wouldn't work as it couldn't mount the file system to make the relevant changes
---------- Post added at 02:19 PM ---------- Previous post was at 02:14 PM ----------
Anyone managed to get Samsung Pass and Secure Folder working? I have Magisk Hide running and Knox Trip is emulated to 0x0. Other apps that would normally detect root don't detect it but Samsung Pass and Secure Folder still can.
Is superSU SR3 working??
its a great work
anyone tried if Samsung Pay still works after this? I have not got my phone yet.
Just for info tried installing the SuperSU binary through TWRP but, as TWRP seems to have no access to the SD card, the flash failed and left me in a boot loop.
Reinstalling TWRP from Odin and reflashing Magisk solved the Boot loop issue.
SuperSU did kill the Knox processes for me though to stop the annoying nagging notifications.
If after flashing from Odin, phone says that needs restore, Just press volume up Bixby Power, wait, then format data, Power off. Now ho back in download mode, reflash with odin, done.
It works all', except personal area and Samsung health
would this work on the SM-G950FD?
if i use this method i lose warranty ? is it possible to do evrything later on normal without having any trouble ?
Phone brick...LOL...
help : just tried to root my g950f Uk 02 - i've flashed it a few times and used the two flash but im getting verification failed and it wont erase anymore when i try use the recovery flash i get invaled mount /data when using that decrypt .zip in flashables do i need to redo the stock firmware and start again?
i am still waiting for my S8(exynos) to arrive and here comes the twrp i did not even wished yet....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1.1
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Siddhant NAik said:
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTEN SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1-0
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
Did you build it from source?
Siddhant NAik said:
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1.1
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
thanks sir, work in my j5 prime
Sent from my SM-G570Y using Tapatalk
---------- Post added at 11:11 AM ---------- Previous post was at 10:50 AM ----------
i already install,
but, i cant install from internal..
& i try to backup my rom, but failed..
please sir, fix this...
thanks before
Sent from my SM-G570Y using Tapatalk
fahri01 said:
thanks sir, work in my j5 prime
Sent from my SM-G570Y using Tapatalk
---------- Post added at 11:11 AM ---------- Previous post was at 10:50 AM ----------
i already install,
but, i cant install from internal..
& i try to backup my rom, but failed..
please sir, fix this...
thanks before
Sent from my SM-G570Y using Tapatalk
Click to expand...
Click to collapse
Flash the modded kernel
Any grace ux rom
Gautham Asir said:
Any grace ux rom
Click to expand...
Click to collapse
not yet, does my injustice rom flash with new TWRP??
I will try to flash
Unable to flash since it failed
Who knows if Recovery worked?
Screenshot
Twrp is working fine except data and mtp
It does not receive the machine memory and resets it when it is not set
Is normal that the custon kernel take too much time to install? odin freezes in:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
Please revise any flash files to reboot
Dont flash kernel
use advance wipe
select data partion
click on repair
th format it using ext 2 or other
boom data will be mounted
thanks :3
Very good work. No problems on SM-G570M
Nothing else MTP and data
Thanks for making it possible I've been waiting for TWRP for some time.
TheFlash said:
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1.1
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
hi
how to flash modded kernel by odin or twrp ?
Cannot flash modded kernel
Wait for some GraceUX ROM
andro_harsh said:
cannot flash modded kernel
Click to expand...
Click to collapse
extract it and flash the img from twrp and format data
boom internel will be mounted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Moto G5S Plus. It can boot any Android ROM, besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action in general.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. But it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_sanders_YYYYMMDD-xx.img) - download the IMG file from second post and use fastboot or Normal TWRP recovery if you have or any other third party image installers from Google Playstore.
MultiROM (multirom-YYYYMMDD-v33e-UNOFFICIAL-sanders.zip) - download the ZIP file from second post and flash it in recovery.
2. Via MultiROM Manager app
We do not have Official Support, an unofficial APP can be downloaded from second post)
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/MR-op3/multirom (branch mr-7.1)
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery (branch mr-7.1)
Device Tree - https://github.com/MR-op3/device_motorola_sanders (branch mr)
Credits
nkk71 (For no-kexec workaround)
XDA:DevDB Information
[MOD][OCT 16][Sanders] MultiROM v33 || no-kexec workaround, Tool/Utility for the Moto G5S Plus
Contributors
premaca, syed sajid, GeneticEnginer
Version Information
Status: Beta
Current Beta Version: v33
Beta Release Date: 2017-10-16
Created 2017-10-17
Last Updated 2017-10-31
Changelog and Downloads
If you have come across with WRONG-PIN on Primary after the installation of secondary, flash the following Lock Fix.
Lockfix.zip
20171114
multirom-20171114-v33e- UNOFFICIAL-sanders
TWRP-multirom_sanders_20171114-01.img
20171016
multirom-20171016-v33e-UNOFFICIAL-sanders.zip
TWRP_multirom_sanders_20171016-02.img
- Initial Release
Flash this ZIP file multirom_uninstaller.zipto remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Multirom manager APP: Will be uploaded Soon.
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will Motorola Stock works as Primary or Secondary ROM?
Yes, Motorola Stock version works with Multirom as Primary ROM, It is not advised to install stock as Secondary, use only as Primary ROM. You can then install other Android ROMs as secondaries.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
Enabling no-kexec workaround
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
[url]http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4[/URL]
Reserved
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
nkk71 said:
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
Click to expand...
Click to collapse
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
premaca said:
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
Click to expand...
Click to collapse
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
nkk71 said:
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
Click to expand...
Click to collapse
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
---------- Post added at 12:33 PM ---------- Previous post was at 12:32 PM ----------
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
winpooh said:
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
Click to expand...
Click to collapse
Yes ,it can work after reset only, you have to do a backup first.
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
abhinav2hd said:
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
Click to expand...
Click to collapse
Be careful and do read the instructions also.
syed sajid said:
Be careful and do read the instructions also.
Click to expand...
Click to collapse
I've used multirom before.. i know how it works ?
abhinav2hd said:
I've used multirom before.. i know how it works ?
Click to expand...
Click to collapse
That's good, I'm not talking about how to use multirom?
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
[URL="https://androidfilehost.com/?fid=889964283620765983]https://androidfilehost.com/?fid=889964283620765983[/URL]
Do I have to wipe data again after updating?
gaurav.saroya said:
Do I have to wipe data again after updating?
Click to expand...
Click to collapse
Nope, just flash it as normal..
syed sajid said:
Nope, just flash it as normal..
Click to expand...
Click to collapse
Okay thanks
syed sajid said:
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
https://androidfilehost.com/?fid=889964283620765983
Click to expand...
Click to collapse
Second link not working
gaurav.saroya said:
Second link not working
Click to expand...
Click to collapse
Working ...afh too slow wait till open..
syed sajid said:
Working ...afh too slow wait till open..
Click to expand...
Click to collapse
It's working now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Extra Fixes :-
Switched To 60 fps from 30 fps
Variant Script Fixed
Boot Control Revision from 1.1 to 1.2
Added Fix for Transferring File Above 4GB
Added Recovery Recovery Variant Of Fastboot Client
Working :-
Decryption
Fixed TWRP Boot up time
Backup(except data partition)/restore
ADB/MTP
Flashing Rom
stock rom flashing
fastbootd and adb sideload
Etc. Cuz I don't remember What else I fixed and What was working
BUGS :-
Other Bugs You tell me that !!!
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Oneplus 8T/9R
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
@TheIncognito
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Trees:
Device: https://github.com/ApexLegend007/twrp_device_oneplus_lemonades
Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_s_12.1
Download:
https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Flashing Rom :-
Make Sure That you have OOS 12 firmware On both slots before flashing rom based on OOS 12 firmware
Copy Rom.zip in your internal Storage Take Backup if you want to take backup Data Backup instruction are given below
After Flashing rom format data and reboot
(!!!!! Warning After flashing custom rom zip The recovery will get changed to AOSP recovery in the inactive slot in which rom got flashed if you want to flash twrp in that same recovery you can do it in bootloader mode!!!!!)
TWRP for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T/9R are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
VBMETA
VBMETA_SYSTEM
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
Reserved For me
Reserved For me
@Siddhant221 Nice to see you here! Good work, and keep it up!
Twrp Lemonades skirrrrrrrrrrah nice job ...
Oho
Hi, could this recovery be tested on a oneplus 9 (LE2115)? fastboot boot or flash.
thx
javi2246 said:
Hi, could this recovery be tested on a oneplus 9 (LE2115)? fastboot boot or flash.
thx
Click to expand...
Click to collapse
It won't work as oneplus 9 is a gki device which requires other work over on recovery trees you can check on twrp.me for further to check if you device is available or not for twrp
Siddhant221 said:
It won't work as oneplus 9 is a gki device which requires other work over on recovery trees you can check on twrp.me for further to check if you device is available or not for twrp
Click to expand...
Click to collapse
thanks for the reply. I'm following the project in zulip to see if there is any news for op9
Hi, i have installed the latest 1.5 twrp on my 8T phone.
used the flash recovery, recovery is booting! but screen in not responding to any touch.
I can use only the power key and then recovery show lock, and ask to swipe to unlock, but screen is not responding.
I have OOS ROM 12 official.
with rooted kernel.
Unlocked.
Please fix, thank you for recovery!
Thanks! It works fine.
If I have OOS12 I can update it by TWRP? Incremental updates are allowed?
If I flash ROM (update, full rom) I must do it at slot A and after that change slot to B and do it again?
Any possibility to support 9 pro?
Any updates for A11?
As TWRP can sometimes take a long time to load, I modified the ramdisk to show a very dark, black splash screen to avoid the risk of burn-in.
Hey, where do I get the image file? Nothing shows up under the link for the release.
I see by the link provided in this topic's header a new version of TWRP based on OOS13 is available for download:
TWRP_V3.7.0_V1
Download:https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases* Did someone test this version of TWRP already?
Siddhant221 said:
View attachment 5671251View attachment 5671257View attachment 5671259
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.
Extra Fixes :-
Switched To 60 fps from 30 fps
Variant Script Fixed
Boot Control Revision from 1.1 to 1.2
Added Fix for Transferring File Above 4GB
Added Recovery Recovery Variant Of Fastboot Client
Working :-
Decryption
Fixed TWRP Boot up time
Backup(except data partition)/restore
ADB/MTP
Flashing Rom
stock rom flashing
fastbootd and adb sideload
Etc. Cuz I don't remember What else I fixed and What was working
BUGS :-
Other Bugs You tell me that !!!
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Oneplus 8T/9R
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
@TheIncognito
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Trees:
Device: https://github.com/ApexLegend007/twrp_device_oneplus_lemonades
Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_s_12.1
Download:
https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Flashing Rom :-
Make Sure That you have OOS 12 firmware On both slots before flashing rom based on OOS 12 firmware
Copy Rom.zip in your internal Storage Take Backup if you want to take backup Data Backup instruction are given below
After Flashing rom format data and reboot
(!!!!! Warning After flashing custom rom zip The recovery will get changed to AOSP recovery in the inactive slot in which rom got flashed if you want to flash twrp in that same recovery you can do it in bootloader mode!!!!!)
TWRP for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T/9R are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
VBMETA
VBMETA_SYSTEM
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
Click to expand...
Click to collapse
Hello Siddhant221
* Does this verison (TWRP_V3.7.0_V1) works with Lineageos 20?
Gogi_M said:
Hello Siddhant221
* Does this verison (TWRP_V3.7.0_V1) works with Lineageos 20?
Click to expand...
Click to collapse
Yep try it