Related
Hi, I'm new to the forum and to the wonderful world of rooting, custom roms and such so bare with me if I ask something stupid.Okay well the title basically says it all, I have 2 Samsung Galaxy note II phones which my dad bought from china. When we turned then on the OS was completely in Chinese so without even thinking about it I downloaded the official firmware for our region and started flashing it onto 1 of the phones just like I did when we received a Samsung Galaxy Note 10.1 tablet. But now something was different, Odin claims that the flashing failed. So I did a little further googling a found out that the Chinese note II had a custom bootloader preventing me from installing firmware from a different region (link to source below). I really don't know what to do further from this point I restored to the Chinese firmware just so that the phone would still work, but it suck not having gmail and that kind of thing so if anybody know of a way to bypass this custom boot loader or some other solution I could try it would really be appreciated!
http://forum.xda-developers.com/showthread.php?t=1982814&page=2
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
I was looking through Samfirmware.com and could not figure this out.
Where can I get the stock firmware file for the USA version of the T700?
Looking over the site and a few other posts for different devices, is this the right firmware for the model sold in the USA?
http://www.sammobile.com/firmwares/database/SM-T700/XAR/
The model number for my exact device is SM-T700NTSAXAR
The firmware list on samfirmware/sammobile says that it is cellular south.
None of the xar variants I have found (last three letters of the model number) seem to have cellular connection though.
Yea, never understood why they refer to it as Cellular South, but that is the correct region for us T700 users.
That is a bit confusing yeah.
Thank you for confirming that for me.
Want to make sure that I have the right stock software to flash back to if I want to unroot it.
Just got mine 3 days ago and probably going time be rooting it soon.
Don't think Knox really matters on this. Holding off for root on my s6 until can be rooted without tripping Knox so I don't lose Samsung pay.
Although on October everyone should be using chip and pin so it might be useless anyway.
I’m sorry if my English is not perfect since I’m from Malaysia and this is my first posting in XDA Forum. And I’m not sure if this is the right forum to post my questions to.
So recently I’ve bought a new Note 4, knowing that the international variant can be rooted easily. Having successfully rooted a few Samsung phones in recent years, I thought that the root method for Note 4 is more or less about the same (either through ODIN flashing, Kingroot, Towelroot etc). After some frustrating attempts, it seemed that I couldn’t get the phone rooted. I managed to get some sort of root using Kingoroot (verified by root checker, and Titanium Backup) but I couldn’t update the SU binaries.
Here are some phone details from the About Device info:
Model Number
SM-N910F
Android Version
5.0.1
Baseband Version
N910FXXU1BOC4
Kernel Version
3.10.40-4160876
Build Number
DONGCHAO.A916
However, from the Phone Info app, I got this detail:
Product Code:
SM-N910AZKECHN
CSC Country:
USA / US
Bootloader Version:
N910AUCU2COC6
PDA Version:
N910AUCU1COC4
CSC Version:
N910AATT1COC4
Baseband Version:
N910AUCU2COC6
Kernel Version
3.10.40-4160876
I’ve tried booting the phone in bootloader, and it says that the product name as SM-910A.
1. Does this mean that the actual phone model is SM-N910A with a European firmware SM-N910F installed?
2. If it is a yes, how is it possible that other firmware version can be installed on the AT&T variant? I was under the impression that any firmware must be signed by AT&T before it can be installed on the said model.
3. I’m quite concerned with the build number DONGCHAO.A916. I’ve tried to get more info about it but none can be found. Anyone know for which market is this firmware meant for?
4. Do I need to use only the firmware updates from AT&T in the future?
I have so many questions running in head right now but I’m afraid to tinker with the phone any further for fear of bricking it. I’ve never seen the AT&T stock firmware before so I don’t know how my phone might function with the stock rom in Malaysia.
Hope someone can shed a light on this. If it is indeed the SM-910A variant (which is weird since it is sold in the Asian market), I might be stuck with the locked bootloader with no rooting method as of now.
First thing you need is to know what you really have...
Download this and report back what you find
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Bootloader will block any firmware attempt but at&t branded.
Sent from my SAMSUNG-SM-N915A using XDA-Developers mobile app
Shanghai.Knight said:
First thing you need is to know what you really have...
Download this and report back what you find
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Click to expand...
Click to collapse
That is exactly the app I used to check the phone info as posted above (the second part of the info, not the one from About Device).
I believe I cannot post the screenshot since my total post counts is less than 10. But please tell me what other info should I report here from the app
Apparently I was mistaken about posting the image file. Please refer to the attached screenshot for the info of my phone, including the info from the rom's About Device
Looks to me like you have an ATT Phone... Perhaps someone rooted the phone and edited the information to make it look like you have the international variant?
Shanghai.Knight said:
Looks to me like you have an ATT Phone... Perhaps someone rooted the phone and edited the information to make it look like you have the international variant?
Click to expand...
Click to collapse
This shouldn't be possible since the only root obtained on the ATT variant was temp root. If the information was edited (build.prop), wouldn't it revert back to stock upon a reboot?
Also, speaking of reboot, shouldn't the phone not say that it's rooted since a reboot would unroot it?
Sent from my SAMSUNG-SM-N910A using Tapatalk
Im wondering if what you have is a clone and not genuine
giga8547 said:
Im wondering if what you have is a clone and not genuine
Click to expand...
Click to collapse
That's the thing. I've actually thought of that but with all the standard Samsung built quality on this phone, I can't even tell. And I bought it at legit retailer with the Samsung warranty. Aside from the physical inspection, is there any way to test it through an app or something?
Here's the thing... EVERYTHING in the Samsung INFO app shows you have an ATT phone (See below)... The ONLY thing that is different is your Device "About" screen.
Something's fishy.
Model: n910A = ATT Model
Type= trlteatt = TR LTE AT&T
Bootloader = 910A = ATT
PDA = 910A = ATT
CSC = 910A = ATT
Baseband = 910A = ATT
Check out this thread http://forum.xda-developers.com/showthread.php?p=63526184#post63526184
It appears that it is possible to flash a different system.img file - to make it look like a N910F...
But in reality you have a N910A - ATT
If this upsets you, bring it back to the "genuine" samsung dealer and show him the Samsung INFO app and demand your money back...
You probably will not be able to get Marshmallow updates, except through ODIN...
Shanghai.Knight said:
Here's the thing... EVERYTHING in the Samsung INFO app shows you have an ATT phone (See below)... The ONLY thing that is different is your Device "About" screen.
Something's fishy.
Model: n910A = ATT Model
Type= trlteatt = TR LTE AT&T
Bootloader = 910A = ATT
PDA = 910A = ATT
CSC = 910A = ATT
Baseband = 910A = ATT
Check out this thread http://forum.xda-developers.com/showthread.php?p=63526184#post63526184
It appears that it is possible to flash a different system.img file - to make it look like a N910F...
But in reality you have a N910A - ATT
If this upsets you, bring it back to the "genuine" samsung dealer and show him the Samsung INFO app and demand your money back...
You probably will not be able to get Marshmallow updates, except through ODIN...
Click to expand...
Click to collapse
I agree with you, with warranty he should return it and get his money back or a new phone.
I'm just curious here. OP, what country do you live in? In the US, that legitimate retailer would have to give you a refund.
Sent from my SAMSUNG-SM-N910A using Tapatalk
I believe he said he's from Malaysia...
giga8547 said:
Im wondering if what you have is a clone and not genuine
Click to expand...
Click to collapse
Shanghai.Knight said:
Here's the thing... EVERYTHING in the Samsung INFO app shows you have an ATT phone (See below)... The ONLY thing that is different is your Device "About" screen.
Something's fishy.
Model: n910A = ATT Model
Type= trlteatt = TR LTE AT&T
Bootloader = 910A = ATT
PDA = 910A = ATT
CSC = 910A = ATT
Baseband = 910A = ATT
Check out this thread http://forum.xda-developers.com/showthread.php?p=63526184#post63526184
It appears that it is possible to flash a different system.img file - to make it look like a N910F...
But in reality you have a N910A - ATT
If this upsets you, bring it back to the "genuine" samsung dealer and show him the Samsung INFO app and demand your money back...
You probably will not be able to get Marshmallow updates, except through ODIN...
Click to expand...
Click to collapse
Thanks for pointing out the other thread to me. I guess I have to wait until end of month to revisit the retailer which is considerably far from my place of work. I don't actually mind having the ATT variant if it could be rooted though. I believe it is the only Note 4 variant that cannot be rooted, isn't it?
spexwood said:
I'm just curious here. OP, what country do you live in? In the US, that legitimate retailer would have to give you a refund.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
I live and bought my phone in Malaysia
kentangz said:
Thanks for pointing out the other thread to me. I guess I have to wait until end of month to revisit the retailer which is considerably far from my place of work. I don't actually mind having the ATT variant if it could be rooted though. I believe it is the only Note 4 variant that cannot be rooted, isn't it?
I live and bought my phone in Malaysia
Click to expand...
Click to collapse
As far as I know, the only root on this phone has only been temporarily root...
Sorry you got something different than what you paid for. I lived in Asia 12 years and occasionally dealt with this myself.
Some have tried to go back to earlier versions (4.4.x) but get stuck in boot loops, or soft brick. I don't think there is any way to root. Some threads to examine:
http://forum.xda-developers.com/note-4-att/help/help-downgrade-att-note-4-sm-910a-5-0-0-t3212163
http://forum.xda-developers.com/note-4-att/help/att-galaxy-note-4-n910a-5-1-1-root-cm-t3348539
http://forum.xda-developers.com/note-4-att/help/help-downgrade-att-note-4-sm-n910a-5-0-t3210452
But even KitKat only had temporary root:
http://forum.xda-developers.com/note-4-att/help/note-4-rooting-t3146579
Thats Exactly I am trying to do!!
Hi All,
I am using Note 4 (SM-N910A) which I purchased in United States, Originally this phone was locked on AT&T Carrier so I had to unlock it to use in India. It still running on 4.4.4 (KitKat) and there is no OTA update as well. I want to update my phone's firmware version to 6.0.1 (Marshmallow) by SM-N910G's firmware (N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4) but while doing so Odin is throwing error "Secure Check Fail: Aboot" (if I use latest Odin 3.11, in next line it says "eMMC write fail: ABOOT")
I was searching for the solution, and I stumble upon this thread. If someone knows how to achieve this (may be by reverse engineering) it would be AWESOME...
(Kindly let me know if you need more info)
Hope to get a positive reply
roronoa.zoro said:
Hi All,
I am using Note 4 (SM-N910A) which I purchased in United States, Originally this phone was locked on AT&T Carrier so I had to unlock it to use in India. It still running on 4.4.4 (KitKat) and there is no OTA update as well. I want to update my phone's firmware version to 6.0.1 (Marshmallow) by SM-N910G's firmware (N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4) but while doing so Odin is throwing error "Secure Check Fail: Aboot" (if I use latest Odin 3.11, in next line it says "eMMC write fail: ABOOT")
I was searching for the solution, and I stumble upon this thread. If someone knows how to achieve this (may be by reverse engineering) it would be AWESOME...
(Kindly let me know if you need more info)
Hope to get a positive reply
Click to expand...
Click to collapse
If you have the SM-N910A phone you cannot put any other firmware on it except the official one. As of this time there is no MM but you can install 5.1.1 using Odin. There is a form that has the files and instructions to do so. When MM is released you will need to wait a little longer for someone to get the firmware files so that you can flash them with Odin.
There must be something ...
maluk said:
If you have the SM-N910A phone you cannot put any other firmware on it except the official one. As of this time there is no MM but you can install 5.1.1 using Odin. There is a form that has the files and instructions to do so. When MM is released you will need to wait a little longer for someone to get the firmware files so that you can flash them with Odin.
Click to expand...
Click to collapse
Thanks for the prompt reply Maluk , But I believe in this post was create by kentangz, as he has N910A with N910F firmware .... my phone is already 18 months old and it has no warranty left... so I just want to install MM even if it trip Knox counter.
Can't I install MM after rooting my phone... Sorry if my questions are stupid.. I have next to no knowledge about any of this...
roronoa.zoro said:
Thanks for the prompt reply Maluk , But I believe in this post was create by kentangz, as he has N910A with N910F firmware .... my phone is already 18 months old and it has no warranty left... so I just want to install MM even if it trip Knox counter.
Can't I install MM after rooting my phone... Sorry if my questions are stupid.. I have next to no knowledge about any of this...
Click to expand...
Click to collapse
This isn't a stupid question but it is asked often.
The N910A has a locked bootloader. Which means unless its an official AT&T firmware, you wont be able to flash anything else. Even if the Note 4 had a permanent root (which it doesn't) you would only be able to flash modified versions of the AT&T firmware. There really is nothing you can do except wait like the rest of us for AT&T to release the firmware of MM. If you do live in India then you could sell your phone and buy the international note 4 version which has an unlocked bootloader and root.
This thread is possibly about how Kentangz might have flashed something to make his phone think its the N910F phone but its still N910A AT&T locked bootloader.
Hi Kentangz,
i had exact situation and experience.. i just bought Note 4 recently, and the inFO under about is not tally with the Phone Info .. and even the sticker on back (back)
the sticker on back (battery removed) showing N910F, but all the bootloader, system pointing i using ATT version
i going to "talk" the that "genuine" guys, He has confimed that is devices from MYS itself, and original
how your phone now, do you sell it or ?
I'm not sure where this should be posted.
I bought an unlocked S9 (SM-G960U) last February whilst flying through the US.
I knew something was fishy because even though it worked with my sim, the AT&T splash screen appeared when booting, but I was in a different country before I realised.
It's Android 8.0
Whenever I go to Software Update it says that i'm on the latest version of Android, nothing I can do to try and force this, tried Smart Switch, same issue. So my next avenue was to use a custom ROM or something - my experience with this is limited to many years ago (the Samsung Galaxy One!), and I believe it's a little easier now.
Anyway, I cannot flash or do anything, I've followed various guides, including to try and get TWRP on there but it looks like I cannot see the OEM feature to enable/disable in the developer tools options.
I'm hoping someone with a little patience can help me out a bit, I just want to get the best out of this phone (and Android Auto).
fakegeordie said:
I'm not sure where this should be posted.
I bought an unlocked S9 (SM-G960U) last February whilst flying through the US.
I knew something was fishy because even though it worked with my sim, the AT&T splash screen appeared when booting, but I was in a different country before I realised.
It's Android 8.0
Whenever I go to Software Update it says that i'm on the latest version of Android, nothing I can do to try and force this, tried Smart Switch, same issue. So my next avenue was to use a custom ROM or something - my experience with this is limited to many years ago (the Samsung Galaxy One!), and I believe it's a little easier now.
Anyway, I cannot flash or do anything, I've followed various guides, including to try and get TWRP on there but it looks like I cannot see the OEM feature to enable/disable in the developer tools options.
I'm hoping someone with a little patience can help me out a bit, I just want to get the best out of this phone (and Android Auto).
Click to expand...
Click to collapse
This device has a locked bootloader. possibly sim unlocked. You cannot flash twrp. No custom roms. Root at the best. You can search on how to use odin. Use a pc program called samfirm or frija to get the latest firmware to update
thank you, this is helpful!
I downloaded Samfirm, and as typical with everything I'm trying, I've immediately hit a hurdle as ATT is not listed as a CSC code on there.
fakegeordie said:
thank you, this is helpful!
I downloaded Samfirm, and as typical with everything I'm trying, I've immediately hit a hurdle as ATT is not listed as a CSC code on there.
Click to expand...
Click to collapse
You might have better luck cross-flashing your AT&T phone to unbranded firmware. See the thread here for more information. The best firmware to download and flash might be the SM-G960U1 firmware using the XAA CSC code. I flashed it on my unlocked Sprint S9 to de-brand it.
fakegeordie said:
thank you, this is helpful!
I downloaded Samfirm, and as typical with everything I'm trying, I've immediately hit a hurdle as ATT is not listed as a CSC code on there.
Click to expand...
Click to collapse
Yea att is hard to come by. M
Hai Karate said:
You might have better luck cross-flashing your AT&T phone to unbranded firmware. See the thread here for more information. The best firmware to download and flash might be the SM-G960U1 firmware using the XAA CSC code. I flashed it on my unlocked Sprint S9 to de-brand it.
Click to expand...
Click to collapse
thank you, I will try this if my other option fails...
So infuriating