Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when trying to dump 0xf7 #11

Open
Toomoch opened this issue May 26, 2018 · 10 comments
Open

Error when trying to dump 0xf7 #11

Toomoch opened this issue May 26, 2018 · 10 comments

Comments

@Toomoch
Copy link

Toomoch commented May 26, 2018

https://imgur.com/a/ZnUSdoj

@minealex2244
Copy link

minealex2244 commented Jun 5, 2018

Same here for 0xf1 (SEE THE FIX BELOW)

minealex2244@minealex2244-desktop:~/Desktop/i9300_emmc_toolbox-master$ exploit/sboot_exploit.py --shellcode shellcode/dump_fw_bootrom.bin -o 0xf1.bin
Traceback (most recent call last):
File "exploit/sboot_exploit.py", line 470, in
exploit = Exploit()
File "exploit/sboot_exploit.py", line 30, in init
self._odin.open()
File "/home/minealex2244/Desktop/i9300_emmc_toolbox-master/exploit/odin.py", line 38, in open
self.handle.claimInterface(self.interface)
AttributeError: 'NoneType' object has no attribute 'claimInterface'

@minealex2244
Copy link

minealex2244 commented Jun 6, 2018

The fix is pretty simple: just type "sudo su", enter your password and it will work.

@Toomoch
Copy link
Author

Toomoch commented Jun 10, 2018

Ok now i got the dump from the good phone (0xf7) but the checksum is 9a171aca6a556121461d09b76d3ba6da0d98e46dfb4e971ae9790fb61e4eb419
insted of
1c3ce3148704e21749c6b59ff88c7a133d385024f70038615806ae9e95798dbf

@oranav and i can't dump 0xf1 from my bad phone (sboot I9300BVBLH2) because it gives me

root@ubuntu-mate:/home/ubuntu-mate/Desktop/i9300_emmc_toolbox-master# exploit/sboot_exploit.py --shellcode shellcode/dump_fw_bootrom.bin -o 0xf1.bin
Traceback (most recent call last):
File "exploit/sboot_exploit.py", line 479, in
exploit.run_shellcode(args.shellcode.read())
File "exploit/sboot_exploit.py", line 254, in run_shellcode
raise Exception('Could not find mmc_startup() in this sboot')
Exception: Could not find mmc_startup() in this sboot

@minealex2244
Copy link

To be honest I'm not sure if reviving a dead S3 it's worth. You will loose EFS forever, you won't be able to recover any files but I think that it's still good as a non-daily driver. P. S. I successfully revived my S3.
Regarding your problem, did you got XXELLA sboot on your SD card?

@Toomoch Toomoch closed this as completed Jun 10, 2018
@Toomoch Toomoch reopened this Jun 10, 2018
@minealex2244
Copy link

P. S. I didn't check the MD5 sums and it worked. :))

@Toomoch
Copy link
Author

Toomoch commented Jun 10, 2018

My bad phone has the sboot partition intact, because i can boot to download mode no problem
Gonna try writing now the 0xf7 in the bad phone
EDIT: i get the same error as dumping

@ghost
Copy link

ghost commented Jun 15, 2018

@theandroid02
I got the same checksum. Any Idea what version this is?

@Toomoch
Copy link
Author

Toomoch commented Jun 19, 2018

Nope i have no idea

@oranav
Copy link
Owner

oranav commented Jul 10, 2018

@theandroid02 I'll take a look at your sboot binary and try to fine-grain the heuristics I'm using. Will update soon.
In addition, can you email me your eMMC firmware dump? You can find my contact information here

@oranav
Copy link
Owner

oranav commented Jul 10, 2018

@theandroid02 I couldn't find the sboot you mentioned. Do you have the ROM that contains it? If not, can you dump it (sudo exploit/sboot_exploit.py --dump --output sboot.bin) and send it to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants