Develop Bugs

[Q] Help!! ROM flashing problems

Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/

dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486

Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help

dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991

Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?

dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks

[Q] No carrier/SIM support after 4.3 stock restore

My ATT SGH-i747 was rooted and running 4.4.2 until an OTA this past weekend soft-bricked the phone. Phone would boot to a blank screen but still allowed access to download and recovery modes, thankfully.
With help from this awesome forum, and a stock 4.3 flash via ODIN, thanks to enewman17's epic efforts and thread , the phone is back, but now won't recognize the SIM - and baseband version is "unknown" - I suspect I need to now go up to 4.4.2 to get the hw recognized by the sw. Went to ATT and they put a new SIM in but to no avail
CWM recovery is gone, but I can reload that easily enough...
Do I need to just flash the modem, or is the bootloader involved too?
Is there a single flash or .zip that will get the ROM (incl CSC and Modem) up to 4.4.2 in one shot?
I never really wanted to go this deep but here I am so now I'm looking for advice or direction as there are so many directions to look... thanks in advance!

Mismatch in firmware
Digging deeper, using Phone Info *Samsung*, I have noted the following
bootloader version: I747UCUFNJ1
baseband version: <blank>
pda version: I747UCUEMJB
csc version: I747ATTEMJB
skip a bit...
modem version: <blank>
hardware revision: <blank>
mobile operator name: <blank>
mobile network code: <blank>
So it would seem I have a mis-match of versions, where it seems all should be the same..
Would it be safe to flash to MJB following this thread?
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654

OCTANEJUNKIE said:
My ATT SGH-i747 was rooted and running 4.4.2 until an OTA this past weekend soft-bricked the phone. Phone would boot to a blank screen but still allowed access to download and recovery modes, thankfully.
With help from this awesome forum, and a stock 4.3 flash via ODIN, thanks to enewman17's epic efforts and thread , the phone is back, but now won't recognize the SIM - and baseband version is "unknown" - I suspect I need to now go up to 4.4.2 to get the hw recognized by the sw. Went to ATT and they put a new SIM in but to no avail
CWM recovery is gone, but I can reload that easily enough...
Do I need to just flash the modem, or is the bootloader involved too?
Is there a single flash or .zip that will get the ROM (incl CSC and Modem) up to 4.4.2 in one shot?
I never really wanted to go this deep but here I am so now I'm looking for advice or direction as there are so many directions to look... thanks in advance!
Click to expand...
Click to collapse
Your modem (baseband) appears to have been compromised in the process of downgrading from Kitkat. You could try either of the following solutions...
1) Flash the UCUEMJB modem via custom recovery to return you to complete stock 4.3. You can see the modem file here ....
https://www.androidfilehost.com/?fid=23269279319197285
2) Do a complete stock restore to 4.4.2. You can find the stock update zip via the following thread ...
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you can reflash the 4.3MJB modem, you can check to see if you can get an OTA update to 4.4.2. Using Option 2 requires you to be on complete stock 4.3 so this may not work if you currently don't have the baseband/modem. I would strongly advise you stick to the custom recovery flashable files for now and avoid Odin. You would, however, need to restore custom recovery via Odin.
Hope this works for you.

Larry2999 said:
Your modem (baseband) appears to have been compromised in the process of downgrading from Kitkat. You could try either of the following solutions...
1) Flash the UCUEMJB modem via custom recovery to return you to complete stock 4.3. You can see the modem file here ....
https://www.androidfilehost.com/?fid=23269279319197285
2) Do a complete stock restore to 4.4.2. You can find the stock update zip via the following thread ...
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you can reflash the 4.3MJB modem, you can check to see if you can get an OTA update to 4.4.2. Using Option 2 requires you to be on complete stock 4.3 so this may not work if you currently don't have the baseband/modem. I would strongly advise you stick to the custom recovery flashable files for now and avoid Odin. You would, however, need to restore custom recovery via Odin.
Hope this works for you.
Click to expand...
Click to collapse
Thanks for the detailed reply with links, Larry :good:
So I guess my plan of actions will be
1) re-install custom recovery w CWM to my external SD card as was previous
-do I *need* later version of CWM? Previous one of mine was 6.0.2.3, IIRC, that is what I can easily flash back to the phone
2) install .zip (from https://www.androidfilehost.com/?fid=23269279319197285) via CWM
If that doesn't work, I was interested in the S3Rx ROM vs. a stock 4.4.2 ROM - is there any way to go straight to a custom 4.4.2 ROM or should I get the modem working in 4.3 first?
Lastly, Where can I find a later version of a CW Recovery Touch .tar to flash via ODIN? (third stoopid noob question in this post, I know...)

Attempt to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip via CWM Recovery FAILED with Status 7, Installation aborted...
Bootloader version: I747UCUFNJ1
Baseband version: <blank>
Blank stare into space...

OCTANEJUNKIE said:
Attempt to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip via CWM Recovery FAILED with Status 7, Installation aborted...
Bootloader version: I747UCUFNJ1
Baseband version: <blank>
Blank stare into space...
Click to expand...
Click to collapse
You aren't the first to have this issue. This is why I am still on NE4 and did not take the OTA to NJ1. The update is pointless anyway, all it does is patch the kernel so towelroot won't work anymore aside from updating the bootloader.
Since your bootloader is NJ1, that is your firmware which cannot be downgraded. If you try, you will brick. You have to work with NJ1 files here only. Sure you can flash older modems, but stick to NJ1. I suggest using ODIN to flash a custom recovery, then use enewman17's NJ1 .zip file in said recovery to reflash all the NJ1 stuff. Then do a complete factory reset. You might need to flash stock recovery to do the hard factory data reset, as I am not sure if it can be done in CWM or TWRP.
In the future, I suggest freezing the update and not upgrading until people on here do it and report how it's working or rather not working in this case.

StoneyJSG said:
You aren't the first to have this issue. This is why I am still on NE4 and did not take the OTA to NJ1. The update is pointless anyway, all it does is patch the kernel so towelroot won't work anymore aside from updating the bootloader.
Since your bootloader is NJ1, that is your firmware which cannot be downgraded. If you try, you will brick. You have to work with NJ1 files here only. Sure you can flash older modems, but stick to NJ1. I suggest using ODIN to flash a custom recovery, then use enewman17's NJ1 .zip file in said recovery to reflash all the NJ1 stuff. Then do a complete factory reset. You might need to flash stock recovery to do the hard factory data reset, as I am not sure if it can be done in CWM or TWRP.
In the future, I suggest freezing the update and not upgrading until people on here do it and report how it's working or rather not working in this case.
Click to expand...
Click to collapse
Thanks for the response, Stoney :good:
I have CWM and TeamEpic v5 on external SD, so a version of custom recovery is there (CWM 6.0.2.3) - but do you have a link to enewman17's NJ1 .zip /recovery?
As far as freezing the updates in the future, yes. I tried to keep the OTA push from happening, apparently not ardently enough :crying:

OCTANEJUNKIE said:
Thanks for the response, Stoney :good:
I have CWM and TeamEpic v5 on external SD, so a version of custom recovery is there (CWM 6.0.2.3) - but do you have a link to enewman17's NJ1 .zip /recovery?
As far as freezing the updates in the future, yes. I tried to keep the OTA push from happening, apparently not ardently enough :crying:
Click to expand...
Click to collapse
Not a problem, glad to help when I can. I THINK this is the link you need: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
You might want to post in that thread asking if it works when you are already on NJ1 though, or get a hold of enewman17 via PM or something.

SOLVED!
enewman17 posted NJ1 modem .zip here, and now me has modem and cellular service again!
Question: can I update the thread tag from [Q] to [SOLVED] myself?

Try editing your original post.

audit13 said:
Try editing your original post.
Click to expand...
Click to collapse
Yup... Done [emoji222] [emoji222] [emoji222]

[Q] need help finding i747 4.4.2 stock rom

New galaxy user, here its a s3 for ATT 4.4.2 i747CUCFNE4. I have rooted using the Cf Auto-Root method.
Along the lines of trying to flash a new task manager apk, (for I had to factory reset my phone because the original task manager was missing) I came across a thread that had s5 apps (settings apk) and tried flashing this apk(don't laugh I know.) Then I couldn't get my phone to boot through the standard setup wizard. So I tried booting into recovery and factory resetting my phone clearing cache, dalvik, and partition.
My biggest problem arose when I chose to format system from ghe recovery.
I know all this can be fixed with odin but I can't find a 4.4.2 os link, I have read I can't simply downgrade my os. A link to a 4.4.2 stock rom thread would be greatly appreciated. I also have the Ktoonsez kernel installed if that makes any difference.

AT&T never released a full 4.4.2 ROM. AT&T released 4.3 and 4.4.2 via OTA updates only.
Since you are on the NE4 bootloader, do not flash anything that will attempt to downgrade the bootloader or the modem. A mismatched modem/bootloader combination may cause other problems.
Have a look here: http://forum.xda-developers.com/showthread.php?t=2789917

Ok I just reviewed your link in your response but just to be clear I'm starting where it says step 3: stock deodex and root and finishing the walkthrough from there?
And also will this reset me to my factory kernel?? Either or it doesnt matter to me I'm still trying to find one that I find suitable.
And I appreciate the speedy response you've been a huge help.

If you just want to get your phone up and running, I would flash Philz and then CM11. Confirm the bootloader and modem then decide if a stock ROM would be best.
I am always paranoid when it comes to flashing bootloaders on the s3 so I prefer to know exactly whan my phone is running.
I have never used the thread I linked because I no longer have an s3 i747m. Infact, I haven't had my s3 for several months.

Ok and my last question is you can flash Philz and CWM 11 through odin?
Nevermind I see it now greatly appreciated

I hope it all goes well. With CM11, you will also need to flash Gapps via CWM as CM11 does not include certain apps such as the Play store.

Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.

glyph2 said:
Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.
Click to expand...
Click to collapse
DO NOT downgrade to a bootloader older than your NE4 -- doing so will cause a hard brick.
You did mean i747 instead of 747i, didn't you?
Odin is designed to not flash any stock rom that would install a bootloader than the one on your phone. this is to save you from hard bricking your phone. Since you are on 4.4.2, any stock rom in a .tar.md5 format has an older bootloader than your NE4. As far as I know, the only stock NE4 rom on the forums is in a .zip format for flashing from recovery, it was posted by enewman17. (The thread audit13 linked.) If you tried to flash an older bootloader and baseband package through recovery you will probably hardbrick the phone.
Otherwise, there are roms based on TW in the forums: S3Rx, TMS3KK, Likewise, and others. Some use the stock kernel, others give you an option from their Aroma install. The iBubbler's kernel in a couple of these roms is reported to be excellent.
I'm guessing you pulled your S5 apk from either the S3Rx or Likewise thread.

I appreciate everyones feedback and guideance. Yeah I meant i747. It gets pretty easy to misread something when all you've been doing was researching roms and guides. And now its back to researching and finding one of the roms you mentioned. Much appreciated everyone I hope u all have a blessed day..

i know this a zip , but maybe could find help in the thread.
http://forum.xda-developers.com/showthread.php?t=2788357
good luck.
"all I can really do, is stay out of my own way and let the will of heaven be done"

Softbricked to download mode, unsure which versions are in my phone

I have a few specific questions at the bottom, but first, here's the long details:
I ran the custom ROM Hyperdrive RLS 16 (4.1.2) for years and loved it, but the past week I felt it was time to upgrade to a new ROM that was more up to date. I started to try out R3ARMED (4.4.2), did a full wipe in CWM and installed the zip files provided (the ROM and a d2att specific file).
Unfortunately, in my excitement I forgot to make sure that I had a 4.4 bootloader and modem, which seems to be rather essential for this particular ROM. The install failed and I thought I may have bricked the device, but I was able to update CWM and get back into recovery mode. This time, I got through the AROMA installer for the new ROM, but on reset I got stuck in a hard bootloop. It's pretty nasty--I can't use the key combination to reboot into recovery or download mode, and I only get as far as the opening "SAMSUNG" screen before the device blacks out. However, I can use a USB jig to force reboot into download mode--it's the only interface I can get with the phone at this point. ODIN recognizes the device, and when I use Heimdall and its drivers, I'm able to use those tools to interact with the phone. So I hope I'm not completely lost, but not being able to access CWM recovery mode definitely hurts.
Here's what I've tried so far to fix it:
- Without a USB jig, load recovery images onto a 16 GB SD card, insert into phone and power up (no successes, some images actually made it so the "SAMSUNG" screen no longer showed, others corrected this issue)
- Re-flash CWM with heimdall (failed)
- Used the Ultimate Android Toolkit to convert the CWM img into a tar that ODIN can flash, and tried to load it (failed)
I'm looking into trying to flash a full recovery onto the phone to see if that can fix it. But I have a few concerns:
1. I know that once my phone gets a 4.4 bootloader and modem, I can't go back to an earlier stock version.
2. I had an unsuccessful 4.1 -> 4.4 install attempt in the process of bricking updating my phone.
3. I have no idea if the install impacted the bootloader--so I don't know whether I can try a 4.3 stock flash or need to use some of the more recent phone dumps.
My first question is, as usual, what is the best route to take to recover this phone?
My second is, are there tools I can use for a phone in ODIN mode to check the version of the bootloader/modem, check on the integrity of the file system, etc. etc.?
I have a replacement phone on its way, but I view this as an excellent learning opportunity, and would love to hear some advice.

You have an i747 or i747m?
Do you see anything about warranty bit in download mode?

On the positive side, flashing the R3ARMED rom would not have changed your bootloader and modem. If you were on 4.1.2 before the flash, you should still be on 4.1.2 bootloader and modem.
There is at least one MJB_MJB Odin flashable stock ROM with active download links, it is for the i747. If you have the i747 and not the i747M you could try it.
If you have the i747M there are Odin packages for all of the stock ROMs at sammobile.com. Or, you could extract the system.img from the i747 ROM and flash it with Heimdall. BUT only if you are careful to avoid all of the files pertaining to bootloaders, radios, etc. (*.mbn, non-HLOS.bin, etc.) This route may not be for the faint of heart, but I promise I am not the only one to have done so. I didn't do so until I read of others having done this.

dawgdoc said:
On the positive side, flashing the R3ARMED rom would not have changed your bootloader and modem. If you were on 4.1.2 before the flash, you should still be on 4.1.2 bootloader and modem.
There is at least one MJB_MJB Odin flashable stock ROM with active download links, it is for the i747. If you have the i747 and not the i747M you could try it.
If you have the i747M there are Odin packages for all of the stock ROMs at sammobile.com. Or, you could extract the system.img from the i747 ROM and flash it with Heimdall. BUT only if you are careful to avoid all of the files pertaining to bootloaders, radios, etc. (*.mbn, non-HLOS.bin, etc.) This route may not be for the faint of heart, but I promise I am not the only one to have done so. I didn't do so until I read of others having done this.
Click to expand...
Click to collapse
It's a regular i747, not i747M. Thanks for the advice... you've given me a few things to try now! Will report back later with results.

[Q] Help with going back to stock (from CM11)

Hey, sup?
I need your help, I'm trying to go back to stock firmware on my i747, currently I'm running CM11 latest snapshot.
Background: Some time ago, I accidently erased my imei. Took the phone to a guy who restored it but the phone doesn't work with 3G now, only 2G. So I wanted to try going back to stock firmware to see if that fixes the issue.
I tried downloading the CUEMJB file from here, but it doesn't work (keeps looping the same page) http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Can you help me? Also, it is safe what I'm trying to do?
Thank you!

Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes the IMEI matches.
I was able to download the file.
Unfortunately, the thing didn't went ok. After flashing my phone is unresponsive, black screen, no more boot
If I connect it to the computer at this point, it tries to search for a QHSUSB_DLOAD driver. Not sure what is that, I think I bricked my phone.
I've seen some guides for unbricking by placing a sd card in the phone at boot but so far it haven't worked

Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.

dawgdoc said:
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
Click to expand...
Click to collapse
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back

Alright! I just tried the SD card method w/ one of the files in the threads linked. Phone boots!
So it seems my bootloader is bad right?

japi2000 said:
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Click to expand...
Click to collapse
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.

dawgdoc said:
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
Click to expand...
Click to collapse
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?

japi2000 said:
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
Click to expand...
Click to collapse
That is the stock recovery. If you were successfully running one of the latest CM11 snapshots, you were probably on one of the three 4.4.2 bootloaders ( and modems ), they are NE4, NJ1, and NJ2. This would explain why the MJB (4.3) image you downloaded and flashed would soft brick your phone. It looks like that flash may be responsible for you being back on stock recovery, at best guess. Before anything else, do a factory reset from the stock recovery. This is frequently necessary to boot when going from a CM/AOSP LP rom back to stock.
Since you can get to download mode, I think the best bet would be to install a custom recovery. TWRP for the i747 is here, the top image is flashable with Odin while in download mode. Remember not to reboot from Odin. Instead remove the cable, pull the battery, then boot straight to recovery. Once you have TWRP loaded, boot into recovery and use the terminal emulator in it to determine bootloader and modem with these commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Once you know the version of bootloader and modem you had been on, reflash that version from TWRP you will probably need the file on an external sdcard to do so. After this you can flash your rom of choice from TWRP, stock or otherwise. Since you were having imei issues go with one of enewman's stock roms, as @DocHoliday77 suggested. He can then help you with the imei issues if still necessary. Any other ideas Doc?

Ok, so
Bootloader = I747UCUEMJB
I don't get anything when running getprop | grep version.baseband in the recovery.
This is what I've done so far.
Booted w/ the sdcard trick (bootloader in the sdcard).
Installed twrp
Installed the following files:
AT&T_I747UCUEMJB.zip
d2att_I747UCUEMJB_bootloader.zip
d2att_I747UCUEMJB_modem.zip
d2att_Kernel_Stock_init.d_4_3_MJB_v1.0.zip
That brought the phone to life again (w/ stock 4.3). Then I flashed CM12 from the recovery. All went ok.
Problem is, I still don't have 3G connectivity, only edge.
What would you recommend try next?
Thank you

Alright, I was able to upgrade to UCUFNJ1 for both the bootloader and baseband. Still no 3G. Ideas?

Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Alright thank you

Alright, I'm happy to say that with the help of our fellow DocHoliday77 I was able to solve the issue !
Thanks everyone!

Glad you have it working.
Way to go Doc.

Damn japi2000. You did that quick good job.

Thank you!
I can't believe I went from a almost dead phone to a fully working one in only a few days, even with the 3G/4G working again !
This forum and people are amazing! Thank you!