[q] help required for bricked samsung gt-s6102 - General Questions and Answers

My friend has a Samsung GT-S6102 and he tried to flash a custom firmware without pre-rooting the phone. The phone was stuck in bootloop and he gave the phone to me for repair because I have been flashing phones like my Xperia mini pro and Samsung Monte, etc.
However, this is the first time I had to use Odin to do something like this. As per my experience so far, the most difficult part is to find the right firmware for this phone (I require the Indian firmware). So, after lots of brainstorming in the XDA forum I flashed these files (a) BOOT_S5360DDKK1_REV05.tar (b) torino_1205.pit (c) PDA, Phone and CSC files from S6102_DDMC1_ODDMB1_DDMC1. Now after successfully completing the flash process the phone still goes to bootloop and the Samsung Galaxy logo appears upside down (mirror image). I am attaching the screenshot here for your reference. Moreover, I cannot view the download mode because of white screen when I press volume down+home+power keys. But I can still reflash following the steps as it would if it was normal.
Here's the odin flash log.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S6102_DDMC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_S6102_DDMC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_S6102_ODDMB1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> BcmBoot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> param.lfs
<ID:0/008> system.img
<ID:0/008> userdata.img
<ID:0/008> BcmCP.img
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> csc.rfs
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Any help would be greatly appreciated. Please note that this phone is not rooted so can't go to CWM either.

So, frustrating... somebody got to have a way to revive this bricked phone.
Can somebody tell me how to root and to flash a custom kernel on an already bricked phone.....?

From the screenshot it shows that the odin version is not correct (Its for galaxy grand)
Try using Odin 3v1.8
For firmwares
Go here
Sent by typing by my fingers

@AMIT
Thank you very much for your reply Amit but I'm afraid that it's not going to work either. I've also used the older version of odin the one that you mentioned but with no luck. My only chances are if I can somehow alter the root permission and flash a custom kernel and then flash a new rom. However, I've searched many forums but nobody knows anything about rooting an already bricked phone.
It's quite easy otherwise to root a phone that's in a working condition. So sad...
Anyways, thanks a lot buddy....

Withe Screen on GT-S6102
Hello people
I'need a little help
I was trying to apply a monster rom to my girlfriend galaxy y duos.
Then it reboot and I could see the Monster boot animation but with the picture all mess up.
Then I enter in to Recovery mode an the menu was also mess up.
finaly I could enter with the odin 3 an flash the CSC_S5360_ODDLK1 pack (3 files)
then After reboot all I have is a with screen.
I can go in recovery menu or download menu, at least that I see, because all I see is a the withe screen
Can somebody help to riveve this brick
Thanks

Related

Failed Root Resulting in Problems. Please Help.

So I went to root the phone and I did so with CF Auto Root. I went into Super Su and decided it was not what I was looking for. I was hoping for more of a GUI TWRP system and decided to unroot and factory restore the phone. I'm stressed to the point where i have no memory of how the phone got screwed up at this point. Here is what I do know.
When I power the device on normally it is frozen at the Samsung Galaxy S6 boot page and at the top it says KERNEL REV CHECK FAIL DEVICE 3 BINARY 2. Is this because I have the wrong firmware on the device? Is there any way I can get the bootloader, the firmware and everything else and just restore everything at once? Samsung Smart Switch fails to recover the device and I would absolutely love to do an emergency recovery, but it keeps asking for a code from a previous computer and I have no idea what it's talking about.
Any help would be appreciated.
jblevins1991 said:
So I went to root the phone and I did so with CF Auto Root. I went into Super Su and decided it was not what I was looking for. I was hoping for more of a GUI TWRP system and decided to unroot and factory restore the phone. I'm stressed to the point where i have no memory of how the phone got screwed up at this point. Here is what I do know.
When I power the device on normally it is frozen at the Samsung Galaxy S6 boot page and at the top it says KERNEL REV CHECK FAIL DEVICE 3 BINARY 2. Is this because I have the wrong firmware on the device? Is there any way I can get the bootloader, the firmware and everything else and just restore everything at once? Samsung Smart Switch fails to recover the device and I would absolutely love to do an emergency recovery, but it keeps asking for a code from a previous computer and I have no idea what it's talking about.
Any help would be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
There you go..
brenner650 said:
https://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
There you go..
Click to expand...
Click to collapse
I have already done this. It failed. I need help getting into Emergency Recovery. This is just Recovery.
jblevins1991 said:
I have already done this. It failed. I need help getting into Emergency Recovery. This is just Recovery.
Click to expand...
Click to collapse
Is your device SM-G920F?
forumber2 said:
Is your device SM-G920F?
Click to expand...
Click to collapse
It's the sm-g920t.
jblevins1991 said:
It's the sm-g920t.
Click to expand...
Click to collapse
So, your phone should be T-Mobile.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920T
Region: TMB (write XAR here if your phone is not T-Mobile variant)
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Downlaod" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
forumber2 said:
So, your phone should be T-Mobile.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920T
Region: TMB (write XAR here if your phone is not T-Mobile variant)
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Downlaod" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
Click to expand...
Click to collapse
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
This is the log when I tried your solution. Any ideas?
jblevins1991 said:
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
This is the log when I tried your solution. Any ideas?
Click to expand...
Click to collapse
Try with another usb cable, another usb port or another PC.
I bought an official samsung charger and fixed it. I think the old charger was disconnecting during the smart switch initialization process.
Any way to fix knox?

S6 Stuck at Logo Screen, flashed new ROM twice with no change

Hello,
A bit of back story first - yesterday, my mother's Galaxy S6 (SM-G920F) suddenly rebooted to the device's logo screen ( the "Samsung Galaxy S6....powered by android" one) and it's been stuck there since. There had been no "tinkering" so to say with the device; debugging was disabled, the bootloader had not been tampered with at all, and all the updates were done through the official android route. The last major update was around a month ago, to Nougat from MM, after which I cleared the cache. The latest update was about 10 days ago, a minor Nougat one, but the cache had not been wiped.
Now down to business. The phone does not turn off at all. Holding the power button and the volume down just reboots it to the same screen. That being such, I cannot access recovery mode. I can however access Download Mode which makes be believe that all hope is not lost.
Using Odin, I attempted to flash a stock ROM, which for this model was Android v5.1.1, and now I understand why that wouldn't work. At this point instead of the logo screen, it showed a blue screen saying something along the lines of "An error has occurred while updating your phone, please use Smart Switch emergency recovery". I had tried to connect to smart switch before but it wouldn't recognize the device. I was saving initialization as a last resort.
I then flashed the most recent MM ROM for this model (which I found on sammmobile) using Odin, having read it was possible to still downgrade, and believing that perhaps Nougat was causing this problem. And it was successful, except the phone now returned to the logo screen. Again, with the same problems as before. And I still couldn't wipe the data and cache because I still couldn't access recovery mode.
Finally I connected the phone to Smart Switch and chose to initialize it. After going through all the steps, and downloading the files, it said it was successful but the phone is still stuck at the damn logo screen. I can still access download mode for what it's worth but I haven't a clue now as to what I should do next.
Any help or suggestions would be greatly appreciated. Thanks.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: PHN
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this Odin (even if you have another one);
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfirm) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.
no luck
forumber2 said:
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
...
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.
Click to expand...
Click to collapse
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
(also I'm running Odin with only "Auto Reboot" and "F.Reset Time" ticked, don't know if that will help)
rayofmoonshine said:
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
Click to expand...
Click to collapse
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.
forumber2 said:
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.
Click to expand...
Click to collapse
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?
rayofmoonshine said:
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?
Click to expand...
Click to collapse
Replacing motherboard will not help You unless You have a way to program EFS and IMEI information to it.

SM-G955U1 boots directly to download mode with error message

The error message reads "An error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software."
Im picking up from a lot of you by reading various threads that this is no longer an option.
Backstory: This phone was given to me and from day 1 all the system apps would crash to the point where android would reboot. The phone wouldnt shut off completely like it was losing power, but it would go back to the second screen you see on boot. At this point, the settings reported the software build number as being G955USQS5CRI4, which i dont fully understand. Because on the back side of the phone, the model number reads SM-G955U1.
In an attempt to resolve this issue, i used odin and flashed various builds of g955u1 across a few versions of odin and even attempted some g955u builds. At some point during all of this, download mode switched from normal looking download mode to displaying a big ! in a triangle on the screen. None of the usual information youd see is displayed. However, odin still connects and it appears as though i can still flash. I fear i may have made a mistake.
This log is my latest attempt using SM-G955U1_1_20190709124427_xh7461wrxv_fac pulled from SamFirm. G955U1UES6DSG1 either XAA or VZW, i cant remember which.
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 5808 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> bksecapp.mbn
<ID:0/008> xbl.elf
<ID:0/008> tz.mbn
<ID:0/008> hyp.mbn
<ID:0/008> devcfg.mbn
<ID:0/008> pmic.elf
<ID:0/008> rpm.mbn
<ID:0/008> cmnlib.mbn
<ID:0/008> cmnlib64.mbn
<ID:0/008> keymaster.mbn
<ID:0/008> apdp.mbn
<ID:0/008> msadp.mbn
<ID:0/008> sec.dat
<ID:0/008> NON-HLOS.bin
<ID:0/008> storsec.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When this fails, on the screen of the phone, red text appears that says "secure check fail: system".
Does anyone have any suggestions on what I should do next? Im kind of stumped. Ive been at this for a couple days and cant seem to get different results. I have downloaded several firmwares attempting to resolve this and some of those i believe failed due to bootloader version, but the others typically say fail (auth) or SHA256 is invalid. Although that may be due to me kind of switching between odin 3.13.1 and some patched version of it with this ODIN3B logo in the banner. I would be grateful if anyone could offer me some advice or at least explain what is happening to me. Thank you.

[SOFT BRICKED SM-G930F] [NEED HELP]

So... I screwed up badly. I'm a noob and I was trying to get root access on my S7. I first followed this guide on the xda forums to step 15. While following this I had issues writing \data for the backup so I changed the partition from EXT2 to EXT3 fixing the issue. Then I was advised by someone that I shouldn't be following such an outdated guide and he sent me this one. But instead of going through the whole thing I only went from the part where I install the newest TWRP and everything worked. After a reboot on the the phone I booted into android and it was like after a factory reset with everything fine. I set some stuff on the phone up but didn't enable OEM unlock. Then the phone couldn't boot android with the FRP error. So I tried installing the stock firmware from here and that kept failing. Now whe I try to boot regularly instead of the samsung bootscreen with the FRP Lock error I get a light blue screen telling me to use the smart switch but ss didn't help me (it recognizes the phone and that something is wrong but the integrate fix option doesn't recognize the phone).
In odin I get this error when trying to flash the stock rom I linked to (Odin v 3.13) :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4043 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can get my phone to currently only boot into the download mode and the broken boot mode where it tells me to use smart switch
If anyone has any idea on what I could do to to somehow restore the phone or to get it to a semi functioning state I'd be very grateful.
I'm currently downloading a stock rom from another website: https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/AUT/#SM-G930F 2020-03-26 edition and will try it out once it's downloaded.
[EDIT] No luck with the different ROM, still the exact same issue.
Snapdragon or exynos?
SM-G930F=exynos more roms etc.
eg. Galaxy S7 G930U is = snapdragon USA version
mb. u try flash exynos rom having snap device?
GeloXD said:
Snapdragon or exynos?
SM-G930F=exynos more roms etc.
eg. Galaxy S7 G930U is = snapdragon USA version
mb. u try flash exynos rom having snap device?
Click to expand...
Click to collapse
nope, I have an exynos chip in my phone, but thanks for the suggestion

Galaxy S7 (SM-G930F) Exynos help with bricked phone

My phone; Galaxy S7 (SM-G930F) Exynos.
Stupidly tried to revert phone back to stock without doing enough research first! now phone seems to be bricked!. could have hard bricked it this time!!.
I started by first uninstalling root then thought it might be a good idea to use smart switch for first time to sort software out. really BAD IDEA now phone bricked. first time using smart switch
Now when I start phone all i get is,
( An error aoccured while updating the device software. Use the Emergency recovery function in the smart switch PC software)
but when i try and that all I get is " This function does not support your device" I wish trhey said that when I open the bloody software but it let me start !!!! now I can't get phone back.
I can get another screen which is ( Warning A custome OS can cause critical problems blar blar blar Press volume up key to continue or down to restart) screen. I tried to download a stock rom and use Odin to install it at that screen but it fails every time it sees it in odin and after applying all the lines and starting it it fails after img installing. Not sure I have right stock rom.
Can any one please help I need a link to this phones original stock rom so I can return it to its old self so i can update the software and then perhaps root it to remove bloatware.
I had [ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 installed worked ok untill i noticed an issue with net. it had really bad network speeds on both wifi and phone network so needed to revert it.
can anyone please point me in right direction to stock rom and perhaps give a detailed way out of this mess!.
I want to install my original stock rom and update it then root that rom and debloat it.
any help here would be greatfully recieved.
thanks
Go to https://www.sammobile.com/firmwares/ and select your country and your device.
hedgehog99de said:
Go to https://www.sammobile.com/firmwares/ and select your country and your device.
Click to expand...
Click to collapse
Thanks for replying
I have been there but was unsure what to choose!
I'm assuming I choose (BTU) but there are a few options to choose under United Kingdom
is BTU the right one. do you know how I can check!.
Thanks again.
Update: downloaded that version used Odin but it still fails! I get this in Odin,
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> modem_debug.bin
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4004 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!.
Would really appreciate some help on how to proceed I.
Hi, I don't know if this solution can help you. But it can give you a clue.
I think there is an Odin problem with the .lz4 compression format. You should unzip the official firmware packages, unzip them with 7-zip and pass them to .tar
Here you can see how to do:
In principle it should work.
You already know that when you do this kind of thing you have a risk. But you can try.
Logeate said:
Hi, I don't know if this solution can help you. But it can give you a clue.
I think there is an Odin problem with the .lz4 compression format. You should unzip the official firmware packages, unzip them with 7-zip and pass them to .tar
Here you can see how to do:
In principle it should work.
You already know that when you do this kind of thing you have a risk. But you can try.
Click to expand...
Click to collapse
I fully understand and know what you mean I know its a bit risky but no worries buddy and thank you for replying very much appreciated I will certainley give that a try good idea. I was on the verge on buying a new phone any way so no loss really but it was a good little phone and would love to use it for my grand child for kids youtube. been way behind upgrades for some time now and was kind of coerced by family to join the dark side! because there are some benifits android just can't match and I'm missing out on with my grandkids
I bit my lip and bought the fruit from Eve :/ I'm now a sinner and traitor lol being a windows man like for ever .
again many thanks for your help I will update this thread to let you know the outcome fingers crossed cheers buddy

Categories

Resources