My brand new unit has updated VRALG1 firmware and VRLG1 radio. Knowing the original "Root66" was built from VRALF2 firmware, I'm thinking I'm stuck - for the moment, right? I *could* downgrade the SYSTEM.IMG to the insecure Root66 (VRLF1), but still hardware version 10, just like the first ones shipped on "Day 1" in North America.
Any suggestions, folks? I've not found anything specific to rooting VRALG1 firmware, yet. Everything seems to be VRALF2-specific.
Related
I'm just wondering how people are upgrading to the KitKat bootloader. I haven't been on in nearly a half year and I'm sure I've missed something. Will I have to put on my stock firmware and upgrade from there first? Is there even a stock KitKat ROM for the XT925?
I am not sure if Fido has released their kitkat update yet, however I am aware that many others european and south americans have such as orange and others. So what we have been doing is flashing stock from those carriers and either taking the OTA or flashing it as well.
check here,
http://forum.xda-developers.com/showthread.php?t=2760840&page=52
Well, I managed to upgrade my bootloader when I used the Brazil stock ROM plus modified OTA zip file but my modem partition got gibbled... I don't have LTE anymore. Well, not a band that works here.
I did see there was a patching process when I did the KK upgrade though and I seem to recall the modem partition being patched. Think it'll work if I used swapped the Rogers one in before I do the KK upgrade? I'm about to go back to 4.1.2 (erasing the partition and tz lines).
I've tried flashing BTU - the SIM free firmware - with ODIn, and whilst it seems fine, updates don't seem to work. I have factory reset after every flash yet still software updates don't work. I know this because the version of BTU firmware I flashed was at least three versions old. When I check for updates I just get 'your software is up to date' - yet there are at least three newer versions of BTU on Sammobile.
The only thing I can think is that the low-level Computrace software that Samsung allegedly puts in their firmware is messing with the updates server. I know that Computrace still exists in the App Manager when I flash BTU. I've also just flashed 5.1.1 and it's still there.
I'd like to know if anyone with an EE S6 has managed to successfully get updates after flashing to a stock ROM, or if EE have crippled it. I wouldn't mind using EE's firmware as there is next to no bloatware; but their updates are horribly slow.
I should point out that I have never rooted the phone and the KNOX counter is not tripped. I've only ever flashed official firmware.
Thanks.
It could be your CSC is still pointing to EE and not BTU?
Nope, CSC shows as BTU when I boot into recovery.
Hi All,
I have a moderate experience in flashing firmwares and modding my samsung devices over the years.
I have recently purchased an S7 which is unfortunately a SM-G930V model, i thought it would have been the SM0G930F which would have made life much easier.
I want to know if it is possible to get the original Australian firmware or even generic stock firmware on this device?
My issue is with the network settings where i have manually put in APN settings my match my carrier and 4G coverage in australia.
If not am i able to just flash a different baseband to this device preferably Australian?
I have read that flashing a different model firmware will soft brick the device, i just want some insight before i start breaking things, also what are my options.
Much appreciated, thanks, Will
You have the snapdragon s7, you can't flash the exynos 930f firmware on it, you can only flash the american firmware. You might have luck with the 930u unbranded firmware just do some research on it.
Thanks mate,
I'm going to flash this firmware using ODIN, do you know if it will be successful?
https://forum.xda-developers.com/att-galaxy-s7/how-to/xda-community-love-g930u-t3415875
not sure how to check my bootloader version etc
No clue, goto the verizon subforum and see if anyone flashed the 930u firmware on their 930v.
Just tried to flash the firmware to my phone and recieved an error, the phone is now stuck at download mode with error:
sw rev check fail : [system] fused 3 > binary 4
this means the bootloader won't accept the firmware?
LOL, guess ill try another firmware.. Any ideas?
Hi guys,
it's been a few weeks that I'm struggling to understand why I'm not getting software updates.
My phone is stock, never rooted nor flashed. It's been with this software since when I bought it.
My CSC is VDI and I was noticing that potentially the modem version on my phone (CP) is wrong.
Here's my details:
AP: G930FXXU1DQEI
CSC: G930FVFG1DQE3
CP: G930FXXU1BPJJ
Model: SM-G930F
I was trying to figure out why I'm not getting updates and from what I can see here: http://fota-cloud-dn.ospserver.net/firmware/VDI/SM-G930F/version.xml I should have a different CP version in order to get the update (G930FXXU1DQD7) which also seems in line with what this firmware page has: https://samsung-firmware.org/download/Galaxy__S7__/n494/VDI/G930FXXU1DQEI/G930FVFG1DQE3/
Now, a couple of questions.
- Any idea of the why? Could it be just a mistake in the production of the device?
- Is my hypothesis correct that I'm not receiving updates because of this?
- Would it be safe to only flash the CP part with ODIN and let the device receive the OTA normally?
Looking forward to hearing your thoughts!
I've not heard of a modem stopping updates, but it's not an area I'm fully familiar with.
Flashing modems with Odin is probably the most harmless flash you can do as long as it's for the same android version (e.g. don't flash a nougat modem on a marshmallow device)
You could also try flashing the latest home_csc, and bootloader (BL) if you really wanted to. Both of those are pretty trivial to flash too. If you do flash csc just make sure it's home_csc, and regular csc wipes your data.
Beanvee7 said:
I've not heard of a modem stopping updates, but it's not an area I'm fully familiar with.
Flashing modems with Odin is probably the most harmless flash you can do as long as it's for the same android version (e.g. don't flash a nougat modem on a marshmallow device)
You could also try flashing the latest home_csc, and bootloader (BL) if you really wanted to. Both of those are pretty trivial to flash too. If you do flash csc just make sure it's home_csc, and regular csc wipes your data.
Click to expand...
Click to collapse
Hi, thanks for your reply.
I ended up flashing CP only for the firmware I was at and I straight away got the update notification and the subsequent security patches up to December 2017 ( was stuck at may ). I'm at the latest firmware for my CSC now.
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