Related
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Rachel Ambler said:
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Click to expand...
Click to collapse
The main reason that some users bricked their phone is that they wiped the OS and had a locked bootloader which leaves no possibility ro recover the phone
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Unless something is special about the N6 that I'm not aware of, the OS you update FROM only matters if you're sideloading an OTA file. Flashing factory images, you could be coming from a custom ROM(I just took my old N4 from CM12.1 to stock 4.4 on Sunday).
The current build for VZW is 5.1 LMY47E. I think they are updating to 5.1.1 now(LMY47Z, which seems to be universal now except for maybe T-Mo). I flashed mine from E to Z on Saturday because I bought mine unlocked but it had the VZW build, and I'm on an AT&T MVNO.
gee2012 said:
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
If you root, you'll.never get an OTA anyway, sonit doesn't matter which rom you flash aa you can flash any other rom.over it
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Rachel Ambler said:
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
Click to expand...
Click to collapse
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
danarama said:
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Click to expand...
Click to collapse
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Rachel Ambler said:
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Click to expand...
Click to collapse
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile adds a kernel fix to allow their wifi calling to work. And that's it...
gee2012 said:
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
Click to expand...
Click to collapse
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
danarama said:
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile addsna kernel fix to allow their wifi calling to work. And that's it...
Click to expand...
Click to collapse
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
gee2012 said:
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Click to expand...
Click to collapse
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
danarama said:
"Well all Nexus 6 used to get the same updates but tmob and red, ..."
Click to expand...
Click to collapse
Great info, very useful.
Rachel Ambler said:
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Click to expand...
Click to collapse
There were no carrier specific ROMs when Nexus 6 came out. Using any rom on any Nexus and they will all act the same, except you wont get improved volte or wifi calling on those carriers. Their changes will not prove detrimental on other carriers
danarama said:
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
Click to expand...
Click to collapse
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Rachel Ambler said:
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
Click to expand...
Click to collapse
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on xda that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Rachel Ambler said:
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Click to expand...
Click to collapse
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
danarama said:
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on sea that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Click to expand...
Click to collapse
I'm sorry if that sudden flash of the light coming on in my head just blinded you, but that's what happens when things start to make sense!
OK, so, this all being the case, and that the OTA's are incremental, then in order to go 5.1 with the build from http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 then I WOULD need 5.0.1? Would that work though if I'm on a generic build since, if it's expecting to patch existing VZW files, wouldn't it fail because they're not there? Failing that I'd need to find a flashable 5.1 for VZW (if one even exists)?
endlessryan said:
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
Click to expand...
Click to collapse
But it wouldn't have the VoLTE improvements, etc, right? Besides, right now I'd like to stay as stock as possible as it's not just my phone I'm working on, both myself and my wife got one at the same time and I know she will most definitely NOT want anything other than stock.
*Utter noob alert!*
tl;dr - can i update to MM 6+ without totally screwing my phone and entering a whole world of pain?
Proud owner of mongrel SM-N920A purchased from HK via eBay. Device has no branding on hardward / software other than Samsung.
Settings > System > About Device shows model number = SM-N920F. LIES!!!!!
Phone INFO *Samsung* apk shows it's really an SM-N920A
I've attached output from Phone INFO showing 'General', 'CSC', 'Firmware' and 'Android' info.
Having read over threads on Sammobile and here on XDA, it appears some people are losing anything from mobile reception & data to full on apocalyptic bricking. Most of these posts are from earlier in 2016 so I'm wondering, now we're further down the line and the dust has settled, whether there's any consensus on best way forward to get Marshmallow / Nougat and beyond - if at all.
Anyone out there able to offer help and guidance?
Please :crying:
Ah come onnn! Someone here must be able to help!?
dmlargo said:
Ah come onnn! Someone here must be able to help!?
Click to expand...
Click to collapse
This is commonly done to increase the value of the phone by tricking the buyer into thinking it's a non-US model.
Anyway, AT&T and T-Mobile are better than Verizon or Sprint if it comes to using them outside the US, because of better LTE band support.
Since an AT&T phone will only receive OTA updates with an AT&T SIM inserted, you have to sideload the MM update yourself through adb and then keep on sideloading every new build as it comes out.
murtaza02 said:
This is commonly done to increase the value of the phone by tricking the buyer into thinking it's a non-US model.
Anyway, AT&T and T-Mobile are better than Verizon or Sprint if it comes to using them outside the US, because of better LTE band support.
Since an AT&T phone will only receive OTA updates with an AT&T SIM inserted, you have to sideload the MM update yourself through adb and then keep on sideloading every new build as it comes out.
Click to expand...
Click to collapse
So...
If I can get my hands on a prepaid / payg at&t sim here in the UK I could theoretically just get an OTA update that way?
If not, I'll look into sideloading. Do you know of any instructions on how to do?
And, thanks for replying. Very much appreciated
dmlargo said:
So...
If I can get my hands on a prepaid / payg at&t sim here in the UK I could theoretically just get an OTA update that way?
If not, I'll look into sideloading. Do you know of any instructions on how to do?
And, thanks for replying. Very much appreciated
Click to expand...
Click to collapse
Not necessarily, since the device needs to be connected to AT&Ts network, the SIM would either not work, or start Roaming in the UK.
Sideloading means you will have to get the OTA Zip files and install them on your phone using the Android Debugging Bridge (ADB).
This is the thread HERE: http://forum.xda-developers.com/att...ow-to-manually-update-to-marshmallow-t3380624
It's a very well written guide on how to update the AT&T Note 5.
Your current build number is different from the one used in the main post of the guide, so you're going to have to browse through the thread, grab a different build of Lollipop, flash that, then sideload the Marshmallow updates, one by one, till you get to a fairly new build, then what you do is, factory reset the phone, so you have a clean install of Marshmallow on your phone.
murtaza02 said:
Not necessarily, since the device needs to be connected to AT&Ts network, the SIM would either not work, or start Roaming in the UK.
Click to expand...
Click to collapse
Of course! I'm an idiot. Doesn't bode well does it! :laugh:
murtaza02 said:
Sideloading means you will have to get the OTA Zip files and install them on your phone using the Android Debugging Bridge (ADB).
This is the thread HERE: http://forum.xda-developers.com/att...ow-to-manually-update-to-marshmallow-t3380624
It's a very well written guide on how to update the AT&T Note 5.
Your current build number is different from the one used in the main post of the guide, so you're going to have to browse through the thread, grab a different build of Lollipop, flash that, then sideload the Marshmallow updates, one by one, till you get to a fairly new build, then what you do is, factory reset the phone, so you have a clean install of Marshmallow on your phone.
Click to expand...
Click to collapse
Build number being LMY4X.N920AUCU1AOGG
Doesn't matter that bootloader, PDA,CSC and baseband versions are mostly all different?
You're a great help. Thank you! +1
dmlargo said:
Of course! I'm an idiot. Doesn't bode well does it! :laugh:
Build number being LMY4X.N920AUCU1AOGG
Doesn't matter that bootloader, PDA,CSC and baseband versions are mostly all different?
You're a great help. Thank you! +1
Click to expand...
Click to collapse
You're on AOJ1 According to your screenshot.
You need to downgrade to UPB2 Or something and then flash the OTAs from Marshmallow to your phone from PB2.
I'm out of the house at the moment, will be home very soon, and try to find a link for you.
murtaza02 said:
You're on AOJ1 According to your screenshot.
You need to downgrade to UPB2 Or something and then flash the OTAs from Marshmallow to your phone from PB2.
I'm out of the house at the moment, will be home very soon, and try to find a link for you.
Click to expand...
Click to collapse
Thanks man.
For that version AOJ1 - that's bootloader version right? Just so I can differentiate what to look for.
Take it easy
dmlargo said:
Thanks man.
For that version AOJ1 - that's bootloader version right? Just so I can differentiate what to look for.
Take it easy
Click to expand...
Click to collapse
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.
murtaza02 said:
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.
Click to expand...
Click to collapse
Epic. If I take it back to 2BPE6 successfully, I'm guessing it's then just the same process to push up to 6.0.1 and beyond?
dmlargo said:
Epic. If I take it back to 2BPE6 successfully, I'm guessing it's then just the same process to push up to 6.0.1 and beyond?
Click to expand...
Click to collapse
Nope, that was the process I described initially that required you to flash 2BP2 First and then onwards to Marshmallow.
The file I've linked (2BPE6) isn't an OTA. It's the entire full ROM file for the 6.0.1 update for the N920A. Once you flash this and the phone reboots, it'll go directly to Marshmallow.
murtaza02 said:
Nope, that was the process I described initially that required you to flash 2BP2 First and then onwards to Marshmallow.
The file I've linked (2BPE6) isn't an OTA. It's the entire full ROM file for the 6.0.1 update for the N920A. Once you flash this and the phone reboots, it'll go directly to Marshmallow.
Click to expand...
Click to collapse
And, more importantly, I'll hopefully have a standardised stack across csc, PDA and what not.
Like I said in op - there's unsurprisingly a lot of talk out there about note 5 on at&t when it comes to updates. I'd hoped because mine was already rooted and had a CHN / TGY csc that it kind of showed if someone in China had done stuff to it, and it still worked, then there was a possibility of moving it to 6.0.1
I'll get all files together along with your notes and have a go after getting a nandroid back up. Might be a while given time of year though.
Nice one
dmlargo said:
And, more importantly, I'll hopefully have a standardised stack across csc, PDA and what not.
Like I said in op - there's unsurprisingly a lot of talk out there about note 5 on at&t when it comes to updates. I'd hoped because mine was already rooted and had a CHN / TGY csc that it kind of showed if someone in China had done stuff to it, and it still worked, then there was a possibility of moving it to 6.0.1
I'll get all files together along with your notes and have a go after getting a nandroid back up. Might be a while given time of year though.
Nice one
Click to expand...
Click to collapse
The CSC and everything will go back to the default ATT one and it'll have no trace of ever being a fake N920F.
Everything will show N920A and you may also have a bit of AT&T bloat ware, most of which can be disabled.
But the main point is that the phone will no longer be modified in any way and will be completely stock.
murtaza02 said:
The CSC and everything will go back to the default ATT one and it'll have no trace of ever being a fake N920F.
Everything will show N920A and you may also have a bit of AT&T bloat ware, most of which can be disabled.
But the main point is that the phone will no longer be modified in any way and will be completely stock.
Click to expand...
Click to collapse
But doesn't that mean it'll be region locked / potentially losing network connection?
dmlargo said:
But doesn't that mean it'll be region locked / potentially losing network connection?
Click to expand...
Click to collapse
Nope. Once it's unlocked, it's always unlocked.
I live in Pakistan, American carrier phones are very common here. AT&T, Verizon, T-Mobile and Sprint, all the variants of Note 5 are available here and I've flashed updates on a friends AT&T Note 5 and it didn't get re-locked. I've flashed a T-Mobile Note 4 and 5, neither got re-locked.
Point being, that re-locking crap only used to happen on phones that were unlocked using a glitch or a software based unlock.
murtaza02 said:
Nope. Once it's unlocked, it's always unlocked.
I live in Pakistan, American carrier phones are very common here. AT&T, Verizon, T-Mobile and Sprint, all the variants of Note 5 are available here and I've flashed updates on a friends AT&T Note 5 and it didn't get re-locked. I've flashed a T-Mobile Note 4 and 5, neither got re-locked.
Point being, that re-locking crap only used to happen on phones that were unlocked using a glitch or a software based unlock.
Click to expand...
Click to collapse
Cool. I'll have a look this weekend. Fingers crossed.
After that I'll have a go a re-rooting using something similar to: https://www.search4roots.com/how-to-easily-root-samsung-galaxy-note-5-sm-n920a-marshmallow-6-0-1/
murtaza02 said:
I happened to come across the 2BPE6 Marshmallow ROM file for the N920A Note 5.
Here's the link: https://mega.nz/#!8Ep0DRZA!jXd4QtMcmN47QIOQSHV8h0CqAc7aVMB5aR4VA_Zw1Pw
You can flash it with Odin, a bit easier to use than ADB, so it'll be better for you as well.
The file is zipped, once you extract it, there'll be 4 different files, one containing system and the main ROM, the other will contain the BL (Bootloader), another with the modem (Radio) and the last with the CSC (Customer Sales Code). Match each file to it's respective field in Odin, the BL file will have BL in the filename so add the BL file to the BL tab in Odin, the CP file to the CP tab, the AP file to the AP tab and the CSC file to the CSC tab.
Then turn your phone off, once it's completely off, hold Power + Home + Volume Down, it'll ask Continue or Cancel, press Volume Up to Continue. You'll be in Odin / Downloading mode, from here, just connect your phone to your PC, flash the Odin files, the phone will reboot itself a few times, not to worry, and it'll eventually boot to the marshmallow start screen.
As for grabbing Odin, I'd recommend the latest version 3.12.3, it supports the newest devices up to S7 and S7 Edge, and it has all the bug fixes as well, so it should work fine on your phone. Link here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Good luck.
Click to expand...
Click to collapse
I had a very similar situation ( AT&T re-custom Note5 ) , followed the procedure and everything went straight
so thanks to both of you for this thread and pretty straight guide
really
the only "issue" is that quite many thing ( graphically speaking ) changed from Lollipop , not in a "good" way , and I'm not sure wheter they're supposed to change for Marshmallow or for the AT&T bloatware/customization ..what is sure is that the phone was running bit cleaner before . ( i.e. no extra icons , no recording or "AT&T video call " icon available on phonecall screen when calling ..just an example among some things i noticed besides some at&t apps in the home screen )
is there a way to know it and to remove any of it , besides rooting the phone ? - which I'm not sure can be done on a n920a
boodi said:
I had a very similar situation ( AT&T re-custom Note5 ) , followed the procedure and everything went straight
so thanks to both of you for this thread and guide
the only thing is that quite many thing ( graphically speaking ) changed from Lollipop , not in a "good" way , and I'm not sure wheter they're supposed to change for Marshmallow or for the AT&T bloatware/customization
is there a way to know it and to remove any of it , besides rooting the phone ? - which I'm not sure can be done on a n920a
Click to expand...
Click to collapse
Package Disabler Pro. It's a paid app. You can use it to disable (not remove) some bloatware that's preinstalled by Samsung and AT&T.
No root possible, so you can't remove the apps.
Sent from my SM-G935F
Hi! Former Note 4 owner here, about to switch from One Plus 3T to Note 8. It has been a sweet ride with the OP3T but I am getting Note withdrawal already ! I just realized I buy (and lose) cheap styluses (styli?) every other week as I spend a lot of time editing pictures on the fly for our home business FB and IG ads.
Have a simple question:
In my country we have 2 variants available, N950F and the Korean N950N. almost same price, gladly both Exynos which is what I want. However, I would like to know if there is any advantage for any of them regarding system updates timing from Samsung, security updates and the like. Also, any chances of Oreo being rolled out for one of them earlier than the other?
I dont feel a need to root at the moment although just in case I would like to know if there are any major differences or ease of doing that for any of them . I did some research before posting the question and looks like N950F has more dev support but correct me if I am wrong.
I just need to decide on this "XDA world problem" to pull the triger. No one I know understand my conundrum and they look at me like I am from Mars.
Garoto1973 said:
Hi! Former Note 4 owner here, about to switch from One Plus 3T to Note 8. It has been a sweet ride with the OP3T but I am getting Note withdrawal already ! I just realized I buy (and lose) cheap styluses (styli?) every other week as I spend a lot of time editing pictures on the fly for our home business FB and IG ads.
Have a simple question:
In my country we have 2 variants available, N950F and the Korean N950N. almost same price, gladly both Exynos which is what I want. However, I would like to know if there is any advantage for any of them regarding system updates timing from Samsung, security updates and the like. Also, any chances of Oreo being rolled out for one of them earlier than the other?
I dont feel a need to root at the moment although just in case I would like to know if there are any major differences or ease of doing that for any of them . I did some research before posting the question and looks like N950F has more dev support but correct me if I am wrong.
I just need to decide on this "XDA world problem" to pull the triger. No one I know understand my conundrum and they look at me like I am from Mars.
Click to expand...
Click to collapse
Updates will be released in tandem. One after other. So not much delay
950N , yes I said it.
Sent from my SM-N950U using Tapatalk
Limeybastard said:
950N , yes I said it.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Lol...you might as well give OP a reason why you suggest one over the other
sefrcoko said:
Lol...you might as well give OP a reason why you suggest one over the other
Click to expand...
Click to collapse
It believe you have better color options and memory?plus made in Korea. LOL
Sent from my SM-N950U using Tapatalk
n950n = no possible OEM jail time issue. F's are a hit or miss. Uk seem ok but the rest of asian and Oceania seem to have the dreaded 7 day jail time.
bober10113 said:
n950n = no possible OEM jail time issue. F's are a hit or miss. Uk seem ok but the rest of asian and Oceania seem to have the dreaded 7 day jail time.
Click to expand...
Click to collapse
Really? Why is there no possibility of "jail time" on the SM-N950N? Kindly elaborate.
MrElectrifyer said:
Really? Why is there no possibility of "jail time" on the SM-N950N? Kindly elaborate.
Click to expand...
Click to collapse
because the OEM unlock is there by default. My first attempt at a note 8 was a dual sim 950F and OEM unlock was not there. Not being able to root/flash twrp for 7 days and possibility of jail time every time a new rom or csc is flashed is not my cup of tea.
bober10113 said:
because the OEM unlock is there by default. My first attempt at a note 8 was a dual sim 950F and OEM unlock was not there. Not being able to root/flash twrp for 7 days and possibility of jail time every time a new rom or csc is flashed is not my cup of tea.
Click to expand...
Click to collapse
Well then, that makes me better appreciate my 256GB SM-N950N.
I was on the lookout for the 256GB SM-N950FD 'cause I wanted a globally unlocked, Multi-CSC supported, and unbranded bloatware-free Exynos device with support for OTAs. The Dual SIM support is a welcome added bonus. However, never came across a 256GB version of the SM-N950FD, only 64GB version, which I'm not willing to settle for, especially as I plan on keeping this device (my first ever Samsung Smartphone) for the next 5+ years (unless something a whole lot more useful becomes available) and I'm using it more and more as a full-fledged Pocket PC.
After you've rooted, do you always clean install via Odin in order to install the monthly security updates? Or how do you update the device? Please and thank you.
MrElectrifyer said:
Well then, that makes me better appreciate my 256GB SM-N950N.
I was on the lookout for the 256GB SM-N950FD 'cause I wanted a globally unlocked, Multi-CSC supported, and unbranded bloatware-free Exynos device with support for OTAs. The Dual SIM support is a welcome added bonus. However, never came across a 256GB version of the SM-N950FD, only 64GB version, which I'm not willing to settle for, especially as I plan on keeping this device (my first ever Samsung Smartphone) for the next 5+ years (unless something a whole lot more useful becomes available) and I'm using it more and more as a full-fledged Pocket PC.
After you've rooted, do you always clean install via Odin in order to install the monthly security updates? Or how do you update the device? Please and thank you.
Click to expand...
Click to collapse
for monthly updates, no need to be rooted.
If you root then chances are you have twrp and probably are on a custom rom. the dev which makes the rom will update their Rom(monthly?) and then just flash that in twrp.
only thing you need to do is maintain your bootloader and modem up to date via odin. never flash these 2 firmwares that might be provided within roms or as seperate files as they are almost always for n950F.
I too have a 256gb version and it has been nothing but smooth sailing!
bober10113 said:
for monthly updates, no need to be rooted.
If you root then chances are you have twrp and probably are on a custom rom. the dev which makes the rom will update their Rom(monthly?) and then just flash that in twrp.
only thing you need to do is maintain your bootloader and modem up to date via odin. never flash these 2 firmwares that might be provided within roms or as seperate files as they are almost always for n950F.
I too have a 256gb version and it has been nothing but smooth sailing!
Click to expand...
Click to collapse
Thanks for the information. I don't have a custom ROM (frankly, I really like Samsung's feature-packed stock ROMs), I rooted so that I could switch the CSC to the Canadian Fido CSC (FMC) to enable WiFi Calling and also native call recording. Unfortunately, haven't figured out how to get either of those working yet, but also using Magisk root for other handy root applications like Titanium Backup, DisableService, etc., all while keeping Safetynet happy
In this situation, how would you suggest I do the updates without losing system data? Is there a way via PrinceComsy Odin? Thanks in advance.
MrElectrifyer said:
Thanks for the information. I don't have a custom ROM (frankly, I really like Samsung's feature-packed stock ROMs), I rooted so that I could switch the CSC to the Canadian Fido CSC (FMC) to enable WiFi Calling and also native call recording. Unfortunately, haven't figured out how to get either of those working yet, but also using Magisk root for other handy root applications like Titanium Backup, DisableService, etc., all while keeping Safetynet happy
In this situation, how would you suggest I do the updates without losing system data? Is there a way via PrinceComsy Odin? Thanks in advance.
Click to expand...
Click to collapse
updates meaning CSC ? just flash the note 8 CSC pack from tkkg1994
you can also manualy extract the files to your device(dont forget to set file and folder permissions after. I acctualy post updates for the Canadian xac region file in that dev,s thread so he can incorporate them in his flashable zip.
Regarding csc options for wifi calling, unfortuantely Fido is Rogers. they blacklist foreign imei codes. meaning that you need a device sold by them which is total BS.
this is the only "downside" of having a non-carrier branded device
bober10113 said:
updates meaning CSC ? just flash the note 8 CSC pack from tkkg1994
Click to expand...
Click to collapse
Thanks again for the information. Sorry for not being clear, I meant entire firmware updates, like the security updates and the upcoming Oreo update. How would you flash them on the SM-N950N without losing data? I once attempted updating via Odin with HOME_CSC of the SM-N950N in the CSC slot, but it factory reset my Note 8. I then re-attempted with the HOME_CSC of the SM-N950W (the Canadian Note 8), but Odin threw back an error. Again, I'm not on a custom ROM, only changed the CSC.
MrElectrifyer said:
Thanks again for the information. Sorry for not being clear, I meant entire firmware updates, like the security updates and the upcoming Oreo update. How would you flash them on the SM-N950N without losing data? I once attempted updating via Odin with HOME_CSC of the SM-N950N in the CSC slot, but it factory reset my Note 8. I then re-attempted with the HOME_CSC of the SM-N950W (the Canadian Note 8), but Odin threw back an error. Again, I'm not on a custom ROM, only changed the CSC.
Click to expand...
Click to collapse
stock csc firmware will wipe your fone at first but once its changed then it should not wipe after. it wipes when carrier/region is switched. flashing stock firmware from an F device to a N is not going to work.
logically is you flash the next korean full firmware update(bl,ap,cp,csc) it shouldint wipe. anyways if i remember right once csc was switched on your 1st attempt then it shouldint wipe on your subsequent tries. only thing that dies wipe is when sim triggers region to change.
if you have trwp then flash the CSC pack. it won t wipe that im sure of.
bober10113 said:
...it wipes when carrier/region is switched...
only thing that dies wipe is when sim triggers region to change.
Click to expand...
Click to collapse
So given that logic, it would always wipe my Note 8. 'Cause after flashing the official SM-N950N (SKC) firmware via Odin (which makes it now the SKC CSC), I again changed CSC to FMC via @Tkkg1994's CSC Selection tool. Attempting to flash future updates would again trigger a CSC change from FMC to SKC, right?
bober10113 said:
if you have trwp then flash the CSC pack. it won t wipe that im sure of.
Click to expand...
Click to collapse
I understand and can confirm that. However, that's used after flashing the official firmware updates, which results in a wipe in Odin as it's changing from FMC back to SKC, if I understood correctly. I'm looking for a way to avoid the wipe when doing the firmware update.
just don't flash csc part in odin next update. always use the CSC packs. of course since you flash AP then you have to reflash twrp each time and prolly have to format storage?
but all things put aside, you really should try his Iron man rom! make a trwp backup of your current state incase you want to go back.
So what about SM-N9500, the last update I received had Android January Security fix.
I jave the F edition.
Never went to jail. Flashed over 30 times different roms.
Maroc_Specops said:
I jave the F edition.
Never went to jail. Flashed over 30 times different roms.
Click to expand...
Click to collapse
you are part of the 1%
maybe not literally 1 per cent but alot of F owners have had issues with "jail" time. there is a whole thread dedicated to the OEM unlock issue.
---------- Post added at 04:48 AM ---------- Previous post was at 04:47 AM ----------
itsmohsink said:
So what about SM-N9500, the last update I received had Android January Security fix.
Click to expand...
Click to collapse
your on chinese snap dragon. totally different beast.
not sure if that makes updates come faster or not.
n950n just got an update 1 day before the Fs.
the rest are trailing at lest 10 days behind.
so id say the update speeds is:
Ns
Fs
U's
0's
W's
time = X quantity of space... lol
Ok... So where to begin...
I've searched the threads for a few days now and tried several flashing methods and tools, but I'm having no luck. So please bare with me, and I will get into it...
I recently purchased a new Note 9 international unlocked model. I was super excited and ready to get it running. Except, I started it up and then no Bixby Voice. Unlike most, I prefer to use it and find it helpful to me regularly, so I'd like to keep it. Anyway, when pressing the button I received the much noted "Bixby Voice is not available in your country" message. Well, I found from Samsung support live chat, that this is because of two reasons. One, I currently live in Japan. Two, the phone is a Singapore model phone. My immediate thought was "Oh, ok well, I'll just flash it with another country's firmware then". Seemed easy enough. I flashed it with firmware baring an OXM csc, and after booting up I noticed the the VoLTE feature that was not select-able before was now able to turned on. "Ooow, extra win!" I thought, but of course same issue with bixby. So I searched and found a csc for a location that has bixby is available and is also a carrier unlocked Exynos chipset firmware (XEU). I flashed this, but guess what... still no Bixby Voice. Frustrated, I began looking into changing the Sales code. Using the *#272*IMEI# code and found that MM1 was the sales code for some reason. I changed this to XEU and the phone rebooted. I restored and then tried Bixby Voice again... same. Except, I noticed I also lost the VoLTE option completely. It doesn't even show in the menu bar anymore. I tried the code again to change the sales code back, but now I get error "Connection problem or invalid MMI code." So now, I lost that too. "To hell with it", I thought. I'll flash it back to the old firmware... nope. Now I get:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
This will sometimes change slightly if I try to flash a single part of the new firmware, BL, AP, CSC, etc...
I have done some research and found via the serial number that the firmware I should have installed is: N960FXXU1ARH5_N960FOXM1ARGD_N960FXXU1ARGC_N960FXXU 1ARH5_XSP (according to the Chimera Mobile tool)
I've obtained this, but I still get the same Revision error. I found that the one last one I successfully flashed is a newer version than the others. So now what can I do? Is it possible I can just manually manipulate the CSC details? I rooted the phone and got ES Explorer going, set all the access rights to R/W but I cant find the /System/CSC folder that people keep going on about. Did they do away with that on the Note 9?
It looks like I also have some regional troubles with the Play store too.
WTH... I'm really not sure what to do here. Can anyone please help? I'll be satisfied if I can just get it back to the stock firmware...
Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.
who uses bixby use google assistant for peats sake!!!"!!!!
willhemmens said:
Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.
Click to expand...
Click to collapse
Hi willhemmens! Thanks for replying back.
I was also speculating the same thing about having to wait for the revision, but I know the people here are significantly more knowledgeable, so I thought I'd try to pick some brains. My first though was that there must be something in one of the package files that identify to the phone what "version" it is, and then perhaps that can be modified and then re-packaged. But if that were the case, this would be the best place on the planet to verify that. I have tools to un-package and repackage, maybe I'll make a duplicate copy and tinker around in it.
It looks like everyone is complaining about it. It's been a while since I rooted a device (7 years maybe?), so I hadn't realized Samsung took a dump in the downgrade pool. I also found some other new 'glorious' features they've graced us with-after the fact of course. Now, when I un-root... it's still flagged as modified! Woohoo. ....Fricken' KNOX. Now all of the nifty Samsung apps are blocked. Is it just me, or has Samsung turned a little extra Ass-hat recently?
Anyway, I guess I'll have to deal with this lame iOS quality version of Oreo until then... By the way, off the top of your head do you know where I can go to keep an eye out for that update to happen? All I know is SamMobile.com
Thanks again.
mikey_sk said:
who uses bixby use google assistant for peats sake!!!"!!!!
Click to expand...
Click to collapse
Hi Mikey! Yeah, I suppose your right. I've just been using it a lot and have gotten accustomed to it. Plus I enjoy creating my own custom Bixby voices, attitudes, and responses. Bixby on my Note 8 has split personality.
Luckily she doesn't randomly laugh in the dark like Alexa. If she did she'd fly out the window like a Note 7.
csc was omc and now odm.
bober10113 said:
csc was omc and now odm.
Click to expand...
Click to collapse
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.
VetteMike69 said:
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.
Click to expand...
Click to collapse
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?
VetteMike69 said:
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?
Click to expand...
Click to collapse
Ah sorry, nevermind... I was able to make a ps1 for it instead. I'm good one decoding and encoding the XMLs now.
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file
yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
Click to expand...
Click to collapse
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw
bober10113 said:
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw
Click to expand...
Click to collapse
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!
hkalltheway said:
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!
Click to expand...
Click to collapse
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.
yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file
Click to expand...
Click to collapse
Hi @yakapa40!
Thank you, this looks like it'll be a bit more convenient than the one I made previously. I'll put it on record for next time. Luckily I was able to find what prevented me from flashing the older revision CSC and modify that. So now I was able to use Odin to drop down my PDA and CSC while keeping the newer Bootloader and Baseband. I guess it's a bit of a Frankin'-Firm now. Whats weird though, is that now my knox sometimes shows tripped and sometimes doesn't; sometimes root checker fails and sometimes it passes.
I wonder if I grazed on something that's related to the knox handler... Nagh... probably just wishful thinking. Still weird though.
bober10113 said:
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.
Click to expand...
Click to collapse
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.
VetteMike69 said:
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.
Click to expand...
Click to collapse
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.
bober10113 said:
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.
Click to expand...
Click to collapse
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
well then root might be food for you.
have a read at Dr Ketan roms thread for the root procedure and details of what it involves.
hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.
bober10113 said:
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.
Click to expand...
Click to collapse
I'm currently with fido but thinking of switching to freedom mobile. Still too worried about all this rooting stuff that it seems the best thing to do is stay away from now and choose from one of the 2:
1- use wifi calling / VoLTE by getting the rogers/fido phone directly; that phone will not have dual sim capability
2- forget wifi calling / VoLTE and use this dual sim version, which has a lot of advantages while traveling
Seems like I'll stick to the 2nd option for now. Thanks for the help!
I have Note 9 (SM-N960U1) unlocked in USA. I am currently on AT&T.
I seem to have many dead spots inside my house so want to enable wifi calling but found out that I need to flash carrier specific firmware on my phone. As I am complete noob, have some questions:
1) What does flashing a firmware does? Pros? Cons?
2) I am currently on Android 10 (One UI 2.0 Build QP1A.190711.020.N960U1UEU3ZSL2). If I flash a new firmware, will my phone be downgraded to a lower version of Android?
3) If answer to @2 is Yes, how will I get latest Android updates? Will it depend on Samsung or AT&T?
4) Last but not the least, HOW THE HELL I FLASH THIS FIRMWARE?
Any help will be a great help. I have a interview on Friday so don't have much time to get this fixed.
TIA.
1) Flashing is a way to manually install or update firmware or operating system through the bootloader. This provides a way to restore the devices operating system during an emergency or failed OTA Update etc. The cons of this however is it is quite easy to mess up your device if you don't know what you are doing. And Flashing different firmware that is not originally meant for your device easily carries this risk. The bootloader is what tells your device how to boot the operating system and happens before any user interaction knock on wood you theoretically corrupt the bootloader or somehow mess it up you are left with a 1000 dollar doorstop. Im not sure how a carrier's firmware would react on an unlocked phone. I personally wouldn't risk it but it's up to you. I'm pretty sure that other users here have tried it you should look around and do your research. Remember this would not only be changing Android this would also change the CSC and Modem.
2) Android 10 has not yet been released for the Note 9 so I would assume that you are on the beta. You would need to factory reset and downgrade to Android 9 before flashing ATT's firmware.
3) Carrier's handle OTA updates. However im not sure you would even receive OTA's anymore.
4) You need to use Odin3 and get the firmware from somewhere like sammobile.
In conclusion I personally would advise you to contact ATT with your problem. Considering your interview tomorrow if something did for some reason go wrong you most likely wouldn't have time to fix it.
UndeadAnarchy said:
1) Flashing is a way to manually install or update firmware or operating system through the bootloader. This provides a way to restore the devices operating system during an emergency or failed OTA Update etc. The cons of this however is it is quite easy to mess up your device if you don't know what you are doing. And Flashing different firmware that is not originally meant for your device easily carries this risk. The bootloader is what tells your device how to boot the operating system and happens before any user interaction knock on wood you theoretically corrupt the bootloader or somehow mess it up you are left with a 1000 dollar doorstop. Im not sure how a carrier's firmware would react on an unlocked phone. I personally wouldn't risk it but it's up to you. I'm pretty sure that other users here have tried it you should look around and do your research. Remember this would not only be changing Android this would also change the CSC and Modem.
2) Android 10 has not yet been released for the Note 9 so I would assume that you are on the beta. You would need to factory reset and downgrade to Android 9 before flashing ATT's firmware.
3) Carrier's handle OTA updates. However im not sure you would even receive OTA's anymore.
4) You need to use Odin3 and get the firmware from somewhere like sammobile.
In conclusion I personally would advise you to contact ATT with your problem. Considering your interview tomorrow if something did for some reason go wrong you most likely wouldn't have time to fix it.
Click to expand...
Click to collapse
Thanks a lot for your help mate..cheers
rockstar283 said:
I have Note 9 (SM-N960U1) unlocked in USA. I am currently on AT&T.
I seem to have many dead spots inside my house so want to enable wifi calling but found out that I need to flash carrier specific firmware on my phone. As I am complete noob, have some questions:
1) What does flashing a firmware does? Pros? Cons?
2) I am currently on Android 10 (One UI 2.0 Build QP1A.190711.020.N960U1UEU3ZSL2). If I flash a new firmware, will my phone be downgraded to a lower version of Android?
3) If answer to @2 is Yes, how will I get latest Android updates? Will it depend on Samsung or AT&T?
4) Last but not the least, HOW THE HELL I FLASH THIS FIRMWARE?
Any help will be a great help. I have a interview on Friday so don't have much time to get this fixed.
TIA.
Click to expand...
Click to collapse
You have SM-N960U1 with One UI 2.0? Did you just buy it used? You are on bootloader 3, so you cannot flash another firmware with bootloader less than 3.