OK guys, I've got a slight dilemma, I'll try and keep it short as possible but I cannot find any solution online as of yet..
I have been trying to resolve an issue with my partners S6 (G920F on ThreeUK) in which it keeps randomly freezing then rebooting (sometimes not rebooting!). At least 15-20 times a day.
It's already been repaired once by Samsung because of main board failure, and that was an absolute nightmare.(.basically took 2months and WE had to chase them up for it!)
Anyway, I've done all the noob stuff (factory reset, ALL WIPES, Odin flash the original FW it came with which I got from Sammoble..)
Correct me if I'm wrong but if it was software issue causing these hard reboots/freezes I'm sure one of the above processes would've eliminated it?
So. Last option was to flash Nougat via Odin, although it wasn't the Three branded one but the XEU UK one, I really had hoped this would've sorted it.
Nope.
Still freezing. Defo hardware yeah?
So now she wants to send it for second repair.
My concern is that I've flashed a non-brand FW on it, and it ODIN won't let me flash the original 6.0.1 back!!! (Locked bootloader I'm guessing???)
I really need to make sure (by Tues) that the phone is back to how it came as if they see that the FW doenst match up (also, the Three branded 7.0 hasn't been released yet!)
I've seen about an 'OEM UNLOCK' option in some S6 FW's..which would technically enable me to roll back....but XEU doesn't have this in dev options.
I hope someone can help. Sorry for the long post but I feel the details are necessary.
match
match_stick said:
OK guys, I've got a slight dilemma, I'll try and keep it short as possible but I cannot find any solution online as of yet..
I have been trying to resolve an issue with my partners S6 (G920F on ThreeUK) in which it keeps randomly freezing then rebooting (sometimes not rebooting!). At least 15-20 times a day.
It's already been repaired once by Samsung because of main board failure, and that was an absolute nightmare.(.basically took 2months and WE had to chase them up for it!)
Anyway, I've done all the noob stuff (factory reset, ALL WIPES, Odin flash the original FW it came with which I got from Sammoble..)
Correct me if I'm wrong but if it was software issue causing these hard reboots/freezes I'm sure one of the above processes would've eliminated it?
So. Last option was to flash Nougat via Odin, although it wasn't the Three branded one but the XEU UK one, I really had hoped this would've sorted it.
Nope.
Still freezing. Defo hardware yeah?
So now she wants to send it for second repair.
My concern is that I've flashed a non-brand FW on it, and it ODIN won't let me flash the original 6.0.1 back!!! (Locked bootloader I'm guessing???)
I really need to make sure (by Tues) that the phone is back to how it came as if they see that the FW doenst match up (also, the Three branded 7.0 hasn't been released yet!)
I've seen about an 'OEM UNLOCK' option in some S6 FW's..which would technically enable me to roll back....but XEU doesn't have this in dev options.
I hope someone can help. Sorry for the long post but I feel the details are necessary.
match
Click to expand...
Click to collapse
All international (g920F) variants have their bootloaders unlocked, so you don't need to go through any process for that. What I will say though is newer bootloaders, Samsung implement something in them that prevents downgrade from one os version to another.
But alas as aslong your knox counter is intact (meaning you haven't rooted) having a different firmware on there shouldn't stop them from attempting to repair the phone.
P.s try installing the 3 branded nougat firmware.
sofir786 said:
All international (g920F) variants have their bootloaders unlocked, so you don't need to go through any process for that. What I will say though is newer bootloaders, Samsung implement something in them that prevents downgrade from one os version to another.
But alas as aslong your knox counter is intact (meaning you haven't rooted) having a different firmware on there shouldn't stop them from attempting to repair the phone.
P.s try installing the 3 branded nougat firmware.
Click to expand...
Click to collapse
Ah ok. Unfortunately I am unable to roll back meaning the phone is stuck with an international unbranded firmware, which I'm hoping Samsung will not pick up on...another big giveaway is that there is no '3' logo boot animation as you would get with the 3 branded FW.
If only the 3 Nougat was out that would be my next step but typical of Three, they take the longest to release the newest update...so unless they release it before Tues morning then the phone will be sent off with the unbranded FW. hopefully you are right in saying that it shouldn't effect any warranty issues etc...
match_stick said:
Ah ok. Unfortunately I am unable to roll back meaning the phone is stuck with an international unbranded firmware, which I'm hoping Samsung will not pick up on...another big giveaway is that there is no '3' logo boot animation as you would get with the 3 branded FW.
If only the 3 Nougat was out that would be my next step but typical of Three, they take the longest to release the newest update...so unless they release it before Tues morning then the phone will be sent off with the unbranded FW. hopefully you are right in saying that it shouldn't effect any warranty issues etc...
Click to expand...
Click to collapse
If it's going straight to Samsung then aslong as knox is intact they won't care it has an unbranded firmware, the only thing that would stop them would be a phone which has been rooted, so I'm sure there shouldn't be any issues with this.
sofir786 said:
If it's going straight to Samsung then aslong as knox is intact they won't care it has an unbranded firmware, the only thing that would stop them would be a phone which has been rooted, so I'm sure there shouldn't be any issues with this.
Click to expand...
Click to collapse
Knox is intact, all legit apart from the one time ODIN flash of XEU.
So you mean if I flash a different stock nougat on a g920t1 it will continue to boot up even with frp lock on? This prevents the phone from booting up witj official metro pcs nouhgat
sofir786 said:
If it's going straight to Samsung then aslong as knox is intact they won't care it has an unbranded firmware, the only thing that would stop them would be a phone which has been rooted, so I'm sure there shouldn't be any issues with this.
Click to expand...
Click to collapse
Ok. Took phone into Samsung Support shop to see if they can repair...
Half hour we get phone call saying to come back as they have discovered 'some interesting things..' (me, sh*tting myself...)
The tech guy says that the phone has the wrong software on
(me looking shocked..)
After explaining that the phone has been previously repaired by Carphone Warehouse, the tech guy said ' they shouldn't have taken it for repair as it was a 3UK branded phone, so they've obviously replaced mainboard and installed unbranded FW instead of 3 brand...
So. Don't think that they overlook anything like This, they knew exactly what happened. Odin flashing does void warranty.
match_stick said:
Ok. Took phone into Samsung Support shop to see if they can repair...
Half hour we get phone call saying to come back as they have discovered 'some interesting things..' (me, sh*tting myself...)
The tech guy says that the phone has the wrong software on
(me looking shocked..)
After explaining that the phone has been previously repaired by Carphone Warehouse, the tech guy said ' they shouldn't have taken it for repair as it was a 3UK branded phone, so they've obviously replaced mainboard and installed unbranded FW instead of 3 brand...
So. Don't think that they overlook anything like This, they knew exactly what happened. Odin flashing does void warranty.
Click to expand...
Click to collapse
No way really? I've had phones repaired from them before with different firmwares and it's been fine, I suppose it depends on the tech who's looking at it. What was the end result? Was they not willing to repair it?
sofir786 said:
No way really? I've had phones repaired from them before with different firmwares and it's been fine, I suppose it depends on the tech who's looking at it. What was the end result? Was they not willing to repair it?
Click to expand...
Click to collapse
End result is we've taken it back to Carphone Warehouse for second repair, which was recommended by Samsung guy as he believes they were the ones who flashed unbranded FW after main board replacement (even tho it was me but no one needs to know that lol)
If CarphWhs come back saying "can't touch it as FW doesn't match" then obviously we can argue that the phone came back with that FW from first repair...I can't imagine they will.suspect that my misses has Odin flashed her phone with odd FW...
Lesson learnt - I will not intervene or use ODIN unless it's on MY PHONE.
Ultimately I tried to fix it with Nougat flash, thinking that I could revert back to 6.0.1 three brand FW if that didn't fix issue.
It's funny to see the Samsung guy baffled at how this FW ended up on the phone, Carphone Warehouse can be the scapegoat for my errors hopefully
Phone came back. Fixed and with UNBRANDED nougat lol
Win win.
Wow I remember this problem lol
Related
So I bought a 2nd hand S6. The price was good, not great, but good and the phone functions very well with no issues. I probably didn't look at it as closely as I should have, but live and learn. Anyhow, the phone is still on 5.1.1, so I went to flash it in Odin to 6.0.1 - nothing worked. The model says it's an SM-g920f, however, when I go into download mode it's listed as an SM-g920p. Also, the bootloader etc are all 920p. I didn't think twice about it being the f model as I am an American, but I live in the philippines. It is very common to see the international versions of phones here. I know that the p model is common in the US as a sprint phone, and I should have keyed on the fact that when I opened the browser, it took me to the sprint webpage right away. The device is of course rooted. I cannot upgrade it using smart switch. Of course when I initially tried to flash it in odin with a 920f rom, it failed miserably. So, I am wondering if I flash it back to a stock 920p, will it cause me issues?
jaymac99 said:
So I bought a 2nd hand S6. The price was good, not great, but good and the phone functions very well with no issues. I probably didn't look at it as closely as I should have, but live and learn. Anyhow, the phone is still on 5.1.1, so I went to flash it in Odin to 6.0.1 - nothing worked. The model says it's an SM-g920f, however, when I go into download mode it's listed as an SM-g920p. Also, the bootloader etc are all 920p. I didn't think twice about it being the f model as I am an American, but I live in the philippines. It is very common to see the international versions of phones here. I know that the p model is common in the US as a sprint phone, and I should have keyed on the fact that when I opened the browser, it took me to the sprint webpage right away. The device is of course rooted. I cannot upgrade it using smart switch. Of course when I initially tried to flash it in odin with a 920f rom, it failed miserably. So, I am wondering if I flash it back to a stock 920p, will it cause me issues?
Click to expand...
Click to collapse
Anyone?
Just FYI, it appears with the new Blv3 firmwares, the device will only accept official firmware. Meaning, no more flashing U1 firmware on the carrier models, or vice versa. No more flashing U or U1 firmware to the Canadian W models. Flashing between carrier firmwares is fine as long as it's on a carrier branded device (running TMB on a VZW device, etc). But running 950U firmware on a 950U1 will result in a brick, that is this far unrecoverable.
If your currently are running U1 firmware on a U device, vice versa, or running W firmware on a U or U1 device, or vice versa, you need to flash back to the firmware version that shipped with your device BEFORE you accept any OTAs that take you up to Blv3. Currently the S series is still on BlV2, but may go to Blv3 like the Note series just did.
This has been tested and confirmed.
Credit goes to @me2151, @FatalONEM8 for discovering this and warning people. I didn't find the issue or test, it just passing on the info to hopefully save some bricks.
Update from @mweinbach:
"EDIT: After being tested by XDA Senior member me2151, it turns out cross region flashing does work. Prince Comsy Odin is working, but we can not test if the factory binary flashing will hard brick your phone. So flashing US unlocked onto a US carrier device should work."
To expand a bit on what @mweinbach*just said, @me2151*did some more testing, and he was able to successfully carrier switch from a 950U to 950W using Comsey ODIN. So it looks like Comsey ODIN is not patched as we originally thought. Not sure exactly what caused the tester's phone to brick, but it HARD BRICKED and had to be RMA'd at his expense. So we jumped on the forums here to warn others until more testing could be done. @mweinbach*wrote the article and @xdanilvaand I began posting here.*
We may have overreacted, but wanted to err on the side of caution to protect people from hard bricks.*
The Blv3 factory binary has not been tested, so still unsure if/how we will be able to use it, or if it will cause issues.*
For now, carry on as usual, but understand we still don't know the full implications of the Blv3 patches. One person has already HARD BRICKED, and @me2151*almost hard bricked testing all of this for us.
There is currently a group working on a fix for bricked devices, but for now consider it a hard brick. Don't chance it.
Is Oreo for the S8/S8+ a Blv3 firmware or is it BLV2?
just curious as I flashed my Verizon branded GS8 to U1 firmware to take the Oreo beta..
So If I own a Sm-G950U1 but I have been running G950U Tmobile Oreo beta and upgrade to the stable oreo I'll brick my phone? In order to prevent this I'll have to first go back to G950U1 on nouget and then go up to oreo?
I don't really want to do this because I am loving using the T-Mobile variant because it gives me multiuser (digits) since it's built in.
Does the same apply to exynos devoces?
As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.
ironbesterer said:
As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.
Click to expand...
Click to collapse
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?
vimerate said:
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?
Click to expand...
Click to collapse
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.
ironbesterer said:
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.
Click to expand...
Click to collapse
My question is I have an ATT unlocked device on Cricket Wireless running the oreo beta since I flashed it to unlocked firmware. Should I revert back to Nougat before the final oreo build or just stick with it?
Mr. Orange 645 said:
If your currently are running U1 firmware on a U device, vice versa, or running W firmware on a U or U1 device, or vice versa, you need to flash back to the firmware version that shipped with your device BEFORE you accept any OTAs that take you up to Blv3.
Click to expand...
Click to collapse
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?
raduque said:
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?
Click to expand...
Click to collapse
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.
Mr. Orange 645 said:
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.
Click to expand...
Click to collapse
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?
raduque said:
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?
Click to expand...
Click to collapse
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.
Mr. Orange 645 said:
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.
Click to expand...
Click to collapse
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?
raduque said:
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?
Click to expand...
Click to collapse
No on a U1. They tried to carrier switch on either a U or a W.
Ok... so they tried to go from a device running a Carrier fw on blv3 to... what? A carrier fw on blv2?
I know this is still early, but the more questions and answers I see, the more confused I am.
Do we know if all of these scenarios will have the same result?
a) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. A BLv3 OTA will brick the device. True/false/not yet known?
b) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. Assuming a) is FALSE. Device will operate as normal U1 phone, but I will never be able to put 950U carrier branded software on it (via modded Prince Comsy), because that will brick it. True/false/not yet known?
c) I have a AT&T (950U) branded device. I flashed it to become TMobile (950U) device. It now get updates via Tmobile. Future OTAs will continue as normal and I can even use Odin to flash other carrier software (950U), but I can NEVER use modded Odin to flash unlocked software (950U1)? True/false/not yet known.
Based on what I've read right so far. It seems that the answers all remain theoretical, thus not yet known, but based on the Note8 update, the answers would be a) False. b) True. c) True.
Am I far off base???
The thing right now that I understand the least is the scenario a). I don't understand why if I have a phone that was 950U but is now 950U1, why it would get bricked. I do understand that attempts to change it once BLv3 hit are currently DOA, but that's different than simply keeping your phone in the stream that it is currently.
There are some good questions in this thread, I realize that its an evolving situation... So I have to ask directly... I have a Verizon branded 950U that I followed https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817 to switch to XAA and flash the U1 firmware, and I have taken part in the Oreo beta.
Currently my phone has Baseband Version G950U1UEU2ZRA8. There is an OTA update pending right now that is G950U1EUE2ZRAE/G950U1OYM2ZRAE/G950U1UEU2ZRAE. From what I understand, and what I am reading about this BLV2 vs BLV3 issue, based on the numbers in this, if I take this update, I'll still be BlV2, and be ok? If I should want to return to stock Verizon firmware, I can still do it safely?
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?
KidJoe said:
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?
Click to expand...
Click to collapse
I am basically the same as you except AT&T beginning rather than Verizon. I currently have the ZRAE Oreo beta software running on my phone. Based on everything said so far, there is no danger yet in downloading that OTA because it is still BLv2. The danger would be if the final Oreo version drops with BLv3 and you apply it. Then we're left with these different scenarios that are still being figured out.
Absent any concrete info, I'm going to just avoid the Jan security patch on my Note8.
If I have to flash back the Verizon software to have a non-brick device, well I'll just sell this thing and buy a cheap unlocked phone with microsd, wireless charging and a nice screen.
So, this has probably been answered before, but I am honestly too busy (also lazy due to the extreme workload of my professional life) to search through thousands of threads for the answer to my issue.
I got a SM-G955U that was originally used on the sprint network from a guy on Craigslist (Mistake number 1). I immediately performed the carrier switch tasks to change it to a SM-G955U1. The firmware change was easy as pie, and the device runs smooth as butter right now. The issue I ran into is that it is telling me that I have to contact sprint to unlock the device. I am sitting here going, "Wait, what?"
So, I may have overlooked some details when I flashed the firmware. I am going to try reinstalling the firmware for XAA without using the Home_CSC file while I wait on replies to see if I can solve this issue with some tinkering. I am extremely tech savvy and I ha e been rooting devices and changing firmware files for a long time now, and I have been involved in a lot of development projects.
Anyway, my question is this: How do I go about removing the Sprint OMADM protocols. I assumed that flashing the firmware to the XAA firmware would have handled that, and as I said before, I either overlooked something simple when I flashed it over the first time, or there is something I missed all together.
I cant really go to Sprint about it since I am not a Sprint subscriber, and I dont know who to co tact at Sprint about this. Also, if the guy I got it from defaulted on his bill, then the device is probably black listed by them and they wouldn't unlock it for me anyway. Yeah, I know, this is stuff I should have looked into before I bought this damn thing (Mistake #2).
These are the details of the device just in case somebody has a solution:
S/N: R28J42MCXBT
IMEI:Removed for your saftey by @TheMadScientist
Brand: SPRINT (I don't know why considering I flashed the SM-G955U1 XAA firmware to it, and the SIM was not installed during this process).
Baseband: G955U1UES3CRE2
Kernel: 4.4.78-13001792
[email protected] #1
Fri May 4 11:57:40 KST 2018
Build number: R16NW.G955U1UES3CRE2
Android Security Patch Level: May 1, 2018
Android Version: 8.0.0
Any answers would be greatly appreciated since I have been tinkering with this thing on and off for about a month now.
Darkstar-Actual said:
So, this has probably been answered before, but I am honestly too busy (also lazy due to the extreme workload of my professional life) to search through thousands of threads for the answer to my issue.
I got a SM-G955U that was originally used on the sprint network from a guy on Craigslist (Mistake number 1). I immediately performed the carrier switch tasks to change it to a SM-G955U1. The firmware change was easy as pie, and the device runs smooth as butter right now. The issue I ran into is that it is telling me that I have to contact sprint to unlock the device. I am sitting here going, "Wait, what?"
So, I may have overlooked some details when I flashed the firmware. I am going to try reinstalling the firmware for XAA without using the Home_CSC file while I wait on replies to see if I can solve this issue with some tinkering. I am extremely tech savvy and I ha e been rooting devices and changing firmware files for a long time now, and I have been involved in a lot of development projects.
Anyway, my question is this: How do I go about removing the Sprint OMADM protocols. I assumed that flashing the firmware to the XAA firmware would have handled that, and as I said before, I either overlooked something simple when I flashed it over the first time, or there is something I missed all together.
I cant really go to Sprint about it since I am not a Sprint subscriber, and I dont know who to co tact at Sprint about this. Also, if the guy I got it from defaulted on his bill, then the device is probably black listed by them and they wouldn't unlock it for me anyway. Yeah, I know, this is stuff I should have looked into before I bought this damn thing (Mistake #2).
These are the details of the device just in case somebody has a solution:
S/N: R28J42MCXBT
IMEI:Removed for your saftey by @TheMadScientist
Brand: SPRINT (I don't know why considering I flashed the SM-G955U1 XAA firmware to it, and the SIM was not installed during this process).
Baseband: G955U1UES3CRE2
Kernel: 4.4.78-13001792
[email protected] #1
Fri May 4 11:57:40 KST 2018
Build number: R16NW.G955U1UES3CRE2
Android Security Patch Level: May 1, 2018
Android Version: 8.0.0
Any answers would be greatly appreciated since I have been tinkering with this thing on and off for about a month now.
Click to expand...
Click to collapse
More than likely a paid unlock service as the device is carrier locked and no feasible methods really that I know of....
TheMadScientist said:
More than likely a paid unlock service as the device is carrier locked and no feasible methods really that I know of....
Click to expand...
Click to collapse
That's what I was afraid of. I figured it would end up being something like that. You would think there would be a way to accomplish it simply with some reprogramming.
You know, I might have an idea...its risky, but if I refreshed the XAA firmware with Prince Comsey's Odin and performed a Nand Erase, could that potentially wipe out all of Sprint's programming? Or would that wipe out the factory recovery and brick the device? I know it is an overkill solution, but if it's possible for that method to work then I may have a go at it. I just figure that there HAS to be a way to wipe literally everything from the device and start with a new install from scratch.
Darkstar-Actual said:
That's what I was afraid of. I figured it would end up being something like that. You would think there would be a way to accomplish it simply with some reprogramming.
Click to expand...
Click to collapse
Prob not. On older lgs models we used to get into the lot hidden menu and switch it to lab mode. But I'm pretty sure sprint blocked all the good stuff
TheMadScientist said:
Prob not. On older lgs models we used to get into the lot hidden menu and switch it to lab mode. But I'm pretty sure sprint blocked all the good stuff
Click to expand...
Click to collapse
Ahhh yes, the good old days. I remember the days of being able to simply root a device and having multi carrier functionality. More than that, I remember how easy it used to be to root and install custom bootloaders.
Coincidentally, I always thought it would be awesome to run some variant of CyanogenMod OSs on devices like the GS8+.
Well, theoretically, could I just root the Sprint S8+ on the unlocked firmware and just modify the build.prop file to ignore all things sprint?
Darkstar-Actual said:
Ahhh yes, the good old days. I remember the days of being able to simply root a device and having multi carrier functionality. More than that, I remember how easy it used to be to root and install custom bootloaders.
Coincidentally, I always thought it would be awesome to run some variant of CyanogenMod OSs on devices like the GS8+.
Well, theoretically, could I just root the Sprint S8+ on the unlocked firmware and just modify the build.prop file to ignore all things sprint?
Click to expand...
Click to collapse
the unlocked firm should be free of any sprint stuff...If its not than the 3 part csc isnt setup right
XAX/XAX/XAX or xaa or something like that
if device code shows a spr anywhere then its still trying to default to sprin software
TheMadScientist said:
the unlocked firm should be free of any sprint stuff...If its not than the 3 part csc isnt setup right
XAX/XAX/XAX or xaa or something like that
if device code shows a spr anywhere then its still trying to default to sprin software
Click to expand...
Click to collapse
Okay. So it looks like I missed something. When I flashed it initially, I was on severe lack of sleep due to being severely understaffed at work (we still are, and I have been pulling doubles for over a month now), and I bet I used the Home_CSC instead of using a clean CSC file.
So, to correct this, I will have to flash the ENGboot again, then flash the XAA firmware over to the device again, and set up Comsey's Odin for a clean install instead of copying and applying Home_CSC. Is this correct? Or, because I already have the "unlocked" firmware, I should be able to just do a clean flash of the stock G955U1 software? I just wanna make sure I dont wipe and repeat what I did the first time.
Hi guys. This is my very first post here. I searched all over the internet for my problem but nothing. But it seemed that similar questions redirected me to this forum and that's why I decided to join.
So, all started this morning, when the colors of my Galaxy S7 Edge became faded, it was more noticeable on the black color. I tried to find a solution online and they suggested doing something under Developer Tools. The next problem and my big big mistake, was that I unchecked and rechecked something, that after restarting my phone, wouldn't let me enter, showing a text "Custom binary blocked by FRP Lock". I searched for a solution and I saw that the only way was to install a new firmware.
I always thought my phone was SM-G935FD, because that is what it read on the "About device", but at the download screen it showed SM-G935W8. So I downloaded a firmware for the SM-G935W8. This is what it says also on the back of my phone, i noticed it just some minutes ago. So I went and I searched for W8 firmwares. I got the 6.0.1 from Canada and Bell carrier if I am not mistaken. I did the instalĺ. It started well, but after some updates it went from 6, to android 7 and it blocked my actual carrier. I can't make any phone calls.
Now I don't know what to do. I live in Albania and I purchased the phone here, it was a used one. I think at some point the phone was rooted because I had some very strange apps that has to do with rooting apparently (I never rooted a phone and I don't know much).
I want to know if there is a way to have an unlocked firmware. I don't even know what carrier was the phone on the first place.
Edi1994 said:
Hi guys. This is my very first post here. I searched all over the internet for my problem but nothing. But it seemed that similar questions redirected me to this forum and that's why I decided to join.
So, all started this morning, when the colors of my Galaxy S7 Edge became faded, it was more noticeable on the black color. I tried to find a solution online and they suggested doing something under Developer Tools. The next problem and my big big mistake, was that I unchecked and rechecked something, that after restarting my phone, wouldn't let me enter, showing a text "Custom binary blocked by FRP Lock". I searched for a solution and I saw that the only way was to install a new firmware.
I always thought my phone was SM-G935FD, because that is what it read on the "About device", but at the download screen it showed SM-G935W8. So I downloaded a firmware for the SM-G935W8. This is what it says also on the back of my phone, i noticed it just some minutes ago. So I went and I searched for W8 firmwares. I got the 6.0.1 from Canada and Bell carrier if I am not mistaken. I did the instalĺ. It started well, but after some updates it went from 6, to android 7 and it blocked my actual carrier. I can't make any phone calls.
Now I don't know what to do. I live in Albania and I purchased the phone here, it was a used one. I think at some point the phone was rooted because I had some very strange apps that has to do with rooting apparently (I never rooted a phone and I don't know much).
I want to know if there is a way to have an unlocked firmware. I don't even know what carrier was the phone on the first place.
Click to expand...
Click to collapse
Try flashing the SM G935FD, it probably had the G935FD firmware flashed on it so that it would work in your region, flashing G935FD again might make it work again.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try flashing the SM G935FD, it probably had the G935FD firmware flashed on it so that it would work in your region, flashing G935FD again might make it work again.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Okay but, which version of FD? Because I search it and I see versions for countries like Vietnam, Thailand, Nigeria etc etc, and I am not sure if it will be a locked version again.
Edi1994 said:
Okay but, which version of FD? Because I search it and I see versions for countries like Vietnam, Thailand, Nigeria etc etc, and I am not sure if it will be a locked version again.
Click to expand...
Click to collapse
If it was rooted before, it was probably rooted so that some things could be modified to make it work in your country.
You said you flashed an android 6 firmware then you did an OTA update to android 7. That might be a problem because it might not be able to root again in order to make the modifications that were originally done to make it work in your country.
Here is a link to all the Russian firmware for SM G935FD, try the 6.0 firmware, try the various 6.0 firmwares and see if any of them work. After flashing the 6.0 firmware, if you get a notification saying there is an update available, DO NOT ACCEPT IT, keep the 6.0 android version. You will probably still be blocked by FRP, according to XDA rules, we can't help you bypass FRP, you'll have to figure that out yourself.
https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935FD/SER/
Once you get FRP straightened out, do some searches for:
"How to root SM G935FD"
Then you can work on getting it configured to work in your region on your carrier. Sometimes this involves flashing a separate modem(radio) file that has been extracted from a different firmware in order to make your radio work with your specific carrier. You might be in for more than you bargained for. I don't know which specific modifications you'll need or what files you'll need to make it work in your region, im just trying to give you an idea of what you need to look into.
You can try some of the Russian android forums, someone there might know how to make the device work in Albania. You might want to ask around in those forums first before you try anything, that way you won't waste time trying things that might not work. It will save you time if they know where you need to start and what you need.
Sent from my LGL84VL using Tapatalk
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
ecc25 said:
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
Click to expand...
Click to collapse
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
cooltt said:
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
Click to expand...
Click to collapse
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
ecc25 said:
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
Click to expand...
Click to collapse
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
cooltt said:
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
Click to expand...
Click to collapse
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
ecc25 said:
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
Click to expand...
Click to collapse
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
cooltt said:
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
Click to expand...
Click to collapse
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
ecc25 said:
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
cooltt said:
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
Click to expand...
Click to collapse
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
ecc25 said:
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
Click to expand...
Click to collapse
Well you could flash G930U which opens up all of the radios for the US and you may have less issues but US and European devices have different chips so your never going to be able to flash any EU generic firmware. I'm addition the US and Europe are different cellular regions with different operating frequencies. You can get by with what you have but never get full functionality.
I think you were just unlucky with this phone on ebay, there are plenty which are genuine EU region devices.