I am trying to flash a stock ROM onto my SM-G930F using Odin3 v3.10.7 . I am in the United Kindom and the phone is H3G. I have tried 3 different ROMS from sammobile but none will flash onto the device. I can now only get into download mode.
On the device it says
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWREV: B:1 K:0 S:0
None of the text on the phone changes whilst flashing.
The log on Odin is:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I have also tried using the "Firmware and initialization" tool in Samsung Kies 3 but get the error "failed to upgrade firmware due to an unexpected error".
Any help would be greatly appreciated.
Tried different usb cable? (Especially try the one that came with your phone)
Tried a different USB port? (no hub in between)
Tried different drivers?
Tried different computer?
edit: maybe this works: http://androidforums.com/threads/resolved-soft-bricked-cant-flash-with-odin.473420/
LowLatency said:
Firstly, I know this is posted under S7 Edge but couldn't find a Q&A topic for the S7.
I am trying to flash a stock ROM onto my SM-G930F using Odin3 v3.10.7 . I am in the United Kindom and the phone is H3G. I have tried 3 different ROMS from sammobile but none will flash onto the device. I can now only get into download mode.
On the device it says
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWREV: B:1 K:0 S:0
None of the text on the phone changes whilst flashing.
The log on Odin is:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I have also tried using the "Firmware and initialization" tool in Samsung Kies 3 but get the error "failed to upgrade firmware due to an unexpected error".
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi mate
Did you unlock your bootloader? , try it with a newer Odin
check this thread , there are step by step instructions
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
MAX 404 said:
Hi mate
Did you unlock your bootloader? , try it with a newer Odin
check this thread , there are step by step instructions
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
Click to expand...
Click to collapse
How do I unlcok the bootloader? Is this by turning on developer options? I couldn't access the settings so was unable to do this if so.
LowLatency said:
How do I unlcok the bootloader? Is this by turning on developer options? I couldn't access the settings so was unable to do this if so.
Click to expand...
Click to collapse
Unlocking the bootloader is when you go into your SETTINGS/ABOUT DEVICE and tap the build number until you get a message that you have unlocked the developer options. You then back out of ABOUT DEVICE and enter DEVELOPER OPTIONS and enable OEM UNLOCK. Did you do any of that?
I think this may be progress. My phone now boots into Recovery where at the top it says:
Android Recovery
MMB29K.G930FXXU1APC8
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1APC8
user/release-keys
I think this is showing a ROM that I flashed onto it in an attempt to fix the problem but it didn't work.
Then has all the options for recovery.
At the bottom it says
Supported API: 3
dm-verity verification failed...
E:failed to mount /system (Invalid argument)
I have tried a few different ROMS that I have on my computer through Odin v3.11.1 (I believe the newest version) but to no avail.
As you can probably tell, I'm not 100% sure what I am doing but have worked out that it is the main file that goes under AP in Odin that is the problem.
I am about to try the upgrade tool in Kies now I can get into recovery mode and see if that works.
kettir said:
Unlocking the bootloader is when you go into your SETTINGS/ABOUT DEVICE and tap the build number until you get a message that you have unlocked the developer options. You then back out of ABOUT DEVICE and enter DEVELOPER OPTIONS and enable OEM UNLOCK. Did you do any of that?
Click to expand...
Click to collapse
I hadn't done this no, because the phone bricked whilst I was updating it through Kies. After the update failed I couldn't get back into the phone at all other than "download mode" so this wasn't an option.
Update!
My phone still won't update through Kies. I'm still getting the same error message
LowLatency said:
I think this may be progress. My phone now boots into Recovery where at the top it says:
Android Recovery
MMB29K.G930FXXU1APC8
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1APC8
user/release-keys
I think this is showing a ROM that I flashed onto it in an attempt to fix the problem but it didn't work.
Then has all the options for recovery.
At the bottom it says
Supported API: 3
dm-verity verification failed...
E:failed to mount /system (Invalid argument)
I have tried a few different ROMS that I have on my computer through Odin v3.11.1 (I believe the newest version) but to no avail.
As you can probably tell, I'm not 100% sure what I am doing but have worked out that it is the main file that goes under AP in Odin that is the problem.
I am about to try the upgrade tool in Kies now I can get into recovery mode and see if that works.
Click to expand...
Click to collapse
Hi mate
First of all "OEM unlock" is not necessary to odin flash a stock rom...please forget i said it
The issue seem that is caused by dm-verity verification failed , same symptoms .. keeps device in boot loop ( Samsung Logo) , not sure yet what the solution is i seem lots of threads about it on S6 and Note 5
Check this thread:
http://forum.xda-developers.com/showpost.php?p=66605862&postcount=48
@CuBz90 with a S7 had the same problem and mention it did not work........maybe he can help out
In the same thread they suggested this..you could try it ..just in case
http://forum.xda-developers.com/showpost.php?p=67217747&postcount=52
Only thing i got for now......
With frp lock on and drm error. There is no way around it at the moment.
Sent from my SM-G935F using Tapatalk
CuBz90 said:
With frp lock on and drm error. There is no way around it at the moment.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks for replying mate
Bad news indeed......in your case you had knox bit tripped off?
I see that twrp recovery
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Has a
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
I know it means to trip knox , but i wonder if it would help
MAX 404 said:
Thanks for replying mate
Bad news indeed......in your case you had knox bit tripped off?
I see that twrp recovery
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Has a
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
I know it means to trip knox , but i wonder if it would help
Click to expand...
Click to collapse
No because with frp on you cannot flash twrp
Sent from my SM-G935F using Tapatalk
CuBz90 said:
With frp lock on and drm error. There is no way around it at the moment.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
How annoying, hopefully somebody finds a fix soon
LowLatency said:
How annoying, hopefully somebody finds a fix soon
Click to expand...
Click to collapse
Just one thing I noticed in your posts, you refer to Kies 3 if you are trying to do it with Kies 3 this isn't compatible with the S7, if you don't need it uninstall it and install Samsung Smart Switch, this will install the correct drivers for the S7, you may be able to get the Initialization and Recovery process to work then.
The problem with Odin is if you don't have USB Debugging enabled it wont work, also you system status says Custom this can prevent Smart Switch from working as well but give it a try you have nothing to lose
I have the same problem.
What damages drk?
ag4751 said:
Just one thing I noticed in your posts, you refer to Kies 3 if you are trying to do it with Kies 3 this isn't compatible with the S7, if you don't need it uninstall it and install Samsung Smart Switch, this will install the correct drivers for the S7, you may be able to get the Initialization and Recovery process to work then.
The problem with Odin is if you don't have USB Debugging enabled it wont work, also you system status says Custom this can prevent Smart Switch from working as well but give it a try you have nothing to lose
Click to expand...
Click to collapse
Still no luck using Smart Switch, I get the same error message as with Kies.
As you say, it was worth a try, so thanks!
Anyone have a fix for this? I ran into the same thing. Mistakenly (like an idiot) reset all of my settings before using Flashfire to flash an OTA update. The result is the same as the OP. Tried using Odin to flash stock, running into failures and the same dm-verification problem.
bump
I semi bricked mine not long ago I just put it in download mode plugged it in to my win 10 laptop and flashed twrp with ordinary then flashed stock rom
Sent from my SM-G930F using Tapatalk
I cannot flash anithing. All tries ended up in a fail. (Complete write operation fail).
Looks like the samsung protection blocked the Boot.
Related
I rooted my S7 and it deactivated my cellphone service. I searched the internet for solution and there were absolutely none. I decided to flash it back to the stock firmware. Odin didn't work and I accidentally unplugged the phone and now it won't boot up. I can put it in download mode but it's not being detected by ADB. My computer does detect as a Samsung Device though. When I try to use the stock firmware with Odin it says : <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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
When I try to use SmartSwitch it says Unsupported Device. I'm desperate just to get my phone to work again so any help is greatly appreciated!
Has anyone figured out a solution to this? Having the same issue.
Did you try with smartswitch on your pc emergency recovery you will need your serial key
Phantom162 said:
Did you try with smartswitch on your pc emergency recovery you will need your serial key
Click to expand...
Click to collapse
I also have the same problem, and I tried the smart switch method, however when entering my serial number I was told I had the wrong serial number. I double checked multiple times and I always input it correctly.
I dont have any idea for this when mine is soft bricked il always do this!!! Are you sure you enter the exact sn number mine sn number its on sticker on the box!!!
You can try stock firmware on updato
are you using a Windows computer?
lightstryk said:
Has anyone figured out a solution to this? Having the same issue.
Click to expand...
Click to collapse
The issue was that the stock firmware I was trying to flash to was out of date. I used the up to date firmware and my phone is now fine. I was freaked out for at least 2 days about my phone thought, I'm never trying to root it again.
Jetirk said:
The issue was that the stock firmware I was trying to flash to was out of date. I used the up to date firmware and my phone is now fine. I was freaked out for at least 2 days about my phone thought, I'm never trying to root it again.
Click to expand...
Click to collapse
That's what i said when i hard bricked my first phone , i will never even root my phone again!
And what did i do one week after i bought new device? I flashed ROM, don't be worried, bricking will always happen, it is the part of whole experience :angel: :laugh:
I rooted my Girlfriends S7 Edge and when she restarted, it went into a boot loop. I have used every option in oden except autostart,Flash lock, and deviceonfo. I want to return to stock. G935T
this if from standard options using only AP
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_G935TUVU1APB6_G935TTMB1APB6_CL7103056_QB8543665_REV02_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone screen says:
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
It looks like you're trying to flash a firmware which is older than the one installed. Try to find latest firmware.
It was running 6.1 then went custom shoudnt i be able to flash same version?
rhettc2 said:
It was running 6.1 then went custom shoudnt i be able to flash same version?
Click to expand...
Click to collapse
tried newest version and still same problem. Smart Switch and kies wont even recognize the phone. I have installed the samsung driver.
Went to samsung official site and tried download from there thank you very much!
Try flash via odin show fail..ALREADY VIEW ALOT YOURTUBE AND XDA..NOT FIX.. PRESS POWER + VOL BUTTON CAN'T ENTER RECOVER MODE. OR EMMC CHIP SPOIL? THANK
Pls help.
One use the report button and ask a mod to move the post to the correct section .Q&A
Try flash via odin show fail
What fail .
What are you flashing ??
JJEgan said:
One use the report button and ask a mod to move the post to the correct section .Q&A
Try flash via odin show fail
What fail .
What are you flashing ??
Click to expand...
Click to collapse
Because keep stuck on samsung logo. Can't go into recovery mode too. Suspect firmware corrupt. Fail show at 1st pic there Sboot.bin. So try re-flash stock rom, one of my htc problem like this after flash phone work as normal.
Some say this due to EMMC chip issue.
Pls help.
Try flashing a full firmware .
Full as in a single file
JJEgan said:
Try flashing a full firmware .
Full as in a single file
Click to expand...
Click to collapse
All already try. The pic 'FAIL" red color show in odin is single file(full firmware).
This case similar like my other HTC keep reboot in logo, htc after flash work as normal.
Alot of people facing same issue too, search around forum still unable to fix. Probably emmc.
Usual for Emmc fail is Odin fails at Nand write.
Sent from my SM-N930F using XDA-Developers Legacy app
JJEgan said:
Usual for Emmc fail is Odin fails at Nand write.
Sent from my SM-N930F using XDA- Legacy app
Click to expand...
Click to collapse
This note already problem quite some time, before that show the error below, at NAND Write start, so is EMMC problem, need replace the chip?
Also the battery charging bar not running, previously when charge will show the battery bar running.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDPB1_N8000LUXDPB1_N8000XXUDNH1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This note already problem quite some time, before that show the error below, at NAND Write start, so is EMMC problem, need replace the chip?
Probably but ask a service centre .
Enter in download mode and try to flash any recovery cwm, twrp or philz with odin. See if now you're able to boot into recovery mode.
Enviado do meu GT-I9301I através de Tapatalk
skyx1128 said:
Try flash via odin show fail..ALREADY VIEW ALOT YOURTUBE AND XDA..NOT FIX.. PRESS POWER + VOL BUTTON CAN'T ENTER RECOVER MODE. OR EMMC CHIP SPOIL? THANK
Pls help.
Click to expand...
Click to collapse
I have the same problem but mine shows a error at system.img.
View attachment 5290635
And When I power it through the adaptor it shows the charging symbol and then it turns off. (As shown in the above image).
This happen when it ran out of charge for a day since then its been stuck with this logo. (As shown above).
Wrong firmware sys.img.
Wrong size PIT file .
JJEgan said:
Wrong firmware sys.img.
Wrong size PIT file .
Click to expand...
Click to collapse
I appreciate your help but I am new to all this and if you can explain things in detail would be helpful.
I have worked on xiaomi phones before but they use adb & fastboot to flash things, so I am a beginner for the flashing of samsung devices.
I downloaded the files from samobile and one more from other source and they are for the correct model as well.
This log is of the file download from the other source and was a single file.
Odin Log:
<ID:0/009> 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..
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 1764 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> system.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
This log is of the file download from samobile with four different files.
Odin Log:
<ID:0/009> 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/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 1765 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In a post similar to this, someone mentioned that device stuck on logo could be due to a corrupted kernel.
Firmware is tied to the 16 or 32 Gb memory , check yours first.
JJEgan said:
Firmware is tied to the 16 or 32 Gb memory , check yours first.
Click to expand...
Click to collapse
Mine is the 16GB model and the firmware is also correct.
Probable
Flash stock but still custom rom
Hi folks , I installed cyanogenmod rom to my Samsung Galaxy Note 10.1 (GT-N8005) a year ago. It stuck on boot animation. Then I flash stock rom via odin , it passed. But still stuck on cyanogenmod boot animation. Can anyone help ? How can I...
forum.xda-developers.com
JJEgan said:
Probable
Flash stock but still custom rom
Hi folks , I installed cyanogenmod rom to my Samsung Galaxy Note 10.1 (GT-N8005) a year ago. It stuck on boot animation. Then I flash stock rom via odin , it passed. But still stuck on cyanogenmod boot animation. Can anyone help ? How can I...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help but I already checked this link and many others but the conclusion was when the error occurs at "NAND write" step then the emmc chip was probably damaged but mine stops at a different step. And also if I replace the emmc wouldn't I lose the data?
[RECOVERY][OFFICIAL] TWRP 3.6.0_9 [N8000 N8010 N8020]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
try flashing this twrp recovery, note use odin 3.10.5, note disable auto reboot, in options, after sucess reboot recovery, click flash, and see how big the internal storage is. If no sucess flashing twrp recovery or internal storage = 0MB your emmc is fried, else you device still has life.
If your device still has life install this custom android(LineageOS is just the UI name, it is stable android)(follow the steps)(ask @html6405 for questions, I can only help you to here)
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
Hi all,
I am trying to fix a SM-G930F for a girlfriend. The phone crashed during an OTA and is now totally stuck in download mode. I can get into Odin mode, not recovery. Rebooting only takes me back to download mode.
First I have tried Samsung Smart Switch / Kies, but the phone is not recognized and emergency recovery is not available.
Next logical step is to reflash stock firmware. So downloaded the appropiate firmware from sammobile. Since she bought it in a dutch store, and is unbranded (uses a sim-only) i downloaded the latest PHN version G930FXXU1DQL5_G930FPHN1DQL1_PHN.
I added all the files to Odin (BL/AP/CP/CSC), Odin is blue, use an original Samsung USB cable and this is what I get:
<ID:0/003> 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/003> Odin engine v(ID:3.1207)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I downloaded the PIT file and tried that one:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1207)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any advice?
Are you using ODIN 3.12.3 or newer? Older versions have problems
Try flashing just the AP
Try flashing all apart from CSC
Try flash HOME_CSC instead of CSC
Try flashing another CSC firmware with "Repartition" Ticked in ODIN options
*Detection* said:
Are you using ODIN 3.12.3 or newer? Older versions have problems
Try flashing just the AP
Try flashing all apart from CSC
Try flash HOME_CSC instead of CSC
Try flashing another CSC firmware with "Repartition" Ticked in ODIN options
Click to expand...
Click to collapse
I am using the latest Odin v3.12.7
Tried the first 3 suggestions, now get:
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
What do you mean with other CSC firmware? I actually also tried the same with the previous official firmware, see if that helps but unfortunately not.
PHN is the CSC in your case
The CSC contains the PIT file
Try any other firmware/CSC for that model S7 as a test
*Detection* said:
PHN is the CSC in your case
The CSC contains the PIT file
Try any other firmware/CSC for that model S7 as a test
Click to expand...
Click to collapse
no luck, same problem: There is no PIT partition.
lictorian said:
no luck, same problem: There is no PIT partition.
Click to expand...
Click to collapse
Can you double check that it says G930F while in download mode?
*Detection* said:
Can you double check that it says G930F while in download mode?
Click to expand...
Click to collapse
It is definitely a G930F:
Odin mode
Download speed: fast
Product name: SM-G930F
Current binary: Samsung official
System status: official
FRP lock: On
Secure download: enabled
Warranty void: 0 (0x0000)
RP SWREV: B:1 K:0 S:0
Try ticking re-partition in odin since you're using the pit file..
lictorian said:
It is definitely a G930F:
Odin mode
Download speed: fast
Product name: SM-G930F
Current binary: Samsung official
System status: official
FRP lock: On
Secure download: enabled
Warranty void: 0 (0x0000)
RP SWREV: B:1 K:0 S:0
Click to expand...
Click to collapse
Sounds like something has either corrupted the internal storage, or the internal storage is faulty, causing the original crash and now cannot be read for flashing
As it is still 0x0 for KNOX warranty I'd suggest trying to get it repaired via Samsung if still within the time limit
If not, then flashing TWRP custom recovery would give you more options for repairing the file system / partitions if it is not a hardware failure
Be aware that certain apps will not work with KNOX tripped
I could only say that you may be flashing a corrupted rom, have you tried any other from sammobile?
Tried using different USB cables? Try to use a USB 2.0 port if possible.
Try Samsung emergency recovering.
Hello,
I'm creating a new trend because I did try everything what I could find on forums to fix this issue.
I have a problem with Samsung galaxy s7 (SM - G930F) it got stuck on Samsung logo and when I connect it to PC in download mode using USB there is no sign. PC doesn't show anything, I tried all ports and many different cables.
What did I try is:
1) Volume UP+Home Then Power button - Nothing happens. Can't access to the menu for hard reset.
2) Safe mode - Power bottom when it turns on immediately hold power down - Nothing happens, can't run in safe mode.
3) Volume down+Home+Power -
WORKS - Download mode opened, Now the problem is I can't flash a firmware with ODIN3 coz basically PC not recognizing USB.
4) Yes I did download Samsung USB drivers and installed them.
5) I checked on Device Manager there is no sign of samsung USB or anything..
6) I also tried SmartSwitch - Nothing, it asks me to connect to device.
Basically the only things work are download mode and force restart - Volume Down+Power bottom.
The other thing when I charge the phone it shows empty battery logo, no green or red light, percentage or anything.
Any ideas guys? I'm losing a hope with this phone.
If it refuses to charge and the PC won't detect it, it's either an issue with the main board itself or the daughter board that houses the microUSB port.
The latter shouldn't be too difficult to replace.
MeltdownSpectre said:
If it refuses to charge and the PC won't detect it, it's either an issue with the main board itself or the daughter board that houses the microUSB port.
The latter shouldn't be too difficult to replace.
Click to expand...
Click to collapse
But how can it explained that I'm available to access to download mode by pressing volume down+home+power buttons but not available get into hard reset mode menu? I done reseach about hard reset mode and I read that the phone should be over 50% charged to make factory reset. I'm guessing that the phone is charging but not properly charging so I'm only allowed to access into download mode. Because if the phone wasn't charging at all it would be dead. Is this possible theory?
Incognitusum said:
But how can it explained that I'm available to access to download mode by pressing volume down+home+power buttons but not available get into hard reset mode menu? I done reseach about hard reset mode and I read that the phone should be over 50% charged to make factory reset. I'm guessing that the phone is charging but not properly charging so I'm only allowed to access into download mode. Because if the phone wasn't charging at all it would be dead. Is this possible theory?
Click to expand...
Click to collapse
There could be an issue with the recovery partition causing it to not boot into the stock recovery menu for you to do a hard reset.
Normally in circumstances like this, I'd suggest a clean flash of the latest stock firmware, but seeing as though the PC doesn't detect the phone, that won't be possible.
am facing the same problem except my computer does recognize the device although as a modem device and when trying to flash it using odin it fails with <ID:0/003> FAIL! (Auth) error message anybody help
nyarunda said:
am facing the same problem except my computer does recognize the device although as a modem device and when trying to flash it using odin it fails with <ID:0/003> FAIL! (Auth) error message anybody help
Click to expand...
Click to collapse
i am not sure for my answer but are you using the correct firmware version for your device?
maybe it is a carrier or region thing
also check what odin version you are using
rzr86 said:
i am not sure for my answer but are you using the correct firmware version for your device?
maybe it is a carrier or region thing
also check what odin version you are using
Click to expand...
Click to collapse
am using Odin3_v3.14.4;
about the firmware am not sure which to use;
the back of the phone says it an sm-g930t
but on the recoverymode it says it a sm-g930v
i have tried with both firmwares it gives the same error
nyarunda said:
am using Odin3_v3.14.4;
about the firmware am not sure which to use;
the back of the phone says it an sm-g930t
but on the recoverymode it says it a sm-g930v
i have tried with both firmwares it gives the same error
Click to expand...
Click to collapse
Hello, if the phone is reporting G930V in recovery mode then the phone is truly a G930V and that's the firmware you need to flash. It has to be the latest version and for your region.
So a G930V is a Verizon branded device, in your case it's been modified to accept G930F firmware which is always going to be a problem if you attempt to modify the device after that.
Get the latest G930V firmware and flash it with Odin 3.13 not 3.14. Once your phone is up and running you can decide what to do from there, a G930V will only work in the USA.
Tried this procedure still failed....here is odin's terminal log
<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.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5040 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<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> boot.img
<ID:0/004> recovery.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the following is displayed on the phone
odin mode (high speed)
product name:sm-g930v
current binary:samsung official
system status: official
fap lock: on
qualcomm secureboot:enable
rp swrev:b10(2,1,1,1,1) k10 s10
iddq:g(39), s(11) ma
cpu serial num:0xd8df2131
fused open loop voltage:1020mv
rpmb provisioned
sw rev check fail: [boot] fused 10>binary 1
nyarunda said:
Tried this procedure still failed....here is odin's terminal log
<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.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5040 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<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> boot.img
<ID:0/004> recovery.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the following is displayed on the phone
odin mode (high speed)
product name:sm-g930v
current binary:samsung official
system status: official
fap lock: on
qualcomm secureboot:enable
rp swrev:b10(2,1,1,1,1) k10 s10
iddq:g(39), s(11) ma
cpu serial num:0xd8df2131
fused open loop voltage:1020mv
rpmb provisioned
sw rev check fail: [boot] fused 10>binary 1
Click to expand...
Click to collapse
What firmware are you trying to flash?
nyarunda said:
Tried this procedure still failed....here is odin's terminal log
sw rev check fail: [boot] fused 10>binary 1
Click to expand...
Click to collapse
That is your problem.
You are trying to flash an older firmware than what is already on the device.
You need to flash G930V with bootloader 10 or higher.