Develop Bugs

[HELP] Bricked my S3 i747M.

Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!

First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!

Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse

Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.

Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse

I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse

If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.

I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse

Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.

After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse

Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium

pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app

Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks

You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....

Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?

just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices

jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?

I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium

JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.

Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium

Updating Bootloaders? Please read this first

Since the new Jelly Bean bootloaders have shown up, I see a lot of people talking about updating them. There are a few things I would recommend to do when flashing them. The first is the small, but present, danger that you can hard brick your phone. And I mean the "Need jtag to make it work" hard brick. Typically the cause of these bricks is an error or interruption of communications between the device and the computer. The other is mismatched or outright improper bootloaders.
Below is a list of things to decrease the possibility of permaborking. Keep in mind that following this list will not 100% remove the danger of flashing bootloaders, but will increase the chances of a successful flash.
Flashing bootloaders is dangerous. They are one of the few things that has the possibility of hard bricking your phone. For that reason, here are some good things to do to prepare for flashing them.
Have a good, reliable data cable. Interruption of communication between your phone and pc will most likely cause a hard brick with bootloaders.
Use a usb port on the back of your computer (or #1 on a laptop). Communication, again.
Have a jig. Not much help if you hard brick, but if you soft brick its very nice to have.
I personally flash bootloaders from a good laptop with a fully charged battery. If there is a power outage, the battery in the laptop will have saved my phone.
When flashing bootloaders,or anything with Odin, don't touch your phone after you connect it in dl mode until the phone reboots. Goes back to the communication issue.
For problems/tips on connection issues, look HERE

To determine which bootloader you have, check out this app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
To check your bootloader version
(thanks to KorGuy123 for the link)
For those that like to use Terminal Emulator, just type this:
HTML:
su
getprop ro.bootloader

Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium

xlj1000 said:
Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.

Flashing Bell Galaxy S3 Bootloader on AT&T phone
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.

If it's not the exact bootloader for your phone, don't flash it.

mrhaley30705 said:
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.
Click to expand...
Click to collapse
Maybe use Mobile Odin?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.

mrhaley30705 said:
It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
Click to expand...
Click to collapse
Awesome, gotcha. Learn something new every day.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

mi modelo is i747m telcel mexico which should flash

Obridgenut said:
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.
Click to expand...
Click to collapse
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it,
As for the other guy having an issue, you can update your phone over Kies. Your issues sound like its a bad rom you put on your phone. And you can never brick your phone. Its what people to say to scare you to get you to use their methods.

Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium

osmxgohan said:
mi modelo is i747m telcel mexico which should flash
Click to expand...
Click to collapse
The correct firmware from your provider should have bootloader in then

andy_d0 said:
Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
It's possible that the ota update to jelly bean pushed the latest bootloader to your phone.

TheStrokerace said:
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it, ]
The AT&T SGH-I747 does not offer the option to toggle LTE off under the Settings Menu, as do the Bell, Telus etc SGH - I747Ms. And although I can and have flashed all sorts of different ROMs, the AT&T modem is RAT locked and I so far have been unsuccessful flashing any modems other than AT&T modems. I am not sure whether this is a software issue or whether it is to do with the AT&T bootloader, hence the question about flashing a Bell bootloader. Any time that I try to flash a non-AT&t MODEM, I temporarily lose my IMEI number and the phone will not work at all. But there is a work around by entering into the Phone Control settings as discussed on xda, ( http://forum.xda-developers.com/showthread.php?t=2116346) which I have been using successfully.
Click to expand...
Click to collapse

I don't think changing the bootloader will change that for you.

mrhaley30705 said:
I don't think changing the bootloader will change that for you.
Click to expand...
Click to collapse
OK, Thanks anyway for your help.

How can I tell what version my bootloader is?
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason

ubuntujason said:
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason
Click to expand...
Click to collapse
Install this, hit check, goto second screen and it'll say bootlader
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Easiest way to check is install terminal emulator.
Type
su
Grant it permission
Now type:
getprop ro.bootloader
These commands are case sensitive, so type carefully

[Q] IMEI says 0 on 4.4.1

Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.

Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117

Note that if you reinject IMEI, it might screw up your network

audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.

Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?

chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D

pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?

chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)

pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process

pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?

chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it

Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.

pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?

pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"

So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....

chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer

pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...

Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app

elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it

SIM no longer recognized as being inserted; IMEI not visible in software

Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.

dhmmjoph said:
Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.
Click to expand...
Click to collapse
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.

BWolf56 said:
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.
Click to expand...
Click to collapse
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?

dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
No, sorry. And I doubt you'll find one.

dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
http://www.androidfilehost.com/?fid=23212708291680823

Larry2999 said:
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
Click to expand...
Click to collapse
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!

dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
You said you moved it to your sd card? You might have to change TWRP's mounting to it.

BWolf56 said:
You said you moved it to your sd card? You might have to change TWRP's mounting to it.
Click to expand...
Click to collapse
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?

dhmmjoph said:
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?
Click to expand...
Click to collapse
I'm not so sure what file you downloaded but it should be a zip. In order to flash, you need a zip with META-INF folder in it (to put it simply).
Here's what you need: http://forum.xda-developers.com/showthread.php?t=1831898 (The MJB one).

dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.

Larry2999 said:
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.
Click to expand...
Click to collapse
Here's a TWRP flashable zip for the modem if the CWM doesn't work.

[Q] Havent been able to load new roms after having to fix soft brick

First off I NEVER have had rom issues before this, it all started with a failed encryption attempt that soft bricked my phone. instead of re posting what i wrote here is a link to the 2 pg thread in which i received help and thus this is where i am at.
http://forum.xda-developers.com/showthread.php?t=2701706
OK now ever since then i have never been able to update to a new rom. I believe it let me do it once and i believe i am using an older version of S3Rx.
I believe it may be due to how I updated to 4.3 I would like to get 4.4 as i believe kit kat (tell me if im wrong) will probably be the last android os the S3 will support so i basically want to get the most out of it as i can and also be able to try other roms in general like i used to. Because i currently do not have a sd card I have yet to try anything drastic as i normally use my sd card for backups and rom installs because if something happens to the phone i have the sd card backup.
So in all What should I DO, I have fears of using Odin as the one time it failed on me i bricked a phone and I cant really afford to hard brick this one like i did the other. Although the only thing I can think of being a dumb leach user and non dev. Would be to use odin with the most recent root66 then go from there? Although again lol all i can think of is the above.
Thanks for reading and i hope like the last time I will recieve help to bring back the life to this device. TIA!!

Can you give a little more info on why you can't flash, like an error message or something?

serio22 said:
Can you give a little more info on why you can't flash, like an error message or something?
Click to expand...
Click to collapse
for some reason using twrp and cwm they fail with twrp it normally fails instantly and with cwm it will fail sometime during the install.
I need to put a rom on my phone and ill give exact error. I havce been trying to use the likewise port from att http://forum.xda-developers.com/galaxy-s3-t-mobile/development/rom-likewise-s5-4-1-tw-4-4-2-ne4-t2879647 I normally use an sd card as i have the 12gb model and some roms are large but i should still be able to succeed (we will see from the error message)
thanks for replying

Alright. Also make sure you are using the latest recoveries

serio22 said:
Alright. Also make sure you are using the latest recoveries
Click to expand...
Click to collapse
HRM i guess im ok i just installed the latest S3Rx as i wanted to see what made it stop so i chose this rom (because i needed to update anyway) and it had aroma so I thought perfect ill know when it fails but it worked out ive downloaded and tried to install likewise several time at first i thought i got a bad download but ive tried again and for some reason. I have yet to try a 4.4 (i wanted to try likewise so thats why i chose it) so without trying other roms my issue has something to do with going to 4.4 from 4.3 IDK though as i have not tried other roms but no one else seams to have this issue with this rom port?
Any 4.4 rom suggestion to try to find out what the issue is?
currently installed base-band modem should have no impact on rom installation only the fact i wont get signal right?
I just cant think of any reason why i am having the issue?? any ideas anything i should check to make sure its right on my mobile? BTW thanks for coming back to help as this is possibly a stupidity problem which is hard to help how do you help stupid lol?

Try S3rx 4.4.2 or do you mean aosp/cm?.. And correct, baseband/modem won't matter on ROM installation.. I'm sure it's not stupidity, believe me we all get issues we cannot understand at times and the next time you try, problem is gone lol

serio22 said:
Try S3rx 4.4.2 or do you mean aosp/cm?.. And correct, baseband/modem won't matter on ROM installation.. I'm sure it's not stupidity, believe me we all get issues we cannot understand at times and the next time you try, problem is gone lol
Click to expand...
Click to collapse
i personally prefer touchwiz so no aosp or cm and the latest version of s3Rx i though is what i just installed but its only 4.3 not 4.4
http://forum.xda-developers.com/showthread.php?t=2326763
installing that works but i still cant get to 4.4 im going to search for one that has aroma maybe it will work do you have any suggestions on a good touchwiz based rom on the latest version of android?
To me Likewise looked the best but trying to get that rom working is what prompted this OP.
I still have yet to try again after this recent rom update as I havent had the time and the battery level is not high enough yet to start as i will need to create a new backup and delete my old ones as i have the 12 gb model and currently no sd card.
I will post back when that has been done to show my results. In the mean time ill be searching for another possibly suitable rom like i already said something with aroma and if you have a preference ill try that first.

S3rx 4.4.2 http://forum.xda-developers.com/showthread.php?t=2848080 try that and see if it works
Sent from my SGH-T999 using Tapatalk

serio22 said:
S3rx 4.4.2 http://forum.xda-developers.com/showthread.php?t=2848080 try that and see if it works
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
it wont change my modem? and it will be OK I NEVER have used a rom other than roms made specially for t-mobile i was always under the impression that's a bad idea? I know att and t-mobile are sometimes compatible though but Ive still always been weary so before i do it you want me to use an att rom on my t-mobile?
Anythi8ng special i should know before i do it (besides thew obvious like make a backup and follow op directions) because im not on att i dont want another soft brick (cant afford to have that happen right now either) and a HARD brick would totally mess me up. (i just paid this off lol)

serio22 said:
S3rx 4.4.2 http://forum.xda-developers.com/showthread.php?t=2848080 try that and see if it works
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
it wont change my modem? and it will be OK I NEVER have used a rom other than roms made specially for t-mobile i was always under the impression that's a bad idea? I know att and t-mobile are sometimes compatible though but Ive still always been weary so before i do it you want me to use an att rom on my t-mobile?
Anythi8ng special i should know before i do it (besides thew obvious like make a backup and follow op directions) because im not on att i dont want another soft brick (cant afford to have that happen right now either) and a HARD brick would totally mess me up. (i just paid this off lol)
EDIT:
AT&T I747 users should update bootloaders and modem to NE4 http://forum.xda-developers.com/gala...pdate-t2808654 I747M and T999 users need to be on 4.3 firmware or ROM will not boot.
Click to expand...
Click to collapse
after reading this it makes me for comfortable so ill try it out Im currently on S3Rx 4.3 so wish me luck I sure hope it works!!
Edit: well I tried it it installed fine but the screen would not display i could feel the phone vibrate as to start up although like i said no boot screen no Samsung loading screen basically yeah I'm having problems with 4.4.X

You don't need to change anything and it won't change your modem, you just need to be on 4.3 firmware

serio22 said:
You don't need to change anything and it won't change your modem, you just need to be on 4.3 firmware
Click to expand...
Click to collapse
ill try again but the rom you said to try installed fine no problems but after restart no display????? it vibrated so IDK if it even booted. I am really confused I have never had problems like this. Especially with this phone as it has been easy from the start not the case with other devices i have used.
So ill try again maybe a reboot will get it working IDK but i guess ill try it again cross your fingers

BeatnikBandit said:
ill try again but the rom you said to try installed fine no problems but after restart no display????? it vibrated so IDK if it even booted. I am really confused I have never had problems like this. Especially with this phone as it has been easy from the start not the case with other devices i have used.
So ill try again maybe a reboot will get it working IDK but i guess ill try it again cross your fingers
Click to expand...
Click to collapse
That means you are not on 4.3 firmware, so update your firmware and try again

serio22 said:
That means you are not on 4.3 firmware, so update your firmware and try again
Click to expand...
Click to collapse
my phone says its 4.3 but like you said it must be an issue how do i update my firmware again?

BeatnikBandit said:
my phone says its 4.3 but like you said it must be an issue how do i update my firmware again?
Click to expand...
Click to collapse
You could be on a 4.3 ROM, but have a 4.1.x bootloader.. Download latest 4.3 firmware for your device and flash it with Odin

So yes i must be on 4.1.2 as that was the last time i flashed with odin so i believe you help3ed me with my main isssue now this is something i would like to be sure of:
Can i simply flash the following posted on the s3rx page or will i have to use odin i prefer not to as well i don't know much about it and it scares me as idk how to if possible backup in case of error as the only unfixed problem i have ever had was a while rooting a galaxy s 4g (the one that came with inception) and i walked away and the cord was unplugged and there was an error that it still has about firmware upgrade failure connect to kies and neither kies nor odin will connect to it so its currently in the same situation. So i am fearful of using odin unless it must be done.
Complete 4.3 T999, T999L and T999V bootloader and modem packages.
After flashing DO NOT try to install any older bootloaders or use any other odin.tar other then the latest 4.3 or you will brick your phone.
T999 ONLY, T999 ONLY, T999 Only
T999 ONLY, T999 ONLY, T999 Only
Complete MJC bootloader and modem
http://www.mediafire.com/download/5c..._modem_4.3.zip
Complete NC2 bootloader and modem *Added 3-22-14* Thanks to @Synthetic.Nightmare
http://www.mediafire.com/download/fc..._modem_4.3.zip
Click to expand...
Click to collapse
Would this be enough (would probably use NC2) or will i be better of using the latest root66 with odin? and if so can you give me some tips on odin usage as i would get the latest odin and the latest root66 rom and flash it hoping it works I would try to learn more also but yeah.

It's better to flash the full firmware with Odin imo, but it should be fine. And yes, use nc2

So i think the best cleanest way is to use odin although i have a few questions
First the latest version of odin should work right so 3.09 or 3.10?
Can a backup before this? is there a way to do it?
Lastly the best rom to flash is root 66 NC2 fot t999
Then i will be on a 4.3 bootloader and will be able to use 4.3+ roms?
I have the drivers the latest odin and the root66 image can you direct me on how to do it as a refresher?
I appreciate all your help!!

Please go to Android development an look at [baseband] an just go to first page should help with everything

I believe the root66 thread has instructions