Root [Recovery] Team Win Recovery - TWRP - 2.7.0.0

[dontdriveangry]

If you used shabbypenguin's method to root, then you installed Odin on your computer and TWRP on your phone. TWRP should still be there on your phone.

To boot to TWRP, power off your phone, then power on your phone by holding Volume Up, Home, and the Power button together.

 

[stinger2k]

And there it is !! I just didn't see it in my apps so didn't realize it was on my phone. Thanks for the help!!

 

[Planterz]

And there it is !! I just didn't see it in my apps so didn't realize it was on my phone. Thanks for the help!!

It's not an app, it's a (custom) recovery.

 

[Philip Seng]

Team Win Recovery Project 2.x, or twrp2 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:


Tablet look:


CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes

Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.

CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks

CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks

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.
This is for TWRP support only, any questions concerns issues with TWRP on this device ask in this thread please.

While Using This Recovery I Suggest People That Are Bricked To Use This Backup To Restore To Original This Is Only For Metro PCS Version To Restore http://androidforums.com/threads/fr...vice-sgh-t399n-only-for-metro-version.891858/

 

[samsung_guy]

thank-you shabbypenguin.. i am now rooted with my metro pcs galaxy light. i have also unlocked my phone prior rooting. i have also made a back up and a copy to sd card. and as a safety measure, i will be putting a copy on my pc.

 

[GalaxyGurl13]

So good news in advance, here are the instructions on how to root 4.4 when it comes out:

Download the latest version of supersu from SuperSU Download
copy it to your device
flash supersu in twrp
reboot and load up supersu
have it disable knox
reboot to twrp and reflash supersu
that should be all.

Happy Easter all. I'm currently using a Samsung Galaxy Light SGH-T399 cell phone on version T399UVUANI2. My question is how do I root it?

I previously rooted this device, but I was on an earlier version. When T-Mobile pushed an update, my phone died and I had to send it in for a new phone. Now that I have a new phone, it's updated and I'm not quite sure how to safely root it and keep it as close to stock as possible. Can anyone help?

Thanks for any replies.

 

[Luis Villalobos]

I have a problem with TWRP. I installed 3 ROM's in "Rom Toolbox", When i did it rested and went into TWRP, a blue bar loaded to about 80% & has been there for an equivalence or about 24 hours. On the to of the screen to the bottom it reads
"Team Win Recovery project v2.7.0.0
SIMULATING ACTIONS
4:56 am Battery:88%
Running OpenRecoveryScript
Updating partion details...
E:Unable to mount '/preload'
Kernel does not have support for reading SELinu
x contents
E:Storage partion '//TWRP/BACKUPS/4790283f101
9918d' not found
Simulating actions..."
If i shut it off it,when it comes back on goes straight there, like a BootLoop. Only thing i can gt on other than that is "Download Mode"
I dont know what to do, is my phone totaled?

 

[Luis Villalobos]

Happy Easter all. I'm currently using a Samsung Galaxy Light SGH-T399 cell phone on version T399UVUANI2. My question is how do I root it?

I previously rooted this device, but I was on an earlier version. When T-Mobile pushed an update, my phone died and I had to send it in for a new phone. Now that I have a new phone, it's updated and I'm not quite sure how to safely root it and keep it as close to stock as possible. Can anyone help?

Thanks for any replies.

Get TWRP and make a stock backup. then root it with the restart button in the program, it should promt you with a "Would you like to root" message.

 

[n8kh]

I have a T399N with Android 4.4.2.

Other instructions in this thread indicate that flashing TWRP-2.7.0.0-gardaltetmo.tar with Odin is only for Android 4.2 kernels. Is there another image that will work for T399N phones with Android 4.4.2?

I have MetroPCS and not T-Mobile. It seems that TWRP-2.7.0.0-gardaltetmo.tar is for T-mobile. Or do I misunderstand?

Are these images using Samsung's craptastic RFS filesystem? What is the latest Linux kernel for which people have been able to get the RFS filesystem working? (I'm thinking about generating my own image to flash ...) If these images aren't using RFS, what exactly are they?

If I flash TWRP-2.7.0.0-gardaltetmo.tar with Odin, will it change my phone's IMEI number? If so, can I binary edit the recovery.img file and put my phone's IMEI number in place of whatever IMEI is in this image? What IMEI number is in the TWRP-2.7.0.0-gardaltetmo.tar recovery.img file?

Does Heimdall work just as well as Odin? (I'm a Windoze noob, but I've been using Linux since 1991 and Unix before that. I'm a Linux embedded software developer.)

Thanks ...

 

[KA24DERACER]

First off, you should be using TWRP 2.8.4 (or whichever the newest one is). Yes it will work for 4.4.2. Yes it will work for Metro-PCS. No you should NOT have to change your phones IMEI number or anything like that (this flash doesnt mess any of that up, its carrier-neutral).

I dont know about Heimdall vs Odin, but I dont think anything BUT Odin will work for this particular root and flash. I also dont know about the RFS system, but it likely does (the ONLY non-Samsung ROM for our phone out right now is CM12 and you still have to get TWRP on the phone first to flash it).

 

[n8kh]

First off, you should be using TWRP 2.8.4 (or whichever the newest one is).

The instructions for TWRP 2.8.1.0 said it will not root the phone. To use that version, you had to first root with 2.7.0.0-gardaltetmo, and then upgrade to 2.8.1.0.

Is it the same with 2.8.4? Or will 2.8.4 root the phone?

Yes it will work for 4.4.2. Yes it will work for Metro-PCS.

Excellent!

No you should NOT have to change your phones IMEI number or anything like that (this flash doesnt mess any of that up, its carrier-neutral).

It wasn't that I wanted to change my IMEI number. I was confused by some other posts, thinking that it might do so, and then my IMEI number would have to be repaired. So I'm glad to hear that it won't change my IMEI number.

Thanks for your responses.

 

[KA24DERACER]

When they say "it will not root the phone", they mean installing TWRP or the CM12 ROM does not automatically install SuperSU, so you have to flash SuperSU with TWRP before you get root access. And you should do this before rebooting otherwise you have to manually reboot into recovery mode because without root access you cant use a "rebooter".

And those posts you were getting confused by are (I believe) the ones about CM12, not TWRP, which in the original versions didnt have data or cell (then they got data, and finally cell). Either way the TWRP recovery doesnt mess with ANY of that stuff and the CM12 ROM is also carrier-neutral (although it will say T-Mobile on the lockscreen regardless if you have Metro or T-Mobile).

No problem and good luck.

BTW here is the post which has the step-by-step to root http://androidforums.com/threads/galaxy-light-root-metropcs-4-4-kitkat.897509/

 

[Mark4325]

I have rooted the phone but not installed a custom ROM. My phone is carrier locked to T-Mobile. Have searched exhaustively for a carrier unlock with no success. Does this TWRP-2.7.0.0-gardaltetmo.tar custom ROM unlock the carrier? If not, can someone point me to an unlock?

Greatly appreciated.

 

[n8kh]

I have MetroPCS. (Same as T-Mobile, except branding, I think.) They gave me an unlock code after 3-4 months of service with my new phone. The number to call to get the unlock code is: 800-373-2876. But that is for Banas only. (Banas is the company running the stores where I got my phone.) If you have a different company, then that might not be the right number for you.

They will give you two codes: a "Service Provider" code and a "Network Code" code. You need to first buy a new SIM card from another provider, insert it, and then type in the numbers they give you on the phone. Those numbers are different for every different company, so you need to call your own company. It is the company running the store where you got your phone.

Now, was your phone locked to T-Mobile before you rooted it? Or did it become locked to T-Mobile after you rooted it?

 

[n8kh]

They will give you two codes: a "Service Provider" code and a "Network Code" code. You need to first buy a new SIM card from another provider, insert it, and then type in the numbers they give you on the phone.

In other words, you can't unlock your phone until you first buy a SIM card from another provider. So my phone is not yet unlocked. (I haven't gotten around to rooting it either.)

Your answer to my question:

Now, was your phone locked to T-Mobile before you rooted it? Or did it become locked to T-Mobile after you rooted it?

will help me decide if I want to try rooting it with Shabby Penguin's tools. I don't want my phone to become broken by locking it to T-Mobile, because I actually have MetroPCS, and not T-Mobile (even though it is on the T-Mobile network. I don't want to have to buy another MetroPCS SIM card just to get my phone working again. I already have a SIM card that works for MetroPCS.

Somebody please educate me if I don't understand things properly. Thanks.

 

[Mark4325]

I have MetroPCS. (Same as T-Mobile, except branding, I think.) They gave me an unlock code after 3-4 months of service with my new phone. The number to call to get the unlock code is: 800-373-2876. But that is for Banas only. (Banas is the company running the stores where I got my phone.) If you have a different company, then that might not be the right number for you.

I bought the phone outright no contract and activated with straight talk only, therefore I do not think T-Mobile can help me out since I did not have an account with them and I do not think straight talk does that. Was going to try on Monday but figured if someone had the software that would be the easiest. Otherwise for the price of unlocking online I can by another phone already unlocked on E-bay.

Now, was your phone locked to T-Mobile before you rooted it? Or did it become locked to T-Mobile after you rooted it?

Was locked to T-Mobile before rooting.

 

[n8kh]

I bought the phone outright no contract and activated with straight talk only, therefore I do not think T-Mobile can help me out since I did not have an account with them and I do not think straight talk does that.

All phone companies are required (I think) by law (I think) to give you an unlock code after some period of time -- perhaps 3-4 months.

Was going to try on Monday but figured if someone had the software that would be the easiest.

No software is required. You just need to find out the "Service Provider" code and a "Network Code" for Straight Talk.

And of course, to switch networks (providers), you will need to buy a new SIM card for the new network (provider).

Otherwise for the price of unlocking online I can by another phone already unlocked on E-bay.

You shouldn't have to pay anything.

Was locked to T-Mobile before rooting.

Thanks.

 

[n8kh]

There is a new software update for the Samsung SGH-T399 Galaxy Light phone from T-Mobile. There are some details here: https://Support.T-Mobile.com/docs/DOC-7793

According to T-Mobile, you can't apply the update if your phone is already rooted. The update is supposed to give you free inflight texting.

Does anybody know what else the update might do? For example, will the update fix any bugs that prevent rooting the phone by Shabby Penguin's method??

Free inflight texting doesn't seem all that important to me if I lose the ability to root the phone.

Are there any other exploitable bugs that this update might fix?

If anybody has applied the update first, and then tried Shabby Penguin's update method, please post your results.

 

[n8kh]

This site: http://NasirTech.blogspot.com/2014/06/t399uvuane4-android-422-jelly-bean.html suggests that if you update to (previous update) version T399UVUANE4, you will lose root, but you will still be able to root your phone again.

 

[KageBeast]

There is a new software update for the Samsung SGH-T399 Galaxy Light phone from T-Mobile. There are some details here: https://Support.T-Mobile.com/docs/DOC-7793

According to T-Mobile, you can't apply the update if your phone is already rooted. The update is supposed to give you free inflight texting.

Does anybody know what else the update might do? For example, will the update fix any bugs that prevent rooting the phone by Shabby Penguin's method??

Free inflight texting doesn't seem all that important to me if I lose the ability to root the phone.

Are there any other exploitable bugs that this update might fix?

If anybody has applied the update first, and then tried Shabby Penguin's update method, please post your results.

Well it's pretty common knowledge you can't receive an ota update if you're rooted. I don't know where you're getting this inflight texting from though. I see that does apply the stagefright fix though. I'm assuming there's nothing else to the update.

Also an update won't break root unless it's an update to an new version of android.

 

[n8kh]

I see that does apply the stagefright fix though.

Does Shabby Penguin's root method use stagefright?

If I allow the update to occur, fixing stagefright, will I deny myself the ability to root the phone?

 

[n8kh]

Does Shabby Penguin's root method use stagefright?

Shabby Penguin says no, his exploit does not use stagefright.

 

[KageBeast]

Shabby Penguin says no, his exploit does not use stagefright.

Do you know what stagefright is?

 

[n8kh]

Do you know what stagefright is?

No.

 

[KageBeast]

No.

It's an exploit that could allow a hacker to gain access of your phone just by a person opening a video message. So yeah it doesn't affect root ability in any way.