I'm in Australia and want to change the CSC from OPS to TEL. I'm aware that the phone has a multi CSC and it seems the only way to change the CSC is with root. I've tried other methods and none seem to work.
With root, is it a simple matter to change the CSC? Is there a guide for changing it somewhere?
I'm curious about this myself. The store I got mine from sold me the wrong version (which I didn't know until I opened it since there was no way for me to tell on the outside, so they won't let me return it), and I really hate the boot screen from a carrier that isn't mine. More importantly, I can't use tethering, which I assume is because of the CSC, though despite my SIM card, the CSC is still set to the original carrier.
I read something about a different carrier's SIM card switching the CSC upon reboot, or using a USSD code to choose which carrier you're on for the multi-CSC, but those didn't work. I also tried flashing my carrier's CSC (though I used Home_CSC so my data wasn't deleted), even though I knew it would likely be fruitless because of the multi-CSC... and it was.
I'm really puzzled because I just want to change over to my carrier, and since the store won't let me exchange it, I'm not sure what to do. I saw a recommendation to ask Samsung. Maybe they could help. I don't know. I just want a solution for this too.
TankedThomas said:
I'm curious about this myself. The store I got mine from sold me the wrong version (which I didn't know until I opened it since there was no way for me to tell on the outside, so they won't let me return it), and I really hate the boot screen from a carrier that isn't mine. More importantly, I can't use tethering, which I assume is because of the CSC, though despite my SIM card, the CSC is still set to the original carrier.
I read something about a different carrier's SIM card switching the CSC upon reboot, or using a USSD code to choose which carrier you're on for the multi-CSC, but those didn't work. I also tried flashing my carrier's CSC (though I used Home_CSC so my data wasn't deleted), even though I knew it would likely be fruitless because of the multi-CSC... and it was.
I'm really puzzled because I just want to change over to my carrier, and since the store won't let me exchange it, I'm not sure what to do. I saw a recommendation to ask Samsung. Maybe they could help. I don't know. I just want a solution for this too.
Click to expand...
Click to collapse
I'm on the same boat. Wondering if you've figured out a way. ?
Sent from my HUAWEI LYA-L0C using XDA Labs
I've changed the CSC on my S7 without needing to root the device. I think the process should be the same for the Note 9, though I'm not really familiar with multi-CSC. You'll need a Windows computer.
Get the firmware with the CSC you want from SamMobile or Updato (TEL, XSA etc.)
Get the latest ODIN version from XDA
Unzip your firmware so you've got the various files (AP, BL, CSC etc.)
Put the phone into download mode (https://www.youtube.com/watch?v=DkdEcMGFvzY) Don't worry if it takes a couple of tries
Start ODIN and make sure the phone is connected and appearing in ODIN
Add the various firmware files to the corresponding boxes in ODIN. When you come to the CSC one, add that file that starts CSC. NOT the HOME_CSC one.
Run the flash in ODIN
Wait for the flash to complete and the phone to reboot. Both the flash and the reboot will take several minutes, go get yourself a coffee.
Process now complete, you can delete the firmware files from your PC.
This worked on my S7 and the phone was able to take an OTA afterwards.
A couple of notes though.
I have not tried this on a Note 9, but I believe the process should be the same.
This will wipe your phone, so backup first.
You must flash a firmware from the same model. You cannot flash a N960F firmware onto a N9600. They have different hardware.
While you'll only need to do this process once, think carefully about if you need to and what you'll get out of it (Samsung Pay, VoLTE, RCS). If these are features you don't use it's probably not worth the hassle.
Done correctly this won't trip Knox as you're using Samsung signed firmware.
If you give this a go, report back with your experiences.
Thanks but that won't work on the Note 9 now that Samsung has started using a "multi" CSC. I tried lots of methods including the one you have posted. The only method that works on Samsung phones using the multi CSC is this one:
https://forum.xda-developers.com/ga...de-how-to-change-s9-s9-csc-model-csc-t3870836
I used this method on my Note 9 yesterday and it worked. Finally after 2 months I've been able to change the CSC.
I think that they started using the multi CSC from the S8 forward.
Dang. Looks like I have some reading to do to get my head around these multi CSC devices.
Sea-Wolf said:
Dang. Looks like I have some reading to do to get my head around these multi CSC devices.
Click to expand...
Click to collapse
It's a heavy handed approach by Samsung. I even tried to get an authorised Samsung service center to do it for me. I was willing to pay them. They told me that Samsung won't allow them to change the CSC. So if you want to switch service providers, in my case from Optus to Telstra, you can't change the CSC. Without the correct CSC VoLTE and VoWifi won't work.
Thankfully I found the method that I've linked and it works.
appro77 said:
Thankfully I found the method that I've linked and it works.
Click to expand...
Click to collapse
When you followed that method, did you need to do the first step? I'm not sure what he means there but I think he's saying to flash the multi CSC with ODIN first.
Sea-Wolf said:
When you followed that method, did you need to do the first step? I'm not sure what he means there but I think he's saying to flash the multi CSC with ODIN first.
Click to expand...
Click to collapse
The first step is referring to the "Combination Rom". It's a special rom that is used by engineers ( I suppose) to do high level work on the phone. It's not a normal rom. You can't install apps on it etc. It opens to a screen with lots of settings that you don't have to touch. Once the Combination Rom file is flashed with Odin, the phone will reboot into the rom.
Then you do the steps using RealTerm, and then you flash the rom for your phone after rebooting into download mode again and use Odin.
Obviously the CSC file of the rom you flash must contain the CSC that you have nominated when you change the CSC using Realterm in the previous step.
Ah ok, thanks for the info.
mrnovanova said:
I'm on the same boat. Wondering if you've figured out a way.
Sent from my HUAWEI LYA-L0C using XDA Labs
Click to expand...
Click to collapse
Short of rooting or getting it exchanged, not yet. Samsung has been telling me for a month that they'll get it sorted for me but their customer service sucks assssssss.
More info below, if you're interested.
Sea-Wolf said:
I've changed the CSC on my S7 without needing to root the device. I think the process should be the same for the Note 9, though I'm not really familiar with multi-CSC. You'll need a Windows computer.
Get the firmware with the CSC you want from SamMobile or Updato (TEL, XSA etc.)
Get the latest ODIN version from XDA
Unzip your firmware so you've got the various files (AP, BL, CSC etc.)
Put the phone into download mode (https://www.youtube.com/watch?v=DkdEcMGFvzY) Don't worry if it takes a couple of tries
Start ODIN and make sure the phone is connected and appearing in ODIN
Add the various firmware files to the corresponding boxes in ODIN. When you come to the CSC one, add that file that starts CSC. NOT the HOME_CSC one.
Run the flash in ODIN
Wait for the flash to complete and the phone to reboot. Both the flash and the reboot will take several minutes, go get yourself a coffee.
Process now complete, you can delete the firmware files from your PC.
This worked on my S7 and the phone was able to take an OTA afterwards.
A couple of notes though.
I have not tried this on a Note 9, but I believe the process should be the same.
This will wipe your phone, so backup first.
You must flash a firmware from the same model. You cannot flash a N960F firmware onto a N9600. They have different hardware.
While you'll only need to do this process once, think carefully about if you need to and what you'll get out of it (Samsung Pay, VoLTE, RCS). If these are features you don't use it's probably not worth the hassle.
Done correctly this won't trip Knox as you're using Samsung signed firmware.
If you give this a go, report back with your experiences.
Click to expand...
Click to collapse
That doesn't work, unfortunately. I've changed the CSC on an S7 with no issue, but the Note 9 is a whole other beast. No matter how many times you do a complete flash and deep format/NAND erase etc., it won't work. Not really sure how or why. What's annoying is that it seems the N960F models (or, at least, some of them) won't switch CSCs depending on the installed SIM card. If they did, I wouldn't have an issue.
I will add that you definitely need Windows though. Odin on Mac just never seems to work for me. Odin in Windows via Parallels works okay (i.e. sometimes it works, sometimes it doesn't, but it should work more often than not - if it doesn't, set it up via BootCamp first and then it should run fine in Parallels).
appro77 said:
Thanks but that won't work on the Note 9 now that Samsung has started using a "multi" CSC. I tried lots of methods including the one you have posted. The only method that works on Samsung phones using the multi CSC is this one:
https://forum.xda-developers.com/ga...de-how-to-change-s9-s9-csc-model-csc-t3870836
I used this method on my Note 9 yesterday and it worked. Finally after 2 months I've been able to change the CSC.
I think that they started using the multi CSC from the S8 forward.
Click to expand...
Click to collapse
I believe it got more egregious with the S9 and Note 9 though, but I could be wrong. Thanks for the link though, I'm going to give it a try tonight. Here's hoping...
appro77 said:
It's a heavy handed approach by Samsung. I even tried to get an authorised Samsung service center to do it for me. I was willing to pay them. They told me that Samsung won't allow them to change the CSC. So if you want to switch service providers, in my case from Optus to Telstra, you can't change the CSC. Without the correct CSC VoLTE and VoWifi won't work.
Thankfully I found the method that I've linked and it works.
Click to expand...
Click to collapse
Yeah, I can't stand it personally.
As I mentioned earlier, Samsung actually said they'll sort it out for me and replace it, but that's because the retailer I bought it from misled me and sold me the wrong version of the Note 9 (different carrier to what I asked for; they said they were all the same, and I had my father pick it up for me because I was busy so I didn't have the chance to tell them how wrong that is unless it's carrier-unbranded, which wasn't what they were advertising anyway).
I suppose you could always try weaving a tall tale or exaggerating the issue to get Samsung to cooperate with you. It's worth a shot. Just be aware that they're slow as balls to do anything.
I talked to them on their live chat about a month ago and went through a whole process which amounted to nothing, then emailed them about it and they said they would sort it out and they escalated it... and now a month later, I got back on their live chat (Wednesday this week, in fact), and they apologised for not getting it sorted sooner and that they'd sort it out that day and email me back etc. It's Friday night here and still nothing so I'll get in touch with them again if I haven't heard from them by Wednesday next week (and if the above method doesn't work for me).
appro77 said:
The first step is referring to the "Combination Rom". It's a special rom that is used by engineers ( I suppose) to do high level work on the phone. It's not a normal rom. You can't install apps on it etc. It opens to a screen with lots of settings that you don't have to touch. Once the Combination Rom file is flashed with Odin, the phone will reboot into the rom.
Then you do the steps using RealTerm, and then you flash the rom for your phone after rebooting into download mode again and use Odin.
Obviously the CSC file of the rom you flash must contain the CSC that you have nominated when you change the CSC using Realterm in the previous step.
Click to expand...
Click to collapse
The issue with this is getting a combination file compatible with your boot loader. The free ones that are available without paying dodgy Chinese websites didn't work for me (I got ONE of them to run but it wasn't happy about it, and it still wouldn't work, but I could try that process you mentioned with it and see for sure). And as for getting the right combination file even if you're willing to pay for it (which I'd be okay with since the price is low, but I'm not sure if I trust those sites enough to go ahead with it), figuring out which version one needs is a bit confusing, especially for an Android novice like myself.
TankedThomas said:
Short of rooting or getting it exchanged, not yet. Samsung has been telling me for a month that they'll get it sorted for me but their customer service sucks assssssss.
More info below, if you're interested.
Click to expand...
Click to collapse
Oh. Thanks for replying. I was able to change. My CSC using the *#272 trick without issues. Worked like a charm. ?
Sent from my Samsung SM-N960W using XDA Labs
mrnovanova said:
Oh. Thanks for replying. I was able to change. My CSC using the *#272 trick without issues. Worked like a charm.
Sent from my Samsung SM-N960W using XDA Labs
Click to expand...
Click to collapse
Really? On a N960F? Were you running the latest update? That's never worked for me. Just tells me the USSD code is invalid...
And unfortunately, so far, the other method doesn't work for me either: https://forum.xda-developers.com/showpost.php?p=78425738&postcount=38
If only I could get my phone to connected properly to RealTerm, it should work fine... but it won't connect. Dammit...
EDIT: Seems the solution is to keep retrying (and restarting) your PC and phone until it works. Or something like that. I posted an update in the aforementioned thread, and now it works for me. Now I have XNZ/XNZ/TNZ (not super-happy about it remembering it was originally TNZ but it's not like I can change that without getting an entirely new device, or rooting it, anyway, and it doesn't affect anything negatively). The USSD code solution still doesn't work for me though, so there's that.
Related
Hello Everyone,
Today we'll be unlocking the Samsung Galaxy SM-G920T 5.1.1 using the Z3X Samsung Tool or Octopus Box Samsung, which both required you to root your Galaxy S6 SM-G920T. I will guide throughout the steps to root your phone without tripping the knox counter, which will allow us to use one of the programs above. We will use the (sboot.bin) which allows their service centers to do flashing and repairs to the device without tripping the Knox counter. The modified bootloader also disables write protection on the device. Once you are done rooting and unlocking the Galaxy S6 SM-G920T, we will restore the official firmware 5.1.1. Don't worry, your phone is unlock permanently regardless of the times you restore the phone.
The steps to root your Samsung Galaxy SM-G920T 5.1.1
1. Install Samsung USB Drivers
2. Put the phone in download mode by: Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.
3. Plug phone in and wait for drivers to install if necessary.
4. Download Odin
5. Download sboot.bin for Galaxy S6
6. Open odin and then you should now see phone’s modem port highlighted in blue.
7. Click on BL tab and select the correct sboot.bin that you downloaded above. Then click start.
8. When phone comes back on, power it off again and put into download mode.
9. Download UniBase_BOG8_v2
10. Open odin again and this time select AP tab and select UniBase_BOG_V2 file and click start.
11. You're Done!!!
When the phone turn on, it will be rooted. To verify that knox has not been tripped go back to download mode and it should still say KNOX WARRANTY: 0 (0X0000). Now you can go ahead and unlock your Samsung Galaxy SM-G920T 5.1.1 using the Z3X Samsung Tool or Octopus Box Samsung. The sboot.bin isn’t playing very well, causing issues with Calls and Fingerprint sensor, but it is only for the meantime until you restore your phone back to the stock firmware.
Restoring your Samsung Galaxy SM-G920T to the stock firmware 5.1.1
1. Download the SM-G920T stock firmware
2. Open and extract the firmware file, then you should get the a file in .tar.md5 format.
3. Put the phone in download mode by: Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.
4. Open odin and then you should now see phone’s modem port highlighted in blue.
5. Click the AP button tab and select G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
6. Make sure Re-partition checkbox is NOT selected, under the Options tab. Click start and wait for it to finish completely.
7. Enjoy!!! The G920TUVU2COF6 Android 5.1.1 firmware on your Galaxy SM-G920T.
I hope this guide helps everyone who wants to unlock their Samsung Galaxy SM-G920T, but needs their phone rooted first temporarily.
Will this work if I'm on the G920TUVU2COF8 build?
It may work!
yoderz said:
Will this work if I'm on the G920TUVU2COF8 build?
Click to expand...
Click to collapse
I'm sure it works on the G920TUVU2COF8 build, but I'm not 100% sure. If anything, you can always go restore your phone through odin.
Any chance we could get links to the files you reference? Thank you in advance.
ron.cabanillas said:
I'm sure it works on the G920TUVU2COF8 build, but I'm not 100% sure. If anything, you can always go restore your phone through odin.
Click to expand...
Click to collapse
Can confirm it works. Went my own route on some things but Knox is 0 and SuperSU and TWRP are installed and working
Use the Search Engines!
LPoirierIV said:
Any chance we could get links to the files you reference? Thank you in advance.
Click to expand...
Click to collapse
I can't post the file links here, I would recommend you to use the search engine such as: Google, Bing, Yahoo and others to find the files you need. The files will be in the first two pages of the search engines.
Anyone with some credibility willing to try this? Or have tried it... No offense but the two people that posted have a combined 7 posts...
Sent from my SM-G920T using Tapatalk
So at the end of the step I'll end with stock of6 with root?
Will this deleted my saved data and apps?
I found this site if with links if anyone wants to try it out.
I haven't tried it myself so as always at your own risk.
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
ron.cabanillas said:
I can't post the file links here, I would recommend you to use the search engine such as: Google, Bing, Yahoo and others to find the files you need. The files will be in the first two pages of the search engines.
Click to expand...
Click to collapse
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
LPoirierIV said:
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
Click to expand...
Click to collapse
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
noodlev1 said:
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
Click to expand...
Click to collapse
I honestly forget which baseband I was on. I spent all day flashing different builds to try to get the sim unlock to stick. I'm currently on COF9 on a metro pcs rom for the sm-g920t1 in hopes that I can receive a working unlock code. (Metro PCS rom is the only way to enter an unlock code apparently.)
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
It should work without problems
noodlev1 said:
I found this site if with links if anyone wants to try it out.
I haven't tried it myself so as always at your own risk.
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
Click to expand...
Click to collapse
These link should work fine with your galaxy s6 SM-G920t
You have to Root, unlock and restore
LPoirierIV said:
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
Click to expand...
Click to collapse
The Steps are easy, You must root the phone, unlock using Z3X Samsung Tool or Octopus Box Samsung and then restore the phone back to the stock firmware. Regardless of how many times you restore or update, your phone will always be unlock.
It should work fine
noodlev1 said:
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
Click to expand...
Click to collapse
Regardless of the firmware COF8 or COF6, you must have the full stock firmware to restore your phone after it rooted and unlocked.
I can't post the link Yet!
mrvirginia said:
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: this seems to be a much better guide
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
edit: and here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
Click to expand...
Click to collapse
I more than glad to post the link, I don't have any problems. The forum rules don't allow me yet to post the links. The guide you found have the link everyone needs too.
It should work Too!
LPoirierIV said:
I honestly forget which baseband I was on. I spent all day flashing different builds to try to get the sim unlock to stick. I'm currently on COF9 on a metro pcs rom for the sm-g920t1 in hopes that I can receive a working unlock code. (Metro PCS rom is the only way to enter an unlock code apparently.)
Click to expand...
Click to collapse
The latest Tmobile is COF8, regardless COF8 or COF6 build you can unlock it. The Steps are easy, You must root the phone, unlock using Z3X Samsung Tool or Octopus Box Samsung and then restore the phone back to the stock firmware. Regardless of how many times you restore or update, your phone will always be unlock. Now you can also flash to metro pcs, but you have to stay with the metro pcs after you unlock it with the code.
mrvirginia said:
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
Click to expand...
Click to collapse
True i posted there a compilation to root without triping knox and on cof8. Must be on page 24 i think. And the md5 of sboot number to compare from ones in google
rooted but issues
both methods worked for my phone. got my phone rooter and unlocked. but i keep getting security threat warning if i stay rooted
hi
i need to download at&t latest stock firmware to flash it on my note5 as i soft bricked it.
where can i find it?
nothing on sam mobile ..
please help
please help
Unfortunately, the only way to get firmware for att devices is usually from att Ota updates... rarely does it get posted on sammobile.
You may need to take the phone to att and see if they can reflash it. I was on att for many years and I recently left their service because of this issue and their cost.
dandroid7 said:
Unfortunately, the only way to get firmware for att devices is usually from att Ota updates... rarely does it get posted on sammobile.
You may need to take the phone to att and see if they can reflash it. I was on att for many years and I recently left their service because of this issue and their cost.
Click to expand...
Click to collapse
This is false, you can pull it yourself using the Samsung new kies tool(or whatever it's called). Look up the instructions, but be warned it will factory wipe your phone.
Sent from my SM-N920V using Tapatalk
I was not able to do so on my previous note 3 or my note 8... both were att. Maybe I did something wrong, but it never worked for me when I tried it.
If my info is incorrect on this, my apologies.
Give it a try and see if it works.
oh.. didn't know it is so complicated .. i always used no phones from carrier .
all i want to do is download tar file and flash it through odin..
i hate kies and otas...
I found att phones to be a pain in the butt... that was one of the biggest reasons I went to tmobile... because I like to root.
Att is terrible at providing updates, their Ota process is stupid - why can't their updates also be available online for download? the locked bootloaders totally Rob you of the joys of android.
Good riddance att!
AT&T released 5.1.1 a couple of weeks ago, and I still haven't gotten a notification on my phone that the OTA update is ready to be installed. I check manually every day, too, but every time it says that the "update was interrupted" and I have to wait 24 hours. Is that because the server is busy and I'll just have to wait patiently as the update is being rolled out to AT&T phones over the air? (Yes, I know I can simply move the date forward one day and try again manually, but I don't want to inadvertently mess up the automatic OTA checks.)
I would really like to install 5.1.1 on my S6. Is there a way to speed things up? Is there an official AT&T image I can install through Kies or some other way?
Thanks!
--Ron
Make sure you have at least 4GB of storage free when you try the update. I have heard of this sort of thing happening if you don't have enough free space.
I had read that, too, but I have a 64 GB S6, with some 30 GB free, so that's not an issue.
Same here
i'm not sure why i'm not getting the update...i have an unlocked galaxy S6 at&t version.
i'm living outside the US so i'm using another sim card. Is that the problem?
I also have an unlocked AT&T S6, but I live in the U.S., so that shouldn't be an issue either.
--Ron
I know the feeling. I have been checking daily too and finally got it late last night.
Does root effect updating from SmartSwitch?
Still nothing (10/13). Is anyone else seeing the same thing? Should it really take weeks and weeks before we get this update after it's been officially released?
--Ron
Dude just flash the damn thing using odin and be at peace
How?
timde9 said:
Dude just flash the damn thing using odin and be at peace
Click to expand...
Click to collapse
how I do? I download the correct file, I followed all the steps and do not work for me. I get FAIL in Odin. If someone could help me, please
Is there an *official*, AT&T-sanctioned image that I can use? Will this trip Knox?
--Ron
Is it the one in this thread: http://forum.xda-developers.com/att-galaxy-s6/general/stock-odin-tar-files-g920aucu3boi2-t3213306
--Ron
Don't know what to tell you other than the basics.. The correct file is available in the android developnent portion of this forum.. Download make sure you put all four files in proper slots in odin and hit start.. Should wipe everything and complete unless you using the wrong model of s6 or the wrong files in the slots.. Honestly nothing is worth losing root though in my opinion.. I only want 5.1.1 so I can use. Xposed but without the ability to root the update is meaningless to me and really more of a regression to me.. But no it won't trip knox
timde9 said:
Don't know what to tell you other than the basics.. The correct file is available in the android developnent portion of this forum.. Download make sure you put all four files in proper slots in odin and hit start.. Should wipe everything and complete unless you using the wrong model of s6 or the wrong files in the slots.. Honestly nothing is worth losing root though in my opinion.. I only want 5.1.1 so I can use. Xposed but without the ability to root the update is meaningless to me and really more of a regression to me.. But no it won't trip knox
Click to expand...
Click to collapse
I downloaded the correct file, unzipped and I did these 4 files, which put in its proper place and time to flash the firmware gives me error.
I'm in the OF4 version and have not received the update by air today. I restored the phone several times to see if I update and nothing appears. I searched around in various forums and can not find the solution
I bought the galaxy used and I'm not sure if the USB cable is original. Anyway, I've tried other cables and various USB ports. The last thing I did was to restore the PC and start from scratch ... it still did not work for me
I am very good at following tutorials. I have not damaged a phone or electronic equipment and has not gone bad in the process, I always get everything right, but it is the first time you see me in this situation where I can not find the solution
I think it's the cable. Anyway, where I live not sell the USB cable separately. Buy by amazon and I'm waiting for it to arrive, but if not the USB cable and anyone knows anything please help me
Make sure you. Put phone in download mode. I overlooked that when I was a noob
Finally bit the bullet and just flashed the 5.1.1 update using Odin. Very smooth process. My phone is running 5.1.1 now. And with Google automatic backup, it didn't even take that long to set up my phone again.
--Ron
First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!
jfviwerbnv said:
First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!
Click to expand...
Click to collapse
It's a real pain in the butt.... I just went through this 10 minutes ago. The problem: "Custom binary blocked by FRP" - or, FRP lock.
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
It works. Not elegant, but I don't think there is any way round this. No way to use ADB that I can figure, but ODIN will work.
Once you get back up and running, make sure to go into settings and enable developer options. When you get there, allow USB debugging and click on the "bootloader unlock" option. That will keep FRP from screwing you up again.
If you need a more detailed explanation, let me know- but that's the skeleton of the fix. Once you get running again you can set up the phone the way you want it.
Cheers! (argh)
Steven.RN
Get the Odin file here: https://www.androidfilehost.com/?fid=24269982087008345 (N910T3UVU1DOK2_N910T3TMB1DOK2_TMB.zip)
Unzip the file and it will end in ....tar.md5 Just knock off the .md5 so that it simply ends up as .... .tar, and use "AP" placeholder in Odin.
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.
steven.rn said:
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
[...]
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.
Click to expand...
Click to collapse
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.
jfviwerbnv said:
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.
Click to expand...
Click to collapse
Yup.... make sure you get the right flavor of ROM or stock files. I think some devs might have roms that work with either version. But that's the first thing to check, if it's compatible.
Once I reflashed my wifey's phone, I ODIN'ed in the stock twrp recovery TAR file, then got into the recovery and flashed supersu 2.64 in a zip. Rooted, working fine, done (YaY)
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Let me know how things turn out; I don't think you'll have any surprises. It took me about an hour and a half to make sure I had the right solution fer shurrrre, so I think I saved you some time.
You always this lucky? :highfive:
Cheers,
Steven.RN
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this
steven.rn said:
Yup.... make sure you get the right flavor of ROM or stock files.
Click to expand...
Click to collapse
Yep, that turned out to be the problem. Device is a N910T3, I had the stock 5.1.1 rom for the N910T, that's why flashing with ODIN was being blocked. Grabbed the stock 5.1.1 rom for the correct variant, N910T3, and ODIN and the phone were both happy. No factory reset or warranty repair necessary!
Thanks soooo much for the tip!
Unfortunately that image-loading glitch is still there even though I haven't re-rooted yet (now that I think about it, it's maybe more like 5%, and some images don't seem to be vulnerable. maybe it's like a weird bad build of libjpeg or something, I dunno) Well, that's a mystery for another time.
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Click to expand...
Click to collapse
Thanks, I'll keep that in mind. (Don't remember offhand what exactly I did there before.)
You always this lucky? :highfive:
Click to expand...
Click to collapse
Nah, I'm just one stubborn SOB, and once in a while it actually pays off
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this
Click to expand...
Click to collapse
Yea. There were actually several reasons I jumped Verizon -> T-Mobile, but that was one of them. Little over two years ago when I got an S3, all the lockouts from Samsung/Google/Verizon were so heavy it wound up bricking within the first couple weeks (complications trying to downgrade an OTA update I didn't want - long story). Anyway, trying to get a proper working replacement took them several tries (one replacement was DOA, another wasn't even a Samsung at all, let alone the right model) and just trying to even communicate with them at all was like having a roundtable with a cage of chimps. (just one example, I couldn't convince them there really were different models of any phone, like the S3, between different carriers, dev versions etc. Nevermind that I'm a career programmer, I couldn't possibly know what I'm talking about ) Plus Verizon's so much more expensive, and T-Mobile just strikes me as a vastly more level-headed pro-consumer company overall. And with the new Band 12 (the reason I got Note4 instead of Note3, oddly enough), their network's been every bit as good as Verizon's for me anywhere I've taken it.
Flashing DOK2 firmware via Odin will wipe internal memory.
ShrekOpher said:
Flashing DOK2 firmware via Odin will wipe internal memory.
Click to expand...
Click to collapse
Doing that didn't wipe internal memory for me (Odin 3.10.6). It did unroot my phone and I'm sure it probably reset my recovery image back to stock (didn't actually try booting into recovery again yet), but all my data was still 100% intact. And not just the data on the "external" SD but also all user data on the internal storage. (It never wiped user data for me on my old S3 or Nexus S either, but maybe the wiping after flashing is just a newer thing?)
Maybe it only wipes internal memory if you're flashing a different version of android? I was simply flashing 5.1.1 overtop rooted 5.1.1.
Hi, i wish i could figure this out on my own and not trouble anyone but i just i cant. I've already soft bricked the phone trying, though I've fixed that now and its back to normal.
What i am trying to do is put The UK H3G network firmware (SM-G920F) on to my American ATT phone (G925A). The reason is, i'm in the UK on the 3 network so it would be nice if the phone just worked as it should do if i had bought it here. I cant update it OTA and the phone seems to think its American in general.
Is this even possible? Im using Odin3. I downloaded the g920f firmware from sammobile. It was just one file, i put it into the AP section, i assume that's right? It didn't work though, a few different errors resulting in fails and nice soft brick at the end. The files i used to un-brick the phone had AP,CP,BL and CSC files. Sorry for my ignorance but do i need these 4 files to achieve what i want?
Well id be very grateful of any help or advice in this.
You cannot use firmware for a different version of the phone. Trying so can end in a hardbrick
schhy said:
You cannot use firmware for a different version of the phone. Trying so can end in a hardbrick
Click to expand...
Click to collapse
Oh thanks, impossible or just risky? I'm sure i saw others talking about doing it and the guy in my phone shop even said i could try it. Do the phones have different internals or something?
caspergotchi said:
Oh thanks, impossible or just risky? I'm sure i saw others talking about doing it and the guy in my phone shop even said i could try it. Do the phones have different internals or something?
Click to expand...
Click to collapse
The US AT&T and VZW branded devices have locked bootloaders. The international versions (which I would imagine is what your local cellular guy is familiar with, being in the UK) are somewhat more, ummm, flexible on what software they can run. I would guess (but don't know for sure) that you could probably recover with Odin if you bricked in attempting what you want to try.
Sent from my SAMSUNG-SM-G920A using Tapatalk
dandrumheller said:
The US AT&T and VZW branded devices have locked bootloaders. The international versions (which I would imagine is what your local cellular guy is familiar with, being in the UK) are somewhat more, ummm, flexible on what software they can run. I would guess (but don't know for sure) that you could probably recover with Odin if you bricked in attempting what you want to try.
Hey thanks, what kind of file would i need to try it though? I downloaded the at&T firmware from somewhere that matched the model number and it had 4 files, ap,bl,csc and another one, im not sure what they do individually, but they worked. When i looked up the uk firmware, it only had an ap file, which didn't work using odin, i got a fail. Do you know where i can find H3G uk SM-G920F that has all 4 files or at least the files i would need to do this? I am sorry, i'm sure i'm asking stupid questions but i appreciate your help thanks.
Click to expand...
Click to collapse
caspergotchi said:
dandrumheller said:
The US AT&T and VZW branded devices have locked bootloaders. The international versions (which I would imagine is what your local cellular guy is familiar with, being in the UK) are somewhat more, ummm, flexible on what software they can run. I would guess (but don't know for sure) that you could probably recover with Odin if you bricked in attempting what you want to try.
Hey thanks, what kind of file would i need to try it though? I downloaded the at&T firmware from somewhere that matched the model number and it had 4 files, ap,bl,csc and another one, im not sure what they do individually, but they worked. When i looked up the uk firmware, it only had an ap file, which didn't work using odin, i got a fail. Do you know where i can find H3G uk SM-G920F that has all 4 files or at least the files i would need to do this? I am sorry, i'm sure i'm asking stupid questions but i appreciate your help thanks.
Click to expand...
Click to collapse
Check the non AT&T specific S6 forum. Much more activity there than here. If you can't find it in the stickies or with search, someone there can probably point you in the right direction.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
caspergotchi said:
Oh thanks, impossible or just risky? I'm sure i saw others talking about doing it and the guy in my phone shop even said i could try it. Do the phones have different internals or something?
Click to expand...
Click to collapse
Well i think it's just what you flash. For example, messing up the kernal will hardbrick but some thinks like AP and csc i think are fine to flash but may not work