My s7 is making beeping sound instead of vibrating after I installed/flashed firmware with odin. So I installed/flashed android 6.0.1 on my s7 after it updated to 7.0, since I didnt liked Nougat. First I only used the AP file/thing in odin but after the installation was done ,phone wanted a password and default_passoword didnt work so I used AP and SCS file in odin and it worked. Every thing was fine until I found out that my phone was making a weard beeping noise every time I got an notification and later I found out that it wasent vibrating too. Any way to fix it?
And when I change the vibration pattern in settings, the phone is making this weird beeping sound and not vibrating. And often it is losing the wifi connection (it wasn't doing that before).
Have the same issue any updates?
Not sure if I'm up to date, but I faced the same problem today after downgrading from Android 7 to 6... I used Superman ROMs both times.
The problem is - Nougat bootloader with Marshmellow.
I've reinstalled the ROM choosing to "update" bootloader and modem this time (I've skipped at first this because I was sure that BL is up to date after Nougat installation). And it worked fine.
So choose the right bootloader for the Android version you use.
Yep it's a bootloader issue, you can flash just the BL file via Odin for your android version without any issues. That's what I did when going from N back to MM.
i found solution for no vibrator after downgrade nougat to marshmallow
S7 edge is not vibrating after downgrade nougat to marshmallow, it is because you are using nougat bootloader in Marshmallow, you just have to flash with odin the correct MARSHMALLOW bootloader and CP and the vibrator will work just fine.
https://androidfilehost.com/?w=files&flid=54002
thx to tkkg1994
Related
Hi all,
I have an S6 that I am trying to downgrade. It is on 6.0.1 but reboots randomly multiple times a day. I downloaded 5.0.2 stock firmware for Bell and tried to flash via Odin but receive the following error:
sw rev. check fail device 4 binary 1
Not 100% sure what it means. I think the device 4 means that it has been updated and can't be reverted to a lower firmware. If I am wrong, hopefully someone can correct me or provide some guidance. I have already tried clearing the cache and using smart switch to reload the os.
Model is G920W8.
Yeah, I'm on the same boat. I would love an expert to correct me if I'm wrong, but I think once you are past a certain revision of Marshmallow there's no turning back and you basically have to stick with your firmware or move on to a newer one.
You can't downgrade 5.0.2 or 5.1.1 anymore.
Damn, I thought so. If anyone else has ever resolved the random reboot I would love to hear about it. It's such a pain.
I have an S7 (Exynos) and I'm running a custom kernel. (Nethunter), 6.0.1, PHH SuperUser, Magisk, and Xposed.
For some reason any time my phone would normally vibrate, it will make a low beep noise instead. I don't have the slightest clue of what might cause this.
Any suggestions?
Would a logcat dump be helpful?
Thank you.
I have the same problem and its starting to worry me.
If you find a solution that worked for you please let me know!
THE ANSWER TO OUR PROBLEM IS: We are running a Nougat Bootloader on Marshmallow.
i found solution for no vibrator after downgrade nougat to marshmallow
i found solution for no vibrator after downgrade nougat to marshmallow
S7 edge is not vibrating after downgrade nougat to marshmallow, it is because you are using nougat bootloader in Marshmallow, you just have to flash with odin the correct MARSHMALLOW bootloader and CP and the vibrator will work just fine.
https://androidfilehost.com/?w=files&flid=54002
So, here is my first thread to XDA, i hope i will get the help i need.
The problem:
My galaxy s7 is not rooted nor has custom recovery.
I flashed the new official android 7 from sammobile over odin with the official way.
Everything was good since i decided for my reasons to go back to 6.0.1 so i downloaded the latest official firmware again from the same webpage and flash it all the way in (AP,BL,CP,CSC) sometimes just the AP.
Since i rollback to 6.0.1 the vibration wont work, instead it makes a high pitch, low volume sound from the speaker.
Another info, since my first rollback to 6.0.1 vibration was not working but in the boot, now it doesnt vibrate at all!
I tried to reflash it many times, even with older firmwares but again no vibration!!
What should i do?
P.S In order to catch up with some people,
YES its the correct model i am flashing
YES i flashed it correctly
YES i was flashoholic with older devices (over 1.000.000 times format and install roms) THANKS XDA!!
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%
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)