thanks for this.I'm uploading now. Give me about half an hour to post links.
SM-N900A_MI1_Modem_RecoveryFlashable
SM-N900A_MI9_Modem_RecoveryFlashable
SM-N900A_MJ5_Modem_RecoveryFlashable
SM-N900A_MLG_Modem_RecoveryFlashable
SM-N900A_NL1_Modem_OdinFlashable
SM-N900A_NB4_Modem_RecoveryFlashable
SM-N900A_NC2_Modem_RecoveryFlashable
look hereIs there a link for an odin update for the latest nc2. Also I have a question about the modems. I can make a call, text and stuff like that but when I make a call I cant hear anything and they cant hear anything. but if I do a call over google hangouts I can hear and they can hear me. any idea what that might be. Thanks
kernel, bootloader or the same, modem is the same but just renamed to OC2Just curious if there are plans to have flashables of the new OC2 firmware, such as kernel, modem, bootloader, etc.
Sent from my SM-N9005 using Tapatalk
Thanks so much for the file Carl! Unfortunately, it fails to flash in SafeStrap. I'm on Alliance v10 if that helps.kernel, bootloader or the same, modem is the same but just renamed to OC2
SM-N900A_N900AATTEOC2_Firmware_Recovery-Flashable.zip
https://mega.nz/#!XQ1STBjY!-EylZrPJwQEWGgg2Cg5PCEE1wtWT2I-jsiGntVYBO1k
yes it is because your build.prop is not stock OC1, the installer looks for that.Thanks so much for the file Carl! Unfortunately, it fails to flash in SafeStrap. I'm on Alliance v10 if that helps.
Sent from my SM-N9005 using Tapatalk
Thanks for the advice Carl. I edited the script accordingly and the zip flashed but my phone is now in a continuous bootloop. I even went into stock recovery thinking clearing cache might help but it didn't. One thing I did notice is that stock recovery still says OC1. Any ideas?? I don't wanna flash my ROM all overa again.yes it is because your build.prop is not stock OC1, the installer looks for that.
you can edit the updater-script and remove the build.prop check and it will install.
remove this:
file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/hlteuc/hlteatt:5.0/LRX21V/N900AUCUEOC1:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/hlteuc/hlteatt:5.0/LRX21V/N900AUCUEOC2:user/release-keys" ||
abort("Package expects build fingerprint of samsung/hlteuc/hlteatt:5.0/LRX21V/N900AUCUEOC1:user/release-keys or samsung/hlteuc/hlteatt:5.0/LRX21V/N900AUCUEOC2:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
assert(getprop("ro.product.device") == "hlteatt" ||
getprop("ro.build.product") == "hlteatt" ||
getprop("ro.product.device") == "hlteatt" ||
getprop("ro.build.product") == "hlteatt");
it is the same recovery but wrong name. soon as I can pull the recovery from my phone I will update it. If you do the OTA as in my thread it would be the OC2, but in safestrap recovery installer for OC2 firmware, it basically only updated the modem.Thanks for the advice Carl. I edited the script accordingly and the zip flashed but my phone is now in a continuous bootloop. I even went into stock recovery thinking clearing cache might help but it didn't. One thing I did notice is that stock recovery still says OC1. Any ideas?? I don't wanna flash my ROM all overa again.
Much appreciated Carl. What about the bootloop issue though? Dirty flashing my ROM saved the day but will this happen again?it is the same recovery but wrong name. soon as I can pull the recovery from my phone I will update it. If you do the OTA as in my thread it would be the OC2, but in safestrap recovery installer for OC2 firmware, it basically only updated the modem.
Here is OC2 modem OTA patcherCarl would you happen to have just the OC2 modem flashable file?
No it is a SafeStrap recovery installerstill flash in odin under cp?
have you tryed flashing the NC2 firmware and selecting format and using a pit fileThis is the first time I'm posting on a forum about this problem, thought I could tackle it myself.
Turns out I was wrong.
I bought a Samsung Galaxy Note 3 SM-N900A on eBay a couple weeks ago. I've been having a difficult time getting the phone to consistently read a sim card and provide steady service. I've researched a lot on this forum, droidviews, galaxynote3root, and so on.. and haven't been able to get it working. Though, I have at times been able to get service, including data. It's been intermittent and have repeated steps to try and get it working but they haven't worked. There are a few thing's I came across though that may help give me the right steps to fix this.
After a fresh tar file flash using Odin, the baseband is still unknown. I've tried this with a couple different versions such as NC2 (the one I can flash with), NL1 and OC1. I read somewhere that this means the modem file is corrupt, so I flashed the corresponding modem, and tried different ones. This is where I would sometimes have a working phone and sometimes not.
This is so confusing and there's a lot of information I could right on here but I'm really just looking for someone to help me fix this because its so frustrating. I could return it and I might, but my other phone has a cracked screen and lets not go there..
**The most interesting thing that's happening is after a "successful" flash at times the phone will have service, maybe for a very short time or even overnight.
PLeeeeaaaaasseeeee help![]()