GSLEON3
Retired Senior Moderator
To the OP, your device is in no way bricked. Those that say otherwise do not understand Qualcomm architecture & the different layers of firmware.
You are in emergency Dload mode. Something I am very familiar with since I was forcing my device into this mode purposely while working on S-Off a few months ago.
Wit proper & full memory mapping, this can be fixed using a terminal emulator & the Qualcomm Snapdragon developer suite. I won't waste my time, but if you are still having issues & are in Dload still via USB, let me know.
To the naysayers, look up a little old project called FrankenKaiser. I have been in QC_Dload many times & am still using my device today. Much depends on how far the update got & what radio/HBoot & rom version (GB or ICS) you have flashed or partially flashed. I consider you lucky as this is a technical soft-brick.
The trick that is really cool is that from dload, you can write raw data into RAM. Just like I did when fixing Kaisers. If you had the AT&T original rom on your device, you may be in luck, as I have that somewhere between 40 & 60% memory mapped. This allows you to write the SPL from Hboot into ram, making your device think it has hboot, which allows you to then run hboot from ram, using it to re-install a real hboot onto the chip. The downside is that I was working with an S-Off hboot when doing this, but unless QC made some serious changes, it still may work.
Let me know where you are at, if you still have the device & it's status & I will see if I can dig up the S3 memory map. Otherwise, you can sped 30 - 50 & jtag the unit. Either way, you will need to be patient, have some knowledge of arm architecture & adb/fastboot type commands (understand what setting flags means, variables, & basic command (CMD) abilities. You must be precise when loading anything this way or it is big trouble.
Having a device in emergency dload can be a cool thing or a frightening thing depending on your experience. Fortunately, I had a lot of Kaisers & used them to try new things with Oli, Cmonex & Jocky, so I know exactly what it means & what it is doing (looking for). If still there, you can access & give radio commands or even send bytes to radio (rdata), allowing you to unsecure the device radio (2 bytes), which is one step in S-Off.
You are in emergency Dload mode. Something I am very familiar with since I was forcing my device into this mode purposely while working on S-Off a few months ago.
Wit proper & full memory mapping, this can be fixed using a terminal emulator & the Qualcomm Snapdragon developer suite. I won't waste my time, but if you are still having issues & are in Dload still via USB, let me know.
To the naysayers, look up a little old project called FrankenKaiser. I have been in QC_Dload many times & am still using my device today. Much depends on how far the update got & what radio/HBoot & rom version (GB or ICS) you have flashed or partially flashed. I consider you lucky as this is a technical soft-brick.
The trick that is really cool is that from dload, you can write raw data into RAM. Just like I did when fixing Kaisers. If you had the AT&T original rom on your device, you may be in luck, as I have that somewhere between 40 & 60% memory mapped. This allows you to write the SPL from Hboot into ram, making your device think it has hboot, which allows you to then run hboot from ram, using it to re-install a real hboot onto the chip. The downside is that I was working with an S-Off hboot when doing this, but unless QC made some serious changes, it still may work.
Let me know where you are at, if you still have the device & it's status & I will see if I can dig up the S3 memory map. Otherwise, you can sped 30 - 50 & jtag the unit. Either way, you will need to be patient, have some knowledge of arm architecture & adb/fastboot type commands (understand what setting flags means, variables, & basic command (CMD) abilities. You must be precise when loading anything this way or it is big trouble.
Having a device in emergency dload can be a cool thing or a frightening thing depending on your experience. Fortunately, I had a lot of Kaisers & used them to try new things with Oli, Cmonex & Jocky, so I know exactly what it means & what it is doing (looking for). If still there, you can access & give radio commands or even send bytes to radio (rdata), allowing you to unsecure the device radio (2 bytes), which is one step in S-Off.
