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
Related
I recently purchased a used T-Mobile Note 4 from a 3rd party. The box states the model is a N910T. The sticker under the battery states N910T. However, the "About phone" software lists it as a N910W8. The phone currently does not have an option for WiFi calling, but I would like to flash the N910T firmware so I can use WiFi calling. Will this be an issue? Did the user before me install N910W8 firmware on the N910T variant? I have been reading they are very similar, but the N910W8 firmware currently installed does not have WiFI calling support.
Lastly, when the phone boots up, in the top left corner it reads in red and yellow colored font:
KERNEL IS NOT SEANDROID ENFORCING.
Set Warranty Bit : Kernel
Is this cause for concern about the device I purchased?
re: N910T - Firmware
gizmo2431 said:
I recently purchased a used T-Mobile Note 4 from a 3rd party. The box states the model is a N910T. The sticker under the battery states N910T. However, the "About phone" software lists it as a N910W8. The phone currently does not have an option for WiFi calling, but I would like to flash the N910T firmware so I can use WiFi calling. Will this be an issue? Did the user before me install N910W8 firmware on the N910T variant? I have been reading they are very similar, but the N910W8 firmware currently installed does not have WiFI calling support.
Lastly, when the phone boots up, in the top left corner it reads in red and yellow colored font:
KERNEL IS NOT SEANDROID ENFORCING.
Set Warranty Bit : Kernel
Is this cause for concern about the device I purchased?
Click to expand...
Click to collapse
Your phone is definatly a N910T Tmobile.
The operating system (rom) in your phone is a custom rom which the previous owner
installed, the N910T and the N910W8 are similar phones and the main difference in
the two is the wifi calling feature but there are other not so noticeable differences too.
If I were you I would odin flash the original stock firmware before doing
anything else. You can download it from http://www.sammobile.com
Be sure you download the right firmware version for your N910T .
Just do a firmware search on sammoble for N910T and get the NK4
or the COD6 firmware.
Then use odin to flash the N910T original NK4 firmware.
Once that's done the phone will be in the same original state as when it was new.
Good luck!
Thank you! Exactly what I was hoping to hear, but wanted to confirm before going through with the flash. Appreciate it.
Misterjunky said:
Your phone is definatly a N910T Tmobile.
The operating system (rom) in your phone is a custom rom which the previous owner
installed, the N910T and the N910W8 are similar phones and the main difference in
the two is the wifi calling feature but there are other not so noticeable differences too.
If I were you I would odin flash the original stock firmware before doing
anything else. You can download it from http://www.sammobile.com
Be sure you download the right firmware version for your N910T .
Just do a firmware search on sammoble for N910T and get the NK4
or the COD6 firmware.
Then use odin to flash the N910T original NK4 firmware.
Once that's done the phone will be in the same original state as when it was new.
Good luck!
Click to expand...
Click to collapse
I hace n910w8 that mean i can download n910T roms?
daviddiazayuso said:
I hace n910w8 that mean i can download n910T roms?
Click to expand...
Click to collapse
Pretty much, both have exactly the same hardware. N910w8 gets updates faster though.
As in the title I think I messed up when I installed Twi5sted Lollipop; the phone shows the following:
Model Number: SM-G900T (Here I guess is where I messed up because afaik T is for TMobile while I should have A for AT&T)
Android Version: 5.0
Baseband: G900AUCU3BOC4
Kernel: 3.4.0-4432708
Build Number: Twi5ted Lollipop V-7
The phone has lost root and I cannot use Flashfire to install another ROM.
Is there any way to downgrade to stock ROM and then be able to root/flashfire again?
You should be able to I did it with mine 4x in one day trying to get the order right just use Odin to get back to stock and upgrade from there kind of a pain but I think I'm a pro at it now just be sure not to take the 5.1 Ota or you will b screwed
The model number listed in the settings is determined by build.prop, you can make it say butts if you want . I'm the dude who ported the rom, its a T-Mobile rom, therefore the build.prop has the model as g900t, that's fine. The "loosing root" problem you have is pretty easy to fix, you still have root SuperSU is just borked, try reinstalling it and tell me what happens.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Yeah it worked thank for Tha info I love the rom for sure I was wanting to change my bootamation so I dwn loaded the sick bootamation flashed n it sends it into bootloop I've only been doing this for 3 months so I'm pretty new on the changing that stuff using terminal emulator n such
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.
I'm currently running one of the last CM12.1 nightlies on my N910T3 with the N910T3UVU1DOK2 baseband. Now that there are a few seemingly mostly stable Nougat builds I want to try upgrading, but as far as I'm aware this old baseband won't work with a MM or N ROM and I'll have no radios working. Unfortunately it seems that the new basebands aren't compatible with LP ROMs and the N910T3 can not be downgraded, so once I move forward there's no turning back.
I have a few questions:
1. Am I correct that I'll need to upgrade to a newer baseband to expect any MM or N ROM to work correctly?
2. Am I correct that my current LP ROM will no longer work after I upgrade to a newer baseband?
3. Am I correct that since I have a N910T3 I will be unable to downgrade my baseband back to a LP compatible revision?
4. With the previous three questions in mind, when I choose to upgrade should I get a specific version or just grab the latest one? (N910T3UVS3EPK2 at the moment it seems)
edit: Also is the best way to go about it to just Odin/Heimdall back to completely stock and effectively restart from scratch or is there a better way for a phone that's already running TWRP?
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