Develop Bugs

[Q] Unable to flash 4.2.2 stock rom over 4.1.2 rooted stock rom

Hi,
I am using rooted, deodexed stock rom on my Note 8.0. (Android 4.1.2)
I just want to flash stock 4.2.2 rom on the device using Odin.
But it fails with this message:
Code:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
What could be wrong with my setup ?
Btw, my Note 8.0 is N5105 (a version of N5100 without phone app) , but the current ROM on the device is rooted, deodexed N5100 rom.

mrmrmrmr said:
Hi,
I am using rooted, deodexed stock rom on my Note 8.0. (Android 4.1.2)
I just want to flash stock 4.2.2 rom on the device using Odin.
But it fails with this message:
Code:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
What could be wrong with my setup ?
Btw, my Note 8.0 is N5105 (a version of N5100 without phone app) , but the current ROM on the device is rooted, deodexed N5100 rom.
Click to expand...
Click to collapse
Hi,
I guess I've accidentally deleted my partition table. Can anyone help me with a pit file ?

...

Hi,
I'm sorry to ear that, but could you be more specific about your Note 8 ? Is it the LTE Canadien Version from Bell/Telus/Rogers?

no. I have the 3G version (N5100) with 16GB internal sd.

I believe the LTE version pit file could solve this as long as it has 16GB internal memory.

Ok; the problem is solved.
I installed the stock recovery and then made a factory data reset through stock recovery.
That option resets the partition table.
Good to know...

so, now that the partition problem is solved, can anyone give me an idea about why I am unable to flash stock 4.2.2 through Odin ?
Thanks.

mrmrmrmr said:
so, now that the partition problem is solved, can anyone give me an idea about why I am unable to flash stock 4.2.2 through Odin ?
Thanks.
Click to expand...
Click to collapse
Bad download? Check the md5. Happens sometimes.

You may consider to change the ROM file name from tar.md5 to tar. Then, remove tz, sboot and modem from the tar file and flash it. The idea is not to flash the bootloader and the modem. Not sure if this is applicable to your case.

mayday2 said:
You may consider to change the ROM file name from tar.md5 to tar. Then, remove tz, sboot and modem from the tar file and flash it. The idea is not to flash the bootloader and the modem. Not sure if this is applicable to your case.
Click to expand...
Click to collapse
good idea. I will try this.
if sboot is bootloader and modem is modem what is tz.img ?
and which tool should I use to remove files from tar file ?
winrar does not delete.
I would also like to try changing bootloader so that it is totally N5100 from now on.
isn't that possible ? (any other methods ?)

mrmrmrmr said:
good idea. I will try this.
if sboot is bootloader and modem is modem what is tz.img ?
and which tool should I use to remove files from tar file ?
winrar does not delete.
I would also like to try changing bootloader so that it is totally N5100 from now on.
isn't that possible ? (any other methods ?)
Click to expand...
Click to collapse
Tz.img is Trusted Zone. I dunno what it is for. Normally, there is not such file for stock rom from Samsung if bootloader is not updated.
Changing bootloader not for your device is very risky and might hard brick you device.
Sent from my GT-N5120 using xda app-developers app

mayday2 said:
Tz.img is Trusted Zone. I dunno what it is for. Normally, there is not such file for stock rom from Samsung if bootloader is not updated.
Changing bootloader not for your device is very risky and might hard brick you device.
Sent from my GT-N5120 using xda app-developers app
Click to expand...
Click to collapse
thx. how can I remove the files in tar ?

mrmrmrmr said:
thx. how can I remove the files in tar ?
Click to expand...
Click to collapse
How about 7zip?
Sent from my GT-N5120 using xda app-developers app

tried 7zip just now.
when opening the file it says "There is no correct record at the end of archive"
is that because of the md5 ?
and it doesn't also remove files...

mrmrmrmr said:
tried 7zip just now.
when opening the file it says "There is no correct record at the end of archive"
is that because of the md5 ?
and it doesn't also remove files...
Click to expand...
Click to collapse
I also use ALZip. It should work.
Sent from my GT-N5120 using xda app-developers app

Alzip is successful to remove the files.
I will try flashing this crippled tar file later tonight.
but I seriously would like to try updating bootloader.
isn't tehre any safe way to do it ?
is the bootloader integrated with download mode ? I mean does the download mode remain if bootloader is corrupted ?
thx.

Hi again,
I've tried installing the stock rom without tz, sboot and modem files. It was successful.
But there was no app to call "settings" in the app drawer. Also, the settings button on the menu did nothing.
So this stock 4.2.2 for Germany does not have settings app. Is that possible ?

once you are rooted, why arent you flashing roms in recovery, insted of using Odin?

mrmrmrmr said:
Hi again,
I've tried installing the stock rom without tz, sboot and modem files. It was successful.
But there was no app to call "settings" in the app drawer. Also, the settings button on the menu did nothing.
So this stock 4.2.2 for Germany does not have settings app. Is that possible ?
Click to expand...
Click to collapse
It seems abnormal. Anyway, you may try to install another launcher, said Apex, and see if it can call the setting app.
Sent from my GT-I9300 using xda app-developers app

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.

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.

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

Samsung Tab 8.4 sm-t320 bootloader locked?

HI All
Firstly, long time read of this forum/app, first time poster. Flashed a number pf phones/tablets over the years since i first flashed my Windows HTC HD (?) to Android Gingerbread. Forgive the details there, it was a long time ago and I could be slightly wrong.
In any case I usually have no problem following the odd customer rom flashing guide or rooting guide, etc and generally get done what I need to,. However after a few late nights and admittedly having not flashed anythign for a couple of years I am really struggling to flash my t320 with anything!
I cannot seem to flash TWRP so I am coming to te conclusion the bootloader is locked. I have read around and it seems as though it shouldnt be locked or I should have an OEM Unlock option in developer options - I do not!
I have managed to root it though using Odin and the CF Auto Root but if I try runnig TWRP app to flash TWRP or Flashify to flash a lineage ROM I do not seem to get anywhere. It just boots as normal with TWRP and I dont get any TWRP in recovery mode. Flashify result in a boot loop so I had to reflash the root to get it to boot,
When I enter into download recovery mode the following shows on the screen:
ODIN MODE
PRODUCT NAME: SM-T320
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
WRITE PROTECTION: Enable
UDC Start
I am hoping someone can dicipher this and tell me what the problem is. Clearly it looks like somethign is securing the bootloader.
Oh yes and this is the UK WIfi model running stock Kitkat 4.4 (updated as far as I can get it OTA)
Thanks in advance

@radioshed I've flashed my T325 again not to long ago, after I had to return to stock. So I know bootloader isn't locked.
Did you take care to boot directly into TWRP after flashing it via Odin?
If you let it reboot automatically the stock recovery gets reanimated.
Uncheck "auto reboot" in Odin and do it manually.
I never use anything else but Odin and read that TWRP app isn't recommended to use.
Know nothing about flashify.
Rooting stock isn't necessary as you're going to flash a custom ROM anyhow.

Yea I had auto reboot off and booted into recovery when Odin finished.
Looked just the same. No TWRP
Not sure what else to do

bmwdroid said:
@radioshed I've flashed my T325 again not to long ago, after I had to return to stock. So I know bootloader isn't locked.
Did you take care to boot directly into TWRP after flashing it via Odin?
If you let it reboot automatically the stock recovery gets reanimated.
Uncheck "auto reboot" in Odin and do it manually.
I never use anything else but Odin and read that TWRP app isn't recommended to use.
Know nothing about flashify.
Rooting stock isn't necessary as you're going to flash a custom ROM anyhow.
Click to expand...
Click to collapse
Rather than using Odin to flash TWRP and then that for a customrom, can I just use Odim for the rom?
If so which box do I use in Odin?
Thanks for your response btw

radioshed said:
Yea I had auto reboot off and booted into recovery when Odin finished.
Looked just the same. No TWRP
Not sure what else to do
Click to expand...
Click to collapse
Which file did you take and where from?

radioshed said:
Rather than using Odin to flash TWRP and then that for a customrom, can I just use Odim for the rom?
If so which box do I use in Odin?
Thanks for your response btw
Click to expand...
Click to collapse
Odin can not flash custom ROMs

bmwdroid said:
Which file did you take and where from?
Click to expand...
Click to collapse
I have the cf auto root for the t320 which I downloaded. That worked tho
I got the tar file for TWRP from the TWRP website, the apk too.
I've tried both to flash the TWRP recovery but I still seem to end up with the original recovery screen

radioshed said:
I have the cf auto root for the t320 which I downloaded. That worked tho
I got the tar file for TWRP from the TWRP website, the apk too.
I've tried both to flash the TWRP recovery but I still seem to end up with the original recovery screen
Click to expand...
Click to collapse
After flashing turn it off and reboot with button combo.
Perhaps you were not fast enough when rebooting directly after flashing. I sometimes need to flash TWRP several times.
You've put it in "AP" didn't you?

You've flashed tar file?

bmwdroid said:
After flashing turn it off and reboot with button combo.
Perhaps you were not fast enough when rebooting directly after flashing. I sometimes need to flash TWRP several times.
You've put it in "AP" didn't you?
Click to expand...
Click to collapse
Yea in the AP section. Auto reboot off.
Boot straight into recovery. No change

What does Odin say after flashing?

bmwdroid said:
You've flashed tar file?
Click to expand...
Click to collapse
Yeaa I have, don't have the filename to hand as it's on my laptop. But yea I've done it a few times

Which Odin btw?

Ermm I have 2 versions. One that came with the auto root and a slightly newer version.
I'll confirm when I get on my laptop

The older the stock the older Odin has to be.
Try 3.09 or older.

Ooo ok never thought of that thanks for the tip.

OK So i have some more details...still no change here though unfortunately
I have just tried a few TWRP flashes using Odin 3.09 but also tried 3.14.1 and 3.10.6 for CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5 which does work
I have tried flashing the following files from https://eu.dl.twrp.me/mondrianwifi/:
twrp-2.8.4.1-mondrianwifiue.img.tar
twrp-3.1.1-0-mondrianwifiue.img.tar
twrp-3.1.1-0-picassowifi.img.tar (not sure where i got this one from)
twrp-3.5.2_9-0-mondrianwifi.img.tar
not sure what else to do but cant get rid of the download recovery screen

bmwdroid said:
What does Odin say after flashing?
Click to expand...
Click to collapse
<OSM> All threads completed. (succeed 0 / failed 0)
<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> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
<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> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

radioshed said:
OK So i have some more details...still no change here though unfortunately
I have just tried a few TWRP flashes using Odin 3.09 but also tried 3.14.1 and 3.10.6 for CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5 which does work
I have tried flashing the following files from https://eu.dl.twrp.me/mondrianwifi/:
twrp-2.8.4.1-mondrianwifiue.img.tar
twrp-3.1.1-0-mondrianwifiue.img.tar
twrp-3.1.1-0-picassowifi.img.tar (not sure where i got this one from)
twrp-3.5.2_9-0-mondrianwifi.img.tar
not sure what else to do but cant get rid of the download recovery screen
Click to expand...
Click to collapse
After flashing around that much it might be helpful to return to a clean system/device by flashing multiple part stock ROM via Odin and then start again flashing just TWRP without CF prior to that.
picassowifi is the 10.1" tab btw.
I'd stick to 3.09 until TWRP is flashed as I know it worked on mine while having stock.

bmwdroid said:
After flashing around that much it might be helpful to return to a clean system/device by flashing multiple part stock ROM via Odin and then start again flashing just TWRP without CF prior to that.
picassowifi is the 10.1" tab btw.
I'd stick to 3.09 until TWRP is flashed as I know it worked on mine while having stock.
Click to expand...
Click to collapse
Thanks pal, I tried that last night, flashed back to stock 4.4.2 using Odin 3.09.
Altho the download I found for it only seemed to have one tar file. Not sure if I need a BL tar too.
Still no dice tho dammit