Develop Bugs

[Q] 4.4.2 debrick.img i747

So i have an i747 galaxy s3 and was running 4.4.2, and i am hard bricked, let me assure you i have tried the 16gb micro sd debrick.img but it still wont work althought i only had a 4.3 debrick.img.So if some one can give me a 4.4.2 debrick.img by doing this
"busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"
And uploading it i would greatly appreciate it. i am not sure if this method will work and here is why, it was bricked by using a version of ezunlocker for a verizon phone to unlock my att phone's boot loader.If any one can help me out and upload the file that would be great and also if any one has any input regarding the usage of the ezunlocker and the status of my phone and the fix using the 16gb debrick.img method and can give any. again it would be great.

omeadsthename said:
So i have an i747 galaxy s3 and was running 4.4.2, and i am hard bricked, let me assure you i have tried the 16gb micro sd debrick.img but it still wont work althought i only had a 4.3 debrick.img.So if some one can give me a 4.4.2 debrick.img by doing this
"busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"
And uploading it i would greatly appreciate it. i am not sure if this method will work and here is why, it was bricked by using a version of ezunlocker for a verizon phone to unlock my att phone's boot loader.If any one can help me out and upload the file that would be great and also if any one has any input regarding the usage of the ezunlocker and the status of my phone and the fix using the 16gb debrick.img method and can give any. again it would be great.
Click to expand...
Click to collapse
i looked all over the internet for this. finally the right 4.4~ is found
https://www.androidfilehost.com/?w=files&flid=15759

The i747 bootloader is not locked. I have no idea what that Verizon app would have done, but if that's what bricked it, our debrick method may not work. We also have not been able to restore any 4.4.2 bricks yet. Thats why i posted a new script to create the image, in hopes that doing it a little differently would help.
I wish you luck, but considering how it was bricked, dont get your hopes up too much. Its still worth trying of course, but i have a feeling a jtag service might be the only way.

did same on my first s3 i747. tried to unlock a already unlocked bootloader. before i knew any better, went and got a new s3. (back in my pre-newb days...before i could even claim newbness status.lol), then discovered XDA. started reading and found out about jtag. now that s3 belongs to my brother.
not helpful, i know. just my story.good luck with debrick.img method.
:thumbup:
err on the side of kindness

Anybody know where I can get a debrick image for 4.1.2 (i747) ??
- Guy in desperate need who's been googling for wayy too long now

think theres one here.
http://forum.xda-developers.com/showthread.php?t=2525902
thanks to @DocHoliday77
good luck
err on the side of kindness

mrrocketdog said:
think theres one here.
http://forum.xda-developers.com/showthread.php?t=2525902
thanks to @DocHoliday77
good luck
err on the side of kindness
Click to expand...
Click to collapse
Thank you... Here goes nothing.

let us know how it goes.
err on the side of kindness

mrrocketdog said:
let us know how it goes.
err on the side of kindness
Click to expand...
Click to collapse
Unfortunately it did not work
I was orignally on 4.1.2 and flashed task650's newest AOKP release with CWM but for some reason was bootlooping and could not get past the "Swagger Activated" boot animation. So then I tried to revert back to the stock rom via Odin but I must have tried flashing a 4.3 stock rom because it's bricked pretty good now. Odin does not recognize the phone - device manager displays it as QSHUSB_DLOAD. I've tried making my own jig with no luck. And just recently, I've tried 3 different i747 debrick images using the sd card method (16gb / class 10). Up until just an hour ago, I could take the battery out and plug the phone into my laptop via usb cable and the red light would come on but that doesn't even happen anymore. When I hold down the 3 button combination everynow and then I'll hear Windows "device connect noises" as if it's trying to connect but nothing will happen. I know the correct Samsung drivers are installed on my pc because everything was showing up fine prior to me flashing the AOKP rom.
I'm beginning to think there no more hope for me. Idk if I wan't to bother having my phone shipped out and serviced or JTAG'ed or whatever.

Have you tried different sd cards. Many people find some won't work, while others do.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

omeadsthename said:
So i have an i747 galaxy s3 and was running 4.4.2, and i am hard bricked, let me assure you i have tried the 16gb micro sd debrick.img but it still wont work althought i only had a 4.3 debrick.img.So if some one can give me a 4.4.2 debrick.img by doing this
"busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"
And uploading it i would greatly appreciate it. i am not sure if this method will work and here is why, it was bricked by using a version of ezunlocker for a verizon phone to unlock my att phone's boot loader.If any one can help me out and upload the file that would be great and also if any one has any input regarding the usage of the ezunlocker and the status of my phone and the fix using the 16gb debrick.img method and can give any. again it would be great.
Click to expand...
Click to collapse
Try this Its a debrick image from a 4.4.2 SGH-1747 >>> filedropper.com/debrick <<<

Ehaeli said:
Try this Its a debrick image from a 4.4.2 SGH-1747 >>> filedropper.com/debrick <<<
Click to expand...
Click to collapse
do you have the actual link for that file?

think it might be in this thread..
http://forum.xda-developers.com/showthread.php?t=2820019
REMEMBER please....backup and read read read.
good luck:thumbup:
err on the side of kindness

Looking for a debrick image
Hello, I am looking for someone who can upload a debrick image for I747mvlufnh2 4.4.2 for the 16gb I have searched everywhere without any luck.

Gal tales said:
Hello, I am looking for someone who can upload a debrick image for I747mvlufnh2 4.4.2 for the 16gb I have searched everywhere without any luck.
Click to expand...
Click to collapse
ht#tp://d-h.st/w7g This is the one that worked for me on my sgh-i747M 4.4.2 with koodo . . ive got my phone to turn back on and now im working on getting it to turn on without the sdcard boot
i hope i linked it properly . im too new to post outside links so just remove the # when you copy and paste in the url

I need some for i747 only please !!!!

mitch0422 said:
ht#tp://d-h.st/w7g This is the one that worked for me on my sgh-i747M 4.4.2 with koodo . . ive got my phone to turn back on and now im working on getting it to turn on without the sdcard boot
i hope i linked it properly . im too new to post outside links so just remove the # when you copy and paste in the url
Click to expand...
Click to collapse
Im from mexico. And hard bricked my s3 i flashed a canadian nk2 kk. But when i turn it off never came on againg. So please help me. Im new to all this. I need examples with potatoes. Lol. What else do i need besides this image..
Enviado desde mi GT-I9505 mediante Tapatalk

bighleo114312 said:
Im from mexico. And hard bricked my s3 i flashed a canadian nk2 kk. But when i turn it off never came on againg. So please help me. Im new to all this. I need examples with potatoes. Lol. What else do i need besides this image..
Enviado desde mi GT-I9505 mediante Tapatalk
Click to expand...
Click to collapse
you can try here .....
http://forum.xda-developers.com/showthread.php?t=2549068
i see you found it. nevermind.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mitch0422 said:
ht#tp://d-h.st/w7g This is the one that worked for me on my sgh-i747M 4.4.2 with koodo . . ive got my phone to turn back on and now im working on getting it to turn on without the sdcard boot
i hope i linked it properly . im too new to post outside links so just remove the # when you copy and paste in the url
Click to expand...
Click to collapse
Mitch0422 i have downloaded the 4.4.2 image but i cant turn on my s3. Do i just need to write it to sd and turn on s3?
Enviado desde mi SCH-I535 mediante Tapatalk

Yes
bighleo114312 said:
Mitch0422 i have downloaded the 4.4.2 image but i cant turn on my s3. Do i just need to write it to sd and turn on s3?
Enviado desde mi SCH-I535 mediante Tapatalk
Click to expand...
Click to collapse
Sorry for the long wait for reply . i don't often check my email. To answer you question . Yes you have to write it to the microsd as a bootable image then insert the microsd and boot the phone . it might take awhile of holding down the power button before it shows signs of life. You might also have to take the battery out and try a few times . Once you have it booted back up use Odin to flash the stock rom back onto your phone then take out the sd card and try to turn it on. Follow these directions youtube.com/watch?v=8MnikrpUKZw

Identifying my S3 , confused :(

i m new to Android , i have s3 came from dubai. i dont know from where it belongs orignaly but baught from dubai. on its back its model no is I9300 which is international model but when i see its ram its 2Gb. i searched its imei no. it says my phone is T999 Galaxy S III
now i installed stock rom from sammmobile with odin for t999 .. its runing Good. but i am confused about my orignal model no of S3 . please help me

Someone has done a Transplant Surgery. Put the motherboard of T999 into a I9300 case.
You need to treat the phone as a T999 despite what it says on the case.

We seem to be seeing a lot of these "Franken-phones".:silly:

Bass_Man25 said:
We seem to be seeing a lot of these "Franken-phones".:silly:
Click to expand...
Click to collapse
Probably a lot of people are replacing the housing (few bucks on ebay and elsewhere) so they can sell it as "like new" or something. Thats my guess anyway.

Perseus71 said:
Someone has done a Transplant Surgery. Put the motherboard of T999 into a I9300 case.
You need to treat the phone as a T999 despite what it says on the case.
Click to expand...
Click to collapse
is there any way to know its body is changed or not ? i think its a refubrished phone ? should i return this phone because shopkeeper challenged me that its not a refubrished phone

DocHoliday77 said:
Probably a lot of people are replacing the housing (few bucks on ebay and elsewhere) so they can sell it as "like new" or something. Thats my guess anyway.
Click to expand...
Click to collapse
Doc! Good to hear from you man
Farooq Ch said:
is there any way to know its body is changed or not ? i think its a refubrished phone ? should i return this phone because shopkeeper challenged me that its not a refubrished phone
Click to expand...
Click to collapse
You just confirmed it by flashing t999 firmware in Odin, otherwise it would've failed or bricked the phone, it was either the motherboard or housing as Doc said
Sent from my SGH-M919 using Tapatalk

I wouldn't bother with trying for a return if it were me. You know it's a T999, so as long as you treat it as such, you should be fine. Up to you of course, but seems like it'd be a hassle and not much fun or return. And it could be that it is new and simply was a mistake at the factory. New employee grabs wrong box of parts type scenario. ...
Sent from my SM-N900T using Tapatalk

serio22 said:
Doc! Good to hear from you man
You just confirmed it by flashing t999 firmware in Odin, otherwise it would've failed or bricked the phone, it was either the motherboard or housing as Doc said
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
when this phone came it was rooted and model no showing in the about phone was " gt i9300 ". now i flashed stock rom 4.3 for t999 it shows t999 in about phone.. ? is this possible that t999 having rom for gt i9300 ? or gt i9300 have rom for t999?

It's easy enough to change what it reads in the about phone menu. I believe simply changing the build.prop value will do that.
Sent from my SM-N900T using Tapatalk

DocHoliday77 said:
It's easy enough to change what it reads in the about phone menu. I believe simply changing the build.prop value will do that.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
This^^ very easy to do do, I am currently running a ROM for i-9505 and changed it to show my original M919.. Now this two phones you can flash Roms vice versa, i9300 and t999, will brick!!
Sent from my SGH-M919 using Tapatalk

DocHoliday77 said:
It's easy enough to change what it reads in the about phone menu. I believe simply changing the build.prop value will do that.
Click to expand...
Click to collapse
Good to see you back Doc!
@op Best if you treat the phone as T999. I know you can make it look like I9300. But don't ever accidentally flash any of the I9300 stuff.

Perseus71 said:
Good to see you back Doc!
@op Best if you treat the phone as T999. I know you can make it look like I9300. But don't ever accidentally flash any of the I9300 stuff.
Click to expand...
Click to collapse
i have tried flashing i9300 rom when i didnt know the orignal model .. nothing hapend i tried many time to flash i9300 stock rom but it didnt brick my phone . it just get off and dont show any thing .. i tried some methods from internet it went to download mode again ... i think flashing other roms for all s3 model dont brick your phone. ? i dont think flashing t999 to my mobile confirms it that it is t999 motherboard.

If it's a t999, only T999 firmware will flash. Official firmware from any other model should fail.
And you cannot just flash any other S3's roms. I9300 and any US model are quite different from each other. The most compatible is the I747 from ATT. Other models require more work to port to our T999.
Sent from my SM-N900T using Tapatalk

Woah. This thread just opened my eyes. I bought a I9300 phone off of ebay in a "unopened - new" condition. It came in the original box and everything (which I now know he/she just repackaged it). When I got it, I tried to flash a stock I9300 rom on it. It failed, saying "wrong dev" type. And I soft bricked it.
Now, I thought this was all my fault. I booted into download mode and it said "T999" so I thought I installed the wrong bootloader and messed it up. I opened a support thread, which had over three pages of replies. Everyone told me to get a new motherboard because I installed the wrong bootloader. Everytime I tried to flash a stock I9300 rom, it said "wrong dev_type" in download mode. Nothing flashed. I thought my phone was permanently screwed up so I returned it to the seller and he refunded me. So I didn't even have to return it... could have just flashed a T999 stock rom (maybe..).
NOW I realize, my phone was probably ACTUALLY a T999. I could have probably fixed the soft brick by just flashing a stock T999 rom. Woah. I was just flashing the WRONG stock rom the whole time? Because I thought I had a I9300?
Maybe I'm getting this all wrong, but nobody in the 3 page support thread even brought up the idea of me having a T999. This is just mind blowing.
Regardless, I now have a brand new T999 phone. That I purchased as a "T999 phone" not a "I9300-actually-a-T999-phone".

Farooq Ch said:
i have tried flashing i9300 rom when i didnt know the orignal model .. nothing hapend i tried many time to flash i9300 stock rom but it didnt brick my phone . it just get off and dont show any thing .. i tried some methods from internet it went to download mode again ... i think flashing other roms for all s3 model dont brick your phone. ? i dont think flashing t999 to my mobile confirms it that it is t999 motherboard.
Click to expand...
Click to collapse
Well I guess recoveries have been updated to prevent the bricks between this phones, but this was definitely a problem before, saw too many people bricking their phones because they flashed i9300 ROMs on t999.. Either way it just won't work
Sent from my SGH-M919 using Tapatalk

[Q] Stock Firmware

Hello everyone i am in a peculiar situation i recently got s3 from my friend he said that it is I9300 but when i received it i came to know that it is T999 and not I9300 . My problem here is it came with android version 4.1.1 build number : I9300ZSEMC1 i didn't understand why it came with i9300 firmware ( i cannot ask my friend as he does not have much technical knowledge ) everything is working fine occasionally touch does not respond and i have bit of hard time switching on wi fi and weird battery drain problems what i want to know is , is these because of the i9300 firmware being present in t999 and whether is it advisable to update it further from 4.1.1 version to t999 latest stock firmware or to stick with the present version . If it is advisable to update to t999 based stock firmware i want to know whether it will work in indian carriers and wont have any problems and also can someone guide me for the right firmware link / build number to go with. :fingers-crossed:

I didn't know the firmware would actually flash across models.
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
I didn't know the firmware would actually flash across models.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
But it did ! Its a dual core version with 2 gb ram i verified it in download mode it stated as T999 and yet i wonder how is it running I9300 firmware !

toxicated2 said:
But it did ! Its a dual core version with 2 gb ram i verified it in download mode it stated as T999 and yet i wonder how is it running I9300 firmware !
Click to expand...
Click to collapse
Isn't the I9300 the 1gbp ram version?
Anyway, if certified in download mode you could just flash t999 firmware.
If that doesn't sound safe you can also put a t999 recovery on it and try doing a backup and installing a t999 rom
Sent from my SGH-T999 using Tapatalk

tokenpoke said:
Isn't the I9300 the 1gbp ram version?
Anyway, if certified in download mode you could just flash t999 firmware.
If that doesn't sound safe you can also put a t999 recovery on it and try doing a backup and installing a t999 rom
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I was thinking of using root_66 firmware for t999 will i end up locking the phone or will it work in indian network carriers after flashing tmobile firmware ?

toxicated2 said:
I was thinking of using root_66 firmware for t999 will i end up locking the phone or will it work in indian network carriers after flashing tmobile firmware ?
Click to expand...
Click to collapse
Sounds kinda like some of the "frankenphones" we've heard about over the last several months. Or it could also be a fake/chinese knock off. If I were you, I would see if there were any way to send it back to whoever sold it. If you plan to keep it though, understand anything you do is AT YOUR OWN RISK! The only absolutely safe course of action is to do nothing to it. If you try to flash it via Odin, and it allows it to flash, but you chose the wrong firmware, it WILL brick. There is honestly no possible way to know for sure what is up with the device.
If I had to guess, something is lying to you about what you are running. If your current firmware version is from an I9300, then that is most likely what you have. That firmware WILL NOT work on any Qualcomm, US model S3's. This tells me that its probably an I9300, and someone screwed with something, (or was careless when trying to copy Samsung), in the bootloader. Because it tells you it is a T999 in download mode, it will probably not let you flash the I9300 firmware. But if you try to flash the T999 firmware, there is a very good possibility you will brick it.
It is up to you what you want to try, but understand you are taking a bigger than normal risk since you already know the device isnt normal to begin with.
One way you can try to determine what motherboard it uses, (though this is by no means a for certain way to know), is go to the SIM unlock thread in General and try to follow those instructions. Also try the GPS fix thread in the Q&A sticky roll up. If I am not mistaken, both use dialer codes that are specific to Qualcomm devices. If they work, its a better chance of it being a T999. If they do not work, its more likely to be an I9300.

DocHoliday77 said:
Sounds kinda like some of the "frankenphones" we've heard about over the last several months. Or it could also be a fake/chinese knock off. If I were you, I would see if there were any way to send it back to whoever sold it. If you plan to keep it though, understand anything you do is AT YOUR OWN RISK! The only absolutely safe course of action is to do nothing to it. If you try to flash it via Odin, and it allows it to flash, but you chose the wrong firmware, it WILL brick. There is honestly no possible way to know for sure what is up with the device.
If I had to guess, something is lying to you about what you are running. If your current firmware version is from an I9300, then that is most likely what you have. That firmware WILL NOT work on any Qualcomm, US model S3's. This tells me that its probably an I9300, and someone screwed with something, (or was careless when trying to copy Samsung), in the bootloader. Because it tells you it is a T999 in download mode, it will probably not let you flash the I9300 firmware. But if you try to flash the T999 firmware, there is a very good possibility you will brick it.
It is up to you what you want to try, but understand you are taking a bigger than normal risk since you already know the device isnt normal to begin with.
One way you can try to determine what motherboard it uses, (though this is by no means a for certain way to know), is go to the SIM unlock thread in General and try to follow those instructions. Also try the GPS fix thread in the Q&A sticky roll up. If I am not mistaken, both use dialer codes that are specific to Qualcomm devices. If they work, its a better chance of it being a T999. If they do not work, its more likely to be an I9300.
Click to expand...
Click to collapse
I decided to go ahead with flashing root66 firmware and selected the latest 4.3 can't express how nervous i was to find out the outcome of it and then finally when the process was over to my surprise i did not face any bootloops or any other problem infact the network seemed to be working well and no problems as far now happy !! Thanks for the help @DocHoliday77 @tokenpoke

toxicated2 said:
I decided to go ahead with flashing root66 firmware and selected the latest 4.3 can't express how nervous i was to find out the outcome of it and then finally when the process was over to my surprise i did not face any bootloops or any other problem infact the network seemed to be working well and no problems as far now happy !! Thanks for the help @DocHoliday77 @tokenpoke
Click to expand...
Click to collapse
There is a chance that someone modified the model number in the phone to access certain apps or something.
I remember modifying a phone to do that go some exclusive app a couple years ago.
Sent from my SGH-T999 using Tapatalk

[Q] Samsung Galaxy S3 SGH-i747m with Fido Hard Bricked???

Hello from Montreal Quebec,
I unrooted my S3 yesterday back to the original firmware 4.3 (factory reset) Everything was working fine with the phone. I turned off the phone and when I tried to turn it back on... nothing happened, no vibration, nothing, would not power on, screen blank. I did try to get it into download and still nothing. So I think my phone is Hard Brick. Just so you know, my battery is 100%.
I did try putting the debrick image for my phone (debrick-SGH-I747M-UEMK5) on a 16gb sd card using Win32DiskImager. With number attempts of pressing the volume down + home key + power button for 15-30 seconds, nothing works.
One thing I notice, if I plug in my phone to my pc or wall for a few seconds, the red light for charging will come on so I know there is some kind of life. Sometimes when I put in the battery, the Torch light will flash once, but no luck getting the phone into download mode.
Would I need Jtag to get this back up and running and is there any other way to do this without Jtag?
Please let me know, any help would be appreciated.
Thank You.
qks

Plug onto the computer and open device manager. If it shows QHSUSB_DLOAD its hard bricked.
In this case if the debrick method doesn't work, jtag is the only other option. Try different sdcards first if you can. Many times it doesn't work simply because of the sdcard.
What worries me though is how this happened. Did you flash anything before the factory reset? If not, its possible you could be looking at a hardware failure such as the memory. Hopefully not though...
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Plug onto the computer and open device manager. If it shows QHSUSB_DLOAD its hard bricked.
In this case if the debrick method doesn't work, jtag is the only other option. Try different sdcards first if you can. Many times it doesn't work simply because of the sdcard.
What worries me though is how this happened. Did you flash anything before the factory reset? If not, its possible you could be looking at a hardware failure such as the memory. Hopefully not though...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, I did what you said and I see nothing in device manager. The red light came on while the battery and sd card was in the phone...
What happen was I un-rooted the phone using "How to Unroot Samsung Galaxy S3! [No Computer] [AT&T/T-Mobile/Verizon]" on youtube which I can't post here.
I have done this many time with this phone (About 5 times) without any problems. This is a first for me and I'm puzzled.

So you did or did not flash something before resetting?
Did it used to connect to the computer and are you using the stock usb cable? If yes, it sounds like hardware problems.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
So you did or did not flash something before resetting?
Did it used to connect to the computer and are you using the stock usb cable? If yes, it sounds like hardware problems.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I flash the original firmware if that's what you're saying. I did exactly what I mentioned in the video on YouTube which at the moment I can't post outside links but this is the title on YouTube... "How to Unroot Samsung Galaxy S3! [No Computer] [AT&T/T-Mobile/Verizon]"
I used stock usb cable.

Dont take it wrong, not intending this to sound rude, but I generally dont watch vids that people use. I like to answer what I can and move on. It just takes a lot less time to read that you flashed the firmware and factory reset than to watch a vid to see what you did.
One thing the video cant tell me for sure though is what firmware you had before and which did you flash this time. I know you said original, but that original version will depend on when you actually bought the device.
looking back over the thread though, im wondering if you did have 4.3 firmware, and then flashed 4.4.2 firmware with Mobile Odin? Is this accurate?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Dont take it wrong, not intending this to sound rude, but I generally dont watch vids that people use. I like to answer what I can and move on. It just takes a lot less time to read that you flashed the firmware and factory reset than to watch a vid to see what you did.
One thing the video cant tell me for sure though is what firmware you had before and which did you flash this time. I know you said original, but that original version will depend on when you actually bought the device.
looking back over the thread though, im wondering if you did have 4.3 firmware, and then flashed 4.4.2 firmware with Mobile Odin? Is this accurate?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
No worries man, I had firmware 4.3 rooted and then flashed with stock 4.3. with Mobile Odin. Never had a problem before until now.

Ok, just wanted to be sure. If you had flashed 4.4.2 over 4.3 with mobile odin, it would permanently break your phone, but it happens exactly how you described in the op.
Which 4.3 firmware was running on it and which did you flash? I just noticed there are several different 4.3 builds for the I747M. MK5, MK3, ND2, ND3.
You tried the mk5 debrick.img, but if you had ND2, for example, that image probably won't work. It could also just be that your sdcard isnt right. Were you able to try any different ones?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Ok, just wanted to be sure. If you had flashed 4.4.2 over 4.3 with mobile odin, it would permanently break your phone, but it happens exactly how you described in the op.
Which 4.3 firmware was running on it and which did you flash? I just noticed there are several different 4.3 builds for the I747M. MK5, MK3, ND2, ND3.
You tried the mk5 debrick.img, but if you had ND2, for example, that image probably won't work. It could also just be that your sdcard isnt right. Were you able to try any different ones?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I used the I747M 4.3 build as always. I did not try the mk5 debrick cause it's not I747m but I can try that and see if it works. Going to look for one now.
As for SD Cards, I have a 16GB and a 32GB, no luck.

qks said:
I used the I747M 4.3 build as always. I did not try the mk5 debrick cause it's not I747m but I can try that and see if it works. Going to look for one now.
As for SD Cards, I have a 16GB and a 32GB, no luck.
Click to expand...
Click to collapse
Sorry mk5 is I747M, my bad.
I tried
debrick-SGH-I747M-UEMK5
debrick-SGH-I747U-CUEMJB3
No luck...

MJB wont work on the I747M. MK5 will probably only work if you are sure thats what you were running. As I mentioned before there are several 4.3 builds for that model. Some depend on your carrier.
For example Telus and Koodoo, and possibly one or two other carriers got updates from MK5 to ND2. So if you had been updated to the newer ND2 build (still 4.3), that MK5 image isnt going to work.
If you are certain you were running MK5, then it could be the sdcard youre using is the problem, or it may not be recoverable using that method.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
MJB wont work on the I747M. MK5 will probably only work if you are sure thats what you were running. As I mentioned before there are several 4.3 builds for that model. Some depend on your carrier.
For example Telus and Koodoo, and possibly one or two other carriers got updates from MK5 to ND2. So if you had been updated to the newer ND2 build (still 4.3), that MK5 image isnt going to work.
If you are certain you were running MK5, then it could be the sdcard youre using is the problem, or it may not be recoverable using that method.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Yes I am very sure. This one I used. I747MVLUEMK5_I747MOYAEMK5_FMC
Never heard of ND2 till now.

Ok, then its either the sdcard or its not recoverable without a jtag service.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Ok, then its either the sdcard or its not recoverable without a jtag service.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I tried 5 other SD cards... Nothing, so looks like I'm gonna have to pay for Jtag... Thanks for you help.

No problem. Sorry it didnt work out. I cannot remember where it was, but in the last week or two (maybe 3?), someone posted about a jtag service that only cost $25. Cheapest ive heard of. Pretty sure it was in this forum, just haven't been able to find it again. Still, figured id let you know its out there!
Good luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Bricked S3 i747 and not sure where to go from here

I wanted to update my S3 from whatever version it was on to the newest one available. I essentially wanted to start with a blank phone I went into the TWRP recovery and wiped cache, system, data, etc. I guess that was the entirely wrong way to do it because after that I installed the dirty unicorn rom (DU_d2att_5.1.1_20150723-1444.v9.4-UNOFFICIAL), and it got stuck on the boot screen. Thinking there was something wrong with the install I tried a factory reset and reflashing. It got stuck on "patching system image unconditionally" because there was something wrong with the system partition I think. I let it sit overnight and it stayed on this part.
The next day I read a bunch of things and thought it was just a bad ROM file or something. I went and downloaded the newest stable cyanogenmod (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att) to try and make it work. It installed without error and looked like it was going to work, i even wiped dalvik cache to up the chances of success. It also hung on the boot screen. I left it alone for a few hours and it still didn't progress.
After some more research I found a post that I thought would correct my partitions and make it bootable again. It was using adb commands to do something:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
I did this from recovery and the first two commands worked. The third shot back an error. I tried modifying it according to other users who have found success and it didn't work for me. I went ahead and hit reboot anyway and now the phone doesn't respond. It doesn't power on, it only has a charging light when plugged in without the battery.
I have tried to fix this as well, I tried a slew of different debrick.img files on a 16gb sd card formatted with Win32 Disk Imager. None of those were able to get me back to download mode. This is where I'm stumped. Is there a debrick.img I'm supposed to use and haven't found yet? Or am I just SOL with this method?
Thanks in advance

Have you tried using different SD cards?

audit13 said:
Have you tried using different SD cards?
Click to expand...
Click to collapse
I've tried two 16gb, an 8gb, and 64gb.

Not sure why the images didn't work. Did you try the recommended SD cards? The phone is an i747 according to the label under the battery?

audit13 said:
Not sure why the images didn't work. Did you try the recommended SD cards? The phone is an i747 according to the label under the battery?
Click to expand...
Click to collapse
Yes, I've tried the recommended SD cards and the phone is i747. I'm thinking maybe I need to find a debrick image from the android versions I was trying to upgrade to?

scyther3989 said:
Yes, I've tried the recommended SD cards and the phone is i747. I'm thinking maybe I need to find a debrick image from the android versions I was trying to upgrade to?
Click to expand...
Click to collapse
I think it would be more successful to use a debrick image made for the bootloader and modem on your phone rather than that matches the Android version of the ROM you were trying to flash.
Both of the ROMs you mentioned were Android 5.1.1, but the highest bootloader you could have is 4.4.2 on the i747. To get more precise, for the i747 there would be three different 4.4.2 bootloaders; NE4, NJ1, or NJ2. I'm fairly certain that I have seen a debrick image for at least one of these. Do you recall what bootloader is on your phone?

dawgdoc said:
I think it would be more successful to use a debrick image made for the bootloader and modem on your phone rather than that matches the Android version of the ROM you were trying to flash.
Both of the ROMs you mentioned were Android 5.1.1, but the highest bootloader you could have is 4.4.2 on the i747. To get more precise, for the i747 there would be three different 4.4.2 bootloaders; NE4, NJ1, or NJ2. I'm fairly certain that I have seen a debrick image for at least one of these. Do you recall what bootloader is on your phone?
Click to expand...
Click to collapse
I don't remember any of the specs on what version it was before I started tinkering with it. But if it's down to those three bootloaders, can't I just find debricks for all three of them and try them out?
Another thing I'm curious of is I think I had a i747m rom installed as they were very similar when I was using the s3 is it possible to have a i747m bootloader on an i747 device?

scyther3989 said:
I don't remember any of the specs on what version it was before I started tinkering with it. But if it's down to those three bootloaders, can't I just find debricks for all three of them and try them out?
Another thing I'm curious of is I think I had a i747m rom installed as they were very similar when I was using the s3 is it possible to have a i747m bootloader on an i747 device?
Click to expand...
Click to collapse
The ROMs should be interchangeable, but I don't think the bootloaders are. I expect using the other bootloaders would brick a working phone.
There would be a lesser chance of problems using the debrick image with the newest bootloader you can find. (Best would be the one that matched your bootloader, but not possible in this case.) One with an older bootloader than you were running probably wouldn't fix your phone.

dawgdoc said:
The ROMs should be interchangeable, but I don't think the bootloaders are. I expect using the other bootloaders would brick a working phone.
There would be a lesser chance of problems using the debrick image with the newest bootloader you can find. (Best would be the one that matched your bootloader, but not possible in this case.) One with an older bootloader than you were running probably wouldn't fix your phone.
Click to expand...
Click to collapse
So my best bet would be to find the newest i747 and i747m debricks around until one works?

scyther3989 said:
So my best bet would be to find the newest i747 and i747m debricks around until one works?
Click to expand...
Click to collapse
I don't know if the i747M images would work on the i747. But the normal method of using a debrick image would have you booting from the external sdcard and then installing the bootloader and modem. Even if you could boot from a i747M debrick image, I think loading the bootloader and modem from one would be bad. I guess you could boot from the i747M debrick image and then be certain that it is an i747 bootloader and modem you install.
So, I would say the newest i747 that you can find. What say you @audit13 ?
Please keep in mind that I have not used a debrick image of any kind, I am only making suppositions from what I have read and recall from the relevant threads. (Although, it looks like I will be using on to resurrect the i535 I bought for hacking and modding. :fingers-crossed: )
---------- Post added at 02:32 AM ---------- Previous post was at 02:07 AM ----------
See if this post helps. He was in your same predicament.
The only life the phone had was remove battery and plug charger in and the red light came on.
Click to expand...
Click to collapse

dawgdoc said:
I don't know if the i747M images would work on the i747. But the normal method of using a debrick image would have you booting from the external sdcard and then installing the bootloader and modem. Even if you could boot from a i747M debrick image, I think loading the bootloader and modem from one would be bad. I guess you could boot from the i747M debrick image and then be certain that it is an i747 bootloader and modem you install.
So, I would say the newest i747 that you can find. What say you @audit13 ?
Please keep in mind that I have not used a debrick image of any kind, I am only making suppositions from what I have read and recall from the relevant threads. (Although, it looks like I will be using on to resurrect the i535 I bought for hacking and modding. :fingers-crossed: )
---------- Post added at 02:32 AM ---------- Previous post was at 02:07 AM ----------
See if this post helps. He was in your same predicament.
Click to expand...
Click to collapse
After a few more hours of trying a bunch of different debrick images, I haven't been able to make it work. I have about 15 debrick images from anyone who said "this one worked for me." I think at this point I'll just look for some of the newer images around to see if that helps. Also, I see some debrick files coming in 256 and 512 variants, what is that about?