DFU update could not be completed on Samsung Galaxy S8 (Android 8.0)
See original GitHub issueHi, we’ve seen an issue that we don’t think we’ve seen in previous versions (although similar problems have been reported: https://github.com/NordicSemiconductor/Android-DFU-Library/issues/71 ).
Library version: no.nordicsemi.android:dfu:1.8.0
The app that bundles the library version has compile/target SDK: 28 (Android 9)
2018-10-31 09:51:19.1 D/FirmwareUpgradeProgressListener: [I=4, T=M] onProgressChanged(deviceAddress=[C2:30:BA:E4:4F:90], percent=[57], speed=[1.7865353], avgSpeed=[2.262649], currentPart=[1], partsTotal=[1])
2018-10-31 09:51:19.7 D/FirmwareUpgradeProgressListener: [I=4, T=M] onProgressChanged(deviceAddress=[C2:30:BA:E4:4F:90], percent=[58], speed=[3.6065574], avgSpeed=[2.2773843], currentPart=[1], partsTotal=[1])
2018-10-31 09:51:19.8 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:20.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-03-01-00-F0-01-00-97-F1-4D-E0
2018-10-31 09:51:20.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-03-01-00-F0-01-00-97-F1-4D-E0
2018-10-31 09:51:20.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Checksum received (Offset = 126976, CRC = E04DF197)
2018-10-31 09:51:20.4 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:20.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-04-01
2018-10-31 09:51:20.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-04-01
2018-10-31 09:51:20.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data object executed
2018-10-31 09:51:20.4 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:20.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-01-01
2018-10-31 09:51:20.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-01-01
2018-10-31 09:51:20.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data object (32/54) created
2018-10-31 09:51:20.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Uploading firmware...
2018-10-31 09:51:20.6 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Sending firmware to characteristic 8ec90002-f315-4f60-9fb8-838830daea50...
2018-10-31 09:51:21.0 D/FirmwareUpgradeProgressListener: [I=4, T=M] onProgressChanged(deviceAddress=[C2:30:BA:E4:4F:90], percent=[59], speed=[1.6973479], avgSpeed=[2.2643194], currentPart=[1], partsTotal=[1])
2018-10-31 09:51:21.3 D/FirmwareUpgradeProgressListener: [I=4, T=M] onProgressChanged(deviceAddress=[C2:30:BA:E4:4F:90], percent=[60], speed=[6.728395], avgSpeed=[2.2895877], currentPart=[1], partsTotal=[1])
2018-10-31 09:51:21.4 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:22.3 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 03
2018-10-31 09:51:22.3 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-03-01-00-00-02-00-71-A8-0B-27
2018-10-31 09:51:22.3 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Checksum received (Offset = 131072, CRC = 270BA871)
2018-10-31 09:51:22.3 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:22.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 04
2018-10-31 09:51:22.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-04-01
2018-10-31 09:51:22.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data object executed
2018-10-31 09:51:22.4 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:22.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 01-02-00-10-00-00
2018-10-31 09:51:22.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-01-01
2018-10-31 09:51:22.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data object (33/54) created
2018-10-31 09:51:22.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Uploading firmware...
2018-10-31 09:51:22.4 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Sending firmware to characteristic 8ec90002-f315-4f60-9fb8-838830daea50...
2018-10-31 09:51:23.1 D/FirmwareUpgradeProgressListener: [I=4, T=M] onProgressChanged(deviceAddress=[C2:30:BA:E4:4F:90], percent=[61], speed=[1.2166204], avgSpeed=[2.2567873], currentPart=[1], partsTotal=[1])
2018-10-31 09:51:23.7 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:26.4 E/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Error (0x85): GATT ERROR
2018-10-31 09:51:27.1 E/FirmwareUpgradeProgressListener: [I=4, T=M] onError(deviceAddress=[C2:30:BA:E4:4F:90], error=[133], errorType=[2], message=[GATT ERROR])
2018-10-31 09:51:27.1 W/FirmwareUpgradeDialogFragment: [I=4, T=M] Retrying... (try #2)
2018-10-31 09:51:27.1 W/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] [Broadcast] Abort action received
2018-10-31 09:51:28.1 D/FirmwareUpgradeDialogFragment: [I=4, T=M] initFirmwareUpgrade()
2018-10-31 09:51:28.1 D/FirmwareUpgradeDialogFragment: [I=4, T=M] startDfuService()
2018-10-31 09:51:28.1 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] DFU service started
2018-10-31 09:51:28.2 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Opening file...
2018-10-31 09:51:28.2 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Firmware file opened successfully
2018-10-31 09:51:28.2 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Connecting to DFU target...
2018-10-31 09:51:28.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Connected to C2:30:BA:E4:4F:90
2018-10-31 09:51:28.4 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Discovering services...
2018-10-31 09:51:29.4 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Services discovered
2018-10-31 09:51:29.4 D/FirmwareUpgradeProgressListener: [I=4, T=M] onDfuProcessStarting(deviceAddress=[C2:30:BA:E4:4F:90])
2018-10-31 09:51:30.4 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Requesting new MTU...
2018-10-31 09:51:30.5 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] MTU changed to: 23
2018-10-31 09:51:30.5 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Enabling notifications for 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:30.5 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to descr.8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 01-00
2018-10-31 09:51:30.5 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notifications enabled for 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:30.5 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notifications enabled
2018-10-31 09:51:31.5 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:31.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 06-01
2018-10-31 09:51:31.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-06-01-00-01-00-00-88-00-00-00-66-8D-32-10
2018-10-31 09:51:31.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Command object info received (Max size = 256, Offset = 136, CRC = 10328D66)
2018-10-31 09:51:31.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Received CRC match Init packet
2018-10-31 09:51:31.6 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
2018-10-31 09:51:31.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-04-05
2018-10-31 09:51:31.6 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-04-05
2018-10-31 09:51:31.6 E/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Remote DFU error: INVALID OBJECT
2018-10-31 09:51:31.6 D/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Disconnecting...
2018-10-31 09:51:31.7 I/DfuService: [T=M] [C2:30:BA:E4:4F:90] [DFU] Disconnected
2018-10-31 09:51:32.3 E/FirmwareUpgradeProgressListener: [I=4, T=M] onError(deviceAddress=[C2:30:BA:E4:4F:90], error=[517], errorType=[3], message=[INVALID OBJECT])
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Solved Samsung Galaxy S8 Software Update Cannot Be ...
Solution: The first thing you will need to do in this case is to make sure that the phone is connected to a...
Read more >HOW TO UNBRICK YOUR GALAXY S8/S8+ - YouTube
HOW TO UNBRICK YOUR GALAXY S8 /S8+ | HOW TO UPDATE YOUR FIRMWARE VIA ODIN ... try restarting your device. Your browser can't...
Read more >Error 32% systems update, erase, after odin flash for s8 plus ...
Flash firmware with odin when restarting will get stuck in 32% and error will go out, enter the native recovery and make wipe...
Read more >firmware issue Samsung Galaxy S8 (SM-G950FD)
Hi, I have a serious issue with my Samsung Galaxy S8, 64 GB, dual sim. My phone has stock android, never rooted, never...
Read more >How to Install the Leaked Galaxy S8 Android Oreo Update Now
If your S8 or S8+ is not currently on BQL1, you can use Samsung's Odin ... to flash the CRA1 update file in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

As a comment to this ticket we have found an issue in our device that was causing this problem (something about a watchdog that should have been included in the bootloader or similar). The firmware developers told me that the issue was on their side and not in the DFU library. For this reason I am now closing this.
… And again (pasting this in the hope of adding additional information to this ticket, maybe some pattern?):