Database Info

Downgrade MM to LP?

I know there are a lot of threads. I read it's impossible. But another says possible using pda file with pit info, but i can't file proper file for g920i.
Are there any workaround to dowgrade?
I googled everything, but no luck. Stuck on MM.
Mm battery is bad for me.
Can we install custom rom LP while on MM bootloader using twrp? I know that only the bootloader part cannot be downgraded. Have someone created a hacked bootloader or somehow?
Or maybe prefer upgrade to nougat? I'm afraid because i will not be able to get back to MM after that.

duke_dreadmoore said:
I know there are a lot of threads. I read it's impossible. But another says possible using pda file with pit info, but i can't file proper file for g920i.
Are there any workaround to dowgrade?
I googled everything, but no luck. Stuck on MM.
Mm battery is bad for me.
Can we install custom rom LP while on MM bootloader using twrp? I know that only the bootloader part cannot be downgraded. Have someone created a hacked bootloader or somehow?
Or maybe prefer upgrade to nougat? I'm afraid because i will not be able to get back to MM after that.
Click to expand...
Click to collapse
There is only one way and that's with an engineering bootloader but this breaks fingerprint other than that it's not possible to downgrade to lollipop even with custom Rom this is down to being on newer marshmallow bootloader.

sofir786 said:
There is only one way and that's with an engineering bootloader but this breaks fingerprint other than that it's not possible to downgrade to lollipop even with custom Rom this is down to being on newer marshmallow bootloader.
Click to expand...
Click to collapse
Thanks. Anybody did this already? I'm not using fingerprint so i'm fine.

duke_dreadmoore said:
Thanks. Anybody did this already? I'm not using fingerprint so i'm fine.
Click to expand...
Click to collapse
There is a guide in the general section I think, you might need to search for it. From what I saw last in it, some users got it working but others not so can't really comment on the success rate and plus it's nothing something I've done myself.

New Update - QH2

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.

Delete .bin files from older firmware to downgrade to an older bootloader version?

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

Downgrading my (unrooted) carrier locked At&t Note 8.

My note 8 had OneUI pushed to it about a week ago even though I kept refusing not wanting to while I was sleeping. It says my bootloader is v5. This is actually what it says (N950USQU5DSD3). My problem is that when I search for the firmware I'm wanting to downgrade to (the last oreo update possible for this particular phone) on Sammobile I can't find the one for At&t. I see ones for Verizon, sprint, etc. But nothing for at&t, which one am I supposed to use and where can I get it? This is going to be my very first downgrade/upgrade, really my first time doing anything like it on android. And I CAN do this right? There's nothing I should be aware of that makes what I'm trying to do not able to be done is there? The biggest reason I'm asking is because I have very limited tools to work with, I have a little 12" Acer aspire one (no disk drive) running windows 7 home basic, mobile hotspot from my wife's phone(the last software I tried to download and use came from xda out of a thread I found titled, "Stock Oreo N950USQS5CRF6 Odin*files*for AT&T*NOTE*8" it failed halfway through 2 nights ago during the beginning of storm, and the whole time it would only download around 32kbs so it literally to FOREVER! Only for it to fail halfway through. Was I wasting my time or was this in fact the firmware I'm looking for? If not, as I asked before, where could I find it?? Thanks a bunch for any help.

https://forum.xda-developers.com/at...n950u-stock-n950usqs5crf6-odin-files-t3821222
^^^^^^^Is this all I need? Do I need to follow this tutorial or a different one?? What version of odin, do I need anything else
Sorry for so much all at once, I really hate this update and want Oreo back.

https://forum.xda-developers.com/ga...m-n950u-u1-t3685884/post74087340#post74087340
Follow the steps from the above-linked post, and follow them very carefully. I did, and I was able to successfully downgrade from Pie to Oreo on my AT&T NOTE8.
I actually flashed the unlocked firmware, which has zero AT&T bloat. It works just fine for my needs. I don't think AT&T WiFi calling works on this unlocked firmware (I haven't tried - I don't use it).
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!

pyrolad said:
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!
Click to expand...
Click to collapse
A little off topic, but has anyone seen an AT&T security update for May yet? I'm still on April security, and it's basically mid June?

Tha k you I'll check it out when I get off work, I didn't know you could flash the unlocked firmware on a carrier locked phone

Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.

I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.

marhodges said:
Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.
Click to expand...
Click to collapse
Yes you CAN downgrade back to Oreo. BUT you MUST go to a bootloader 5 firmware.
---------- Post added at 07:55 AM ---------- Previous post was at 07:54 AM ----------
Superloud024 said:
I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.
Click to expand...
Click to collapse
Yes you can go to that firmware. You will want to back up and allow it to factory reset. Be sure to use the modified version of Odin. Go HERE, post #2

Question Android 13 downgrade to Android 12?

Is it possible to go from Android 13 One UI 5.0 back to Android 12 One UI 4.0? Android 13/One UI 5.0 is terrible in so many ways I am down with it. Is the bootloader the same or anything else that would cause me to downgrade back to Android 12? Let me know thank you!

oneandroidnut said:
Is it possible to go from Android 13 One UI 5.0 back to Android 12 One UI 4.0? Android 13/One UI 5.0 is terrible in so many ways I am down with it. Is the bootloader the same or anything else that would cause me to downgrade back to Android 12? Let me know thank you!
Click to expand...
Click to collapse
Odin is the only way, however doubtful whether it will let a previous firmware flash go through.

JazonX said:
Odin is the only way, however doubtful whether it will let a previous firmware flash go through.
Click to expand...
Click to collapse
Yeah Odin is no problem but that is what I am worried about. Trying to figure out if they changed to bootloader or something that wouldn't allow it to flash.

oneandroidnut said:
Yeah Odin is no problem but that is what I am worried about. Trying to figure out if they changed to bootloader or something that wouldn't allow it to flash.
Click to expand...
Click to collapse
How would you then block the future OTA's ?
Are you rooted ?

JazonX said:
How would you then block the future OTA's ?
Are you rooted ?
Click to expand...
Click to collapse
I am not rooted, Unlocked S22 Ultra but you can freeze the OTA updater. I had that done before and "thought" android 13 would be nice but boy was I wrong. Guess I will buy another S22 and sell mine lol

As long as bootloader is the same , going back to 12 is not an issue..which it is. To block future updates just install AdbAppControl and disable the software update.

butchieboy said:
As long as bootloader is the same , going back to 12 is not an issue..which it is. To block future updates just install AdbAppControl and disable the software update.
Click to expand...
Click to collapse
Is it the same bootloader? I guess I could download both updates and compare correct?

You can block info about update info too by download other version soft (older or even from A13) and flash only modem via Odin different from your current soft.
After that you will not see info about update.