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!!
Related
Hi All,
Hoping for some advice
Ages ago I installed some custom roms on my UK N8010 - I now want to pass the tablet onto a non technical family member and want OTA updates to work
I did a restore before and in download mode it showed Binary as official and system status as official but OTA was not working
I've used Odin to flash the BTU N8010XXUCMG1 stock rom on there from samsung-updates.com
All seemed fine, though now there is no OTA update to test.. when I hold Power+Volume to get into download mode it is still showing "Odin Mode" at the top
Can anyone advise how I can be sure that OTA will work?
Thanks in advance!!
connect the note to Kies on pc , and check on Kies for updates, if it says u r modified then OTA will not work, if it says u r on latest firmware , then u r good (I think )
Thanks - It did that before but still failed when upgrading on the device itself
I did some more digging and managed to find an older firmware on sammobile.com, flashed that and it's updating ok it seems
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.
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
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!
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number