Related
Again, sorry if this is in the wrong place but i dont know who else to ask but you guys.
I originally got my galaxy s4 (AT&T) when it first came out and couldnt wait to root and flash. A couple months later i had to do a warranty exchange just to figure out that it came preinstalled with MF3 (damn mf3) i ended up rooting and like most of you guy who arent/wouldnt be able to flash probably are bored. I then had to do another warranty exchange and when i powered the phone on i went to the more tab in settings and the "about device" was blue not yellow. I knew the phone was on an older firmware and i did confirm it to be on MDL (Sigh of relief) right away i started to root and downloading roms. i havent flashed any yet. My question is, on my stock rom (i am rooted) i keep getting a message. the the red and blue arrows for a new software (its that damn mf3) I DONT WANT IT!!! lol is there any way to stop it from asking me. i keep postponing it but i rerad somewhere u can only do that so much, im all nervous that im gonna wake up one morning and see MF3 took over my phone again lol.
sorry for the essay, if anyone has any info on how to stop it from asking that would be very much appreciated!!!
Thanks,
Dave
This should got in the QA forum. You can download a custom rom to get rid of the message or a freeze a few apps. If I were you, I'd get a custom rom, otherwise why would you care about not having MF3.
ddix585 said:
Again, sorry if this is in the wrong place but i dont know who else to ask but you guys.
sorry for the essay, if anyone has any info on how to stop it from asking that would be very much appreciated!!!
Thanks,
Dave
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2268946
Good luck
And for future, please post in Q & A section.
Or do this.
http://forum.xda-developers.com/showpost.php?p=41424569&postcount=4
And i would freeze those apps right away like the 2 links that were post it on top if not MF3 will automatically update you phone so you need to hurry and do this Good Luck!
Custom ROM and MF3
visuelz said:
This should got in the QA forum. You can download a custom rom to get rid of the message or a freeze a few apps. If I were you, I'd get a custom rom, otherwise why would you care about not having MF3.
Click to expand...
Click to collapse
So if i do flash a custom rom i dont need to worry about it asking or updating on its own. i just flashed vision x ROM TW with Ktoones Kernel and i am loving the rom so far. But if i just keep a custom rom i dont have to worry about the update doing it by itself or freezing it?
Thanks to all the answers,
David
ddix585 said:
So if i do flash a custom rom i dont need to worry about it asking or updating on its own. i just flashed vision x ROM TW with Ktoones Kernel and i am loving the rom so far. But if i just keep a custom rom i dont have to worry about the update doing it by itself or freezing it?
Thanks to all the answers,
David
Click to expand...
Click to collapse
That is correct, good sir. If you froze the update apps/apks you will not be prompt for an update.
However, if you do end up odin'ing your phone for some reason, be sure to quickly block the update by rooting your phone and freeze once again. Odin removes root
Enjoy your custom rom as you are one of the lucky ones still on the old MDL update :good:
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
EDIT:
Here's the deal; my main problem was with Wifi not working. The Stock MF9 Kernel was not working, but the 4.2.2 TW Kernel found here finally did.
did you try this?
leaderbuilder said:
did you try this?
Click to expand...
Click to collapse
Yes. Nothing changed when I did that. I suppose that I should call out that I am currently on MF9.
dante042 said:
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
Click to expand...
Click to collapse
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
I have read that the WiFi issue may be a Kernel issue.. Did you try a different TouchWiz kernel and see if it worked out?
Sent from my SPH-L720 using XDA Premium 4 mobile app
lmayes69 said:
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
Click to expand...
Click to collapse
This is actually what I was trying to do, sadly. Titanium was backing up my info to the phone storage rather than the SD card, and I had to do a data wipe to get to MJA, so I lost them. I figured I could restore to my MF9 backup to redo them, and that's when the trouble started.
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
rosa styhome
dante042 said:
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
Click to expand...
Click to collapse
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Scott02 said:
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Click to expand...
Click to collapse
Scott, check my first post. I edited it with a link to the page with the kernel I used. Make sure that you choose the correct kernel for your Android version. The MF9 and MJA designators have nothing to do with which kernel you need, so make sure to check in your "aboout phone" section to find out what android version you're running. Using the 4.3 kernel on 4.2.2 will cause a bootloop, which is easily fixed by flashing the correct kernel.
Somewhat of a noob here so bare with me...
I have an AT&T S4 here in the US and just downloaded the 4.4 kitkat update but postponed it from installing. I imagine firmware comes with this where i wont be able to install a custom recovery and ROM, is that correct? I have my phone rooted which is running MK2 but have yet to install a recovery and ROM on it. I read on AT&T's website that i can only postpone the update 3 times for 4 hours at a time so i guess i have to figure this out soon. What do you guys think? Install the update OR immediately install a recovery and a new ROM so i am not forced to install this update? Thanks for the help fellas, this site has helped me so much already!
Here is info on the AT&T website http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820#fbid=sUc0HQQUHF_
jermo said:
Somewhat of a noob here so bare with me...
I have an AT&T S4 here in the US and just downloaded the 4.4 kitkat update but postponed it from installing. I imagine firmware comes with this where i wont be able to install a custom recovery and ROM, is that correct? I have my phone rooted which is running MK2 but have yet to install a recovery and ROM on it. I read on AT&T's website that i can only postpone the update 3 times for 4 hours at a time so i guess i have to figure this out soon. What do you guys think? Install the update OR immediately install a recovery and a new ROM so i am not forced to install this update? Thanks for the help fellas, this site has helped me so much already!
Here is info on the AT&T website http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820#fbid=sUc0HQQUHF_
Click to expand...
Click to collapse
At the moment yes that is correct.. You can freeze att update to postpone things while you figure it out..
hankbizzo5 said:
At the moment yes that is correct.. You can freeze att update to postpone things while you figure it out..
Click to expand...
Click to collapse
well yeah i know i can postpone which i did and will continue to do, im wondering if i should hurry up and install a custom recovery and ROM to not have to install this update? Im also wondering what recovery people like the most Clockwork Recovery or Team Win Recovery?
jermo said:
well yeah i know i can postpone which i did and will continue to do, im wondering if i should hurry up and install a custom recovery and ROM to not have to install this update? Im also wondering what recovery people like the most Clockwork Recovery or Team Win Recovery?
Click to expand...
Click to collapse
I don't think there is custom recovery for you.... Unless you are talking about safe strap.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
jermo said:
well yeah i know i can postpone which i did and will continue to do, im wondering if i should hurry up and install a custom recovery and ROM to not have to install this update? Im also wondering what recovery people like the most Clockwork Recovery or Team Win Recovery?
Click to expand...
Click to collapse
You CAN NOT install CWM or TWRP on your mk2 S4. Only Safestrap 3.71 is a recovery that works. This is common knowledge that is posted throughout the forums on XDA. Search is your friend. But here, let me give you everything you need so you can not brick your phone in the first place. Please read it & thank the op in the threads. Good luck.
http://forum.xda-developers.com/showthread.php?t=2616221
Check out the "all things mk2 nb1" topic. It's in this section. It tells you which files to freeze or if you safestrap and install custom rom your fine. Postponing the update does not mean it won't do it tonight all by itself.
Dev Time Estimates?
Does anyone have an estimate on about how long it will take devs to analyze the security of the new bootloader for the possibility of custom ROMS/recoveries? We can always hope that AT&T/Samsung has opened up a new exploit while trying to fix the old one. :silly:
JTrocks said:
Does anyone have an estimate on about how long it will take devs to analyze the security of the new bootloader for the possibility of custom ROMS/recoveries? We can always hope that AT&T/Samsung has opened up a new exploit while trying to fix the old one. :silly:
Click to expand...
Click to collapse
If there is 1 thing I've learned here...don't ask for a time frame. It piss them off, and that's the last thing we want. Just use titanium backup to freeze the AT&T updater and wait. I've waited this long for 4.4 a few more weeks won't kill me.
beast3300 said:
I don't think there is custom recovery for you.... Unless you are talking about safe strap.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
well i just installed CWM from this thread http://forum.xda-developers.com/showthread.php?t=2314494
It installed fine and my phone boots into recovery and back into android just fine. after the CWM install i got to the second post in that thread where it said not to install CWM or else it will brick my phone Jesus too much to read and go through now, used to be so easy back in the day on my G1 and other phones. Now i guess i have to install the stock rom to get rid of CWM :crying:
John The Rhino said:
You CAN NOT install CWM or TWRP on your mk2 S4. Only Safestrap 3.71 is a recovery that works. This is common knowledge that is posted throughout the forums on XDA. Search is your friend. But here, let me give you everything you need so you can not brick your phone in the first place. Please read it & thank the op in the threads. Good luck.
http://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
an0ther said:
Check out the "all things mk2 nb1" topic. It's in this section. It tells you which files to freeze or if you safestrap and install custom rom your fine. Postponing the update does not mean it won't do it tonight all by itself.
Click to expand...
Click to collapse
nice thanks guys! i missed that thread, i was in a totally different one...and yeah it will do it itself here in prob 8 hours so i guess that is why i am trying to install a recovery and ROM so i dont have to update
jermo said:
nice thanks guys! i missed that thread, i was in a totally different one...and yeah it will do it itself here in prob 8 hours so i guess that is why i am trying to install a recovery and ROM so i dont have to update
Click to expand...
Click to collapse
If you are on stock 4.3 & don't want the OTA update & just want to stop it from downloading & installing automatically, then do this.
Freeze the following applications...
AT&T Software update v42_1_1309_1_1
LocalFOTA v2_1308_1_1
wssyncmlnps v43_1309_3_1 ----> Samsung updater service
(Pulled from http://forum.xda-developers.com/show....php?t=2506101.
John The Rhino said:
If you are on stock 4.3 & don't want the OTA update & just want to stop it from downloading & installing automatically, then do this.
Freeze the following applications...
AT&T Software update v42_1_1309_1_1
LocalFOTA v2_1308_1_1
wssyncmlnps v43_1309_3_1 ----> Samsung updater service
(Pulled from http://forum.xda-developers.com/show....php?t=2506101.
Click to expand...
Click to collapse
i was actually reading through that right now, i went into application manager and was only able to force stop the last two. it wont let me force stop the ATT software update v42 and it wont let me turn off any of them...must be missing something
jermo said:
well i just installed CWM from this thread http://forum.xda-developers.com/showthread.php?t=2314494
It installed fine and my phone boots into recovery and back into android just fine. after the CWM install i got to the second post in that thread where it said not to install CWM or else it will brick my phone Jesus too much to read and go through now, used to be so easy back in the day on my G1 and other phones. Now i guess i have to install the stock rom to get rid of CWM :crying:
Click to expand...
Click to collapse
If you are on MK2, you did not install CWM recovery. You think you did, but you actually booted back into the stock recovery. Which is the best thing that could have happened to you because a lot of people brick their phones and lose recovery completely trying to install a custom recovery (beside Safestrap) on any firmware past MDL. Fortunately, there is a method for most people to recover even if they do Derp their phone. I suggest you take time to read about what is and is not possible with your phone and the different firmwares because the next time you might not be so lucky. Good luck.
scott14719 said:
If you are on MK2, you did not install CWM recovery. You think you did, but you actually booted back into the stock recovery. Which is the best thing that could have happened to you because a lot of people brick their phones and lose recovery completely trying to install a custom recovery (beside Safestrap) on any firmware past MDL. Fortunately, there is a method for most people to recover even if they do Derp their phone. I suggest you take time to read about what is and is not possible with your phone and the different firmwares because the next time you might not be so lucky. Good luck.
Click to expand...
Click to collapse
actually i think you are right, because i was going to keep following those instructions to do a backup in CWM but there is no backup and restore option. so i guess that does mean i still have the stock recovery...whew!
jermo said:
i was actually reading through that right now, i went into application manager and was only able to force stop the last two. it wont let me force stop the ATT software update v42 and it wont let me turn off any of them...must be missing something
Click to expand...
Click to collapse
You need an app like Titanium Back up Pro to be able to freeze the updaters. It works, I've done it on mine.
John The Rhino said:
You need an app like Titanium Back up Pro to be able to freeze the updaters. It works, I've done it on mine.
Click to expand...
Click to collapse
I have Titanium Backup but not the Pro, is it worth the 7 bucks?
jermo said:
I have Titanium Backup but not the Pro, is it worth the 7 bucks?
Click to expand...
Click to collapse
Absolutely.
I have Verizon Galaxy Note 3, and my problem is that Wifi button is greyed out and simply wouldnt turn on.
I have done a lot of homework so far, and before, I had 4.3 Jelly Bean, and Wifi being greyed out started around 2 weeks ago (early Dec/2014 - until then, it worked fine).
So I updated to 4.4.2 Kitkat thinking software issue, but wifi is still not working.
I had already searched for hours, and did many things to try to isolate the problem.
*I tried Safe mode
*Reset Cache/Factory several times
*Battery in-n-out, SD card in-n-out, any external peripherals i had alrdy taken everything off and tried
*Tried Alliance/Jasmine/Eclipse ROMs, but still same
*Not router issue @ home since Phone Wifi simply wouldn' turn on
I thought of downgrading back to 4.3 Jelly Bean, but there were many articles saying I can not downgrade, so I think it's out of option.
I now think it's hardware issue, but can not confirm... went to Verizon store too, and the guy just feels it's more software by 51/49, but the ultimate problem is that I just can not 100% ID what the exact problem is - software or hardware.
I really don't want to spend $ for another phone... I also feel it is Kitkat since I also found many articles with Note 3 Kitkat wifi problem, and I read a lot of them, but couldn't really find any solution to my specific issue.
My understanding is that I have 2 options - wait for proper fix by Dev/Samsung for Kitkat firmware or get a new phone
I really did everything I can within my power, and making this post is my last resort...
Hope I can shed some light from experts or anyone who knows any more beneficial details so that @ least i can try to sort my options and situation more clearly...
Thanks much in advance!
Have you tried using Samsung Kies to return to complete stock? Why didn't the Verizon tech offer this choice and flash stock firmware?
My guess is you have a baseband/firmware mismatch somewhere. 4.4.2 firmware and baseband can be found in this thread.
Or flash nc4 in odin.
KennyG123 said:
Have you tried using Samsung Kies to return to complete stock? Why didn't the Verizon tech offer this choice and flash stock firmware?
My guess is you have a baseband/firmware mismatch somewhere. 4.4.2 firmware and baseband can be found in this thread.
Click to expand...
Click to collapse
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Gl2u81 said:
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Click to expand...
Click to collapse
ok, i did already check out your thread before, and when i had tried to download 4.3 (1st one), it had me download like .exe file, and these kind of files tend to be virus/spyware so i just didn't... i also read many posts about how i can NOT downgrade to 4.3 from 4.4 so software wise, my current understanding is that I am **** out of luck until someone fixes firmware... or am i wrong? I guess I am trying to be proven wrong, and hope someone can show me a solution to my weird unique problem...
Btw, already on NC4 (I had updated to NC2 firstly, and Jasmine got stuck on bootloop, so I got NC4 and used Odin, then it fixed the bootloop)
Merry Xmas, huh?
P.S. Thanks for replying on Xmas day, lol
Correct you can not downgrade. Flash nc4 in odin.
https://www.androidfilehost.com/?fid=23487008491963309
Gl2u81 said:
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...
Lemme check our your link and see
Click to expand...
Click to collapse
You specifically stated in the OP that you went to the Verizon store. They should have just flashed the most recent firmware/OS at that time.
You need to just Odin the latest stock tar or use Kies to do the same. Somewhere along the way the baseband, firmware and ROM OS have been mixed which causes the wifi problem.
drewcam888 said:
Correct you can not downgrade. Flash nc4 in odin.
https://www.androidfilehost.com/?fid=23487008491963309
Click to expand...
Click to collapse
Yes, running nc4 right now
KennyG123 said:
You specifically stated in the OP that you went to the Verizon store. They should have just flashed the most recent firmware/OS at that time.
You need to just Odin the latest stock tar or use Kies to do the same. Somewhere along the way the baseband, firmware and ROM OS have been mixed which causes the wifi problem.
Click to expand...
Click to collapse
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Gl2u81 said:
Yes, running nc4 right now
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Click to expand...
Click to collapse
In your phone settings, what does it say in about phone for baseband and software versions? It should all end in NC4 then.
I directed you to a link for nc4 then flash in odin. That is the correct step to try right now
Gl2u81 said:
Yes, running nc4 right now
Yes i did go, and i feel we are getting somewhere...
iam not like total expert on micro details on flashing, but from what i understand, baseband version and firmware are same, and firmware is like BIOS for computer while ROM is like Windows, Linux or an Operating System.
so wut i understood is that u are saying that my firmware (BIOS) and ROM (OS) are incompatible?
http://forum.xda-developers.com/showthread.php?t=2553357
I am running this Alliance rom, and also NC4 i got from XDA forum for my phone... so i think I am on Kitkat firmware running ROM that was made to run on this firmware?
Please point anything out to me if i had something wrong - open to anything to try to resolve this so that i dont have to dump $ for another phone...
Click to expand...
Click to collapse
You have lots of things wrong in the above. So to keep it simple just get OFF of the alliance ROM, get back on the NC4 ROM and modem. If nothing else...go back to the Verizon store and have them totally wipe and reflash the phone. You can also do that at the Samsung section of a Best Buy store.
Sent from my Note 3 via Tapatalk
KennyG123 said:
In your phone settings, what does it say in about phone for baseband and software versions? It should all end in NC4 then.
Click to expand...
Click to collapse
baseband ends in nc4 and base version also nc4...
drewcam888 said:
I directed you to a link for nc4 then flash in odin. That is the correct step to try right now
Click to expand...
Click to collapse
I successfully flashed this via Odin, but wifi is still an issue... and safestrap 3.75 doesnt work any more
Gl2u81 said:
I successfully flashed this via Odin, but wifi is still an issue... and safestrap 3.75 doesnt work any more
Click to expand...
Click to collapse
If you successfully flashed Odin and factory reset the phone (important), and tried wifi immediately after and it still will not turn on (without adding anything else) then it must be some hardware failure.
KennyG123 said:
If you successfully flashed Odin and factory reset the phone (important), and tried wifi immediately after and it still will not turn on (without adding anything else) then it must be some hardware failure.
Click to expand...
Click to collapse
yeah... wifi doesnt turn on... i'll settle as hardware issue, not software and move on with my life...
Warranty replace it and be done.
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!