Help! I just pulled an all nighter - Samsung Galaxy S7 Edge Questions and Answers

My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.

UPDATE!
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
MajinMight said:
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
Click to expand...
Click to collapse

UPDATE #2
As you can tell I haven't given up yet. I found my current firmware version for download on a different website:
https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/"]https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/
It's another slow download option which really sucks. But I'll be able to test If I can flash the same firmware to the phone (not technically a downgrade and carries the same fused binary). So we shall see. If this doesn't work I'll be looking into the other android 9 or 10 roms and rooting the phone.
Thanks, Derek
MajinMight said:
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
Click to expand...
Click to collapse

TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.

Dang! Well thanks for the info! I guess all the videos I've seen with S7's and custom roms have not been done on the US-Verizon phone. What a bummer. Well this was a major learning experience at least.
My only idea now is to crack her open and make sure the camera didn't come unplugged from a drop. I also seen camera replacements were really cheap online. I don't know if it's worth my time....we are due for a phone upgrade anyway.
SkylineDriver said:
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Click to expand...
Click to collapse

Related

[Q] Quick Question If Someone Has a Moment, Please

I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?

Soft-bricked AT&T S7 Edge trying to unroot / go back to stock

I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
vexx32 said:
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
Click to expand...
Click to collapse
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
dirtydodge said:
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
Click to expand...
Click to collapse
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
vexx32 said:
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
Click to expand...
Click to collapse
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
dirtydodge said:
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
Click to expand...
Click to collapse
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
vexx32 said:
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
Click to expand...
Click to collapse
Yea it works. I know that one does. You'll get a message that says "unauthorized SIM card: or something like that. Just ignore it and use WiFi to setup the phone. Once you have it setup use package disabler or titanium to freeze "setup wizard" and that'll get rid of that notification. You'll have to manually setup your AT&T APN. After that your golden.

Samsung Galaxy Sky J3 SM-S320VL TracFone not flashing....

Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Hey folks,
I'm having the exact same issue as the OP. Odin does a successful install on the phone but I get the unauthorized reset message and then Wifi does not work when prompted on the next screen.
Is there a tracfone version of the rom or a fix that anyone here knows of? Thanks!
@drasnah
I have yet to get any kind of reply from anyone on this. Either now one knows, and is not stating so, or doesn't care.
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
20eyes said:
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
Click to expand...
Click to collapse
First this is not a wi-fi problem it is a re-flashing of the rom problem.
Second, I do not have access, root or otherwise, to any of the system files on the phone.
Third, with the first two in mind this possible solution is of no help.
Fourth, Re-read my original post. I have given complete detailed information as to what I have access to and what I have done.
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Curtis1973 said:
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Click to expand...
Click to collapse
Not sure if that's correct? It depends on the firmware and odin version being used.
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Nate1k904 said:
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
Click to expand...
Click to collapse
Post more details on the error, screenshots, firmware and odin version used.
Need to know if works. Or if needing to settle for a different route.
The_WABBIT said:
Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Click to expand...
Click to collapse
J3 sm s320vl... tracfone root availability? Just bought phone hopefully got a good one to root? Or maybe someone knows who maybe be able to... please help
No updates? Interested, I have the same phone.
There is no solution for this phone. It will forever be a Trac-phone.
Yes, it nice to imagine what could had been. If there was a fix for the locked bootloader. Its encrypted, and is highly unlikely to be broken by anyone.
Do not flash the boot.image that some people have suggested
Although that method works on some devices such as the AT&T Samsung Galaxy S5. In this case flashing the boot.image from an unlocked device does nothing but places the phone into an even more precarious situation, that makes it unusable even as a Trac phone.
While its true that this very low budget phone could had been decent with a custom Rom ,
You will not be able to get it working.
I have one that belonged to my daughter a couple of years ago and I managed to get it boot into the system again.
Its only function is as a calculator, or preschool game, the cellular reception and Wifi connections are highly unstable and will not stay connected.
Now it serves as my nieces play toy. I would donate to some poor person at the Salvation Army it if it was useable.
By the way, for anyone reading this.
If you have an old phone that is useable. You could dramatically help a Homeless people, by gifting them with a phone especially, if it has some minutes on it.
This gift will help them schedule job interviews, doctors appointments , etc and you will feel good knowing that you helped someone in need.
I have done this before, and will be dropping off a Blu phone, and Kindle Tablet this week.
tsongming said:
There is no solution for this phone. It will forever be a Trac-phone..
Click to expand...
Click to collapse
It is possible to gain root on this device.
ashyx said:
It is possible to gain root on this device.
Click to expand...
Click to collapse
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
tsongming said:
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
Click to expand...
Click to collapse
See the thread below. Root was gained, albeit temporary. However I believe this is due to kernel panics which may be solved by a few build.prop edits. We had to do the same on the J327T1.
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-galaxy-j3-sm-s320vl-rooted-t3561762
Also if you firmware S320VUDU1APG2 then why not just update it to the firmware that has been reported to work?
I have found one these phones left on a table of a food truck area, screen was cracked - the device was only getting the android guy with triangle on it, I done some research and found the stock rom and flashed it with odin; as some have mentioned in comments above I also experienced wifi issue, so I thought I had installed incorrect rom - downloaded a different one this was a combination file that was the factory repair rom used for testing the device, but wifi worked - it wasn't a fully working telephone it didnt have the app store, well it really didnt have any apps, but I found I could copy over apk files from my PC to the device and then install them, so the phones not completely useless or junk --- it could be used for something. I myself am using that device as a security camera using IP CAM app works great. I was actually using this device for quiet some time as my roku tv remote, because my actual roku remote grown legs and walked off... i havent tried this, but I am sure you could install a launcher apk such as "apex launcher"
well i wasted enough of your time today...

GS5 verizon 4.4.4 to rooted marshmallow

I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.
Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.
I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!
bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.
Ok. I'll read the guides on the head of this list and see if I can find the right information.
FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.
Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.
bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.
bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5
Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!
Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!
Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?

S7 SM-G930P ~ Boot Loader Issues? SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4

Hi All.
Thank you for any help you might give me in advance with this issue...
Last week, I tried to root the phone with the SM-G930P CF-Autoroot heroqltespr files with Odin found in this forum. I have rooted a few other phones but am no expert. The root after a few attempts failed (verified a few ways), however, some files must have been affected because the phone "identifies" as heroqltespr. Identifies as when I could plug into my PC heroqltespr would be the name. It was not set this way in the obvious name your device areas. I ended up doing a hard reset to clear the phone and other than the ghost naming everything was working fine.
A day or 2 ago Sprint rolled out a new OTA update which the phone installed. Since then the phone was draining battery life. After uninstalling and reinstalling the SD card today, it seems to have tripped a "Security Notice: Unauthorized Actions". That is when the trouble started. The phone started running hot, basically leaking battery power, and was all lagging. I'm assuming the CPU going Ludicrous speed.
Now, I am in a Samsung Splash screen loop, or or a recovery loop. The only thing it does is go into download mode.
I have tried flashing stock firmware, it fails. I've tried flashing with and without the SD or Sim card. Not really sure what I should be doing. The "P" version of my phone seems to be the bastard child of S7s. Any help you guys cold give me would be great. THANK YOU!
The Download Screen Reads:
Odin Mode (High Speed)
Current Binary: Samsung Official
System Status: Custom
FAP Lock: Off
Warranty Void: 8x8
Qualcomm Secure Boot: Enabled
AP SWREV: 85(2,1,1,1,1) K1 S4
I get this error when I try to flash back to stock SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
Stupid question but is your phone in a case?
Sw rev check fail : [aboot]fused 5 > binary 4
freakboysays said:
Stupid question but is your phone in a case?
Click to expand...
Click to collapse
No it isn't.
I get this error message on the download screen. SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
If you dont mind me asking, did you ever find a way to root the G930P with the 5th bootloader updates? Is it even possible at this point in time? Im new when it comes to rooting but with the amount of time Ive spent browsing the web it seems as if there is nothing. Thanks.
tonysak said:
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
Click to expand...
Click to collapse
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Chanman said:
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Click to expand...
Click to collapse
EDIT: Nevermind...sounds like you aren't on sprint.
lvpre said:
EDIT: Nevermind...sounds like you aren't on sprint.
Click to expand...
Click to collapse
Actually, I am on Sprint, and your directions were awesome, thank you so much! The only thing I had to do was change the line to:
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
I'm going to put a link to the thread so others can refer to it. https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446
Hi all,
EDIT: I posted this in another thread that was about two years old, where I followed the instructions that caused this: https://forum.xda-developers.com/sp...msung-galaxy-s7-sm-g930p-root-xposed-t3503599
That thread seems dead-ish and if you managed to fix this issue maybe you can help me also. Also what was lvpre's original post before he edited it, and would it apply here?
So the worst has happened - got a new (used) phone from Boost Mobile, tried this guide, and now I can only boot to the "An error has occured while updating the device software. Use the Emergency Recovery function in the Smart Switch PC software." screen. Sometimes it does take me to the original "Download mode" screen.
Now, I should be able to resolve this by flashing the original firmware correct? (As in, the firmware that was installed when it came)? Or does it just need to be firmware from the same date range that has the same bootloader? ODIN will still let me attempt flashing on this screen, but I still get the same error when I try again, which on the Download mode screen showed "SW REV CHECK FAIL : [system]Fused 4 > Binary 1"
Any advice here? My S6 bricked when somehow OEM unlock enabled itself and I can't get around the FRP lock, I will be VERY annoyed if the same thing happens with a NEW phone. If I can't fix this I am never buying Samsung again. Any advice on this is very welcome! I emailed Boost to ask them which firmware is installed (because I'm an idiot and didn't write it down but have never had flashing go this wrong before).
EDIT: Booting to recovery just shows a blue "RECOVERY BOOTING...." for a second in the corner and gives a recovery bootloop, just keeps flashing that.
EDIT: I apparently tried to flash an earlier bootloader/etc through ODIN according to the directions in the post I linked above, and after that I now have this problem. Nobody else in the thread seems to have had this problem, and your post is the closest to anything I can find on this issue. I would be in your eternal debt if you could help me out here.
PLEASE HELP!
EDIT: Theoretically if I can find the original firmware it was on I should be fine, right? Everywhere I read if flashing goes wrong you just flash the original stock on it. I guess worst case scenario I download gigs upon gigs of firmwares for Sprint 930P over the last year and find the one that sticks? Or is the fact my recovery is bootlooping and I can only go into download mode mean I'm bricked?
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
slvmecha said:
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
Click to expand...
Click to collapse
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Switched from Sprint to T-Mobile. Am I out of luck?
lvpre said:
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Click to expand...
Click to collapse
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
jbuck2 said:
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
Click to expand...
Click to collapse
If your phone is uicc [sim] unlocked from sprint... you can try the following.
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Here is an article https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/
Is this triggers the knox counter ?

Categories

Resources