Develop Bugs

What a mess

Hi everybody! Here's where the story begins... I replaced the digitizer/lcd on my GS3 sgh-i747. In the process my antenna connector on the main board decided to unroot it's self. I replaced it with a t999 board and noticed a Sim unlock code pop up on startup after transplant. I went through the normal factory reset b.s. Then I rooted and flashed Synergy thinking I could get around the Sim unlock and not displaying or allowing me to save any apn's. I just want my old phone back lol. Any help is appreciated.

Still nothing.

IAmSam140 said:
Hi everybody! Here's where the story begins... I replaced the digitizer/lcd on my GS3 sgh-i747. In the process my antenna connector on the main board decided to unroot it's self. I replaced it with a t999 board and noticed a Sim unlock code pop up on startup after transplant. I went through the normal factory reset b.s. Then I rooted and flashed Synergy thinking I could get around the Sim unlock and not displaying or allowing me to save any apn's. I just want my old phone back lol. Any help is appreciated.
Click to expand...
Click to collapse
What made you think using a t mobile branded board would work with whatever carrier (whom you failed to mention) sim you posses? In any case the best advice i can give you is take the sim out which will get your past the sim unlock prompt temporarily for you to flash 4.1.1 and do the hidden menu sim unlock from THIS thread.

dntesinfrno said:
What made you think using a t mobile branded board would work with whatever carrier (whom you failed to mention) sim you posses? In any case the best advice i can give you is take the sim out which will get your past the sim unlock prompt temporarily for you to flash 4.1.1 and do the hidden menu sim unlock from THIS thread.
Click to expand...
Click to collapse
Because the boards both had SGH-I747 stamped on them. Figured the hardware was probably the same just different firmware. The phone started as an At&t branded phone on straight talk. I'll try flashing 4.1.1 if I can find a stock rom. Thanks.

On sammobile you will find the 4.1.1 firmware
Sent from my SGH-I747M using Tapatalk

I've tried to get 4.1.1 two different ways..
1.) ODIN 3.06, ODIN (Download mode), File: root66_ATT_I747UCDLK3.tar.md5.
Outcome;
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: YES
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
SECURE CHECK FAIL : aboot
2.) CWM Recovery v6.0.4.3, File: I747UCDLK3_I747ATTDLK3_ATT (1).zip
Outcome;
-- Installing: /storage/sdcard1/download/I747UCDLK3_I747ATTDLK3_ATT (1).zip
Finding update package...
Opening update package...
E: Can't open /storage/sdcard1/Download/I747UCDLK3_I747ATTDLK3_ATT (1).zip
(bad)
Installation aborted.
Whatever additional info you guys need just let me know. Appreciate it!

Still trying. Phone's been down for a month now.

Since you replaced your board with a T999 board you have a T-Mobile s3 now pretty much. You're trying to flash att Tars and roms but you can't because your phone is no longer att its T-Mobile
Just my theory

DAT be the case, you need T999 firmware to flash, if you want just rooted stock firmware and you can always root stock with Android Kitchen and flash it
Sent from my Nexus 7 using Tapatalk 4
---------- Post added at 03:08 PM ---------- Previous post was at 02:57 PM ----------
http://forum.xda-developers.com/showthread.php?t=1949687
[Firmware/OTA's] [root66] SGH-T999(All Variants!) Official & Root66 FW & OTA Updates!
This is the place to d/l the Roms you need and Odin flashable.
Sent from my Nexus 7 using Tapatalk 4

Flashed in T999UVDLJC_T999TMBDLJC_T999UVDLJC_HOME.tar.md5 (4.1.1.) then typed the sim unlock code in for debug turned it off and viola!!! Thanks everybody! Noobs around the globe appreciate what you guys do. lol

Glad it worked for you
Sent from my SGH-I747M using Tapatalk

[Q] Problem with 4.4.2, and with downgrading to 4.2.2

Hi, so after I updated to Kit Kat 4.4.2 on my S4 mini, my phone kept dropping my network (Canada - Bell mobility) randomly usually either ten or twenty minutes after I connect to it but sometimes right away. I've tried taking it in to Bell and I have had the SIM card replaced three times and I've factory reset it numerous times with the problem still occurring. I've been told by a cell phone recovery shop that I could try downgrading back to Jellybean. I've searched for a while and noticed some people have had success with this method -> http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 so I decided to try it out myself. Every time I try to download it onto my phone with Odin I receive an error code:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help me with either one of my problems? Any help would be gratefully appreciated.

BoJo963 said:
Hi, so after I updated to Kit Kat 4.4.2 on my S4 mini, my phone kept dropping my network (Canada - Bell mobility) randomly usually either ten or twenty minutes after I connect to it but sometimes right away. I've tried taking it in to Bell and I have had the SIM card replaced three times and I've factory reset it numerous times with the problem still occurring. I've been told by a cell phone recovery shop that I could try downgrading back to Jellybean. I've searched for a while and noticed some people have had success with this method -> http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 so I decided to try it out myself. Every time I try to download it onto my phone with Odin I receive an error code:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help me with either one of my problems? Any help would be gratefully appreciated.
Click to expand...
Click to collapse
What jelly bean firmware did you try to flash...As I mentioned in the post :: http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 you must use BRAZIL UNBRANDED JELLYBEAN 4.2.2 UBUBNE2
Here is the sammobile link to that firmware page :: http://www.sammobile.com/firmwares/3/?download=30561
Also wipe data, cache and flash the firmware. I downgrade thrice :: from Germany KK, from slovakian KK , Newzealand KK , and Belgium branded KK. Anyway Good luck.

sasank360 said:
What jelly bean firmware did you try to flash...As I mentioned in the post :: http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 you must use BRAZIL UNBRANDED JELLYBEAN 4.2.2 UBUBNE2
Here is the sammobile link to that firmware page :: http://www.sammobile.com/firmwares/3/?download=30561
Also wipe data, cache and flash the firmware. I downgrade thrice :: from Germany KK, from slovakian KK , Newzealand KK , and Belgium branded KK. Anyway Good luck.
Click to expand...
Click to collapse
I flashed the Brazilian firmware you linked to in your post. Could you please provide links to the firmwares you downgraded to? I'm rather new to this and I have not been able to navigate Sammobile very well. Thank you so much for your time and I apologize for any inconveniences I cause.

BoJo963 said:
I flashed the Brazilian firmware you linked to in your post. Could you please provide links to the firmwares you downgraded to? I'm rather new to this and I have not been able to navigate Sammobile very well. Thank you so much for your time and I apologize for any inconveniences I cause.
Click to expand...
Click to collapse
I do not think you can downgrade further. Brazil UBUBNE2 has same bootloader as kitkat. While older jelly bean firmwares have 1st revision of knox and odin gives fail message when you try to downgrade from UBUBNE2 JB. I tried it only once and it failed, so fearing I might hard brick my phone I never tried that again. I need senior members to confirm what I said.
BTW can you remember the fail message on your phone when odin failed....??
Also I found brazil JB to be very stable and with f4k kernel I had great battery life.

sasank360 said:
I do not think you can downgrade further. Brazil UBUBNE2 has same bootloader as kitkat. While older jelly bean firmwares have 1st revision of knox and odin gives fail message when you try to downgrade from UBUBNE2 JB. I tried it only once and it failed, so fearing I might hard brick my phone I never tried that again. I need senior members to confirm what I said.
Also I found brazil JB to be very stable and with f4k kernel I had great battery life.
Click to expand...
Click to collapse
When I had tried to flash the Brazil UBUBNE2 onto my phone, it gave me the error I posted in the original post. I am only trying to downgrade to it, not past. I re-downloaded the firmware from the link you supplied earlier, and when I tried flashing it onto my phone I received the same error as I posted at the beginning.
Could it be something that I'm doing wrong? I open up Odin, put my phone into download mode, plug my phone into my computer, place the firmware into the AP spot, then I press start, and after a little bit it displays the error. I am using Odin v3.09.

BoJo963 said:
When I had tried to flash the Brazil UBUBNE2 onto my phone, it gave me the error I posted in the original post. I am only trying to downgrade to it, not past. I re-downloaded the firmware from the link you supplied earlier, and when I tried flashing it onto my phone I received the same error as I posted at the beginning.
Could it be something that I'm doing wrong? I open up Odin, put my phone into download mode, plug my phone into my computer, place the firmware into the AP spot, then I press start, and after a little bit it displays the error. I am using Odin v3.09.
Click to expand...
Click to collapse
That is strange. You downloaded the proper firmware from link I gave you and also steps of flashing are correct.
Did you try to remove knox files from firmware??? Or flashed it untouched.
Actually many users did exactly what I did and successfully downgraded. Try one last time after wiping data and cache. Good luck. Also is your device I9195 or any variant of that like I9195L / I9195T. All the above procedure must be done on I9195 international S4 Mini LTE. Good luck.

sasank360 said:
That is strange. You downloaded the proper firmware from link I gave you and also steps of flashing are correct.
Did you try to remove knox files from firmware??? Or flashed it untouched.
Actually many users did exactly what I did and successfully downgraded. Try one last time after wiping data and cache. Good luck. Also is your device I9195 or any variant of that like I9195L / I9195T. All the above procedure must be done on I9195 international S4 Mini LTE. Good luck.
Click to expand...
Click to collapse
I flashed it untouched, I don't know how to remove the knox files. My device's model number is SGH-1257M, so could that be the problem? Am I out of luck for being able to downgrade? If I can't downgrade do you know if there is a way for me to stop losing connection to my cell network, the initial problem I described, that is the reason I want to downgrade my phone.

BoJo963 said:
I flashed it untouched, I don't know how to remove the knox files. My device's model number is SGH-1257M, so could that be the problem? Am I out of luck for being able to downgrade? If I can't downgrade do you know if there is a way for me to stop losing connection to my cell network, the initial problem I described, that is the reason I want to downgrade my phone.
Click to expand...
Click to collapse
THAT IS THE PROBLEM. As you can see the model number of your device is I257M. The firmware you flashed is meant for I9195 international S4 Mini LTE. The phone you have is carrier branded S4 Mini. Not the international one. Do not flash firmwares and ROMs meant for other model numbers. I cannot advise you on SGH-I257M as I have no idea how the kitkat is seeded to that device.
http://www.sammobile.com/firmwares/1/?model=SGH-I257M&pcode=0 --- This is the list of latest firmwares for I257M. Use these firmwares, not I9195 firmwares.

sasank360 said:
THAT IS THE PROBLEM. As you can see the model number of your device is I257M. The firmware you flashed is meant for I9195 international S4 Mini LTE. The phone you have is carrier branded S4 Mini. Not the international one. Do not flash firmwares and ROMs meant for other model numbers. I cannot advise you on SGH-I257M as I have no idea how the kitkat is seeded to that device.
Click to expand...
Click to collapse
Oh, well that is disheartening. Thank you for your time and patience. I really appreciate you trying to help.

BoJo963 said:
Oh, well that is disheartening. Thank you for your time and patience. I really appreciate you trying to help.
Click to expand...
Click to collapse
No mention. It is essential to learn from little mistakes.

Stock Restore Error

Hello all,
I've been perusing through many threads on the XDA forum looking for how to solve a download problem on my SGH-i747m but haven't found it. Hopefully, one of you intelligent folks can help me.
Long story short, I screwed up the bootloader a while back which hard bricked the device. I originally recieved the phone in a soft bricked state from a buddy so I don't know many particulars about the Android version before I hard bricked it. I sent the phone for JTAG which allowed the the phone to boot to the Samsung screen. I'm not sure how the JTAG process works, but I assume it cleared everything except the bootloader. All I want to do now is restore the phone back to stock so it's usable.
The following is a summary of what I tried....Using Odin v3.07 and a stock firmware I747MVLUEMK5 I attempted to download the firmware into the device. Unfortunately, in the early stages, I get these errors
From Odin:
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone:
Warranty Bit: 1
Bootloader AP SWREV: 2
SW REV CHECK FAIL: Fused 2 > Binary 1
I tried re-rooting the device with CF-Auto-Root and then was able to flash CWM 6.0.4.7 to do a full wipe of everything. On my next attempt, I get the same errors.

You're trying to flash an older build than what is already there, which cannot be done. You can only flash the same or newer from now on.
Judging by the SW REV CHECK, you can flash builds ND2, NE6 or NF2. (Depending on your carrier, NF2 may not be available.)
Flash one of those and it should work.

Can you explain some detail about these build designations? I'm not familiar with those.
When I researched the stock firmwares for Telus, I discovered that the MK5 build (if "build" is the correct term) was the newest available. To my understanding..isn't 4.3 is the newest is gets for the i747m?

Go to http://sammobile.com/firmwares
The latest build is 4.4.2.
Youll have to sign up to download, but its free and as far as i can tell they dont spam your email or anything like that.
ND2 is a newer 4.3 build, and is what you are currently running. The others are 4.4.2

Samsung tech support trashed wife's phone after Settings App failure fix

It seems that after the November AT&T OS upgrade that my wife was unable to get into the Settings App (Settings Failed Error). :crying:
1. Got on with Samsung support, they took me through several reboot sequences, etc.
2. Finally they said we need to Factory Reset. We backed up data with Kies and proceeded.
3. While rebooting from the factory reset, OP Sys fails on the language selection screen (Settings Failed Error)
4. Samsung took us too Kies and tried to flash the Op Sys.
5. Now getting "Firmware upgrade encountered an issue".
6. Tried Kies again but does not find my device.
7. Downloaded the I747 AT&T Rom and using Odin
8. Am able to get the "Downloading" screen to work
8. Odin sees the Com but when trying to flash, it Fails every single time.
HERE IS THE SEQUENCE:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I am stuck as to what to do next. PLEASE HELP :crying:

Ur wife seem to enabled the protection against odin flash. Too sad, else it would work.
This is why u should never enable that crap.
Good luck
Skickat från min SM-G900F via Tapatalk

Sachitoge said:
Ur wife seem to enabled the protection against odin flash. Too sad, else it would work.
This is why u should never enable that crap.
Good luck
Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse
Sachitoge, thanks for your reply!
So what your saying is that my Wife's phone is as good as being Hard Bricked?

Kinda
Samsung has implemented knox to prevent theft to reset phone, this will fail wth odin no matter what you do, its impossible because its locked and encrypted.
For now it seems its hard bricked, but if u never got root on it or if your knox trigger is 0x0, and u got this far with brick, then your operator or samsung is responsible to fix it no matter what, stay on what you say and push them saying you didnt do anything and that you enabled knox protection thus Odin flash fails. Say to them with a more serious speech and deeper speech like you its kinda feeling that you seem like you are angry. Tell them you need asap phone and replace it asap. You can even say to diagnose the phone and see that you didnt do anything illegal (root proccess) or dropped phone.
Just never take a break with whatever they say about refusing it, stay behind your words and phrase, they should and MUST help you fix the phone or replace it.
EDIT: This knox protection is additional optional protection, and is not must, so u know. Its impossible to turn it off without getting into your Settings app and disable it manually.
Skickat från min SM-G900F via Tapatalk

Sachitoge said:
Kinda
Samsung has implemented knox to prevent theft to reset phone, this will fail wth odin no matter what you do, its impossible because its locked and encrypted.
. . .
Just never take a break with whatever they say about refusing it, stay behind your words and phrase, they should and MUST help you fix the phone or replace it.
Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse
I talked to the voice tech support and they said that i should first try to image the operating system at the BestBuy store. If I can't get it to work then to send it into them and they will do a "free" evaluation. However since i started with a good phone, they are liable. Although they may try and get me to pay for fixing it
As it is, should i really send it to them? Or is there any other software solution, or a JTAG??? (not sure all that would involve)
Thanks!

Look, that knox protection is as good as Apple's remote iCloud lock function. It is encrypted, and it requires decryption of the system partition (i may be wrong, i just say what i believe is/can be). The Knox is a type of a Encryption, it's really secure and safe and is used widely worldwide, the decryption is hard because it must be protected with your samsung account and password, because it required that during enabling it. This indicates it is encrypted according to your specified Samsung account. I may be wrong, but try to find on internet whether it's possible to disable it remotely. Try to boot phone normally, then go on PC/Laptop and search to login to Samsung account and by any chance, look to remotely unlock this Knox security.
Other than that, without access to "Settings" app, you wont be able to disable it. Simply impossible. It is encrypted.
Same for iOS Devices that got locked with remotely iCloud lock app, it is locked and encrypted remotely and requires remotely decryption to system partition and this is why almost nobody can bypass it. There are ways but sadly are private from public to prevent Apple team patch the exploit. I do believe they use this exploit for iDevice that is stolen to afterward sell to another end-user the stolen phone, or possibly they could be unlocking devices in exchange of money. Easy money from my view, however, it is encrypted and is no way possible. MAYBE samsung can do it from their end without saying "we decrypted it and did clean install rom" instead of that, they will speak in a manner speech like "We did put the phone into a developer-only software from our end on our PC and did a full disk-clean which also killed all files, and had to re-attempt to install rom and reconfigure IMEI". Maybe not exactly like this but something close this. From what i know, whenever you do full clean, your IMEI mostly stays, this is because you mostly cant really navigate it manually or delete it, usually it is protected lol.
I hope you're not tired with this long message, you shouldn't be charged for such a mess they caused to you, so like i said, dont let your guard down and hesitate, stay behind your phrase/word! I promise, it will work!
You mentioned Voice Tech Support, talk serious, talk that you are not tech heavy, (for ur wife). Play a bit stupid-role about technology and that it happened while OS Upgrade.
Remember, they will be after your money, don't let them do it and get cash into their pocket for free, it's not worth and not your fault to cause you being charged!
Please, try my method and you will see it really saved you a couple 10 dollars. As of sending the phone, im not sure, they wont however pay the shipping fee, other than that any other cost is unacceptable so beware, dont get phished from IT experts.
Remember, reason this is long is to save you from being charged. Hope it helped, good luck buddy.

I recommend not using Odin to flash any ROMs at this point.
The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file.
There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates.
I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.

audit13 said:
The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file.
There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates.
I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
Click to expand...
Click to collapse
You are right, it could be, i dont know how things really work in USA as i always bought unlocked phones and living in europe, so it was good to point that out. The error do happen while knox protection is on too, same type of message so its a bit tricky...
Skickat från min SM-G900F via Tapatalk

I have never seen Knox protection cause that error. I don't think it is not Knox that is stopping the flash, it is the bootloader security.
The only protection that I have seen that would have an effect in download mode would be re-activation lock.

Sachitoge said:
. . . other than that any other cost is unacceptable so beware, dont get phished from IT experts. . . Remember, reason this is long is to save you from being charged. Hope it helped, good luck buddy.
Click to expand...
Click to collapse
Thanks for your long reply! and in helping me with this issue. I will be firm with them. My wife is not tech savvy and I don't know how my wife's phone got encrypted, or if there was someone remotely hacking her phone from our PC or over the wireless. She always complained to me that someone was listening in on her conversations and interfering with her text messages. And we had some evidence this was taking place. She does not know how to encrypt her phone, so she didn't enable knox encryption. So perhaps her phone was hacked somehow.
On the download screen of the phone this is what I am getting:
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECURE BOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 3
SW REV CHECK FAIL : Fused 3 > Binary 0
Downloading.......
Does this mean anything to you that could possible help knowing what the problem is?

I see nothing to indicate that the phone is encrypted.
The existence of the warranty bit line tells me the phone has at least a 4.3 bootloader which caused the Odin flash to fail: the ROM being flashed has an older (probably 4.1.1) bootloader.
Knox and encryption are not the same thing. Encryption can take place in the absence of Knox and Knox can be present on a non-encrypted phone.
Whether the phone is or is not sim-locked isn't relevant to this situation as it can happen regardless of a phone's sim-lock status.

audit13 said:
I recommend not using Odin to flash any ROMs at this point. . . The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file. . . There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates. . . I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
Click to expand...
Click to collapse
Thank you for your suggested solution! I have an Identical phone to my wife's phone. Is there anything else useful i can grab from my phone? The info App states:
Model: SAMSUNG-SGH-I747
Device Type: d2att
Product Name: d2uc
Country origin: MADE IN CHINA
Manuf. Date: 2012.08.31
Knox Warranty Void: 0x0
Storage: 16 GB
Product Code: SGH-I747RWBATT
Orig CSC Code: ATT
Firmware CSC Code: ATT
Active CSC Code: ATT
CSC Country: USA/US
Mobile Operator: AT&T / 310410
Bootloader Version: I747UCUFNJ2
PDA Version: I747ATTFNJ2
Baseband Version: I747UCUFNJ2
Latest Firmware: Not Found
Kernel Version:
3.4.0-1514807
[email protected] #1
32-bit
Java Virtual Machine: Dalvik 1.6.0
Root Existence: No
Android Version: 4.4.2
Build Number: KOT49H.I747UCUFNJ2
Build Fingerprint: samsung/d2uc/d2att:4.4.2/KOT49H/i747UCUFNJ2:user/release-keys
Build Description: d2uc-user 4.4.2 KOT49H I747UCUFNJ2 release-keys
Build Date: Mon Aug 10 14:43:43 KST 2015
Changelist: 1514807
Hardware / Board: qcom / MSM8960 [32-bit]
Platform / Chip: MSM8960
GPU: Qualcomm Adreno 225
Modem Board: MSM8960
Hardware Revision: REV0.4
Firmware: KIES SYMBOL --- I747UCDLK3 --- date: 2012-11-01 ---- USA (ATandT) ---- Version: 4.1.1 --- CSC: I747ATTDLK3

Your phone is running the latest ROM as indicated by the nj2.
The line about kies, where did that come from?

audit13 said:
Your phone is running the latest ROM as indicated by the nj2.. . . The line about kies, where did that come from?
Click to expand...
Click to collapse
That line came from the Firmware Browser page of the Phone INFO *Samsung* App.
Is it possible to extract all the files I need from my phone and burn them over to my Wife's semi-bricked phone?

Nope, that won't work.
If you backed up everything on her phone, I recommend flashing a custom recovery and then a custom ROM to see what baseband is on the phone. I would not flash anything until that has been confirmed.
Flashing the wrong bootloader and modem file could hard brick the phone.

audit13 said:
Nope, that won't work. . . .If you backed up everything on her phone, I recommend flashing a custom recovery and then a custom ROM to see what baseband is on the phone. I would not flash anything until that has been confirmed. . . .Flashing the wrong bootloader and modem file could hard brick the phone.
Click to expand...
Click to collapse
I am still new here, and although I am a computer programmer, a lot of the terms are foreign to me.... i understood the custom recover and the custom ROM but what is the "baseband" that needs to be determined? Can i get the baseband information from my identical phone?

The baseband or modem is software installed on the phone to control its functionality. The last 4 characters of the baseband/modem should match the last 4 characters of the bootloader.
From your post above, notice the fnj2:
Bootloader Version: I747UCUFNJ2
Baseband Version: I747UCUFNJ2
The bootloader and baseband/modem will change as you upgrade the phone's ROM.
If the soft-bricked phone has the mjb bootloader and you try to flash an lk3 bootloader, this will probably hard-brick the phone because the lk3 bootloader is an older bootloader. The i747 can only be flashed with an identical or newer bootloader which makes the bootloader version a very important piece of information.

audit13 said:
.......The i747 can only be flashed with an identical or newer bootloader which makes the bootloader version a very important piece of information.
Click to expand...
Click to collapse
So why not just flash her phone with the newest bootloader available?

If you want to flash the latest bootloader and modem, you'll have to install a custom recovery first. Also, I am not sure if the modem and bootloader need to be upgraded in release order. I wouldn't think so since I have flashed the Canadian version of the s3 (i.e. i747m) from 4.1.2 to 4.4.2 with no problem.
Always flash the bootloader and modem in the same session before rebooting. Don't flash a modem, reboot, and flash a bootloader as this could also cause a brick.
NOTE: flashing a custom recovery will change the warranty bit from 0 to 1 which will tell a Samsung tech that non-official software was installed on the phone and you may wind up with no recourse against Samsung.
I recommend this if you will not be pursuing the matter further with Samsung: install a custom recovery, boot into recovery, wipe cache, and reboot the phone. Hopefully, clearing the cache will allow the phone to boot as I think it is still stuck in a boot loop.
If the phone still will not boot and you have not back up all of the data, boot to recovery, mount the data partition, connect the phone to a computer, copy off what you need, wipe/format the data and cache, then reboot.

audit13 said:
If you want to flash the latest bootloader and modem, you'll have to install a custom recovery first. ... ... ...
Click to expand...
Click to collapse
I am willing to try it. Do you know a thread i can follow or how i can get some instruction on creating and flashing a custom recovery? Also..... i still have the option to bring the phone over to BestBuy store who is a Samsung tech center. I am not sure if they can do anything other that what I have already tried

Re-Partitioning Developer Edition

Can someone please explain to me how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!

doubleplay648 said:
Can someone please explain to me
how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!
Click to expand...
Click to collapse
I replied to you on PM, but this may be helpful for others.
Repartitioning has nothing to do with downgrade-ability. The Safe Upgrade won't work for you either, since it includes older TrustZone. N910VVRU2BPA1_StockRestore_Incremented.tar.md5 didn't change any of the critical partitions. You'll need a similar tar for OG5 to be able to downgrade, which isn't available unfortunately.
Click to expand...
Click to collapse
However, you could flash OG5 ROM via TWRP, if you wish.

Cannot install TWRP
hsbadr said:
I replied to you on PM, but this may be helpful for others.
However, you could flash OG5 ROM via TWRP, if you wish.
Click to expand...
Click to collapse
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?

doubleplay648 said:
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?
Click to expand...
Click to collapse
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.

hsbadr said:
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.
Click to expand...
Click to collapse
So i have the developer edition. I sent it into samsung for repair and i mentioned several times about the bootloader being unlocked. I tried flashing the twrp tar you gave me and it gave me a odin fail and my phone says SECURE CHECK FAIL: recovery
The only thing i did when i got my phone back was upgrade the 5.0.1 to your 5.1.1 incremented stockrestore.
Did i do this right?
1. put phone into download mode (power + volume down+ home)
2. plug into pc and open odin.
3. flash the tar via ap, without checking re-partition
So any idea why this isn't working? Samsung had to replaced the motherboard in my phone. Is it possible that when they sent back my phone they updated the SW to a locked bootloader?

Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!

doubleplay648 said:
Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!
Click to expand...
Click to collapse
Your phone is retail. If you want DevEd you will need to talk to one of the few folks at Samsung that know what a Deved is. Convince them that they retailed your phone when they replaced the main board. They should fix this. The only number you should call is the 800 number on your DevEd receipt. If the CSR doesn't know what your talking about, ask for a supervisor, escalate until they know what you have. They need to be clear what you have, or it will return retail again. The good news is they will flash your fuse 2 retail to DevEd.
The number is 800-757-0280
Click on image,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From Odin Download screen it should say "Mode: Developer"

From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
---------- Post added at 02:22 PM ---------- Previous post was at 02:02 PM ----------
anticloud said:
From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
Click to expand...
Click to collapse
and I can't help but mention - if you happened to use one of the safe upgrades to move forward, there is rollback.