Problems with unrooting my Samsung Galaxy S7 - Samsung Galaxy S7 Questions and Answers

Several months ago I've rooted my Samsung Galaxy S7, but was not satisfied and tried to unroot the phone. But it became a drama.
My phone doesn't start up anymore.
I tried to load the original firmware with Odin, but every attempt failed, showing the error message:
Check fail(bootloader) device: 8, binary: 7
I understood that the firmware I was trying to load, was not the most recent firmware.
But I cannot find newer firmware for my model: SM-G930F - The Netherlands
I've downloaded the most recent firmware from Samdb.org and I've downloaded the most recent firmware with the Frija tool.
Also I've tried the Fixppo software from iMyFone, but without success.
From Sammobile unfortunately I cannot download files, so I could not try this way.
Could anyone give me the golden tip?

sellh1 said:
Several months ago I've rooted my Samsung Galaxy S7, but was not satisfied and tried to unroot the phone. But it became a drama.
My phone doesn't start up anymore.
I tried to load the original firmware with Odin, but every attempt failed, showing the error message:
Check fail(bootloader) device: 8, binary: 7
I understood that the firmware I was trying to load, was not the most recent firmware.
But I cannot find newer firmware for my model: SM-G930F - The Netherlands
I've downloaded the most recent firmware from Samdb.org and I've downloaded the most recent firmware with the Frija tool.
Also I've tried the Fixppo software from iMyFone, but without success.
From Sammobile unfortunately I cannot download files, so I could not try this way.
Could anyone give me the golden tip?
Click to expand...
Click to collapse
Use Sam Firm tool, to downlaod Netherlands (MMO) then flash with Odin. MMO is currently boot loader 8 which you need.

cooltt said:
Use Sam Firm tool, to downlaod Netherlands (MMO) then flash with Odin. MMO is currently boot loader 8 which you need.
Click to expand...
Click to collapse
Thank you very much. This worked for me. The telephone is working again.

sellh1 said:
Thank you very much. This worked for me. The telephone is working again.
Click to expand...
Click to collapse
Your welcome

Related

[Q] About upgrading my device

Hi. I have a Galaxy Note 8 (N5100) and I recently upgraded it to 4.4.2 using Egypt's firmware thru Odin. 2 months ago. Now, the official update has been rolled out to my country (Philippines) and I was wondering how I can upgrade it to the official Philippine firmware. I've downloaded the firmware on sammobile and I just want to make sure if I can just safely flash it thru Odin without doing anything else aside from backing up my apps/data.
Thank you!
VIPNobie said:
Hi. I have a Galaxy Note 8 (N5100) and I recently upgraded it to 4.4.2 using Egypt's firmware thru Odin. 2 months ago. Now, the official update has been rolled out to my country (Philippines) and I was wondering how I can upgrade it to the official Philippine firmware. I've downloaded the firmware on sammobile and I just want to make sure if I can just safely flash it thru Odin without doing anything else aside from backing up my apps/data.
Thank you!
Click to expand...
Click to collapse
Maybe you should flash by odin! Egypt's firmware maybe doesn't support your OTA or kies. If you flash CORRECTLY with your firmware(Firmware version, PIT, or boot loader) Odin should work fine!

NAND write error - same ol' story

Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
See PIT files flashing .
http://forum.xda-developers.com/showthread.php?t=2363703
Hi JJEgan,
Forgot to include that in my original post.
I've tried a few PIT files with no success. It fails at re-partitioning with Odin, and fails to transfer the pit with Heimdall.
Cheers
artois7 said:
Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
Click to expand...
Click to collapse
I've been facing the same thing these days. I was able to install a STOCK ROM here that worked. Well, it's a 4.0.4 android version and it's not recognizing my SIM card, hahaha but it worked until I figure out how to get back to my Gnabo rom OR any other one that can work properly and be rooted after. I can't tell that the same rom i used will work for you cause of the region, but If you would like to try, I can post here and you can flash it and see what happens. Although there is PIT files for 4.0.4 that might me suitable for the rom I've used. =D
vitortakeda said:
I've been facing the same thing these days. I was able to install a STOCK ROM here that worked. Well, it's a 4.0.4 android version and it's not recognizing my SIM card, hahaha but it worked until I figure out how to get back to my Gnabo rom OR any other one that can work properly and be rooted after. I can't tell that the same rom i used will work for you cause of the region, but If you would like to try, I can post here and you can flash it and see what happens. Although there is PIT files for 4.0.4 that might me suitable for the rom I've used. =D
Click to expand...
Click to collapse
What were your symptoms? worth a shot. Thanks.
I have a problem on /efs stuff, well so far I wasn't able to solve it, but as I said, the only rom that was able to be installed was the 4.0.4.
That is the rom i've used.
http://eusouandroid.com/tutorial-rom-original-galaxy-note-10-1-gt-n8000-android-4-0-4/
artois7 said:
Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
Click to expand...
Click to collapse
I found the solutions from another forum.. It's must repair with Z3X box flasher..
forum*gsmhosting.com/vbb/f672/n8000-logo-only-done-via-z3x-jtag-direct-emmc-step-step-inside-1959278/
Can anyone in the UK do this for me? Happy to pay obviously!
derekcfoley2 said:
Can anyone in the UK do this for me? Happy to pay obviously!
Click to expand...
Click to collapse
Local mobile repair shop that carries the tool .
Sent from my SM-N930F using XDA-Developers mobile app

G920F won't flash, SW REV check failed

Hello everyone, I searched here and found several discussions on this problem, but didn't found a solution.
My friend gave me a G920F with a bootlop problem (stock Samsung ROM), it also has a broken recovery which doesn't load at all. I can only go into Download Mode. The fact is, downloading the latest available firmware for ITV, dated 30th March if I remember well, with Nougat, I get the error message on the phone: SW REV CHECK FAIL: DEVICE 6, BINARY 5. Now, how the hell is possible that the phone has a bootloader version greater than the latest firmware available to download?My friend told me she updated the phone few days ago, so it could clearly be the 30th March, which is also the firmware I'm trying to install with ODIN. Anyone could help? I can't really figure it out.
Hi, I've got the same problem. I had stock Nougat on my G920F. Never rooted. Then I recieved a call form unknown caller and the phone crashed. Now it's in a bootloop. I can't access recovery menu, only download mode. Odin fails to push the latest software and I get "SW REV CHECK FAIL: DEVICE 6, BINARY 5" on the phone. I've tried SmartSwitch but it doesn't support G920F anymore. I tried to find sth in here but the only solution I found is to get AOKP, which is dead with no download link. Please help.
I have the same problem. I installed TWRP and LineageOS and want to go back to stock. I downloaded firmware for the phone, start it in Odin and it says in Download screen on the phone: "[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY 5". I Googled it and only found that I'm possibly flashing older bootloader than what I already have. I updated my phone when it was on stock like 2 days ago.
I will try and download newest firmware I can find, 4/4/2018. and see if it works then.
-------------------EDIT--------------------
It worked! I downloaded a ROM from sammobile from 4/4/2018, can't remember which one exactly but it doesn't matter and I didn't get any issues. Everything works fine now.
pilicar said:
I have the same problem. I installed TWRP and LineageOS and want to go back to stock. I downloaded firmware for the phone, start it in Odin and it says in Download screen on the phone: "[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY 5". I Googled it and only found that I'm possibly flashing older bootloader than what I already have. I updated my phone when it was on stock like 2 days ago.
I will try and download newest firmware I can find, 4/4/2018. and see if it works then.
-------------------EDIT--------------------
It worked! I downloaded a ROM from sammobile from 4/4/2018, can't remember which one exactly but it doesn't matter and I didn't get any issues. Everything works fine now.
Click to expand...
Click to collapse
so it works?!

[REQUEST] Galaxy S8+ G955U Sprint CRD4 Bootloader rev3 firmware

Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
esjames said:
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
Click to expand...
Click to collapse
How long do you think that will take since this is my only phone?
You will have to wait until an Odin flashable package of CRD4 or another bootloader 3 firmware becomes available. Without a complete BL3 system flash you are SOL
I think I'll hold off on the OTA update until I hear some safe reports
LordAbolition said:
Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Nitefire77 said:
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Click to expand...
Click to collapse
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Do you have z3x?
You dont need z3x to flash the tmobile variant, but it makes it far simpler. Which version of odin are you using? If its the prince comsey you will more than likely get the mismatch error.
LordAbolition said:
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Click to expand...
Click to collapse
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
SprintBama said:
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
Click to expand...
Click to collapse
No worries. I fixed the situation. Thanks for reading!
I am clarifying this, this is s8 plus now stuck on rev3? I got an s8 and went to another forum thread and was told this isn't true. I am stuck on rev3. FYI, updato has the new s8plus firmware if you haven't got it already.

Need Help With My S6 ASAP Please.

Hello wise people of XDA,
This is my first post.
I currently use an S6 G920F United Kindom unlocked as my phone and i have been using this phone for a long time. Now its past its warranty I decided to root the phone and see what i can do with it and get rid of the bloatware. Normally i either use KingoRoot or KingRoot but both failed so I searched around on the internet and came across CF Auto Root. After seeing it was successful for others i jumped on the bandwagon. I rooted it and everything was golden until i came across a problem, it would randomly turn off. This was random and infrequent. but not it happens like 5 times a day so i decided to flash a stock rom. For some strange reason Sam mobile wont let me download a stock Rom so after poking around the internet i have download a few stock roms however they always fail in Odin. Now my phone wont even boot as it says "error occured while updating use smart switch emergency recovery feature" so i go onto the Smart switch PC app and then it doesnt recognise. After 2 days of trying i haven't had any luck so I don't know what to so. Every time I try flashing something, when it fails i get some red text on the phone which I don't understand.
Someone please help me as I cant just buy a new phone and this is the only phone i have got. Any help would be very grateful and please don't hesitate to ask any questions.
Edit:
It says on the Download Screen:
Odin Mode
Product Name: SM-G920F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Secure Download: Enabled
Knox Warranty Woid : 1 (0x0500)
RP SWREV: B:6 K:2 S:2
(When it fails it says) SW REV. Check Fail. Device:6 . Binary: 5
Hopefully that helped.
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Bryan48765 said:
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Click to expand...
Click to collapse
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
wasim.1.wt said:
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
Click to expand...
Click to collapse
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Bryan48765 said:
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Click to expand...
Click to collapse
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
wasim.1.wt said:
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
Click to expand...
Click to collapse
U6/S6, "Device:6" is in the odin log so it's already 6 and won't return to 5.

Categories

Resources