Develop Bugs

Have I bricked my phone :( - Experts plz help!

Guys,
!!!!! N00B Alert - I am not an expert in what I am doing. Just following instructions from experts like you. I will try to be as technically articulate as possible !!!
I had recently (about a month ago) rooted my phone to install CM 10.2. I love CM.
In an attempt to unlock my phone I wanted to get back to stock ROM. So I googled and bumped into a way to do it from Kies (not sure if it was a good idea). I followed the instructions and boom the firmware initialization failed half way through. Now when I turn my phone on I get this error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So I tried again multiple times but it won't work.
Then I thought may be there is another way and googled and found this thread - http://forum.xda-developers.com/showthread.php?t=2186967
Followed the instructions to the word, but I see the dreaded FAIL message in ODIN.
Below is the log. (I tried twice in one stretch).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Another thing is I am not able to get to recovery mode. When I try I can only get to the Firmware error screen I mentioned above.
Any help to get out of this mess would be great!

did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

andrewjae04 said:
did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I didnt know I have to have the LK3 bootloader, may be I missed in the instructions.
Anyway, how do I flash Clockworkmod from Odin? if I can do that I can get back to CM 10.2 and then try paying for unlock code.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

andrewjae04 said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank You!
andrewjae04 said:
http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I am on AT&T.
After I read your post about flashing CWM with ODIN I researched and found a method. I tried it and it PASSED!. Then my phone restarted and boom it booted directly into CM 10.2. Not sure how, felt a bit creepy. Then I updated to latest Nightly CM 11 build and brough back all my apps and my phone has LIFE right now. Thanks for the tip! :good:

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
I believe if you were originally on 4.1 then you still have that bootloader. I dont think OTA updates the bootloader so you should be able to downgrade with the root66 if that is the case.

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
This is why your flash to stock failed, lucky for you. The MJB bootloader is not downgradable and if 'successful' is bad news...aka brick, requiring serious hacking if not JTAG service to repair. As far as ROM's go as long they do not attempt to change the bootloader (none i've seen do, but you never know) the worst that could happen is a 'status 7' fail in recovery and no change to your firmware, pertaining to the bootloader that is. There are any number of other reasons why something could go wrong during the process. MJB has been around long enough most customs ROM's have probably adapted their updater-script to include it. If not there are ways around this I (and several others) have documented elsewhere. My advice moving forward, make sure to educated yourself thoroughly before attempting anything that can brick your device and if you are not sure, ask first flash later.

dmplus said:
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.
Click to expand...
Click to collapse
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233

audit13 said:
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233
Click to expand...
Click to collapse
I had tried to flash that via odin without success. What I was able to do to fix the issue was to flash a custom recovery via odin (TWRP). Then use the custom recovery to blind flash (no signature or md5 check) the ATT modem, and then I was able to flash the link you sent. After that it still didnt boot, so i had to reboot in TWRP, dump caches, reboot again, wait, literally like 5 minutes and it came back to life. Whew, what a day.

[Q] Can't install a rom

Okay. So I flashed a rom onto my Galaxy S3 (actually a friend's but whatever) and the camera bugged out entirely, far worse than I expected. Okay, no biggy, so I tried to restore the backup I made. That wont work for some odd reason. I get stuck at the white AT&T screen. So I figured it was safe to assume that I needed a new rom. Factory reset yields the same result. I'm okay with going back to stock rom, I don't really care. I just want it to work again.
I tried flashing a stock rom with odin, which yields this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And I cannot figure out how to access the phone in my computer.
I can get into download mode and I have a relatively recent version of TWRP recovery installed. If I can either a) get a flashable rom or b) get into the phone I should be able to fix it.
Any advice appreciated!
EDIT: May have figured out why odin wont flash. Was not aware of the locked bootloader that prevents downgrading. The only stock rom I could find was for 4.1.1, and honestly assumed it was fine. Searching for a new stock rom now and trying that.

Don't flash a stock ROM with Odin. It's failing because the ROM is trying to downgrade your bootloader. Attempts to downgrade the bootloader could brick your phone.
The bootloader is not locked on the s3.
You need to find out which bootloader is on your phone in order to flash the right files.

audit13 said:
Don't flash a stock ROM with Odin. It's failing because the ROM is trying to downgrade your bootloader. Attempts to downgrade the bootloader could brick your phone.
The bootloader is not locked on the s3.
You need to find out which bootloader is on your phone in order to flash the right files.
Click to expand...
Click to collapse
Okay, assume I'm a total moron. What would you suggest?
Before this, it was running stock 4.4.2, if that helps determine the bootloader.

tylerrex96 said:
Okay, assume I'm a total moron. What would you suggest?
Before this, it was running stock 4.4.2, if that helps determine the bootloader.
Click to expand...
Click to collapse
Boot into TWRP. Then go into Advanced -> Terminal Command. You'll have to select a folder. It doesn't matter what you pick, just select one. A less sensitive area like sdcard might be safer than say /, but you won't be entering any commands that alter anything.
To check your bootloader enter:
Code:
getprop ro.bootloader
Knowing that will help with what to do next.

jason2678 said:
Boot into TWRP. Then go into Advanced -> Terminal Command. You'll have to select a folder. It doesn't matter what you pick, just select one. A less sensitive area like sdcard might be safer than say /, but you won't be entering any commands that alter anything.
To check your bootloader enter:
Code:
getprop ro.bootloader
Knowing that will help with what to do next.
Click to expand...
Click to collapse
I don't have the phone on me, just about to go work on it. However, if I could access the SD card and place a rom of some sort on it, would it be safe to flash? I was just thinking. I'll let you know of the results of that in a few minutes.

From custom recovery flashing ROMs is relatively safe because the zips packaged to be flashed from custom recovery don't typically mess with your bootloader. Messing with the bootloader seems to be the most common way to brick an at&t gs3.
Odin is another story. Odin tars often will flash firmware, especially the"return to stock" variety, and from mjb forward the bootloader on the i747 can't be downgraded.
I'd still verify what firmware you're on before flashing anything else.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

jason2678 said:
From custom recovery flashing ROMs is relatively safe because the zips packaged to be flashed from custom recovery don't typically mess with your bootloader. Messing with the bootloader seems to be the most common way to brick an at&t gs3.
Odin is another story. Odin tars often will flash firmware, especially the"return to stock" variety, and from mjb forward the bootloader on the i747 can't be downgraded.
I'd still verify what firmware you're on before flashing anything else.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

I realized that I am in fact a total moron. The original rom (CM12 5.0.1 or w/e) that had the huge problem with the camera was still on the phone. I reflashed that so the phone would show in My Computer, and then just downloaded/flashed a different rom.
Thanks for the help anyway guys! I don't intend to mess with phones that aren't mine anymore haha, getting the recovery to stick was hard enough alone.

Help with a soft-bricked SGH-I747

This SGH-I747 (I think it is for AT&T, but I'm in Canada so I'm not sure) updated OTA from 4.3 to 4.4.2 (I think), and rebooted OK. Next, I let it update KNOX, and on the next reboot it went into a reboot loop. Now I'm trying to fix that. I can't get into recovery mode (it shows the blue "RECOVERY BOOTING..." text at the top of the screen, but reboots before reaching the recovery menu), but I can get it into download mode. Neither Kies or ADB recognize the device when it is plugged in my Windows 7 machine, but Odin can connect and flash firmware to it. This is my first try fixing a bricked phone.
I've tried flashing a few different versions of stock images from sammobile, but most fail within a few seconds of starting the process with Odin (1.85, 3.9, or 3.10) with 'Fail (Auth)' in Odin's messages. I guess that is KNOX blocking downgrades to anything under 4.4.2 or 4.3. I can get all the way through the flashing process with I747MVLUFOB1_I747MOYCFOB1_I747MVLUFOB1_HOME.tar.md5 (Bell 4.4.2 for SGH-I747M) however the phone is still stuck in a reboot loop afterwards. Odin's output from that is:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFOB1_I747MOYCFOB1_I747MVLUFOB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Right now, the top left of the phone's 'Downloading...' screen says:
ODIN MODE
PRODUCT NAME: SGH-I747M
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
The sticker behind the battery says the phone is an SGH-I747 (not a SGH-I747M). I think I should be looking for a AT&T 4.4.2 ROM, but I haven't found one yet (just the Canadian carrier versions, or OTA upgrade packages that look too small to be useful). I don't have a SD card to use. What should I try next to get this phone working again? There's no important data on this phone to lose, and I don't mind using non-official software if I have to. I don't know much about boot loaders or custom recovery mods yet.

Do not try to flash i747m bootloader to an i747 as this would probably brick your phone.
There is no stock ATT 4.4.2 ROM as AT&T never made it available. 4.4.2 was only available as an OTA update.

> Do not try to flash i747m bootloader to an i747 as this would probably brick your phone.
Too late! Did it before I even posted here The fun part is to figure out what I can do next. I can still get to the download screen. I've tried flashing it with an AT&T 4.1.1 ROM (I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5), but Odin fails like this:
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
From what I'm reading, it is a bit more work to downgrade from 4.3 (even I hadn't flashed the I747 with I747M firmware) because KNOX locks the bootloader somehow. I'm guessing that putting a new bootloader on the phone is a step in the right direction towards getting the stock 4.1.1 firmware running. I found this thread, but I'm not sure if it is what I need: http://forum.xda-developers.com/showthread.php?t=2321310

If the phone does not say i747m on the label in the battery compartment, the phone is an AT&T version of the s3. I have 3 s3 phones is various states of disrepair and they all say i747m.
You flashed a 4.4.2 i747m ROM, including bootloader and modem, onto the i747. You cannot flash any bootloader that is older than the one you installed. It is not knox that is blocking the bootloader downgrade.
Knox has nothing to go with locking the bootloader as all bootloaders on the i747 and i747m have never been locked. Using apps that "unlock" the bootloader will probably brick the phone, as will flashing an internation s3 ROM.

Thanks for helping me confirm it is the AT&T version. Since there is no official AT&T 4.4.2 (or newer) firmware, restoring the phone using any sort of official Samsung firmware must not be an option. Do you think using a newer 3rd party ROM is an option? I see this list of ROMs with Android 4.4.4 and 5.x (http://forum.xda-developers.com/galaxy-s3-att#romList), but I wonder if I can install any of them over what's on the phone right now (Bell 4.4.2). I don't think I have anything to lose by trying these out, unless there is something more reliable I should try first.

The phone may not be booting because the file ROM, boot, and modem paritions on an i747 maybe different from an i747m.
You could flash a custom recovery (CWM, Philz Touch, or TWRP) to the phone and use that to install a custom ROM. If the ROM boots, that would be a start. If the ROM can start and you can get a signal to make a call and surf via cellular networks and wifi, that would be great.

Enewman17 has a thread with stock 4.4.2 for the i747, he built it from image dumps. I believe there is an option to revert to stock recovery if needed.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
dawgdoc said:
Enewman17 has a thread with stock 4.4.2 for the i747, he built it from image dumps. I believe there is an option to revert to stock recovery if needed.
Click to expand...
Click to collapse
This is the thread http://forum.xda-developers.com/showthread.php?t=2788357

> The phone may not be booting because the file ROM, boot, and modem paritions on an i747 maybe different from an i747m.
Is this something that a PIT file can help with? I found one called sgh-i747-16gb.pit at d-h.st/x9S that I could try running with Odin.
I rooted the phone with CF-Auto-Root (CF-Auto-Root-d2att-d2uc-samsungsghi747.zip from autoroot.chainfire.eu) via Odin, and flashed it with CWM 6.0.4.7 (CWMS3ATTrecovery.tar galaxys3root.com/cwmtwrp-recovery/) with Odin as well. Now I can get into CWM Recovery! That's progress. I could not get into stock recovery earlier. I'll try more tomorrow.
I'll be very happy if I can get this device running and connecting to Wi Fi. Cellular is not important right now.

Since the phone has a custom recovery, are you able to flash the latest cm11 to the phone and have it boot properly?
The pit file may not help without a stock rom that can be flashed in Odin but I am not sure about this as I have no experience with cross-flashed bootloaders or modems.

Yeah, this must look pretty weird. I bought a SD card and I'm deciding what to try next. I know the bootloader version is I747MVLUFOB1. I downloaded some Cyanogen builds for the I747 and I'm looking in their `updater-script` files to see if any will install over what I have.
cm-11-20140210-SNAPSHOT-M3-d2att is looking for certain boot loaders and won't install on a device with I747MVLUFOB1.
Then there are the newer unified builds:
cm-11-20141112-SNAPSHOT-M12-d2lte isn't picky about boot loaders. It just checks ro.product.device and ro.build.product is acceptable (d2att in my case), so that could work.
cm-11-20150426-NIGHTLY-d2lte isn't picky about boot loaders. It just checks ro.product.device and ro.build.product is acceptable (d2att in my case), so that could work.
I'll try cm-11-20141112-SNAPSHOT-M12-d2lte, then cm-11-20150426-NIGHTLY-d2lte if M12 doesn't work.

I tried installing cm-11-20141112-SNAPSHOT-M12-d2lte and cm-11-20150426-NIGHTLY-d2lte from a .zip file on the SD card (16GB class 10). I wiped the phone's caches first. Neither resulted in the phone booting successfully. After rebooting from CWM, the Samsung logo appears, and then the screen goes back to black. I wait a few minutes, and then pull the battery when it doesn't look like there is any activity.
I can still access CWM which is promising. I'm going to look into riskier stuff like dawgdoc's suggestion, or trying to install a I747 boot loader unless people have other suggestions.

xancow said:
I tried installing cm-11-20141112-SNAPSHOT-M12-d2lte and cm-11-20150426-NIGHTLY-d2lte from a .zip file on the SD card (16GB class 10). I wiped the phone's caches first. Neither resulted in the phone booting successfully. After rebooting from CWM, the Samsung logo appears, and then the screen goes back to black. I wait a few minutes, and then pull the battery when it doesn't look like there is any activity.
I can still access CWM which is promising. I'm going to look into riskier stuff like dawgdoc's suggestion, or trying to install a I747 boot loader unless people have other suggestions.
Click to expand...
Click to collapse
how about trying a different recovery as @audit13 suggested earlier. if i'm not mistaken cwm development stopped long ago.
good luck.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
how about trying a different recovery as @audit13 suggested earlier. if i'm not mistaken cwm development stopped long ago.
good luck.
Click to expand...
Click to collapse
Thanks for the reminder! I skipped over Philz Touch and installed TWRP (twrp.me/devices/samsunggalaxys3att.html) with Odin 3.10.6. TWRP looks like it hasn't been updated in 3 years (github.com/TeamWin/device_samsung_d2att) but it was able to flash cm-11-20141112-SNAPSHOT-M12-d2lte. This time I can boot into CyanogenMOD, use WiFi and both cameras. ADB recognizes the device. Big success! The funny part is the phone still thinks its model number is SGH-I747M in Settings > About Phone.
Next step is installing the Google apps, and then curiosity will drive me to try out other versions of Cyanogen or other operating systems.
Thanks for the help audit13 & mrrocketdog! Hopefully I've left a good trail of info for anyone else who screws their phone up line this.

good to here. all credit to @audit13.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

A pleasant surprise (I swear, this wasn't the goal) - I put a Fido sim card into the phone and it could make and receive calls, and use data. I didn't try texting.

Does everything now work? Your phone is still recognized as an i747m?

audit13 said:
Does everything now work? Your phone is still recognized as an i747m?
Click to expand...
Click to collapse
Everything I've tried so far works. No stability issues browsing the net over WiFi which is what it will mostly be used for. The OS thinks the model number is SGH-I747M. Baseband version is from the Bell 4.4.2 ROM I flashed to it. The Kernel and Build # are from CyanogenMOD.

Well, this is certainly interesting because it appears that cross-flashing will turn an i747 into an i747m which makes recovering from a bad flash much easier.

HELP!!!! Galaxy S3 SGH-747. Cant restore firmware. Think its bricked!

I have a galaxy s3 and i rooted it. Then after a while when i booted the phone it the att logo pops up and the boot sound stops. The phone then stays like that with the LED pulsing blue. I tried odin to restore and it wont work. I tried flashing a new custom rom. Wont work. What do i do?
this is what i get in odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
warranty Bit: 1

After you use Odin to factory reset boot to stock recovery and do a factory reset and then let the phone boot the first time
Sent from my GT-N7105 using Tapatalk

rogersb11 said:
After you use Odin to factory reset boot to stock recovery and do a factory reset and then let the phone boot the first time
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
i tried odin and it failed. SW REV CHECK FAIL: Fused 3> Binary 0
i have cwrm installed. i think somethings wrong with the bootloader? Havent used android inyears so. i dont know whats going on...

donwload TWRP to your phone model, use odin to install and trie to do a reset factory, after that donwload firmware http://forum.xda-developers.com/showthread.php?t=1968625 copy to you phone and install use twrp

I would use Odin to flash TWRP recovery and then factory reset it, or use it to flash a rom, ur CWM may be too old to flash newer roms, try an updated version of TWRP
Sent from my XT1585 using Tapatalk

soupysoup said:
I would use Odin to flash TWRP recovery and then factory reset it, or use it to flash a rom, ur CWM may be too old to flash newer roms, try an updated version of TWRP
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
I ended up installing a rom but i still get the freezing. is thre anyway to flash every bit of the phone so that its as if it was brand new? because i dont know what modem version and other stuff my phone was at. had all the latest updates. what can i do. if i flashed the wrong bootloader or something would it even start?

BakedOnSomeSour said:
I ended up installing a rom but i still get the freezing. is thre anyway to flash every bit of the phone so that its as if it was brand new? because i dont know what modem version and other stuff my phone was at. had all the latest updates. what can i do. if i flashed the wrong bootloader or something would it even start?
Click to expand...
Click to collapse
No if u flashed the wrong bootloader or something it wouldn't even boot, there would be no coming back from a bad bootloader flash, I would try installing TWRP and then reset, then flash it stock with odin
Sent from my XT1585 using Tapatalk

Odin is failing because the ROM you are trying to flash has a bootloader that is older than the bootloader in the phone.
Before flashing anything else, I recommend finding the bootloader and modem version of the phone. Once you have this information, you will have a better idea of what you can and can't flash. An incompatible bootloader/modem combination could hard brick the phone too.

audit13 said:
Odin is failing because the ROM you are trying to flash has a bootloader that is older than the bootloader in the phone.
Before flashing anything else, I recommend finding the bootloader and modem version of the phone. Once you have this information, you will have a better idea of what you can and can't flash. An incompatible bootloader/modem combination could hard brick the phone too.
Click to expand...
Click to collapse
where can i find that info. i know it was updated to the latest software version. i cant remember all the info for it though. is there any way to get it? i cant get the phone to boot into OS so....

BakedOnSomeSour said:
where can i find that info. i know it was updated to the latest software version. i cant remember all the info for it though. is there any way to get it? i cant get the phone to boot into OS so....
Click to expand...
Click to collapse
i think i fixed it. will update

audit13 said:
Odin is failing because the ROM you are trying to flash has a bootloader that is older than the bootloader in the phone.
Before flashing anything else, I recommend finding the bootloader and modem version of the phone. Once you have this information, you will have a better idea of what you can and can't flash. An incompatible bootloader/modem combination could hard brick the phone too.
Click to expand...
Click to collapse
fixed it with this http://forum.xda-developers.com/gal...t/rom-d2att-ucufnj2-stock-rom-deodex-t3183267
without the help of all of you i woulda passed out lol

need to reprogram as the phone stuck at Samsung Galaxy S III

My phone got crashed which can't bootup. The phone always stayed with Official release, never rooted. I am not sure which version has been upgraded to, now it stuck with Galaxy S 3 screen, only thing I know it has the SecureLinux enabled, so it must be either 4.3 or 4.4. I wanted to reprogram to the official firmware, but not sure if I reprogram to the wrong version, would that causes any problem?
Please help.

additional infomation:
at download mode:
PRODUCT nAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE

Does this download menu look like 4.2?
Or it is 4.3 , I dont see warrenty flag.
Thanks.

No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.

audit13 said:
No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.
Click to expand...
Click to collapse
The phone is T999 for T-mobile, but seems there is one time only that it had official release of 4.2.1 or 4.2.2 available. I am not sure if I should flash the 4.1.2 or 4.2.1 back. But I seem can't find the 4.2.1 or 4.2.2 firmware on line anymore.
Question is that if I try to flash 4.1.2 to the phone, would it cause any problem if it was in 4.2.1?
Thanks all, I know this probably an old issue.

Flashing 4.1.1 or 4.1.2 should be fine.

audit13 said:
Flashing 4.1.1 or 4.1.2 should be fine.
Click to expand...
Click to collapse
###Right now I can't go to recovery mode, so I am trying to program the stock recovery, but failed. When I tried to odin the stock 4.1.2 it failed too. Here is the error during flashing stock recovery.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried different USB cables? Different USB ports? The rom cam from sammobile.com?

audit13 said:
Tried different USB cables? Different USB ports? The rom cam from sammobile.com?
Click to expand...
Click to collapse
Here is the error msg:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)

It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.

audit13 said:
It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.
Click to expand...
Click to collapse
thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3?

You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.

thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3? All I want is just get the phone back. I tried to load 4.3 bootloader, but it failed.

audit13 said:
You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
There is possibility that the pit is wrong, I tried to load the downloaded T999-16Gb pit from download site, maybe that file is not right? Since I can flash the stock boot.img by using Odin for version 4.1.2, the bootloader must be right???, Don't know what aboot.mbn would be affected by anything else.
I am wondering if someone can provide the T999 regular 16GB pit file, the early version of T999, Thanks.

A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.

audit13 said:
A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.
Click to expand...
Click to collapse
is it possible that the phone is upgrading from 4.1.2 to 4.3 and got crashed. but the bootloader is still showing 4.1.2?
what other possible reason that I can't flash aboot.mbn?

Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.

audit13 said:
Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.
Click to expand...
Click to collapse
Reboot to download mode, it is saying the same.
I am trying to flash stock recovery, modem, bootloader, all stock version 4.1.2 Only it can flash 4.1.2 bootloader, the recovery and modem always fails. Also the stock rom got failed.
With the same setting I can flash my other S3 recovery without problem, so the Odin, USB cable should not be an issue.
Thanks.

Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.

audit13 said:
Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.
Click to expand...
Click to collapse
the only problem is that my other working phone is running 4.3. I don't know what is the procedure to program it to 4.3 if my crashed one is in 4.1.2