Try Odin 3.07 which is what I always use.
When connecting to your computer, any unknown or new devices appear in the device list?
Do you have a screen shot of the download screen on your phone?
Yes, my computer does detect the phone now. I tried flashing the stock rom with odin v3.07 and it gives an error saying there is no PIT partiton. (succeed 0/failed 1) Here is a screenshot of the phone, sorry for the terrible quality its from my old iphone 3gs:
im on sgh-i747 pre 4.3im getting this message in odin when trying to flash twrp
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 /
when trying to flash full stock mjb firmware it says no pit partition even tho i have one..
im doing this because my phone wont boot up..always a message "unable to do normal boot" tho odin
says pass still cant access recovery.. only unuseful odin now..
ATT S3 i747 previously broke when flashing 'stock 4.4' through Odin.
Still have a problem though. Was previously on 4.4.2 and I found this cache of 4.4.2 bootloader, modem, ROM: https://www.androidfilehost.com/?w=files&flid=15759
I was able to load up the bootloader and that allowed me to then boot into at least recovery without the debrick card. The modem also loaded up okay but I cannot get the ROM to load. I had to use a custom 4.4.x kernal since that link didn't have an explicitly separate kernal (I expect it's built into the ROM file) I've tried this stock one as well as CM11. Any ideas?
Error message: "error executing updater binary in zip..."
I would like to try to Odin back to 4.3 but I read all this stuff about how once you go to 4.4 you cannot go back...maybe would want to try to load up all the separate files but the only files in the OP are for the i747M and I feel like that will brick my i747 if I even try. I can't find a good stock 4.4 source to Odin...obviously the one source I had didn't work so I don't trust anything that's not XDA. All help HUGELY appreciated and again, THANK YOU!
updated to TWRP 2.8.5 and now get the following error: assert failed: getprop...
getprop | grep version.baseband
Definintely do not try to Odin back to 4.3 if you installed any 4.4.x bootloader and modem.
Before doing anything else let's be absolutely certain of the bootloader and modem your phone is running on. (I was not certain what you used based on the link you provided. There are a number of debrick images, bootloaders, and stock ROM dumps on that page.) Since you have TWRP installed you can use the terminal emulator built into it. Run these commands for a definitive answer.
getprop ro.bootloaderWas the error message you received from attempting to install CM11, a 4.3 ROM, or some other ROM? Specifiy the ROM that gave the message, please. I would expect that message from trying to install a ROM that was built before the release of your installed bootloader.Code:
getprop | grep version.baseband
BTW: AT&T did not release any complete 4.4 ROMs compatible with Odin. Most of the Stock 4.4.x ROMs in the forum are from XDA folks who captured the images from OTA prior to flashing and then built them as Recovery flashable zips. But, for the i747M there may be Odin flashable 4.4.x series Stock ROM. That could be the root of the issue.
All that being said, I still don't understand why you cannot downgrade. As stated and evidenced, the bootloarder, modem, even kernel (which is usually built into the ROM anyways) is compatible with both 4.4 and 5.0. What about the higher ROM breaks things such that it no longer allows one step back to work? Is there any real way to reverse it? For future knowledge...so I'm more careful about what I'm doing.
Generally the NE4 and NJ1, the most recent bootloaders released for the i747 by AT&T, should be safe with all of the current Lollipop ROMs. I guess it is feasible that an updater-script of a ROM would only allow the NJ1 bootloader, I just haven't read of one yet. For now there should be no issues downgrading from Lollipop to KitKat if you do not try to change bootloaders and modems. The caveat is that it may require wiping /system and very possibly the internal sdcard due to changes in the partition layout. I have read of several having troubles until they did so.
Interesting. I assume this information pertains to the S3 only, with every other device having their own oddities. I didn't try, but would you think a different custom recovery might have allowed me to install the 4.4 ROM? If I tried to do it right now, it most likely wouldn't work. I sort of want to kick back to 4.4 since it had a fully functional camera and YouTube however it is nice to have Lollipop.
Every time I run into problems, one of the biggest issues is actually finding the files I need. I can understand the ROM's, bootloaders and other phone related things, but I'm just baffled by the lack of flashable recovery files. Every custom recovery out there should have links for an Odin flashable, zip flashable, img and app installable available for every device. Additionally, it would be nice if CM started putting out Odin flashable ROM's as well. Just to give us an alternate to stock factory crap that is usually broken by ATT anyways.
Hey guys, I'm curious about the possibilities of downgrading from 4.3. I get the impression that under some circumstances it may actually be possible. If so I'm hoping that I fall into the lucky SOB category. I received an S3 i747 that was still on stock 4.1.1 LK3. Unfortunately I got some files mixed up and flashed a ROM for the international S3 and the only method that finally got it running again was this one. I do have a backup from before the brick when I was running the 4.4.4 Pac Man ROM, but still on the LK3 bootloader. Can I downgrade from the MJB 4.3 using that backup or will I just end up with another brick? Thanks for any help that anyone can offer.
Did the international ROM you flashed include a bootloader?
When you talk about an mjb backup, are you referring to a nandroid backup?
How to UNBRICK:
Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3
What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...
What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.
What you need:
- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
- The ability to write the dump image to the micro sdcard.
What to do:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
Odin that thing back to the 4.3 stock rom. Yes you have to. You ain't getting 4.1.2 bootloaders back so dont think about odining that thing either. it wont boot, with out the SD with the 4.3 bootloader on it installed. Odining back is the best thing to do, it will get the right boot loader on your EMMC. If you are feeling adventurous and you had a custom recovery installed. You can boot to recover instead of download from the debricking SD boot, and install a 4.3 flashable zip bootloader there, if all goes well, you wont lose your data and the bootloader will be functional on the EMMC. Either method you choose after its done "flashing" what ever method. remove the sd and verify it boots on its own.
Note: a user stated that he flashed a bootloader via recovery and flashable zip, and he stated it appeared to flash the bootloadeerr to the micro sd. if this happens, ODIN back to the proper rom to get the internal EMMC rebuilt and booting.
If it does, do a dance or something.
Here is a flashable Bootloader for the i747M 4.3
Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Broken link I will update IF/AFTER it is fixed is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)
This one is for AT&T phones.
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.
dmesg | tail
dd if=/path_to_debrick.img of=/dev/sdX
parted /dev/sdX print