Hey guys!
I am new to XDA, so if I have posted incorrectly here please forgive me. So I have a Samsung Galaxy S9 Live Demo Unit (SM-G960XU) and I wanted to flash a non-demo version onto the device, but I am unsure about which version to try.
So I was able to disable the Retail Mode (It will now allow Factory Reset, it won't wipe itself every few minutes, and will not play the annoying demo screensaver, etc), but the LDU version of the Android Software on this phone limits charging the battery to only 70% which is not ideal.
I have read a few forums stating that flashing the Demo Unit with the original International version of the software works, but these demo units all have the model number SM-G960X (not SM-G960XU). So I was wondering if anybody has done this on the G960XU device and if so did you use a SM-960F ROM or SM-906U ROM? Also, if you had any suggestions or ideas, please let me know! I am worried about which version to choose as I do not want to brick the phone.
No, the device is not stolen or illegal. The phone was purchased legitimately and legally from a store who no longer needed the demo unit. Yes, I know the phone does not have a modem and will never be able to make calls or act as a normal phone. I was able to get the phone just to experiment with and to have fun exploring Android.
Any suggestions or help you guys can provide is greatly appreciated!
delete
Hola pudiste resolver
You could resolve the Demo s9 friend
zodey13 said:
Hey guys!
I am new to XDA, so if I have posted incorrectly here please forgive me. So I have a Samsung Galaxy S9 Live Demo Unit (SM-G960XU) and I wanted to flash a non-demo version onto the device, but I am unsure about which version to try.
So I was able to disable the Retail Mode (It will now allow Factory Reset, it won't wipe itself every few minutes, and will not play the annoying demo screensaver, etc), but the LDU version of the Android Software on this phone limits charging the battery to only 70% which is not ideal.
I have read a few forums stating that flashing the Demo Unit with the original International version of the software works, but these demo units all have the model number SM-G960X (not SM-G960XU). So I was wondering if anybody has done this on the G960XU device and if so did you use a SM-960F ROM or SM-906U ROM? Also, if you had any suggestions or ideas, please let me know! I am worried about which version to choose as I do not want to brick the phone.
No, the device is not stolen or illegal. The phone was purchased legitimately and legally from a store who no longer needed the demo unit. Yes, I know the phone does not have a modem and will never be able to make calls or act as a normal phone. I was able to get the phone just to experiment with and to have fun exploring Android.
Any suggestions or help you guys can provide is greatly appreciated!
Click to expand...
Click to collapse
By all logic you should flash U (US), U1 (US Unlocked, slower updates but wider CSC), 0 (Glogal Snapdragon Unlocked, wider CSC but not for North America) or W (Canada) firmware and you'll be good to go. Just install AIDA64 and check which CPU you have. I suspect you have the Snapdragon, so the said ROMs will work. ONLY the said ROMs. Flashing F or N will brick your phone. But if you have the Exynos, flash F (N is for Korea)
I have problem with G960XU. I'm flash it to G960U and now it stuck booting on "SS RDX Subsystem Crashed: MODEM!". Can sombody help me?
From what I've read I don't think you can actually flash the G960XU/G965XU because of the modem issue
any updates on what firmware has worked in flashing the s9 plus G965XU?
I have problem with G960XU. I'm flash it to G960U and now it stuck booting on "SS RDX Subsystem Crashed: MODEM!". Can sombody help me?
Related
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.
Hi there guys,
long story short, i got Samsung Galaxy note 10.1 2014 (sm-p600xzwebtu) Live Demo Unit from work, which i believe is specifically manufactured for retail and comes with quite a lot of limitations, so i need to flash it and install either custom os (i was thinking cyanogenmod) or at least official android.
First of all, it does have developers mode, and it allows me to volume down+power to get it to "downloading os" screen, so i assume i should be able to flash it with odin, but before i do try, maybe someone has dealt with same problem before and has ready to go solution?
reason i am asking is that last year i got couple of Archos devices, those as well were made for retail demo, and they had hardware limitations on ability to flash roms
Staypoh said:
Hi there guys,
long story short, i got Samsung Galaxy note 10.1 2014 (sm-p600xzwebtu) Live Demo Unit from work, which i believe is specifically manufactured for retail and comes with quite a lot of limitations, so i need to flash it and install either custom os (i was thinking cyanogenmod) or at least official android.
First of all, it does have developers mode, and it allows me to volume down+power to get it to "downloading os" screen, so i assume i should be able to flash it with odin, but before i do try, maybe someone has dealt with same problem before and has ready to go solution?
reason i am asking is that last year i got couple of Archos devices, those as well were made for retail demo, and they had hardware limitations on ability to flash roms
Click to expand...
Click to collapse
Yeah, you should have no problems. what i would personally do first is download the stock samsung firmware for consumer/non demo mode tablets and flash that. then just follow root procedures and all that.
I could be mistaken, but I don't believe that's an actual LDU device. LDUs usually have an X at the end of the model number (ie SM-N900X), and I've only seen LDU phones, never any LDU wifi-only tablets. BTU is the region code for the UK, you probably just have a normal UK tablet with retail mode software on it. The hardware and firmware on the device are no different than a retail UK device, but it's running a special Samsung Retail Mode that restricts a lot of functions.
If you know the proper passwords, you should be able to remove the retail mode. Flashing a stock firmware might not work, as the retail mode software is a user app and NOT part of the device's firmware (unless you DO have an LDU, but based on the model number I don't believe that's the case), but it's worth a try. A factory reset would remove the retail mode, but some of the newer retail mode software prevents you from doing that.
Hey guys, so I have a US Live Demo unit I got from ebay a couple days. I decided to try and flash through odin the SM-G960U1 Pie update and now it looks like my Galaxy S9 is stuck.
I get an error that says: Secure Check Failure: Modem. Which is weird because I was under the impression that demo units don't have Modems since they can't be used as phones.
Then it tells me the device is locked.
Does anyone have any suggestions? I've attempted flashing the only combination rom I could find, but it doesn't work through Odin for some reason.
Hey did you find the firmware yet? I have the same issues. Anyone help?
I converted the firmware of G960XU to G960U
Hello Everyone, a google search brought me over here to these forums towards this thread about the same specific phone! anyone has any idea how I can change the flash of the demo unit? I'm new to this and would like to get all the useful information as possible. Also, I know for sure demo unit's can't be connected to a carrier as their motherboards doesn't have an IMEI/baseband (found out all of this through google searches) now, I'd like to know if I were to change the motherboard, are there possibles to use the phone?
Hi, I recently bought an s9 sm-g960u from eBay. I'm based in the UK. The phone is not receiving updates and I've been told my Samsung that this is because it originated from outside the EU. If I want to update it it looks like my best option is Odin and I've looked through the tutorials on how to do so.
I'm just wondering if anyone can help with a couple of questions I still have. Given that I'm in the UK, can anyone recommend a firmware to flash to which will enable auto updates? Or am I stuck manually updating via odin each time?
Also, what are the risks involved, say if the usb port fails halfway through the update. Will this brick the phone?
Sorry for the novice questions I'm just trying to weigh up what to do!
I am by no means a tech savvy person so please bear with me. Last year I purchased a Galaxy Note 10+ from Swappa. I thought I had properly inspected the device and it seemed flawless. Over the past year I was aware that Android 10 had been released and was waiting patiently to receive the update. For the record this phone was advertised as unlocked and associated with no carrier. I run the device via AT&T. I have since figured out that the IMEI number does not match the device and only after finding an additional IMEI on the outside of the device did I discover this phone was originally a Sprint product and had been altered in some way. The phone will not update.
The device was last successfully updated October 3, 2019. It is currently running Android version 9 and One UI version 1.5
When I manually check for updates the system says I am up to date…. Obviously this is not the case. I suspect that the alterations to this phone that I was unaware of until recently are playing an active role in the stagnation of my updates.
I’m not sure what to do at this point. I’ve seen a few things about using Frija and Odin to force a system update in some way, but all of this is absolutely a foreign language to me. This was my first Swappa purchase and I’m really disappointed at this point. If anyone could offer some constructive advice (in layman's terms) it would be greatly appreciated.
Samsung Galaxy Note 10+
Model #: SM-N97U1
Download the latest firmware from Frija and flash with Odin. Once firmware is loaded, extract it leaving you with files BL..AP..CP..CSC..HOME_CSC.
Open Odin put BL in BL spot, AP in AP spot and so on. When using csc it will wipe device..I suggest saving any important things to SD card or computer. But since you said device is messed up I would do a factory reset anyway.
Sent from my SM-A300FU using Tapatalk
I personally regret that I updated my note10+ from pie to Q, on pie, the battery lasted longer, and the starage management in Q is somewhat problematic for some apps, I definitively liked Pie more.. But that is just my opinion