-
Notifications
You must be signed in to change notification settings - Fork 17
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
Comments
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 |
The fix is pretty simple: just type "sudo su", enter your password and it will work. |
Ok now i got the dump from the good phone (0xf7) but the checksum is 9a171aca6a556121461d09b76d3ba6da0d98e46dfb4e971ae9790fb61e4eb419 @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 |
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. |
P. S. I didn't check the MD5 sums and it worked. :)) |
My bad phone has the sboot partition intact, because i can boot to download mode no problem |
@theandroid02 |
Nope i have no idea |
@theandroid02 I'll take a look at your sboot binary and try to fine-grain the heuristics I'm using. Will update soon. |
@theandroid02 I couldn't find the sboot you mentioned. Do you have the ROM that contains it? If not, can you dump it ( |
https://imgur.com/a/ZnUSdoj
The text was updated successfully, but these errors were encountered: