Need to downgrade s7 g930fd - Samsung Galaxy S7 Questions and Answers

Hello devs i need to downgrade s7 back to marshmallow.. is that possible by flashing m frimware ?
Anyone have tried downgrading back to Marshmallow after updating to dec security patches?

I've downgraded to MM from N a few times. Pretty simple, all you need to do is download the stock firmware from sammobile.com or updato.com and flash with Odin (both sites have a flash guide I believe).
Make sure you flash all 4 files.

Yeah bro??☺ successfully downgraded without any issues.. camera ,battery is far better in Marshmallow?

Bro.. fingerprint sensor is not working?.. while dailing *#0*# in sensor fingerprint it says initialisation failed..

I don't use the sensor so I never tested it during my roll backs. You flashed all 4 firmware files? BL, CP, CSC and AP?

Yeah ive flashed all 4.... fingerprint sensor is working only in nougat frimware..?

I know the bootloader differs in N to MM which impacts a few things but if you flashed all 4 it should be fine, I would suggesting trying to wipe cache/davlik but an Odin flash should have been a full wipe already.

Yeah..bro.. i hve cme back to n ..bzo of this issue

Is fingerprint wrng fr u?.. in mm

I don't have MM at the moment, it's been a couple months since I was doing my upgrades and roll backs

Hi all,
I need to downgrade a new g930fd (MFD 2018-01) as well to MM for xprivacy since I'm not one of the mass fools giving away all their accounts on their devices, everything on storage, phone numbers, IMEI, MAC address, etc. to every app that I need to run for my job, as well as every factory ROM and pre-installed app. Oh, I forgot to mention every app talking to like 5 or more mobile app tracking servers including graph.facebook.com!
Anyhow, I ran into the fingerprint sensor issue as well with downgrading to MM. It seems to be something to do with the S7's with a newer manufacture date since I have other older g930fd's I was able to downgrade and have the fingerprint sensor work fine.
It appears to be that the driver in Samsung MM ROMs isn't compatible with the newer fingerprint chips.
This is the only difference I could find in the sensor information:
Working Downgraded to MM Fingerprint Sensor
Flex ID 2291
Product ID 144
Sensor ID 4099
Non Working Downgraded to MM Fingerprint Sensor
Flex ID 295
Product ID 144
Sensor ID 4103
I'm guessing the fingerprint sensor drivers included in S7 MM firmware don't support the "Sensor ID 4103" chips yet. All we would have to do is move over the drivers to MM with root, but I have no idea how to do this.
Can anyone with ROM building experience that's migrated drivers help out here please?
Thanks!

Update:
It appears the "Version" displayed in *#0*# under FingerPrint test is actually the driver version since there is a separate FwVersion displayed when you hit SensorInfo.
From a shell,
ls /sys/module
Shows the fingerprint sensor as a kernel driver. It's the Egis ET320 Sensor.
So, sadly, apparently you can not use MM with a newer hardware revision of the ET320.
The only option would be to either find an older phone maybe someone could figure out how to get the newer driver out of the newer Samsung builds so we can have an external kernel module in /lib/modules/<kernel version>/extra
Samsung source code is freely downloadable here if anyone could please compile the ET320 driver into an externally loadable module and instruct on overriding...
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=g930f
Swapping the sensor out with an older version will not work since the fingerprint sensor is paired with a chip on the logic board as many who have tried to replace their home button have regrettably learned.

Update2:
I downloaded Nougot and MM Sources from Samsung and see that the fingerprint drivers have definitely been modified. There is a makefile for building the fingerprint driver, but I have no idea what's all involved with getting this going.
Anyone?

Can anyone help a brother out here?
What's the right thing to do - try to attempt to get just the driver compiled into a module that could possibly override the kernel module driver (if it's supported) and drop it in /lib/modules/<version>/extra or recompile the entire kernel with the newer drivers and figure out how to install it?

Related

how to combine generic firmware and Japanese drivers?

Not sure if this is the right place to ask this, if not just move it. TY
I have an Xperia Z3 SO-01G from Japan.
I updated it with the latest firmware from xperifirm, however, the lollipop version is only 5.02 and they don't have 5.1.1 from Docomo
When I use the generic firmware NFC doesn't work.
My question is, is it possible to use the generic firmware and just extract the NFC drivers from the docomo firmware?
I want to use the generic firmware with the latest version of lollipop with no issues regarding the drivers.
I will highly appreciate if someone could help.
Thanks a lot
Id also love to hear if this is possible. Same phone and same issue
First, to clarify, there is no 100% working method to port NFC firmware from Japanese variants to Global firmware. Sony Japan uses different method to encrypt the drivers of all Japanese model, and it can be only used by using the required firmware.
Secondly, if you want to use NFC badly, STAY WITH STOCK. There is NO USE updating the software to 5.1.1 since the stock software from those network providers is fully compatible with the devices.
If you just want to use NFC for devices to devices connection, you can port the whole NFC packages and firmware from the stock rom and flash it to the Global one (I don't have SO-01G but the SOL26 from KDDI AU, and the package is call NFC Osafu/Keitai).
And if you are not using NFC really much, you can just disable the package from root.
Note: I used to obsessed with new OSes and try to do as much as I can to port every apks from Japanese firmware to Global, but after then I realized: Tons of bugs shown in catlogs, unstable system, apps crashed a lot, overheating even when not using (with NFC-Wifi-Bluetooth disabled too, no background apps), etc...
Now I'm sticking with the stock from providers and happy with it.
Thanks N0K0m3
I'm not so much obsessed with having the latest latest software as I am about root. I'd go back to 5.0.2 (or whatever the current global) firmware if NFC still worked. I don't suppose I could flash the previous kernel on top of this ROM and everything would be honky dory.
Any more advice you have is welcomed. I'm sure I'm not the only person curious.
Thanks again
this is my work long time ago for firmware (23.1.A.62), can not guarantee 100% working with NFC driver, because I don't have condition to test.
If you like, you can flash it as flashing prerooted zip.
https://drive.google.com/open?id=0B0EOZK8Eg5HBYjdGVVlsclNadm8
if wifi get problem, after flashing rom, flash this fix
https://drive.google.com/open?id=0B0EOZK8Eg5HBYjdGVVlsclNadm8

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 to Stock 6.0.1 firmware makes the rear camera fail.

Hello guys,
I downgraded my Samsung Galaxy S7 to 6.0.1. The phone itself came with 7.0 out of the box. However, it seems the rear camera does not work when I flash 6.0.1 stock firmware. It works fine on 7.0. Any idea what is causing this or could be there a fix?
Did you flash all 4 firmware files via Odin (CP, AP, CSC, BL)? MM and Nougat use have fairly different bootloaders, and having the wrong bootloader version breaks a few things.
I believe S7's also come with two different camera sensors with different third party support, but that shouldn't matter if you're using stock firmware and stock camera app.
Yes, I am flashing all 4 firmware files.
The phone itself came with Android 7 out of the box. I wonder if it's possible to dump camera firmware/driver of Nougat so that I can flash it on MM?
Everything seems to work fine besides the camera.
Goldspark said:
Yes, I am flashing all 4 firmware files.
The phone itself came with Android 7 out of the box. I wonder if it's possible to dump camera firmware/driver of Nougat so that I can flash it on MM?
Everything seems to work fine besides the camera.
Click to expand...
Click to collapse
did you find a solution for this?

marshmallow rom with nougat bootloader - vibration fix?

As many others have come across, i lost vibration after downgrading to marshmallow from nougat. The solution is said to upgrade back to nougat and then flash all 4 files for marshmallow with odin including bootloader. this is not possible due to sw rev check, even with root access and "phone bootloader update" checked in odin. i dont understand the purpose of an unlocked bootloader, if the phone it self is hardcore locked right up and wont let you change/downgrade the bootloader anyway... i dont do any banking or anything extreme on my phone, im not *that* worried about security and identity theft. frp lock is off already/still. purposely havent even played with screen locks yet until i hopefully get things the way i want
so im wondering now, if theres some sort of a patch or a fix for this issue, since flashing all 4 files is not possible. ive even tried making and md5 for bootloader with out sboot.bin. it still does it. failed instead at param.bin, so i tried another with literally just cm.bin in it. and that also triggered sw rev check.
has anyone figured out a fix for vibration, without saying screw it and staying on nougat or oreo? is there something i can rename to make sw rev check think its a version 3 bootloader when its actually a version 2?
I was thinking this method of using BL from nougat and AP from marshmallow was the same as making my own combination firmware. which does mostly work.... mostly.
i even thought about trying the superman rom for marshmallow but since it uses samsung official components like bootloader id probably run into the same issue.
anyone have any solutions?? besides custom roms (want that touchwiz look and feel. i know, call me crazy)

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.

Categories

Resources