I rooted my note 5 (sm-n920w8) and installed sick as hell rom. Apparently, I installed the t-mobile version of the rom (sm-n920t), as this is what the model number of my phone now says.. I am now trying to unroot my phone, but odin fails to flash the stock firmware for model sm-n920w8. I dont want to just flash the t-mobile firmware, as I am worried it will make the phone useless in my area. Any solutions to this problem?
Related
Hello,
Just bought a topaz blue unlocked S6. I think it came from an Asian country. The phone arrived perfectly with plastic in box with the same IMEI as phone. However it was rooted with SU. I went into the app and clicked to remove root. It was on 5.0.2. They I tried to flash original firmware with Smart Switch with no success.
I used odin to flash stock 5.1.1 firmware from the UK. The firmware was for 920F. It went all good. I have LTE, SMS and phonecalls. However, sometimes the baseband appears as unknown, but I still can make calls and have LTE. And it still shows the same IMEI as it is on the box and it has always shown it. Is there a way to fix this? Now, I try to flash stock firmware with Smart Switch and it says it can't initialize.
I would REALLY appreciate help. I would love to be able to flash stock firmware from Smart Switch.
I'm in México with Telcel, which uses the same bands as AT&T.
P.S. I really searched and couldn't find anything on my specific situation.
That happened to me when I was still on 5.0.2 and flashed only the 5.1.1 modem. I would suggest downloading the modem.tar file and flash that. Should all be good after that.
I'm currently downloading G920FXXU1AOD4 BTU firmware to flash it with Odin. Might that help me better? My main goal is to be 100% stock without any weirdness. And having Smart Switch recognize my phone!
Well, I'm sad.
calot said:
I'm currently downloading G920FXXU1AOD4 BTU firmware to flash it with Odin. Might that help me better? My main goal is to be 100% stock without any weirdness. And having Smart Switch recognize my phone!
Click to expand...
Click to collapse
You cannot downgrade to 5.0.2 from 5.1.1. Your bootloader will not support. I have the issue with 3G connection. Where to get the Modem.tar?
I'm thinking no, but wondering if it is OK to flash a stock Odin fw that is different from the device's carrier? Has anyone tried this? From what I recall from other Samsung devices, worst case is it would fail but not brick the phone. But still want to see if there's any feedback for this phone.
Have a SM-N915V here (SIM unlocked) in Canada and would like to flash a Rogers stock fw onto it if possible.
I guess NO
Reason : both the device have different partitions(that is the only thing i guess). if partitions can be matched it can be tried as hardware is more or less same.
Still i would suggest take a full Nandroid backup including the efs, and flash the firmware, even if you brick you can recover.
Thanks. I assume this is where .PIT's come in - but I understand the danger of force-flashing a PIT of one model to another model. Too scared to brick. Will stick with Verizon firmware ;D
I recently received a T-Mobile Galaxy S6, and it was rooted and had a custom kernel, which was a complete mess (the person who owned the phone previously clearly did not know what they were doing) so I just wanted to restore it back to full stock.
I am decently experienced with ODIN, rooting, custom firmware etc, but I have just done one of the biggest rookie mistakes I have ever done. I had accidentally downloaded the most recent firmware for my G920T, not realizing that the file was not for T-Mobile. It was the (XAR) carrier (I believe that is C-Spire but i could be wrong) and the latest was PK1.
It flashed perfectly and all seemed fine until I decided to unlock the device. The T-Mobile S6 requires the use of the "Device Unlock" app and since I had flashed the wrong ROM, the phone thinks the Device Unlock app is not compatible. When I put a different GSM SIM card in the phone, it prompts me to use the Device Unlock app.
I do not have a previous NANDROID backup from the original T-Mobile ROM, and now that I am on the lastest Bootloader for XAR, it will not let me downgrade. I have tried flashing pretty much every MM bootloader and TWRP for both T-Mobile and XAR and none will work (except for what is currently on the device of course) I always get the error "Device: 5 Binary: 4" (sometimes the binary is 3, depending on which version of MM rom or BL I try)
To sum it all up, I am on PK1 (latest for XAR) and I need a way to get back to the official T-Mobile ROM (latest is PD1). Is there a magic method to get this figured out or am I pretty much stuck with what I got until T-Mobile releases an update that is PK1 or higher?
Thank you in advance to all of you that take your time to help (and I am sincerely sorry if I am posting in the wrong section)
I have an 950U running N950USQS2BQL5 firmware but the boot screen and software is ATT branded.
It's stuck on 7.1.1 for obvious reasons. Is there any way to get it to Oreo besides flashing ATT firmware on it?
Thanks for all help!
If I remember right, the files from Samsung look at the installed sim card and install the correct version from that. You "should" be able to Oden the latest firmware and it will correct itself. It will wipe everything on the phone, so make a backup.
So both my phone and vzw branded phone are same model, and android 11 firmware is out for verizon and my phone received the G715U1UEU7BUC3 ota 11. Is the latest Odin software and verizon G715USQU7BUC1 firmware what i need to get it done?
Also, do i need to do the full flash or can i get by with just one file that includes all the vzw bloatware. From what ive read i can get by with flashing just the userdata file. Once complete ive also read i need to do a factory reset and that it can be done i DL mode. Is that true? Finally can i leave my sim in for this or should it be out
?
?
Anybody??
Not even a response from Europe where they must hand these xcover pro's out with every gas tank fillup.
I have the latest version of odin installed and downloaded the verizon ota firmware G715USQU7BUC1 and am ready to give it a shot. I would just like a little confirmation im on the right track. Bootloader versions are the same. (bootloader is still locked) Even a grunt would do..........