Database Develop

Is there an "odin tutorial"? (how to flash modem/radio with odin?)

I'm a bit (more than a bit) rusty on the ODIN tool, and was wondering if there was some kind of complete tutorial for it floating around. In particular, I'm wondering if I could use it to replace ONLY the radio/baseband for a device.
I have the AT&T firmware zip (containing files starting with "AP", "BL", "CP", and "CSC") and I'm wondering if I could use that to flash the AT&T modem on a n920c device. (And to use a proper n920c firmware set to get back to the n920c modem if flashing the AT&T one doesn't work out.)
(Why? I live in the US and have AT&T as a carrier. The AT&T provided modem most likely contains radio tweaks to optimize usage of AT&T towers.)

garyd9 said:
I'm a bit (more than a bit) rusty on the ODIN tool,
I have the AT&T firmware zip (containing files starting with "AP", "BL", "CP", and "CSC") and I'm wondering if I could use that to flash the AT&T modem on a n920c device. (And to use a proper n920c firmware set to get back to the n920c modem if flashing the AT&T one doesn't work out.)
Click to expand...
Click to collapse
I do not know of a guide but you flash the modem in the CP slot. However if the Note 5 is anything like the Note 4 you cannot flash an AT&T modem on the C version. I believe it is because of the partition table being laid out differently. I have also read that you cannot even change the partition table anymore but I do not know about that for sure as I am limited in knowledge in that area.

CodeNameRedNeck said:
I do not know of a guide but you flash the modem in the CP slot. However if the Note 5 is anything like the Note 4 you cannot flash an AT&T modem on the C version. I believe it is because of the partition table being laid out differently. I have also read that you cannot even change the partition table anymore but I do not know about that for sure as I am limited in knowledge in that area.
Click to expand...
Click to collapse
It sounds like you've messed with something similar on the note4? I wonder if I could swap modems by pulling the .img file out of the odin tarball and using 'dd'.
(Honestly, I'm more comfortable with 'dd' anyway... if it can be used.)

garyd9 said:
It sounds like you've messed with something similar on the note4? I wonder if I could swap modems by pulling the .img file out of the odin tarball and using 'dd'.
(Honestly, I'm more comfortable with 'dd' anyway... if it can be used.)
Click to expand...
Click to collapse
Indeed. I used to unpack C version firmwares to flash onto my H version so I could have LTE on it.

Have you swapped the modem out for at&t or still stock??

Neva Eva Forget 1984 said:
Have you swapped the modem out for at&t or still stock??
Click to expand...
Click to collapse
no.. never got around to it (and at this point, I don't feel the need.)

In Note 3 the trick is to do a battery pull then go straight to download mode and flash modem in CP slot. It won't "stick" otherwise. If this is also true in Note 5, how to emulate a battery pull?
Sent from my SM-N920I using Tapatalk

kopitalk said:
In Note 3 the trick is to do a battery pull then go straight to download mode and flash modem in CP slot. It won't "stick" otherwise. If this is also true in Note 5, how to emulate a battery pull?
Sent from my SM-N920I using Tapatalk
Click to expand...
Click to collapse
I guess you could do the force reset option using the power + volume down buttons. I'm not sure

Octa_core said:
I guess you could do the force reset option using the power + volume down buttons. I'm not sure
Click to expand...
Click to collapse
Didn't work that way in Note 3.
Sent from my SM-N920I using Tapatalk

Decided to tinker with my modem via flashfire... (with isn't as restrictive as ODIN in terms of what it'll flash and what it won't.)
Keep in mind that I have a N920I device and an AT&T SIM inserted... My kernel is currently a permissive custom compiled kernel targeted for the N920I. The /system partition (what I call "firmware" and too many on XDA incorrectly refer to as "ROM") is a stock N920T firmware that's been deodex'd and some of the TMobile specific stuff stripped out. If the RIL is part of /system, that means I'm using a tmobile RIL. If the RIL is in the boot partition, I'm using a N920I RIL.
Flashing the N920I modem works.
Flashing the N920A modem results in it not seeing the baseband at all. (settings->status->baseband version: unknown)
Flashing the N920T modem results in it not seeing the baseband at all. (same as above.)
Flashing back to a N920I modem restores functionality.
I don't have a "N920C" modem available to me right now, but it might be more likely to work (as the "I" and "C" kernel DTB's are apparently interchangeable.)

"C" modem doesn't work on the "I" device either. (same result as flashing any of the other non-"I" modems on this phone.)
So, while it might be possible to change modems, I don't know how and it's not as simple as just flashing the modem.bin.
Of course, I can switch between different "I" modems with no problem.

Didn't samsung lock us out of flashing different model modem since s4?
Note 5 ?

Idan73 said:
Didn't samsung lock us out of flashing different model modem since s4?
Click to expand...
Click to collapse
No idea. I skipped the SGS 4, 5 and 6 (and the Notes 3 and 4.) I was rusty enough with Samsung and ODIN when I got this Note 5 that I actually had to ask for a quick ODIN refresher.

Didn't know that.
Well, as far as I remember sgs4 was launched with ability to reflash modems from other providers (unlocking wind/mobilicity, and t-mobile bands. At the time most people actually bought att version, which did not have locked bootloader to use it on tmobile, and was also Canadian favourite pastime). Sometimes during that first year, there started to be reports about new bootloader that would start accepting only signed modems from the phone's original region. Not certain if this affected north American phone at the time, but was going hand in hand as the Europe started getting region lock, and Knox started rearing it's ugly head (also affected only certain firmwares and was very limited in scope).
With sgs5 it was all confirmed.
The rest is history, and since, I haven't heard of a case where someone successfully flashed other model modem, as we could with previous generations.
For the past few years, we Canadians get same phone as tmobile (thank God it's no longer att due to bootloader), actually identical (in number of cases there are markings of tmobile inside our phones), except for that modem that is either tmobile or Canadian, which is why our firmwares and kernels are usually built together.
Note that couple of times I tried on this phone, because twrp allows modem backup, I tried to restore my own modem backup for testing, and would lose reception and would have to reflash with Odin to get it back. Maybe my backup was corrupted, so if there is differing experience to this, apologies. I just didn't dare try and mess with it anymore.
Note 5 ?

Idan73 said:
reports about new bootloader that would start accepting only signed modems from the phone's original region
Click to expand...
Click to collapse
Hmm.. unknown to many people, the radio (modem) in many phones actually boots before the boot (kernel) partition. (I can't remember WHY that is, but I do remember it...)
My impression was that the bootloader was blocking ODIN from flashing an improper modem, which was why I was using flashfire. However, it would make sense that the bootloader would also block the radio/modem from starting up if there was a mismatch. I'd guess, in this case, it's more of a regulatory and/or safety issue (to prevent a malicious or corrupted modem.bin from controlling the radio/modem)
That doesn't mean that Samsung isn't ALSO doing it to block people like me...
So, the next question becomes: can the bootloader be changed to allow a different model modem to boot? Changing the bootloader would likely require re-partitioning the device, though... And if you put a bootloader in that has blocks (such as AT&T or Verizon), then you might end up unable to even boot the phone.
Why does all of this even matter to me? Well, it's really a very minor concern: When I had the 'A' model, I'd get an IPv6 address on the note 5 while on LTE. When I had the "C" model, I'd also get an IPv6 address on LTE. However, for some reason I don't get an IPv6 address on the 'I' model while on AT&T LTE. (Yes, the kernel is supporting it, and yes the proper APN is configured and has IPv6 enabled... in fact, it's identical to what I had on the 'C' device.)

Note 4 n910t or n910t3?

Rooted n4 currently running tekhd v4.2. About device says n910t3 running cog2. Box phone came in says it's an n910t. If I go by what device says (t3), and I load the correct f/w, (dog1), soon as I hit 'start', in Odin, it fails. Redownload, no change. Tmo support says it's what the box says unless it's rooted. (???) any ideas how to find out which I have? If it is a t3 then wondering why I can't flash dog1. Thanks for any ideas!

INFO on your SM-N910T
best thing to do is take off the back and look under battery I have a T3 see attached image. The software you are running is based on DOG1 but your modem and firmware are still COG2. I am running a N5 port and mine says I have a SM-920T(N5) running DOG1 baseband. So dont always believe what your about says. To get features working many times things will be changed in the build prop so keep that in mind.
Note:
Do Not flash any roms that are specifically for the N910T3

N910t

Why can't you revert from DOK2 to a previous version?

I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.

phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.

DeeXii said:
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.
Click to expand...
Click to collapse
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.

phoneturf said:
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.
Click to expand...
Click to collapse
go here for your answers
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179

My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.

jazzmachine said:
My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.
Click to expand...
Click to collapse
Canadian note 4 dont seem to have the security lock on them since i rolled back to 5.0.1 bootloader but yes it wont let u roll back to any other 5.1.1 bootloader
U can try to download canadian BOE2 firmware and flash that since tmobile nd canada r pretty mch the same
This can be very dangerous so be cautious

phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
I have been try a lot of time for use odin to flash cog2 or cod6 from dok2. And it allway fail in odin. And you will receive a notice in the download mode screen like that o"Odin fai, binary =2>1". So you can't flash succesfull in odin.
And evething can't change. I have read 5.1.1 plicy and it also said that we can't downgrade from t mobile phone.lol

Perhaps development can recompile bootloader without tmo security and use Canadian firm to patch.

I just upgrade from COG2 to DOK2. Is there any difference? Which is better?
I have the N910T.

Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.

Bruce lee roy said:
Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.
Click to expand...
Click to collapse
I see. My cook ROM say use DOK2. I didnt know about the downgrade. I guess its ok and thanks for the info.

SM 920G Issue

Hey guys I bought a brand new note 5 from Rent a center. paid it in full i own it, and i noticed that i can root and flash this device. This is my second note...the other i had was a verizon note 3. But upon reading all over the web. I noticed that the one i have is the international version of this device and it has twrp and custom roms and kernels. Well I am not new to all this but I know that I need to activate developer options you have to tap on the build number like 7 times. Well On this device it wont let me tap on it. Nothing happens when I do. Is there a way to activate it or unlock it so I can get flashing? Its odd I am tried factory reset and still nothing. I had the idea of flashing the stock software but couldnt find the north american version or something. Sorry its been a while since i had a samsung since the note 3.

You can't flash North American firmware on international version. Go on samfirmware website and download the right version for your phone. Flash it with Odin and you should be OK. After that you can root and flash twrp again with no problem.
Sent from my SM-N930W8 using Tapatalk

rafeba said:
You can't flash North American firmware on international version. Go on samfirmware website and download the right version for your phone. Flash it with Odin and you should be OK. After that you can root and flash twrp again with no problem.
Sent from my SM-N930W8 using Tapatalk
Click to expand...
Click to collapse
ok I will do that but the question i am worried about is. the device i have came with the box that said north america sim only..that going to be an issue?
Update: How can i flash the correct firmware with odin if I cant access the developer options? it wont let me tap on the build number? Do you need developer options enabled to use odin.

You don't need usb debuting enabled to flash stock firmware with odin. Just put the phone in downloading mode and use Odin. But be careful which firmware you're gonna use. Download the firmware for your model number from samfirmware site. About sim card it's all about activation. It has nothing to do with the firmware.
Sent from my SM-N930W8 using Tapatalk

AT&T Note 3 (USA) - Emergency Call Only

Hi Everyone,
I am kind of lost in the upgrade process.
6 months ago, my Samsung Note 3 (USA AT&T) phone was working perfectly fine, but just with OLD firmware. ,then due to urge on upgrading, i searched so many sites and found a link somewhere on droidviews.com (as my firmware was NJ1 or something, website said i need to upgrade to NC2, and then to OC1), this process messed up my phone call receiving & making capabilities.
Most of the time callers see me unreachable and I am unable to call them as i get "emergency calls only"....I still don't have a way out from this issue. Some places I read i need to install right CSC / modem etc, I even tried this thread by reflashing using ODIN & N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar. Even after this, i still have calls related issues same as above.
Can someone guide me to right direct (or) did i totally messed up with this? BTW, i am now in INDIA, using Airtel services...

I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?

audit13 said:
I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?
Click to expand...
Click to collapse
Thanks. I tried flashing to OC1, still same problem. my calls are mostly not working. Is there a way i can go back to original 4.3 stock rom that came with Note3 AT&T? or is there a way i can get current AT&T rom (latest) to try with?
Good part is, i can go between 4.4.3 and 5.0 as i have original stock roms downloaded. But bad part is, my calls still failing...
appreciate any clue/help.

Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.

audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Hi, i downloaded NC2 & OC1 stock firmwares from XDA only. they are loading up fine (using ODIN). But my calling problem remains same.
So, Yesterday, i tried rooting the phone and installed AllianceROM. then i went into series of issues like "unfortunately NFC has stopped", "unfortunately settings has stopped" etc... then followed the instruction to wipe/factory reset, 3 to 4 times and disabled NFC services etc. As of now, phone works fine, but still need to check the calling function for a week...
thanks for your time.

audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Are we SOL with 900a? I was in the wrong forum earlier and was ready to use update to 7...until I realized it wasn't for me.
Dying on Lollipop (where I landed after the 7 fallout)

I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.

audit13 said:
I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.
Click to expand...
Click to collapse
We can flash roms using safestrap and flashfire