Database Users

New User - Problem with Update after rooting

I'm sorry for having to post here, I'm a new XDA member and I've just started using my tablet and found out I can't post in the dev section. I'm not sure how else to get help and a previous boyfriend told me the xda-developers community was a great place so I thought I would try here.
I have the Nexus 7 (2013 edition) and I used WUG's method of rooting - everything went perfectly, but now I'm getting a notification that there is an update (an OTA update - I think that's what they are called?) and it doesn't apply. I'm not sure if I should have, but I did the bootloader unlock and installed a new recovery (TWRP - I think that's how it's spelled?. sorry again)...
Anyway.... At this point my tablet is working great, but I constantly see this notification for an update and I'm not sure what to do.. It says "touch to install" and I've done that but it just boots into my new recovery. If anybody has access to WUG in the dev forum, could you please ask him what I should do?
Thanks!!!!!!!!!!!!!!

BarbaraG said:
I'm sorry for having to post here, I'm a new XDA member and I've just started using my tablet and found out I can't post in the dev section. I'm not sure how else to get help and a previous boyfriend told me the xda-developers community was a great place so I thought I would try here.
I have the Nexus 7 (2013 edition) and I used WUG's method of rooting - everything went perfectly, but now I'm getting a notification that there is an update (an OTA update - I think that's what they are called?) and it doesn't apply. I'm not sure if I should have, but I did the bootloader unlock and installed a new recovery (TWRP - I think that's how it's spelled?. sorry again)...
Anyway.... At this point my tablet is working great, but I constantly see this notification for an update and I'm not sure what to do.. It says "touch to install" and I've done that but it just boots into my new recovery. If anybody has access to WUG in the dev forum, could you please ask him what I should do?
Thanks!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Do you have the WiFi only version or the LTE version? Also, under your settings -> about phone, what build number are you currently on? Since you have rooted and installed a custom recovery, OTA updates will not install correctly. You have a couple of options in this regards, and I or someone will go over them once we figure out what version you are running.

railed said:
Do you have the WiFi only version or the LTE version? Also, under your settings -> about phone, what build number are you currently on? Since you have rooted and installed a custom recovery, OTA updates will not install correctly. You have a couple of options in this regards, and I or someone will go over them once we figure out what version you are running.
Click to expand...
Click to collapse
ThankYou so much for the help... It's the WiFi only version. The build number is: JSS15J

http://forum.xda-developers.com/showthread.php?t=2404833

BarbaraG said:
ThankYou so much for the help... It's the WiFi only version. The build number is: JSS15J
Click to expand...
Click to collapse
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.

railed said:
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.
Click to expand...
Click to collapse
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.

BarbaraG said:
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.
Click to expand...
Click to collapse
All your data will be preserved. Only Wipe the Cache/Dalvik Cache, not the Data. Before you install go to Wipe -> Advance -> Check only Cache and Dalvik Cache.
Typically when an update comes out, someone will post a flashable update within a couple of hours so we can install them as well. Hope it helps.
Edit: As always before flashing anything, make a backup, by rebooting into recovery and selecting Backup (i check all the boxes).

BarbaraG said:
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.
Click to expand...
Click to collapse
Also.... If I just load the latest cyanogenmod on it, will that take care of it. I have the same old phone from my previous boyfriend and it's running cyanogenmod.. It will update the OS whenever a new version comes out and I don't lose the data like I did with the unlock bootloader thing?

BarbaraG said:
Also.... If I just load the latest cyanogenmod on it, will that take care of it. I have the same old phone from my previous boyfriend and it's running cyanogenmod.. It will update the OS whenever a new version comes out and I don't lose the data like I did with the unlock bootloader thing?
Click to expand...
Click to collapse
I believe so, Cyanogenmod usually merges the updates pretty quickly into the code and you won't get any update notifications from Google directly any more. There are only nightly releases so far for this device if you feel like going that route.

railed said:
I believe so, Cyanogenmod usually merges the updates pretty quickly into the code and you won't get any update notifications from Google directly any more. There are only nightly releases so far for this device if you feel like going that route.
Click to expand...
Click to collapse
Thank You! Very Much!!!
Do you think I should go the cyanogenmod route?
I've really liked cyanogenmod on the phone on barnes&noble device they are on, but I've been scared to update this tablet since we've broken up and I don't have anybody that can help.

BarbaraG said:
Thank You! Very Much!!!
Do you think I should go the cyanogenmod route?
I've really liked cyanogenmod on the phone on barnes&noble device they are on, but I've been scared to update this tablet since we've broken up and I don't have anybody that can help.
Click to expand...
Click to collapse
That's completely up to you and what you prefer... I like the stock android experience so far, but there are many options out there for custom ROMs besides CM. Take a look here and here and figure out if a ROM in there has something you want... the great thing about this is if you don't like it, flash something else until you find exactly what you like... that's how I plan to do it, once the ROMs get more stable with the 4.3 updates.

railed said:
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.
Click to expand...
Click to collapse
I've been reading through all of the links you sent and some others I've found. Should I go with the odexed or deodexed version?

BarbaraG said:
I've been reading through all of the links you sent and some others I've found. Should I go with the odexed or deodexed version?
Click to expand...
Click to collapse
I use deodexed, as do a lot of people who like to customize. There's not a lot of difference between the two. Here is an article that explains it pretty well: Odexed vs Deodexed

railed said:
I use deodexed, as do a lot of people who like to customize. There's not a lot of difference between the two. Here is an article that explains it pretty well: Odexed vs Deodexed
Click to expand...
Click to collapse
Thank You, I now know the difference between them. I think I'll go with the Deodexed version also.
Thanks again for all of your help!!!!!

Tried two roms, getting the 'com.android.phone' has stopped responding (immediately)

I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.

Taymar said:
I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.
Click to expand...
Click to collapse
Yea, you can't flash cm or pa on your device. They can only be flashed on devices with the mdb or mdl bootloader. If you're using safestrap, and it's the only recovery you can use, you're probably on 4.4.4, nb1 or nc1 or nj4, bootloader. You'll need tw based roms. See the ones that work with safestrap.
Sent from my Nexus 9 using XDA Free mobile app

Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.

Taymar said:
Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.
Click to expand...
Click to collapse
Your stuck to 4.4.4 unless you do the method mentioned on the forums and GoldenEye comments.
But a caution its not for the new, is risky and you lose the safestrap recovery boot because safestrap is not lollipop compatible right now.

Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.

Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
I don't own it so I couldn't tell you but I would look up the forum for it before hand and see what they say about it.
If it's not an ATT and Verizon phone most likely it's not boot loader locked.

Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
Oneplus you will be able to root and recovery, I believe even unlock the bootloader. You just have to pay full price of the phone of course, but it's separate from carrier so no root patching OTAs.

Awesome. Thank you so much guys. I think I'm going to try out the oneplus one. Sounds like it'll be a lot more straightforward than with AT&T's devices.

Rooting the S5

Hi,
I recently rooted my S5 successfully and then got rid of touchwiz and installed Cyanogenmod 13. But then I realized that the root was gone from my phone. So I rooted again and now Cyanogenmod won't boot. (Stuck on Cyanogenmod booting animation.)
I have an S5 g900I (Oceania edition).
I'm guessing the mod went away because I wiped the system through recovery before installing CM but why can't I root again? If anyones had the problem previously which is the best version to go with? I might try CM12.1 now just to be sure. But any ideas?
Thank you

Axle0 said:
Hi,
I recently rooted my S5 successfully and then got rid of touchwiz and installed Cyanogenmod 13. But then I realized that the root was gone from my phone. So I rooted again and now Cyanogenmod won't boot. (Stuck on Cyanogenmod booting animation.)
I have an S5 g900I (Oceania edition).
I'm guessing the mod went away because I wiped the system through recovery before installing CM but why can't I root again? If anyones had the problem previously which is the best version to go with? I might try CM12.1 now just to be sure. But any ideas?
Thank you
Click to expand...
Click to collapse
Flash the latest update supersu.zip and root your phone. I think now you can use supersu2.46.zip on aosp 6.0.1. I've done it and works for me. If not then use the latest systemless root by chainfire. The one that works for me is 2.62. Try 2.46 first. Thanks @Chainfire for all of your hard work and making it easy to root our phones. Good luck

CM13 has root built into the ROM.
Go to settings -- > about device, tap on "Build number" enough times until the Developer options appear, and enable root from within the developer menu.

jlbuck6212 said:
Flash the latest update supersu.zip and root your phone. I think now you can use supersu2.46.zip on aosp 6.0.1. I've done it and works for me. If not then use the latest systemless root by chainfire. The one that works for me is 2.62. Try 2.46 first. Thanks @Chainfire for all of your hard work and making it easy to root our phones. Good luck
Click to expand...
Click to collapse
I didn't try that since after wiping everything again I realized by installing CM13 your phones changes to g900f which is the international version and by installing the root for that version all works good. Thank you for your quick response
tangcla said:
CM13 has root built into the ROM.
Go to settings -- > about device, tap on "Build number" enough times until the Developer options appear, and enable root from within the developer menu.
Click to expand...
Click to collapse
That's actual hell cool but as mentioned above fixed it some other way.
The only other problem I'm having with CM13 which is really annoying is that it seems like its not as optimized for my phone. It overheats and drains the battery way too quickly. Any ideas for that? Thanks

Axle0 said:
The only other problem I'm having with CM13 which is really annoying is that it seems like its not as optimized for my phone. It overheats and drains the battery way too quickly. Any ideas for that? Thanks
Click to expand...
Click to collapse
Yes, it's NFC that's causing the issue. Use a root browser and delete the folder /system/app/NfcNci - try that.

tangcla said:
Yes, it's NFC that's causing the issue. Use a root browser and delete the folder /system/app/NfcNci - try that.
Click to expand...
Click to collapse
Fair enough. I don't use NFC anyways so I'll give that a shot

"New" comer here, I need some help please

Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks

Arturofm2 said:
Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks
Click to expand...
Click to collapse
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?

https://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
follow this (use odin to flash rooted kernel) ......you should search before posting things like this.....google is your friend bro.
GOOD LUCK - BTW use flash fire app in play store to make backups and flash roms

Okay okay.
A quick glance at T-Mobile Samsung Galaxy S7 Edge Guides, News, & Discussion would have led you to the "How to root the S7 EDGE" thread.
I'd take a look in there if I were you.

Binary100100 said:
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?
Click to expand...
Click to collapse
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more

Arturofm2 said:
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more
EDIT: I just checked and the root didn't go through... even though ODIN said it was successful
Click to expand...
Click to collapse
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.

Binary100100 said:
What you wrote above
Click to expand...
Click to collapse
So for what I understood the dev support for this phone is very limited... I know the issues I may encounter, I had them with the galaxy note. but any way... If something I'll unroot it but I want to try it out Thank for you time. I've rooted it.
EDIT: Damn... I really don't like the visual style of Echoe... is that one the only one I can flash??

Binary100100 said:
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.
Click to expand...
Click to collapse
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?

Arturofm2 said:
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?
Click to expand...
Click to collapse
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.

Binary100100 said:
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.
Click to expand...
Click to collapse
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T

Arturofm2 said:
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T
Click to expand...
Click to collapse
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?

Binary100100 said:
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?
Click to expand...
Click to collapse
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?

Arturofm2 said:
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?
Click to expand...
Click to collapse
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammmobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.

forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.

Binary100100 said:
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.
Click to expand...
Click to collapse
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I didn't do it through that page. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?

tduquefjc said:
forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.
Click to expand...
Click to collapse
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?

Arturofm2 said:
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I kept it. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?
Click to expand...
Click to collapse
Arturofm2 said:
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?
Click to expand...
Click to collapse
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.

Binary100100 said:
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.
Click to expand...
Click to collapse
Perfect! All I did was reboot it, and the unlocked padlock went away, thank you very much for all your help! Happy new year!

After root attempt, SM-G900T won't boot to recovery.

Hello, XDA community.
I tried to root my Samsung Galaxy S5 SM-G900T with Chainfire's CF-AutoRoot, but each time I attempt it the phone won't boot into recovery afterwards. I have tried with and without a custom recovery, neither of which are working to fix the problem.
I'm running Android 6.0.1, and I have the latest T-Mobile updates from March 1st, 2017. Could my phone be the wrong version for the AutoRoot? If so, what should/can I do to root my phone while continuing to update my phone with security patches from T-Mobile?
I have tried factory resetting my phone, as well. Is there a certain version I should try with the AutoRoot (Like some version of Android 5.x.x, or 4.x.x of Android and then once rooted re-update to Android 6.0.1?)
I know there are numerous threads that are similar to my problem, but none are from 2017 and none are exactly my problem.
Any tips or suggestions would be great,
Thank you.

I figured it out everybody, thanks!

SolarEpsilon said:
I figured it out everybody, thanks!
Click to expand...
Click to collapse
Lol that was quick! What was i? I'm running QC2, and never had a problem

culiacanazo said:
Lol that was quick! What was i? I'm running QC2, and never had a problem
Click to expand...
Click to collapse
From my research I found that the error was probably from trying to flash the wrong file, and it must have been because I decided to really focus on one single post on how to root the SM-G900T and follow it exactly, and it worked perfectly! It was my first rooting though, and I didn't brick my device so I still see it as a success.
If you or anyone else is interested, this is the post that worked for me. It seems to be more up to date than any of the other ones I saw.
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190