Database Info

Xperia Z5c - How do I remove NFC Driver from 7.0 ROM before flashing via Flashtool

Is it possible to remove the NFC driver from a 7.0 Firmware ROM prior to flashing it with Flashtool?
Background:
I have the US version of the Xperia Z5c (E5803) which came stock with the 6.0 firmware (32.2.A.5.11), thus the Fingerprint scanner is disabled. Read that it could be activated by flashing the UK ROM (E5823) with Flashtool, which worked perfectly and had no issues. Now that Nougat v7.0 is available, I allowed the OTA upgrade to occur which brought the phone up to Build 32.3.A.0.376. Problem is that though everything else works fine, there was an NFC driver update that came along with it the breaks the NFC feature. If I try and activate NFC it just toggles on/off every second and is unusable. By reflashing the US version of the latest Build 32.3.A.0.376, NFC is fixed, but no more Fingerprint scanner. Reflashed the UK version and NFC breaks again.
The Ask:
Can I remove the NFC driver from the UK ROM 32.3.A.0.376 before flashing OR do I need to extract the NFC driver from the US ROM and place it into the UK ROM? If so, do I do this with Flashtool or is there another app I need?
Thnx,
Syver

ringsaker said:
Is it possible to remove the NFC driver from a 7.0 Firmware ROM prior to flashing it with Flashtool?
Background:
I have the US version of the Xperia Z5c (E5803) which came stock with the 6.0 firmware (32.2.A.5.11), thus the Fingerprint scanner is disabled. Read that it could be activated by flashing the UK ROM (E5823) with Flashtool, which worked perfectly and had no issues. Now that Nougat v7.0 is available, I allowed the OTA upgrade to occur which brought the phone up to Build 32.3.A.0.376. Problem is that though everything else works fine, there was an NFC driver update that came along with it the breaks the NFC feature. If I try and activate NFC it just toggles on/off every second and is unusable. By reflashing the US version of the latest Build 32.3.A.0.376, NFC is fixed, but no more Fingerprint scanner. Reflashed the UK version and NFC breaks again.
The Ask:
Can I remove the NFC driver from the UK ROM 32.3.A.0.376 before flashing OR do I need to extract the NFC driver from the US ROM and place it into the UK ROM? If so, do I do this with Flashtool or is there another app I need?
Thnx,
Syver
Click to expand...
Click to collapse
Provided that it doesn't mess with signature verification(if any), you should be able to extract from the US firmware and put it in the UK firmware.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Provided that it doesn't mess with signature verification(if any), you should be able to extract from the US firmware and put it in the UK firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is this done with Flashtool or another app? How do I identify the NFC driver?
Thnx,
Syver

ringsaker said:
Is this done with Flashtool or another app? How do I identify the NFC driver?
Thnx,
Syver
Click to expand...
Click to collapse
Still looking for guidance on this question...
Thanks

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.

Anyone has L19C636B380/360 full firmware package?

I had Nougat(L19C636B360) when I bought my phone. The box had model "AL-10" written on it although the firmware was of L-19. Anyways, an OTA update arrived, I clicked on update and it got bricked. I had never unlocked the bootloader, rooted or anything. After a lot of trial and error, I successfully got my phone working by flashing MM 6.0 - FRD-L19C900B131 through 'dload' method. But this firmware is buggy as hell. My phone's laggy, crashes constantly, the photos are worse etc.
A found a couple of stock firmware packages(L19C636B360) on the forum but they come with two separate files(update.zip and updata_data_full_hw_specxx.zip) and my phone doesn't support them(Installation fail). Also they are of only 2-2.5GB, whereas the one I successfully flashed is 3.3GB
Note : I have unlocked the bootloader now

And you are developer?

Wrong forum to post buddy.

SirDarknight said:
I had Nougat(L19C636B360) when I bought my phone. The box had model "AL-10" written on it although the firmware was of L-19. Anyways, an OTA update arrived, I clicked on update and it got bricked. I had never unlocked the bootloader, rooted or anything. After a lot of trial and error, I successfully got my phone working by flashing MM 6.0 - FRD-L19C900B131 through 'dload' method. But this firmware is buggy as hell. My phone's laggy, crashes constantly, the photos are worse etc.
A found a couple of stock firmware packages(L19C636B360) on the forum but they come with two separate files(update.zip and updata_data_full_hw_specxx.zip) and my phone doesn't support them(Installation fail). Also they are of only 2-2.5GB, whereas the one I successfully flashed is 3.3GB
Note : I have unlocked the bootloader now
Click to expand...
Click to collapse
Bro try flashing L19C636B130 1st then you will recieve a OTA L19c636B360
we have the same problem

june28dane said:
Bro try flashing L19C636B130 1st then you will recieve a OTA L19c636B360
we have the same problem
Click to expand...
Click to collapse
I also have the same problem, did that method work for you? (flashing L19C636B130 1st then) ???
help me plis!

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.

Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction

Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.

Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel

Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.

As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it

Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.

The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.

This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.