[RECOVERY] [SM-G7105 LTE] [ms01lte] [Test build] TWRP 3.0.0 Touch recovery - Galaxy Grand 2 Original Android Development

Team Win Recovery Project 3.0.0.x ONLY For MS01LTE SM-G7105​
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.
Phone look:
TWRP 3.0.0-0 is out now for all currently supported devices.
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
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
DOWNLOAD:
ON post #2
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

---

Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here

---

Nice job perfectly working in 7102.

---

Bro how can I flash this recovery???????
Thanks a lot for helping ms01lte???

---

Sanjay8787 said:
Nice job perfectly working in 7102.
Click to expand...
Click to collapse
This is only for Lte

---

Yuen.Jason22 said:
Bro how can I flash this recovery?������������
Thanks a lot for helping ms01lte������
Click to expand...
Click to collapse
No u need to use flashify to flash this

---

What will happen if there is a failure in flashing?? I can't brick my phone in this period before I get a new one

---

Yuen.Jason22 said:
What will happen if there is a failure in flashing?�� I can't brick my phone in this period before I get a new one
Click to expand...
Click to collapse
If this wont work then u can flash another recovery from odin it will repair

---

how to install

---

adityaupreti said:
Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here
Click to expand...
Click to collapse
İ'm on motion rom v17.my 7105 allways open download mod when i flash with flashify.
SM-G800H cihazımdan Tapatalk kullanılarak gönderildi

---

hey friends
diid it work for samsung galaxy grand 2 duos g7102?
plz reply fast:crying:

---

Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I root the device using "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Then after rooting (I understand that I can't install the recovery without root first), and without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP 3.0.0 recovery.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !

---

mouadk said:
Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I flashed root rom "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP recover.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !
Click to expand...
Click to collapse
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine

---

SoUnd001 said:
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine
Click to expand...
Click to collapse
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?

---

mouadk said:
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?
Click to expand...
Click to collapse
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu

---

SoUnd001 said:
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu
Click to expand...
Click to collapse
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?

---

mouadk said:
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?
Click to expand...
Click to collapse
You need to flash kitkat firmware with odin

---

SoUnd001 said:
You need to flash kitkat firmware with odin
Click to expand...
Click to collapse
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?

---

mouadk said:
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?
Click to expand...
Click to collapse
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates

---

SoUnd001 said:
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates
Click to expand...
Click to collapse
Thank you. Unfortunately there are no updates, says "your device has the latest updated" !
It seems my cell provider decided they don't want to upgrade it.