is it dangerous to install firmware for other carriers to my unlocked phone - General Questions and Answers

Hello, i want to update my Samsung Galaxy S Plus from 2.3.5 (xxkpf) to 2.3.6 (xxkq7) but it says its for DTB (another carrier)? i have a Norwegian phone (unlocked) but is it dangerous to update, will it destroy my phone or something?
Or can i just go ahead and download. And how du i update with Odin?
-Thanks guys.

As long as you have and know how to use odin/heimdall you should be fine. I was experimenting a while back when I had my Verizon Fascinate on Sprint and I flashed the Sprint Samsung epic modem. It completely borked the entire radio, however I was able to re-flash the original modem and it was fine. Read up on the recovery options for your phone first and check the specific forum for your phone. Also in the future please ask device specific question in the proper forum.'
http://forum.xda-developers.com/forumdisplay.php?f=656
Your section is here.

Related

[Q]

Hello all,
!st time poster here. Hopefully I'm in the right place.
I have a rogers Galaxy s2 lte that came to me rooted. I flashed it back to stock using the steps here: http://forum.xda-developers.com/showthread.php?t=1342348
It all worked extremely well, phone boots and runs great, has all the rogers bloatware on it.
Only problem is, when I plug into Kies it tells me "Your device does not support software upgrading via Kies"
Current firmware version shows: I727RUXKJ7/I727RRWCKJ7/I727RUXKJ7/I727RUXKJ7 (ATT)
Any suggestions would be appreciated, thanks
Hey and ya your in the right place. You make sure you downloaded the i727R file not the i727. And also make sure you have the drivers installed on your computer for the phone
Use the sammobile tar and it will fix that. The i727r one

Needed Cspire users, especially SG2 SCH-R760

I am of need of some information. 3 days of bits and pieces here is where I'm at.
I rooted this phone with droids kernel and installed a few different roms only to find that I had a non locking GPS. So after several threads I found I needed to return to stock and get a lock. Here is where the problem started. I have never found a Cspire stock file for the SCH-R760 the best match I could find was a USC easy upgrade tool on samsung. Flashed the util and got a stock lock. After several buil.prop edits apn edits never could get data to work. SO I found a generic carriers stock FF24 total tar package posted by Mcadder on the USC site flashed it with odin and checked the efs clear to wipe out all the USC stuff. When I came out of the flash all device information was gone and prl was gone. So then I went into ##3282## changed all the information that I had to get voice text and prl back. So I'm now rooted with no data.
I need someone who is on Cspire to go into ##3282## and give me some information so hopefully I can get data back.
Also if anyone has a default build.prop for this phone Please post. I have asked in other post but not finding to many people with a Cspire SG2 that can help.
I can help
jasonc331 said:
I am of need of some information. 3 days of bits and pieces here is where I'm at.
I rooted this phone with droids kernel and installed a few different roms only to find that I had a non locking GPS. So after several threads I found I needed to return to stock and get a lock. Here is where the problem started. I have never found a Cspire stock file for the SCH-R760 the best match I could find was a USC easy upgrade tool on samsung. Flashed the util and got a stock lock. After several buil.prop edits apn edits never could get data to work. SO I found a generic carriers stock FF24 total tar package posted by Mcadder on the USC site flashed it with odin and checked the efs clear to wipe out all the USC stuff. When I came out of the flash all device information was gone and prl was gone. So then I went into ##3282## changed all the information that I had to get voice text and prl back. So I'm now rooted with no data.
I need someone who is on Cspire to go into ##3282## and give me some information so hopefully I can get data back.
Also if anyone has a default build.prop for this phone Please post. I have asked in other post but not finding to many people with a Cspire SG2 that can help.
Click to expand...
Click to collapse
What specifics do you need from there. I see lots of information?
If you have this fixed already. Are you staying with the original load for this phone or did you find a ROM that works? I am wanting to flash my CSpire S2 and hope to find a jellybean load to work. I remember having trouble with the data on my S1 after flashing and went back to the original load.
Needed to close this. I got it all fixed and yes ,Using CodeName Android that was ported to USC then reported back to cspire.
need help
jasonc331 said:
Needed to close this. I got it all fixed and yes ,Using CodeName Android that was ported to USC then reported back to cspire.
Click to expand...
Click to collapse
Hey, I'm suffering from the same problem. Accidentally flashed a US Cellular ROM and now i have no data.
Can you post the steps you took to fix this?
jasonc331 said:
Needed to close this. I got it all fixed and yes ,Using CodeName Android that was ported to USC then reported back to cspire.[/QUOTe
Did flashing a us cellular custom ROM to your cspire Samsung galaxy s2 do this or did you lose your data by updating the firmware through us cellular? What I am asking is if it is safe to flash a custom ROM made for a us cellular galaxy s2 to my cspire galaxy s2??
Click to expand...
Click to collapse
tvaughn1 said:
jasonc331 said:
Needed to close this. I got it all fixed and yes ,Using CodeName Android that was ported to USC then reported back to cspire.[/QUOTe
Did flashing a us cellular custom ROM to your cspire Samsung galaxy s2 do this or did you lose your data by updating the firmware through us cellular? What I am asking is if it is safe to flash a custom ROM made for a us cellular galaxy s2 to my cspire galaxy s2??
Click to expand...
Click to collapse
It was caused by running the easy upgrade tool from Samsung, designed for US cellular . I personally run stuff for the Epic4g posted here.Some say it is not wise to do so because they aren't exactly the same,but I have had little issue running CM10,PA,AOKP,AOSP.
Click to expand...
Click to collapse

[Q] HELP G920T flashed wrong carrier stock ROM

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)

Should I flash my Galaxy S7 Verizon to stock firmware in West Africa?

Hello.
I have a Galaxy S7 that I got about 5 weeks ago. I paid to have it in the box but the person got a secondhand one. I am in West Africa but someway somehow I got a Verizon one that is unlocked for any carrier. Anyway I checked and some functions were not working. Private mode is not working, there's no software update option anywhere (I checked developer mode) and some features I've seen on YouTube are not even on the phone. I'm stuck on Android 6 and can't update so I made up my mind to flash a custom ROM but turns out Verizon's bootloader is locked which will make such a task impossible. Some days ago though, I found out that official Verizon ROMs can be flashed without unlocking the bootloader and this raised some questions which I want to ask here.
Here's the info at the about phone page
MODEL NUMBER - SM-G930V (there's Verizon on the back of the phone so I think this is true)
ANDROID VERSION - 6.0.1
BASEBAND VERSION - G930VVRU4API3
BUILD NUMBER - MMB29M.G930VVRU4API3
1. Can I really flash a stock Verizon ROM for the Galaxy S7 without bricking my phone and with a locked bootloader?
2. If I were to flash a stock Verizon ROM will the phone be locked to Verizon again? I'm asking this because this is the only phone I have and I'm supposed to use this for 2 years!
3. Should I flash the same baseband version or will another Verizon one work?
4. If all the above questions are true, where can I get official Verizon stock ROM for my device?
If you have any questions for me please let me know.
Thanks
TheMannyzaur said:
Hello.
I have a Galaxy S7 that I got about 5 weeks ago. I paid to have it in the box but the person got a secondhand one. I am in West Africa but someway somehow I got a Verizon one that is unlocked for any carrier. Anyway I checked and some functions were not working. Private mode is not working, there's no software update option anywhere (I checked developer mode) and some features I've seen on YouTube are not even on the phone. I'm stuck on Android 6 and can't update so I made up my mind to flash a custom ROM but turns out Verizon's bootloader is locked which will make such a task impossible. Some days ago though, I found out that official Verizon ROMs can be flashed without unlocking the bootloader and this raised some questions which I want to ask here.
Here's the info at the about phone page
MODEL NUMBER - SM-G930V (there's Verizon on the back of the phone so I think this is true)
ANDROID VERSION - 6.0.1
BASEBAND VERSION - G930VVRU4API3
BUILD NUMBER - MMB29M.G930VVRU4API3
1. Can I really flash a stock Verizon ROM for the Galaxy S7 without bricking my phone and with a locked bootloader?
2. If I were to flash a stock Verizon ROM will the phone be locked to Verizon again? I'm asking this because this is the only phone I have and I'm supposed to use this for 2 years!
3. Should I flash the same baseband version or will another Verizon one work?
4. If all the above questions are true, where can I get official Verizon stock ROM for my device?
If you have any questions for me please let me know.
Thanks
Click to expand...
Click to collapse
Yes, you can flash Verizon stock firmware without issues, as long as you are not trying to flash an older Verizon stock firmware than the version you already have. In other words, you can upgrade, but you can't downgrade.
As for flashing a west African firmware, Nn, Verizon devices have a locked bootloader, the locked bootloader will not allow you flash anything except Verizon stock firmware. Attempting to flash anything from another region or from a different device will only result in a soft-bricked or hard-bricked device. You can only flash the Verizon stock firmware for your specific model number.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Yes, you can flash Verizon stock firmware without issues, as long as you are not trying to flash an older Verizon stock firmware than the version you already have. In other words, you can upgrade, but you can't downgrade.
As for flashing a west African firmware, Nn, Verizon devices have a locked bootloader, the locked bootloader will not allow you flash anything except Verizon stock firmware. Attempting to flash anything from another region or from a different device will only result in a soft-bricked or hard-bricked device. You can only flash the Verizon stock firmware for your specific model number.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi! Thanks for replying! So where can I get a Verizon stock firmware that is an upgrade of mine and what region should I download from? Also which version of ODIN should I use?
Thank you very much!

Please help with switching firmwares, kind of a weird situation.

Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
finshan said:
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
Click to expand...
Click to collapse
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Youdoofus said:
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Click to expand...
Click to collapse
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
finshan said:
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
Click to expand...
Click to collapse
you cannot go backwards in bootloader revisions, but you can go backwards in android versions as long as theyre on the same BL revision(not likely, but who knows? I didnt look yet). Also, the worst thing that could happen if you try to flash an older BL version is that itll fail in Odin and will still allow the phone to boot normally (usually, and if it doesnt, its still fixable). The only issue with booting it after flashing new firmware with your current sim is that itll install the carrier specific stuff on the phone so long as the CSC needed for that is in the multi CSC pack you flashed on the phone, and if it does install the carrier crap you dont want, just factory reset it and reboot with the actual sim you want you use
no problem man, thats what we are here for

Categories

Resources