-
Notifications
You must be signed in to change notification settings - Fork 0
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
device seems dead after flashing 0xF7 #1
Comments
Is your model number i9300? |
If I remeber correctly, it should boot to sdcard mode with only usb power or the power button, it is a typo |
Yes it's a i9300. |
Did it work for you? I updated the guide with better instructions. |
Hey, sorry for responding so late ^^
Maybe you know something about these? After that I created a recovery sdcard, inserted it and tried to boot. Nothing happened. Not even when i try to boot while shorting the resistor. I still can't get into sdcard mode with the recovery sdcard. I'm just back in the inital state of the "Brick Type 1" state. The next thing I'll try is to use another sdcard. I suspect the flash errors occur because of my sdcard, since I get exactly the same errors while flashing on both MBs. The sdcard might also be the cause of why I can't get into sdcard mode....or the errors occur because I already flashed the 0xF7 firmware and the process can't be repeated. I don't know. I'll try some stuff and post again in some days. |
Please, try a different sdcard. And by different I mean try every sdcard you have. I have had a lot of complaints that the recovery sdcard doesn't have great compatibility, and with a random sdcard it worked in the end. |
I did it! tl;dr: I'm dumb and somehow got two working boards. This time I started from the beginning and did everything with linux. As a total linux noob I recommend mx linux. For me, trying to set up Ubuntu18.04 was the worst pain in the ass ever. For every package I had to install (i.e. libusb, gcc-arm-none-eabi, binutils-arm-none-eabi) I got error after error. To even be able to install them, you have to read so many threads in forums about the 10 other things you need to modify and install. Specifically the gcc thing was the worst to install. On mx linux i just ran the command and everything was installed without any problems. Anyways...back to the S3. I somehow got into the original state where I got into download mode without a sbootsdcard. When I then tried to run the script it gave me a "no mmc_startup() on this sboot" error. Then I did the same with my sbootsdcard inserted and it worked (even without shorting the resistor prior). I didn't even get the errors mentioned the post above. Then I resized the boot partition. After that I created a recovery sdcard and inserted it. So here comes the thing. You have to press the power button for around 3 seconds, release and then do nothing for like 10 seconds. After that the sdcard mode screen appears. I was too impatient the last time. I pressed the button too long and, I assume, restarted the device before it could finish copying the bootloader from the sdcard. If that doesn't work, you can try to short the resistor with the recovery sdcard inserted and press the power button. That way I did it with another board I got from a friend. (It worked with both of my sdcards. I tested it with a SanDisk Ultra 32GB microSDHC and a Nokia MU-37 microSD 2GB.) Then, for some weird reason, I could only get into download mode every 10th time or so with the 3 button combo but always when using a jig. Now that I got into download mode again, I wanted to flash a PIT and TWRP. So I switched back to windows and opened odin...and it didn't list the device. Ok, so now it shows up in odin again. Let's flash the PIT and TWRP. Flashing the PIT file only works if you have the "nand erase all" option not selected (the linked xda-guide says otherwise). So I flashed TWRP again and this time actually got into it. This is where I where I fucked up the whole time. Now that that's fixed, let's get rid of the bootloop. I flashed many different roms but every single one eventually just ended up bootlooping again. Fortunately I found a full nandroid backup from 2014 on my old hdd (even with a efs backup). So I restored that via twrp....and it worked! The phone is fully functional. No crashes, no bootloops, even calling works. As I mentioned before, I have two boards...So let's find a way to get the second one to boot aswell. This one had the same problem. Bootloops after flashing the new emmc firmware and rom. Unfortunately, for this one I didn't have a nandroid backup, so I had to find another way. Ok, we're done. At the and of the day I have one fully working board and one that boots, but has a broken efs partition. So I guess there is nothing else left than thanking you and oranav for all of this. It was a long and painful journey but in the end, I got two working boards and l learned some new stuff ^^ I'm not a native speaker, so if there is anything, that I worded poorly and needs clarification, please point it out. |
Hey! Great news. |
hi, is there a way to do all of this without losing what was in the phone? long story short, i have 1.6 BTC in the stupid phone and no wallet backup. Im a case 3 type of brick. |
can you boot twrp? We would need to dump the entire chip and then maybe recontruct the ftl metadata. Don't format still, maybe I can figure out a way, it would hurt to lose all that. You have a boot screen right? |
Hi, did you succeed in dumping the chip and mess with the ftl metadata? |
Hey man,
first of all thx for creating this guide. I discovered oranav's talk on the 34C3 a while ago but couldn't find a 0xF7 firmware to revive my S3 from the dead. Then I found your guide and gave it a try. (I got the Type1Brick)
So far I managed to flash the new firmware onto the chip and resize the boot partition. But now the device doesn't boot into anything anymore and seems to be completely dead (screen remains black). I prepared sdcards with XXELLA sboot.bin and GT_I9300_unbrick_sdcard_head.bin, but nothing happens when i try to boot into download mode with them.
I'm not sure what to do next. Should I try shorting the resistor with my unbrick.bin sdcard in the device?
How exactly should I proceed with method 3? Connecting the battery + holding (power + home + vol down) + shorting the resistor seems to be physically impossible with only two hands.
Do you have any ideas for me?
Thx in advance.
The text was updated successfully, but these errors were encountered: