Related
Here's the story:
I got my S4 late last year, and decided to use qbking77's root technique to root my phone. After the 4.3 update, I no longer had root. Also, I had the wifi issue plaguing many S4 users at the moment. So I thought maybe re-rooting would solve my problem, but apparently qbking's method no longer works. So, being a crafty individual, I decided to revert to 4.2.2. I downloaded L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar from samsung-updates and used ODIN to load it. Soon after starting the download, I received a FAIL notification in ODIN and an error in the download screen on my phone as follows:
SW REV CHECK FAIL : FUSED : 4, BINARY : 1
I have tried many versions of ODIN but cannot get the file to load. I really don't want to deal with Sprint over this matter, so any help would be appreciated.
[I am also downloading the 4.3 version from samsung-updates at the moment, but I have to get to bed, so I will try tomorrow.]
copulat0r said:
Here's the story:
I got my S4 late last year, and decided to use qbking77's root technique to root my phone. After the 4.3 update, I no longer had root. Also, I had the wifi issue plaguing many S4 users at the moment. So I thought maybe re-rooting would solve my problem, but apparently qbking's method no longer works. So, being a crafty individual, I decided to revert to 4.2.2. I downloaded L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar from samsung-updates and used ODIN to load it. Soon after starting the download, I received a FAIL notification in ODIN and an error in the download screen on my phone as follows:
SW REV CHECK FAIL : FUSED : 4, BINARY : 1
I have tried many versions of ODIN but cannot get the file to load. I really don't want to deal with Sprint over this matter, so any help would be appreciated.
[I am also downloading the 4.3 version from samsung-updates at the moment, but I have to get to bed, so I will try tomorrow.]
Click to expand...
Click to collapse
you CANNOT got back to MF9 or ANYTHING before MJA.
Grab the MK2 tar (OR MJA) - THERY'RE HERE LOOK.
Flash that in PC Odin and you'll be fine
Spend some time and read and you'll be Okay.
leaderbuilder said:
you CANNOT got back to MF9 or ANYTHING before MJA.
Grab the MK2 tar (OR MJA) - THERY'RE HERE LOOK.
Flash that in PC Odin and you'll be fine
Spend some time and read and you'll be Okay.
Click to expand...
Click to collapse
Great news! I got the update installed back to 4.3 and my WiFi is back on! talk about 2 birds. thanks for the help leader!
copulat0r said:
Great news! I got the update installed back to 4.3 and my WiFi is back on! talk about 2 birds. thanks for the help leader!
Click to expand...
Click to collapse
THANK you for reporting back! That is what this community is all about.
Since you have the lates firmware (MJA or MK2) you can now go root, install recovery (via PC Odin or goomanager) and then flash what you wish.
BUT please take some time to read through the developers OPs and followup posts - different ROMs require different recoveries and wipe methods. Recoveries can be switched in recovery too.
Good luck
Hi guys,
I came across this post while searching XDA as I am getting the same error (SW REV CHECK FAIL : FUSED : 4, BINARY : 1) when I try to install "L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar" via various versions of ODIN.
A little background on my phone:
Sprint GS2 L720 that I bought used.The phone gets stuck on the yellow Sprint screen during boot-up. I don't have the whole story but apparently he tried to flash the phone and did so with the incorrect ROM. Rather than try to fix the phone he decided to sell it for cheap so he found a sucker (me) to buy it hoping that I could fix it. I don't have a problem getting the phone into download mode, just can't get the TAR file to install correctly. Since I've never had this phone in working condition I don't know what firmware is on the phone.
I'm sorry if this is a dumb or basic question but I'm completely new at this so any help you can give me in laymen's terms (or links to threads I should read or files I should install) would be greatly appreciated.
LeaderBuilder- You mentioned installing recovery via ODIN? Would you mind elaborating on this. I Googled "Install Recovery with ODIN S4" and came up with videos and links using ClockworkMod and TWRP but I'm not sure if this is what you were referring to. I just hesitant because I don't want to make matters worse or hardbrick my phone.
Anybody willing to respond and help me out- THANKYOU!!!
You install recoveries by using tar files of them
Sent from my SPH-L720 using Tapatalk
Daniel,
Thanks for your reply. Do you know specifically which recovery TAR file I should install? Also, where can I download them?
Thanks,
Matt
MMcCawley said:
Hi guys,
I came across this post while searching XDA as I am getting the same error (SW REV CHECK FAIL : FUSED : 4, BINARY : 1) when I try to install "L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar" via various versions of ODIN.
A little background on my phone:
Sprint GS2 L720 that I bought used.The phone gets stuck on the yellow Sprint screen during boot-up. I don't have the whole story but apparently he tried to flash the phone and did so with the incorrect ROM. Rather than try to fix the phone he decided to sell it for cheap so he found a sucker (me) to buy it hoping that I could fix it. I don't have a problem getting the phone into download mode, just can't get the TAR file to install correctly. Since I've never had this phone in working condition I don't know what firmware is on the phone.
I'm sorry if this is a dumb or basic question but I'm completely new at this so any help you can give me in laymen's terms (or links to threads I should read or files I should install) would be greatly appreciated.
LeaderBuilder- You mentioned installing recovery via ODIN? Would you mind elaborating on this. I Googled "Install Recovery with ODIN S4" and came up with videos and links using ClockworkMod and TWRP but I'm not sure if this is what you were referring to. I just hesitant because I don't want to make matters worse or hardbrick my phone.
Anybody willing to respond and help me out- THANKYOU!!!
Click to expand...
Click to collapse
You are trying to install an older version of the stock tar. Once your phone has been upgraded to MJA or newer you cannot install older tar files. You can download the newest stock tar for are phone from here: http://forum.xda-developers.com/showthread.php?t=2601443
Install using odin 3.07 or newer. Good luck.
Thanks Cruise,
I read through all of the posts on the link that you sent and according to the original poster, flashing that TAR will trip the KNOX which sounds undesirable and potentially dangerous (at least according to the second poster). Is this my best best or only option? Sorry if that's a dumb question but like I said, I'm new to all of this and I really don't want to hard brick my phone. Ideally I'd like to get this to boot properly and bring it back to stock but it sounds like bringing it back to stock might not be an option at this point. Thanks again for your input and the link!
MMcCawley said:
Thanks Cruise,
I read through all of the posts on the link that you sent and according to the original poster, flashing that TAR will trip the KNOX which sounds undesirable and potentially dangerous (at least according to the second poster). Is this my best best or only option? Sorry if that's a dumb question but like I said, I'm new to all of this and I really don't want to hard brick my phone. Ideally I'd like to get this to boot properly and bring it back to stock but it sounds like bringing it back to stock might not be an option at this point. Thanks again for your input and the link!
Click to expand...
Click to collapse
How is it dangerous to trip knox? I personally have it tripped and have really ran into any problems once I rooted. I couldn't install kernels for some reason but I think that was something o was doing wrong .
Sent from my SPH-L720 using Tapatalk
---------- Post added at 09:13 AM ---------- Previous post was at 09:12 AM ----------
And it will NOT trigger Knox because it is a stock unmodified tar straight from Samsung/Sprint.
Sent from my SPH-L720 using Tapatalk
MMcCawley said:
Thanks Cruise,
I read through all of the posts on the link that you sent and according to the original poster, flashing that TAR will trip the KNOX which sounds undesirable and potentially dangerous (at least according to the second poster). Is this my best best or only option? Sorry if that's a dumb question but like I said, I'm new to all of this and I really don't want to hard brick my phone. Ideally I'd like to get this to boot properly and bring it back to stock but it sounds like bringing it back to stock might not be an option at this point. Thanks again for your input and the link!
Click to expand...
Click to collapse
I got news for you, your Knox is already tripped. If the previous owner had already tried to root and install a custom rom that ship has sailed. Installing a stock tar does not trip Knox, installing a custom recovery does.
Sent from my icrap 2 using Tapatalk HD
Hey guys,
Just wanted to follow-up and let you know that your suggestions worked and that I'm now up and running. THANK YOU ALL for your help and suggestions!
I have a verizon note 3 I ordered from insurance when my last note 3 finally bit the dust. My previous phone was running jasmine and stock using safestrap. I strove to do the samewith this phone. Instead, when attempting to use towelroot, it said my phone was no longer supported. I tried to find a viable nc2 and couldn't for the last week. Most links on this website are dead because note 3 is hardly supported anymore. I finally found one, one developed by hrsbad or one someone claimed was, the custom note 3 nc2. When I flashed it using odin, i get an error that pops up with Samsung splash screen, "kernel is not seaandroid enforcing" It then takes me to a yellow exlaimation point with "system software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help. Is there anything i can do? Im sure there's a wiz out there who knows an easier solution.
I would appreciate your help very greatly, and if you could explain to me why i couldnt; use safestrap and even suggest how i could root an alternate way that would be super amazing. Thanks for any help you might be able to lend.
I have attemtped to flash all the nc2 and nc4 finally succeeding with one that had previously failed. The kernel error no longer appears and my phone is behaving normally. I have 4.4.4 and would like to root it, are there any options anyone knows of? Towelroot does not support my version, Im open to any suggestions. Thanks in advance.
try one of these imgs http://forum.xda-developers.com/showthread.php?t=2524572
vzwnexus said:
try one of these imgs http://forum.xda-developers.com/showthread.php?t=2524572
Click to expand...
Click to collapse
EDIT: Thanks for your reply again, but I was wrong. I didn't try any of these because all the links I'd be interested in are no longer being served. Is there anywhere else I can get this at, or anything else I can do. Thank you again I really appreciate it.
thanks for your reply. did try the nc2 in AP spot of odin and it bricked my phone temporarily. Did I use the wrong one? or should I have used multiples of those to do it properly?
do you remember what firmware you were running before going full root? you'll want to get that img to flash. maybe nc4?
vzwnexus said:
do you remember what firmware you were running before going full root? you'll want to get that img to flash. maybe nc4?
Click to expand...
Click to collapse
I have put nc4 back on. This is how the phone was shipped. But I was unable to root with towelroot, I am still without root. And that is the crux ofmy questions now, is where can I get nc2 so I can use towelroot, or is there a better method than that?
what I have tried
nc2kernel.tar.md5
VZW-N900VVRUCNC4-20140512165349
n900v_kk_firmware.tar.md5
It has been very difficult finding these files online, sammobile is where I got one of them, the other two were from a hsrbad post, a comment from "Dutchboy" who still hosted these files lead me to them.
it's hard to say if those work, what I'm trying to determine is the original firmware your phone was running before all of this. I'm not super good at this just fyi.. haha. i usually look for the modem and firmware for the "original" firmware from before rooting.
vzwnexus said:
it's hard to say if those work, what I'm trying to determine is the original firmware your phone was running before all of this. I'm not super good at this just fyi.. haha. i usually look for the modem and firmware for the "original" firmware from before rooting.
Click to expand...
Click to collapse
Sorry for the late response. School and work are kicking my butt. The original is hard to say, I attempted like five different roms after noticing that mine could not be towelrooted. all of these romsfailed, and one finally raised an exception with the security that temporarily soft bricked my phone, I found a nc4 on sammbile that was able to remedy that, but I'd like most of all to get this rooted and safestrapped again so i can dualboot as i had previously. I'm also pretty novice but i enjoy the attempting to do this stuff, even when it ends in me bricking my phone for the day :good:
so have you been able to get your phone running?
deindichter said:
Sorry for the late response. School and work are kicking my butt. The original is hard to say, I attempted like five different roms after noticing that mine could not be towelrooted. all of these romsfailed, and one finally raised an exception with the security that temporarily soft bricked my phone, I found a nc4 on sammbile that was able to remedy that, but I'd like most of all to get this rooted and safestrapped again so i can dualboot as i had previously. I'm also pretty novice but i enjoy the attempting to do this stuff, even when it ends in me bricking my phone for the day :good:
Click to expand...
Click to collapse
Towelroot was supposed to work on NC4.
You can not flash any ROM lower than NC4 due to bootloader. There is also supposedly a rooted NC4 here that you can flash...but towelroot should work.
Sent from my Note 3 via Tapatalk
donc113 said:
Towelroot was supposed to work on NC4.
You can not flash any ROM lower than NC4 due to bootloader. There is also supposedly a rooted NC4 here that you can flash...but towelroot should work.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Thank you both for your replies.
Towelroot had previously worked , this is an insurance replacement as mine bit the dust. I went to towelroot and to my great sadness does not work. I am using:
4.4.4
sm-n900v
n900vvrudnj6
kernel 3.4.0
Truly I'm novice so Im not positive if any of this can help or not, but do you know of a way I can towelroot?
deindichter said:
Thank you both for your replies.
Towelroot had previously worked , this is an insurance replacement as mine bit the dust. I went to towelroot and to my great sadness does not work. I am using:
4.4.4
sm-n900v
n900vvrudnj6
kernel 3.4.0
Truly I'm novice so Im not positive if any of this can help or not, but do you know of a way I can towelroot?
Click to expand...
Click to collapse
Nothing works on 4.4.4 or higher....sorry
Sent from my Note 3 via Tapatalk
thank you.
My phone is rebricked, does anyone know where you can get files to revert back to stock?
They're all here...... well most of then back to 4.3
sammobile.com/firmwares/database/SM-N900V/
Hey guys,
Great site. I have the lag problem with my S7 edge after root. Downloaded fix file from link in other in (Rooting Problem). Not sure what to do now. Do I flash zip with Flashfire? Leave it in the zip state? I realize this is elementary to most, just been a very long time for me. Hated to ask the question again. Wouldn't let me ask it in the thread I mention.
Never mind, figured it out. Thanks for the 37 views without advice.
Well what file did you download and did you use flashfire to install? I don't have root just curious
Sent from my SAMSUNG-SM-G935A using Tapatalk
Jnewell05 said:
Well what file did you download and did you use flashfire to install? I don't have root just curious
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
There's a file on the Verizon forum that helps most if not all the issues with root. Just flash it once and you're good to go. OP just doesn't understand people here aren't obligated to help him, self entitled privilege at it's best.
Sent from my SM-G935U using Tapatalk
buckmaster1967 said:
Never mind, figured it out. Thanks for the 37 views without advice.
Click to expand...
Click to collapse
"Figured it out."
Doesn't explain anything. Nice.
falkon114 said:
"Figured it out."
Doesn't explain anything. Nice.
Click to expand...
Click to collapse
Sorry guy. You are right. I should of explained. I followed directions from this youtube video ( https://www.youtube.com/watch?v=Kqb-p2JO5I4 ). Worked , but was lagging and wifi issues. Came here, found and flashed with Flashfire., the wifi fix file , which I can't seem to find here now. Everything worked great. Until next morning it was stucked on AT&T logo. Only could get it into download mod. Had to do a factory rest. Want to youtube to look for a different way to root. Found this ( https://www.youtube.com/watch?v=QcFEcycZZnU ) followed directions and seem to work great right now. But time will tell. Sorry for the rushed details, busy day. Thanks.
Update. Yesterday got stucked on AT&T logo AGAIN. I decided the heck with this root, 4th time I had to set phone up from start. I did a factory reset. Set my phone back up. Lost my root according to Root Checker. But I am getting security warning, and when it reboots. It still shows custom and unlocked. Any ideals? As so, I tried to do the AT&T update, but it fails.
If it is showing custom & unlocked, you might have a custom recovery and/or unlocked bootloader. Just got the S7 edge, so I haven't really messed around with the internals yet (or anything dealing with rooting or unrooting), but that's usually what that means in my experience. The fix is usually an odin flash to the stock image, but as I said, I haven't really gotten too involved with it yet. A factory reset will set the system back to stock, but I don't think it does anything with the other partitions. Good luck and if I can find anything out that might help, I'll come back by.
So far as the update, do you have all the prerequisite stock bloatware installed? There are apps that are required for an update to work. If you uninstalled any it will freeze you out of getting updates.
And my signature is so out of date it is funny.
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!
Hi guys
I have a spare phone now my son upgraded, the S5 SM-G901F. I thought it wound be fun to install another software, possibly more up to date. So I first set out to root it but I haven't played around much with this sort of thing for long while.
I googled and found it seemed to be Odin to use so I downloaded 3.10. Also downloaded cf root. I went into download mode and when I plugged it in, the light in Odin lit up showing successfully connected. When I added the cf file and clicked start it went through some steps but stuck at Recovery. Img and wouldn't progress further.
I tried multiple times, tried a different cable and USB port and also Odin 3.07 and a different cf file even though I think it was the same one but from a different site. All no better.
Originally I bought it a few years back, used from a colleague. I think it was a carrier phone, EE iirc, and I had to get a code to unlock the SIM to use with mine. Maybe that also means it's software is locked?
Any help much appreciated
Thanks, marc
No one guys?
Please help
Marc
Please help
marc.knuckle said:
Please help
Click to expand...
Click to collapse
well to be honest, i would need to spend some time, "Googling" your model .... . I believe , your S5 is a Dev phone, meaning, it was not set up for any carrier, just for running demo's and such. IF this is true, I have no true answer for you.
Odin yes, you need that, that is true! (Believe 3.07, 3.09 and 3.10 work the best for these phones. Had tried a very newer version, several month back, and it did not do the job.. something like 3.14 or 16)
I recommend going to Sam Mobile, and run your model # through them. They will give you all the info about your model and possibly the latest firmware for it.
Sorry that I can not give you all that you are needing. I just don't know a ton about those S5 Plus models. (( I had to even look 'em up too) the plus has a slight better chip was well as graphics, but again, I dont know of any that actually work on a modern carrier like sprint, Verizon, T-Mobile , etc.)
Thanks for the reply mate.
It definitely isn't a Dev phone, my colleague definitely had it on contact from a carrier initially.
I hadn't actually realised or noticed it being a Plus model as some sites mention the Plus and some don't.
Any other help from anyone appreciated
marc.knuckle said:
Thanks for the reply mate.
It definitely isn't a Dev phone, my colleague definitely had it on contact from a carrier initially.
I hadn't actually realised or noticed it being a Plus model as some sites mention the Plus and some don't.
Any other help from anyone appreciated
Click to expand...
Click to collapse
OK, Was only going off your model # you had given.
Did check... Odin and a good copy of CF auto root... That should be that.
Then of course, get away from a really old non sucure os (6.01 MM was their last made) .
Other than those 2 pieces, you should be good to root
Not pushing, or anything but LineageOS is rather good and does run well on these!
Plus, get a monthly security injection!
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
OK, Was only going off your model # you had given.
Did check... Odin and a good copy of CF auto root... That should be that.
Then of course, get away from a really old non sucure os (6.01 MM was their last made) .
Other than those 2 pieces, you should be good to root
Not pushing, or anything but LineageOS is rather good and does run well on these!
Plus, get a monthly security injection!
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
That's the problem as i mentioned in the first post, I've tried with odin and cf root and it doesn't work. That's why i posted on here. I wondered whether the phone was locked to the carrier.
marc.knuckle said:
That's the problem as i mentioned in the first post, I've tried with odin and cf root and it doesn't work. That's why i posted on here. I wondered whether the phone was locked to the carrier.
Click to expand...
Click to collapse
Well, I would have to say NOPE!
Well only trying to keep your Q, on the top, so folks that might know, could help!
BTW, when I looked your model up, totally different CPU and GPU, which might need a different CF auto root zip, or a different one to actually work... Since hardware is different.
Just guessing on that, but, could be wrong. Rather busy at the moment, but will look up your specs again, and see if I find something for ya.
Mean time, Hopefully someone could chime in and point you towards the correct path to take...
OH
Q- What sort Recovery do you currently have? (Stock or custom (e.g. TWRP))
Might want to check for one for your phone.
I would actually start with TWRP, see what they have for ya.
( Will need Odin for this! BUT, once you have a Recovery in/on the phone, then you could use Magisk to root ot try CF and see 8f that works for you (I use Majisk) Plus add in the fact that you should make a Back up, of your current system! In case of issues, you can always jump back to Stock. )
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Well, I would have to say NOPE!
Well only trying to keep your Q, on the top, so folks that might know, could help!
BTW, when I looked your model up, totally different CPU and GPU, which might need a different CF auto root zip, or a different one to actually work... Since hardware is different.
Just guessing on that, but, could be wrong. Rather busy at the moment, but will look up your specs again, and see if I find something for ya.
Mean time, Hopefully someone could chime in and point you towards the correct path to take...
OH
Q- What sort Recovery do you currently have? (Stock or custom (e.g. TWRP))
Might want to check for one for your phone.
I would actually start with TWRP, see what they have for ya.
( Will need Odin for this! BUT, once you have a Recovery in/on the phone, then you could use Magisk to root ot try CF and see 8f that works for you (I use Majisk) Plus add in the fact that you should make a Back up, of your current system! In case of issues, you can always jump back to Stock. )
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Cheers mate
It's stock recovery at the minute
marc.knuckle said:
Cheers mate
It's stock recovery at the minute
Click to expand...
Click to collapse
Sorry, that I have not gotten back sooner. Issues to deal with.... Just like many others these days...
That said, I take it, that you have a custom Recovery, and also Root?
Hope so, if not, I'm still here for ya
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Sorry, that I have not gotten back sooner. Issues to deal with.... Just like many others these days...
That said, I take it, that you have a custom Recovery, and also Root?
Hope so, if not, I'm still here for ya
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Cheers mate. So, some progression.
Firstly i didn't have a custom recovery or root. I was getting stopped at the first hurdle.
So, i figured it had something to do with it using a carrier firmware, EE, in the UK. So i found a stock European firmware and successfully used odin to flash it. Then i flashed CF root and TWRP. All good.
So with new confidence i flashed Resurrection Remix Android 9. Although it seemed to have worked, each time i tried to complete set up, straight after imputting my gmail address, the screen was black. Not BSOD type though, if i pressed home it went back to the home screen to i just couldn't complete set up.
So i tried Lineage and that was a boot loop.
Not sure if part of the issue was Gapps but i was definitely using the correct version. ARM, Android 9, stock.
I gave up, reinstalled the stock Android marshmallow and rooted again and installed TWRP. that's where i am now.
Shame really as i fancied a more up to date OS.
Thanks, Marc
marc.knuckle said:
Cheers mate. So, some progression.
Firstly i didn't have a custom recovery or root. I was getting stopped at the first hurdle.
So, i figured it had something to do with it using a carrier firmware, EE, in the UK. So i found a stock European firmware and successfully used odin to flash it. Then i flashed CF root and TWRP. All good.
So with new confidence i flashed Resurrection Remix Android 9. Although it seemed to have worked, each time i tried to complete set up, straight after imputting my gmail address, the screen was black. Not BSOD type though, if i pressed home it went back to the home screen to i just couldn't complete set up.
So i tried Lineage and that was a boot loop.
Not sure if part of the issue was Gapps but i was definitely using the correct version. ARM, Android 9, stock.
I gave up, reinstalled the stock Android marshmallow and rooted again and installed TWRP. that's where i am now.
Shame really as i fancied a more up to date OS.
Thanks, Marc
Click to expand...
Click to collapse
Wait, isn't what you were wanting?
Well at least you now have a Recovery installed! Now, with that of course you can now make a back up of your stock!!!
( other words,.. MAKE A BACK UP! That way, you only have to wipe the system, data, cache and BAM, in the Flash of zip, your back at square one...)
OK, not sure if you picked up a new info about LineageOS, across the pond....
But
They ran into some issues, (soon and hopefully sooner, it will be fixed). Now, after that, they will be dropping LineageOS 17.1 Official!! Yes, for Galaxy S5 too
So, keep an eye out for that, cause am in same Boat, waiting for the Official release.
( personal, I run LineageOS, Magisk (Root and some goodies.. Unfortunately I do tend to add Ggogle, but like Pico, nothing larger. Do flash a kernel also. That said, rather stable, and most everything works) at least for me.... Just waiting for Official 17.1 to roll out! (like just about anyone left that has these phones...)
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Wait, isn't what you were wanting?
Well at least you now have a Recovery installed! Now, with that of course you can now make a back up of your stock!!!
( other words,.. MAKE A BACK UP! That way, you only have to wipe the system, data, cache and BAM, in the Flash of zip, your back at square one...)
OK, not sure if you picked up a new info about LineageOS, across the pond....
But
They ran into some issues, (soon and hopefully sooner, it will be fixed). Now, after that, they will be dropping LineageOS 17.1 Official!! Yes, for Galaxy S5 too
So, keep an eye out for that, cause am in same Boat, waiting for the Official release.
( personal, I run LineageOS, Magisk (Root and some goodies.. Unfortunately I do tend to add Ggogle, but like Pico, nothing larger. Do flash a kernel also. That said, rather stable, and most everything works) at least for me.... Just waiting for Official 17.1 to roll out! (like just about anyone left that has these phones...)
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Thanks mate