ODIN: Binary size t...
 
Notifications
Clear all

ODIN: Binary size too large : recovery

14 Posts
7 Users
0 Likes
7,014 Views
(@prisonphones)
Posts: 7
Active Member
Topic starter
 

Using Cellebrite, while trying to do a physical extraction, boot loader, I eventually receive an error and a message on the phone screen saying 'ODIN Binary size too large recovery' and I've had this happen with two Samsungs in a row. Anyone know how to fix this? Thank you in advance.

Update This appears to be an issue with the micoSD card I am using for the extraction. However I am not sure what the issue is as I have used the microSD card in the past and had no problems.

 
Posted : 23/01/2017 11:21 pm
(@danielb)
Posts: 30
Eminent Member
 

Are you using a 64GB memory card, as I spotted UFED recommended that size on a few models of Samsung.

 
Posted : 30/01/2017 5:17 pm
(@thefuf)
Posts: 262
Reputable Member
 

Use a recommended memory card (64GB SanDisk).

This appears to be an issue with the micoSD card I am using for the extraction

It could be a problem with firmware of a mobile device. Also, it is possible for UFED to acquire the image despite the error message you mentioned, so you may want to try the extraction method multiple times.

 
Posted : 30/01/2017 6:04 pm
(@prisonphones)
Posts: 7
Active Member
Topic starter
 

Are you using a 64GB memory card, as I spotted UFED recommended that size on a few models of Samsung.

I am using a 64GB memory card. I actually had to switch to my old memory card I use for extractions and that one is only 4GB. The phone was successfully extracted with the 4GB card for some reason.

 
Posted : 30/01/2017 6:45 pm
Bolo
 Bolo
(@bolo)
Posts: 97
Trusted Member
 

hmm 64Gb….what for ? Data are not stored on SD at end… it's only act as a buffer and extracted dump are saved into local extraction directory

 
Posted : 31/01/2017 3:11 am
(@thefuf)
Posts: 262
Reputable Member
 

hmm 64Gb….what for ? Data are not stored on SD at end… it's only act as a buffer and extracted dump are saved into local extraction directory

No, an SD card is not used as a buffer.

 
Posted : 31/01/2017 10:29 am
Bolo
 Bolo
(@bolo)
Posts: 97
Trusted Member
 

Maybe buffer is wrong word - as far as I checked scheme is similar like this

BL -> eMMC -> READ CHOOSEN OFFSET/RANGE and WRITE to SD CARD (shows as T-FLASH mode) -> MOVE RANGE to EXTRACTION DIRECTORY on Local Drive -> LOOP until end…….

 
Posted : 01/02/2017 12:20 am
(@thefuf)
Posts: 262
Reputable Member
 

Maybe buffer is wrong word - as far as I checked scheme is similar like this

BL -> eMMC -> READ CHOOSEN OFFSET/RANGE and WRITE to SD CARD (shows as T-FLASH mode) -> MOVE RANGE to EXTRACTION DIRECTORY on Local Drive -> LOOP until end…….

Well, this scheme is not correct. Unfortunately, I cannot provide any details.

 
Posted : 01/02/2017 12:50 am
tito
 tito
(@tito)
Posts: 24
Eminent Member
 

I can not quite imagine how the Cellebrite and my opinion might be wrong. However, if the files are copied to the flash (even if interim), you must pay attention to the type of file system. If it is FAT, and bigger than 4 GB file, then an error "large file" can be displayed as FAT does not work with files larger than 4 GB.

 
Posted : 13/02/2017 4:16 pm
(@thefuf)
Posts: 262
Reputable Member
 

I can not quite imagine how the Cellebrite and my opinion might be wrong.

What did Cellebrite tell you?

 
Posted : 13/02/2017 5:09 pm
Page 1 / 2
Share: