Related
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
August 2017 Android security patches.
Fixed an issue where device was unable to connect and pair with some Bluetooth® Low Energy (BLE) devices.
Click to expand...
Click to collapse
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
This update prevent downgrading for older builds?
enmanuel255 said:
This update prevent downgrading for older builds?
Click to expand...
Click to collapse
I doubt it since the only time that really happens is when the number in the bootloader is increased.
For example, the first time the VZW S5 was updated to prevent downgrading was when the firmware version went from G900VVRU1BOD5 to G900VVRU2BOE1.
The VRU1 and VRU2 are the bootloader versions. Once updated to VRU2/VRS2, you can't go back to VRU1. For some reason they keep changing back and forth from VRU2 to VRS2 at random times. The past few updates have either been VRU2 or VRS2 but you can still go all the way back to the first firmware with VRU2.
TLDR; Since this firmware is using the VRU2 bootloader, it is very unlikely that it will prevent downgrading.
On a side note, this is the longest that it has taken for the complete Odin firmware to be uploaded to Samsung's servers. The update was out the 13th. Normally it takes 3 days for it to be available on their servers and it still isn't. I even tried using the Verizon Software Upgrade Assistant and both of my S5's say they are up to date on QF2.
It's rolled out:
Checking firmware for SM-G900V/VZW/G900VVRU2DQF2/G900VVZW2DQF2/G900VVRU2DQF2/G900VVRU2DQF2
Model: SM-G900V
Version: G900VVRU2DQH2/G900VVZW2DQH2/G900VVRU2DQH2/G900VVRU2DQH2
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900V_1_20170824083446_06zw9gofua_fac.zip.enc4
Size: 2292181872 bytes
LogicValue: 0zmklm1qb9k6sfxe
Click to expand...
Click to collapse
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
bbsc said:
It's rolled out:
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
Click to expand...
Click to collapse
Yep I literally just saw that it was. I checked at 12:30am EST and it wasn't.
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems, other than the security related bluetooth problems.
Dudash said:
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems
Click to expand...
Click to collapse
See below.
Lost Hotspot Functionality
Once I flashed this update I lost the ability to bypass Verizon's check to use the hotspot functionality. Now it keeps checking my account and wanting me to pay for the service. Is there anyway I can get around this again, as I was able to with basic root?
I did flash the Developer Bootloader Friendly version using FlashFire.
In addition to my previous post.
Ok, I've been experimenting for a few days with two units of SM-G900V and two pairs of Samsung Level Active wireless earbuds.
I was walking in the same places and listening the same music in the same conditions with different earbuds and different phones, having different (DQF2 and DQH2) firmware (kernel, modem, recovery). In all cases the phones were loaded with the same /system ROM - stock-near ALEXNDR.G900FXXS1CQH1
My conclusion is: DQH2 keeps bluetooth connection much worse than DQF2.
I cannot say that we have a crystal-clear sound in one case and a crappy stuttering in the other.
But the difference is noticeable and obvious.
That's why I personally am reverting back to DQF2 firmware.
wbr.
Updated to this build from QA1, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. No problems here with BT streaming music 2hrs a day in my car for 3 days.
After Flashear everything is fine except autorotation, it does not work for me
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock non rooted retail download available? I would like to revert completely to stock.
MrTrumpz said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock retail download available? I would like to revert completely to stock.
Click to expand...
Click to collapse
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Dudash said:
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Click to expand...
Click to collapse
Thanks so much. I appreciate the response.
If i unlocked my bootloader on PB1 firmware, will I have issues flashing this firmware? For some reason I've always thought updating my firmware without updating the bootloader like I originally had to would cause some serious problems. Or did I misinterpret the necessity of updating the bootloader to match the firmware? Is that even an actual problem if they don't match?
Maphack said:
Is that even an actual problem if they don't match?
Click to expand...
Click to collapse
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
bbsc said:
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
Click to expand...
Click to collapse
Sorry, I was unclear. I unlocked my bootloader and chose PB1 as the firmware to be... Unlocked on, I guess? Not sure the proper phrasing for it.
So I have an unlocked bootloader, but am afraid of updating my firmware in case that messes up something.
If you already answered my question and my response to your question is just due to my lack of knowledge, I apologize.
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
bbsc said:
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
Click to expand...
Click to collapse
Thanks. Yeah, I'm already on an unlocked bootloader running 7.1.4. I'll look into updating an unlocked bootloader. I appreciate the help.
Or is there even a point for me to tweak my phone at this point?
Maphack said:
Or is there even a point for me to tweak my phone at this point?
Click to expand...
Click to collapse
None.
Modem upgrade, maybe...
But if you're satisfied, don't repair a working thing.
Help
Dudash said:
According to the Verizon Galaxy S5 Update Page:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Currently this is my System info.
Model - SM G900V
Baseband - G900VVRU2DPD1
Kernel - 3.4.0 [email protected] #1
Build Number - MMB29M.G900VVRU2DPF4
I flashed NI2 using Odin and have Safestrap. I have been away from this phone for long so lost touch of the updates. I have not flashed the Dev bootloader or unlocked it as far as I remember because when I installed this rom, there was no method to unlock bootloader. Can I still flash the QH2 update on this in Safestrap, the Developer Friendly version or the official.
I have a SM-G955U1 I'm trying to downgrade to Nougat since Oreo totally borked the bluetooth in both my cars (both BMW's - audio connects ~50% of the time, phone book no longer transfers).
I'm failing to flash G955U1UES2AQL1 with Prince Cosmey Odin v3.12. The error I keep receiving is:
SW REV CHECK FAIL : [abl]Fused 3 > Binary 2
I've also tried to flash G955USQS2BRB1.
A quick Google says it's because I'm trying to downgrade versions, but doesn't this model have an unlocked bootloader?
What am I doing wrong? Any guidance is greatly appreciated.
What firmware are you on now? If your on bootloader 2 there's no going back to bootloader 1 which is nougat. Bootloader's are locked on U phones, once you upgrade there's no going back........they took that directly from IOS book of being a holes.
str8shot said:
I have a SM-G955U1 I'm trying to downgrade to Nougat since Oreo totally borked the bluetooth in both my cars (both BMW's - audio connects ~50% of the time, phone book no longer transfers).
I'm failing to flash G955U1UES2AQL1 with Prince Cosmey Odin v3.12. The error I keep receiving is:
SW REV CHECK FAIL : [abl]Fused 3 > Binary 2
I've also tried to flash G955USQS2BRB1.
A quick Google says it's because I'm trying to downgrade versions, but doesn't this model have an unlocked bootloader?
What am I doing wrong? Any guidance is greatly appreciated.
Click to expand...
Click to collapse
Sounds like your on the version 3 bootloader who I believe only noug firmware is the binary all the rest is Oreo. You may be outs luck until either root to fix or Samsung releases a fix
Huh. That sucks. I bought the unlocked version of the phone thinking it'd be totally unlocked (bootloader and all).
Might be time for a pixel. :/
I'm pretty sure that you cannot unlock your snapdragon bootloader kn your US device. You have a "Sim unlocked" device that will work with any provider.
/\- When a manufacturer says "Unlocked" all they mean is sim unlocked. No going back right now, best you could do is flash PartyCyborg Rom for Snap and that will get you to nougat as well as root, since this does work with v3; but you'll only be able to charge to 80%.
Delete
bmxmike said:
/\- When a manufacturer says "Unlocked" all they mean is sim unlocked. No going back right now, best you could do is flash PartyCyborg Rom for Snap and that will get you to nougat as well as root, since this does work with v3; but you'll only be able to charge to 80%.
Click to expand...
Click to collapse
I desperately need downgrade from oreo to nougat version and this is my problem, the bootloader version...
there is something like nougat with bootloader 2 could be official (preferably) or custom rom (last option)
That's the issue. There is no bootloader 3 nougat, you are on 3 not 2 that's the issue with your downgrade. The only thing I see working is flashing PartyCyborg Rom which works on v3 bootloader and pretty sure is still nougat. Go check his thread as I know there are a few things like o only being able to charge to 80%
Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.
details
Another note: AP SW Rev is identified as B:2 K:1 S:1
I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.
JeffDC said:
I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.
Click to expand...
Click to collapse
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
same problem here... If an solution available pls write here
anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
Flashing stock rom and waiting 7 days would be the safe option.
I am not exactly sure what you are trying to achieve.
https://www.samsung.com/us/support/frp/
anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier, and when the phone setup was completed and booted into system, the OEM unlock was available.
Re: CRED I believe once it has been installed on a phone, you can not go back to a previous version (pre CRED).
JeffDC said:
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier,.
Click to expand...
Click to collapse
I wonder if I can do this date trick with combination FW to enable OEM unlock.
anonan said:
I wonder if I can do this date trick with combination FW to enable OEM unlock.
Click to expand...
Click to collapse
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/
Hi, could you send me a link of the combination firmware please Can't find it anywhere My email address is [email protected] I currently have similar experience of yours I thought everythings gonna be okay but it was too good to be true Help
anonan said:
Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.
Click to expand...
Click to collapse
anonan said:
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/
Click to expand...
Click to collapse
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Excellent.
I still can't get this to work. Have you purchased Samsung tool Pro to do the flashing of individual boot files? What version?
Hi there. I already bypassed the frp.. If you need. Hp with android 8.0 even with the binary 2. I have some comb files and working stock roms through odin. Feel free to pm me via my email [email protected]. Thanks!
how
darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx
oz_ezekiel said:
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx
Click to expand...
Click to collapse
Download latest odin and try again. I too got stuck in similar situation. Realised the issue is due to Odin. If you are using latest and encountered this error, try one version earlier.
I too can confirm that the combination-ROM works like a charm with odin. FRP kinda unlocked itself
Id like to downgrade my S7 from nougat to marshmallow. My current lowest factory reset option is nougat on bootloader version 3. Id like to downgrade to a downloaded stock firmware that uses version 1 of the bootloader.
my device is currently rooted and carrier unlocked
ive made a full backup of the nougat system, before ive done anything to it other than the rooting.
ive been reading around that some people were able to bypass the downgrade bootloader lock error in odin by first going into their desired downgraded firmware tar files and deleting any file that ends in .bin , and then successfully been able to flash the older firmware. what I want to know is if i decide to try this, and it still doesnt work in odin, or something still doesnt work properly - am i still able to fully restore from that backup ive just made? has anyone done this without issues? i hate the look and feel of nougat and oreo looks and feels the exact same...
i did make another thread about downgrading, but i didnt know nearly as much at the time. Been told downgrading is impossible and thats true, officially speaking. Id just like to know if anyone has been successful with this workaround.
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Beanvee7 said:
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Click to expand...
Click to collapse
model is sm-g930w8 but yes OEM unlocking is on, and so is usb debugging just to be on the safe side. It is running the very first version of nougat right now, 7.0. But the security patch is from feb 2018. Ive read that the bootloader itself is unlocked on this version of the phone though, its just that downgrade protection in the software that could get in the way, if what i read was correct? in the same place was where i read that deleting those bin files from the firmware i want to install would be a good workaround, it would make the bootloader not check it at all if i read it correctly.
i havent tried anything yet, ive been doing my research first to stay on the safe side. it might work without issues, but I want to be prepared for if issues do arise, what the correct next step should be to keep the device itself not bricked
Yea not 100% sure for the G930W8, it's the same SoC as the G930F but the firmware restrictions could be different since it's the Canada specific version
so, i decided to brave it and try it, since to read around you find alot of conflicting information... i was suspecting that odin would fail shortly after starting at sboot.bin if it was the bootloader thats the issue. but it didnt. it failed the very next step after that at param.bin.
anyone happen to know what param.bin means?
What files are you trying to flash? I have had the same problem, even though the bootloader is unlocked the device has efuses that prevent downgrade to older binary. I was using U2 binary and only managed to downgrade to nougat u2 binary version. Even when I skipped bootloader files, marshmallow would still give an error that system.img is version 0 where as device is v1
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Softwarehttps://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
spawnlives said:
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
Click to expand...
Click to collapse
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
spawnlives said:
tsam19 said:
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Have rooted the device no problem with magisk and patching the original boot img file. Then flashing patched boot img via odin. Causing device verification to need to reformat the device, resulting in correct root.
Once a device , this device is rooted, no official updates can be installed anyway. When you try to uodate software, a pop up shows as the device recognises the software has been modified.
As for TWRP there ISN'T any version of TWRP available for the Samsung Galaxy Active Tab2 (SM-T395). I have even emailed the makers , developers of TWRP why there isn't one in their device inventory list on their webpage.
So no TWRP, and NO custom roms either for this model.
My concern , was all about finding a valid , safe way to downgrade back to original Nougat 7.1. And until someone can produce a working image with a BL with binary 4. Then there's only one optiin and that is to buy another untampered device with Nougat 7.1 out of the box and leave it un updated. :good:
Thanks for replying.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
To answer your question of how is downgrading such a big problem, it is due to security reasons, to keep your device as secure as possible with the newest available software and the latest security updates.
Sent from my SM-S767VL using Tapatalk