Related
I have searched these forums and everywhere else I can find mentioning this problem online, but nothing has worked yet. I'm hoping someone here may be able to point me in the right direction.
I rooted my AT&T Galaxy Note 2 SGH-I317 a couple weeks ago and was messing around and stupidly tried upgrading to 4.3, and now I can't boot and can't enter recovery mode. NOTE: Download mode works just fine, either by manually holding Volume Down/Home/Power or by using a USB Jig, I just can't enter recovery mode by holding Volume Up/Home/Power
I am able to flash just fine with Odin (I have tried version 3.07 and 3.09), it says Pass every time but the darn phone still won't boot and won't let me into recovery mode so that I may clear the cache and get it to boot.
I have tried flashing back to the factory firmware, to which Odin says Pass but still no go on the boot.
I have also tried setting up an ADB connection in Windows 7 (so that I may get the phone into recovery mode without hardware buttons), but since my computer will only recognize the phone when it's in download mode (since I can't boot the phone so Windows 7 will see it like it normally would) ADB won't work.
I'm at my wits end here, does anyone have any clue how I may fix this problem? What's really frustrating is I just bought a Galaxy Gear Watch and about a week later messed up my phone
Thanks, and I appreciate any help you can give me.
EDIT: Forgot to mention something. When I turn the power to the phone on and don't enter download mode, it stays on the Samsung Galaxy Note II screen, and that's all that happens.
Also, this is exactly what my Download screen info says:
FACTORY MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: Yes(6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 1
RP SWREV: A2
Got the phone to finally boot up
I finally got my phone to at least boot up. Although, I still can't get into recovery mode.
I followed this post: http://forum.xda-developers.com/showthread.php?t=2596256 and downloaded this file
It boots, and is currently 4.1.2, however when I try to get to recovery mode, the graphics flicker and the screen goes blank for a couple mins then reboots to the OS.
geekinator said:
I finally got my phone to at least boot up. Although, I still can't get into recovery mode.
I followed this post: http://forum.xda-developers.com/showthread.php?t=2596256 and downloaded this file
It boots, and is currently 4.1.2, however when I try to get to recovery mode, the graphics flicker and the screen goes blank for a couple mins then reboots to the OS.
Click to expand...
Click to collapse
I had a similar issue moving from Jedi to Jedi Master X.
I had to use an older Odin 2.85 to install a CWM recovery(I prefer TWRP UI)
Once I had the CWM I could install Jedi Master X2 and I had to wait about 30 mins for it to get through boot.
I thought I had a good soft brick but eventually I found a combiination of Odin, recovery and Rom to get it to work.
Good Luck
Recovery screen is now up!
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.
geekinator said:
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.
Click to expand...
Click to collapse
Update to 4.3 official will fail if you have a custom recovery...
I suggest using the leaked 4.3 we have...
It will give you all of the gear functions....and allow you to keep root and dump the bloat that you don't want...
A best case situation ....IMHO....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
geekinator said:
After I was able to boot, I tried flashing again to stock firmware, and this time the recovery menu works just fine! I'm almost back to where I need to be. After resetting to factory defaults, I'm hoping I can do an OTA update to 4.3 so my Galaxy Gear will work again.
Click to expand...
Click to collapse
Glad you were able to figure it out... I just had a similar problem because TWRP froze up on me halfway through flashing a ROM. Had to ODIN CWMR back on and flash a ROM... lesson learned... always keep a ROM on your SD card in case your phone soft bricks - if you can get into download mode at least you will be able to work around it!!
I'll give that a try
gregsarg said:
Update to 4.3 official will fail if you have a custom recovery...
I suggest using the leaked 4.3 we have...
It will give you all of the gear functions....and allow you to keep root and dump the bloat that you don't want...
A best case situation ....IMHO....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
Thanks, I'll definitely give that a try.
geekinator said:
Thanks, I'll definitely give that a try.
Click to expand...
Click to collapse
Instead of the leaked you can use the official without locking yourself into the 4.3 bootloader
http://forum.xda-developers.com/showthread.php?t=2589891
hi to all my senior
---------- Post added at 07:25 AM ---------- Previous post was at 07:17 AM ----------
i have problem with my samsung note 2 i317 of white screen of death i tried flashing with many file but no successes it always fail (ODIN) with latest version im able to go to download mode tryed with most of the firmware please help if any body can thankks in adv.
FACTORY MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY:Samsung official
SYSTEM STATUS: Custom
this much it shows on the download mode screen pls help Thanks.
i have problem with my samsung note 2 i317 of white screen of death i tried flashing with many file but no successes it always fail (ODIN) with latest version im able to go to download mode tryed with most of the firmware please help if any body can thankks in adv.
FACTORY MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY:Samsung official
SYSTEM STATUS: Custom
this much it shows on the download mode screen pls help Thanks.
Hey, so my note 2 (sgh-i317m variant) running 4.3 is stuck on the samsung screen and I cannot boot into recovery (it just stays at the samsung screen). What I believe caused this is the fact that I originally had it rooted, but flashed back to stock via odin to update to 4.3. Then I proceeded to re root it via odin and the cf auto root, however I forgot to factory reset before doing this. Now its stuck on the samsung screen and I cannot even get it into recovery mode. I can get it into download mode but whenever I try reflashing the stock rom (I have two different ones) neither of them work and Odin just displays "fail". I really dont know what else to do, hoping someone will know, thanks in advance.
Friend, try Google for KIES3. After installation under the Menu bar..look into something recoveries..
There you'll need to enter your model and serial no.
Boot your hp to DOWNLOAD MODE and plug to your usb. Then let KIES do its work.
Hope it helps
53N53L355 said:
Friend, try Google for KIES3. After installation under the Menu bar..look into something recoveries..
There you'll need to enter your model and serial no.
Boot your hp to DOWNLOAD MODE and plug to your usb. Then let KIES do its work.
Hope it helps
Click to expand...
Click to collapse
That didnt work
Mbrar15 said:
Hey, so my note 2 (sgh-i317m variant) running 4.3 is stuck on the samsung screen and I cannot boot into recovery (it just stays at the samsung screen). What I believe caused this is the fact that I originally had it rooted, but flashed back to stock via odin to update to 4.3. Then I proceeded to re root it via odin and the cf auto root, however I forgot to factory reset before doing this. Now its stuck on the samsung screen and I cannot even get it into recovery mode. I can get it into download mode but whenever I try reflashing the stock rom (I have two different ones) neither of them work and Odin just displays "fail". I really dont know what else to do, hoping someone will know, thanks in advance.
Click to expand...
Click to collapse
POST the complete ODIN log here.
...
Mbrar15 said:
Hey, so my note 2 (sgh-i317m variant) running 4.3 is stuck on the samsung screen and I cannot boot into recovery (it just stays at the samsung screen). What I believe caused this is the fact that I originally had it rooted, but flashed back to stock via odin to update to 4.3. Then I proceeded to re root it via odin and the cf auto root, however I forgot to factory reset before doing this. Now its stuck on the samsung screen and I cannot even get it into recovery mode. I can get it into download mode but whenever I try reflashing the stock rom (I have two different ones) neither of them work and Odin just displays "fail". I really dont know what else to do, hoping someone will know, thanks in advance.
Click to expand...
Click to collapse
Did you end up figuring it out?
I turned on my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected. This occurred after using Odin for something I downloaded from http://forum.xda-developers.com/showthread.php?t=1739426.
asodiu said:
I was messing around with my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected.
Click to expand...
Click to collapse
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Larry2999 said:
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Click to expand...
Click to collapse
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
After flashing, did you boot to recovery and wipe data and cache?
audit13 said:
After flashing, did you boot to recovery and wipe data and cache?
Click to expand...
Click to collapse
As I have said, I am unable to boot to recovery or boot to download mode. I did not wipe data and cache.
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
asodiu said:
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
Click to expand...
Click to collapse
I recommend getting your hands on the Android SDK and using adb to boot into download and recovery modes. I got a water damaged d2att from friend a few months ago and the old volume down key doesn't work and using the command prompt and adb, you can get it to boot to whichever mode you want.
Sent from my SPH-L710 using Tapatalk
asodiu said:
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
Click to expand...
Click to collapse
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Larry2999 said:
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Click to expand...
Click to collapse
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
asodiu said:
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
Click to expand...
Click to collapse
Glad to know it's working fine now. Unless the firmware for the 2 phone models have identical build numbers, I'd be surprised the post suggested that cross-flashing may be OK.
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.
I have the ATT Galaxy S3 SGH-i747. Before I flashed this ROM I was running 4.4.4 from the Cyanogenmod stable release and it worked perfect. I had that with a 3.4 Kernel. Now flashing this rom and going through all the prompts in CWM the phone went black upon restart and has stayed that way ever since. Is there anything I can do?
The rom that screwed me:
http://forum.xda-developers.com/galaxy-s3/development/rom-blekota-s5-lite-beta-4-5-1-t2752331
jcz28 said:
I have the ATT Galaxy S3 SGH-i747. Before I flashed this ROM I was running 4.4.4 from the Cyanogenmod stable release and it worked perfect. I had that with a 3.4 Kernel. Now flashing this rom and going through all the prompts in CWM the phone went black upon restart and has stayed that way ever since. Is there anything I can do?
The rom that screwed me:
http://forum.xda-developers.com/galaxy-s3/development/rom-blekota-s5-lite-beta-4-5-1-t2752331
Click to expand...
Click to collapse
that ROM would have worked perfect if you had the i9300/i9305. did you try the battery pull method to get back to recovery? did you do the button combo to try to get back to recovery? when you hook up to charger , do you get a red led and that only ? do you know your current bootloader/modem version ?
heres a link to de-brick thread.
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
@mrrocketdog is correct in that you need to try the de-brick images. If that doesn't work, you'll have to have it repaired via jtag.
Flashing an i9300 (international s3) onto a North American (i747/i747m) is guaranteed to brick the phone.