Develop Bugs

Unknown baseband

I live in Croatia where we don't have LTE. So I bought Nexus via my career (Vodafone group) VIP and everything was great until yesterday.
When I entered Nexus Toolkit, I found out that I have Verzon LTE build number of my Nexus. It was IMM76K, and my device was toro (?) insted of maguro (gsm version that I was supposed to have as I understood?).
Ok, that's not big deal, I don't really care if I have toro or maguro, but when I flashed CM or any other ROM for Toro, I got unknown baseband problem. And I can't flash maguro ROMs, only toro ones.
I tried to flash gsm radio via CWM (XXLF1), but baseband is still unknown. I can't make calls, sms or any other career action.
Then I flashed JB following THIS thread, and I made it. I have stock JB that works, but again I can't flash any other custom ROM on my Nexus. I can, but then I can't make calls or sms. Everything other is working normal.
Now I'm on stock JB, waiting for someone to help me solve this problem...
P.S. IMEI was also unknown if it means anything (*#06#)
P.P.S. Sorry for my bad english, I'm Croat...

There is a few yakju builds with the build number IMM76K, not just Verizon Nexus.
And you probably f*cked your imei, restore your phone back to stock and get a new device.
And read up on rooting the manual way, gives you less problems. Not saying toolkit sucks, toolkits are a great way of doing things, but one click apps also comes with great risks should you f*ck your device up.
And if only you took your battery out and look at the label.....

qube310 said:
I live in Croatia where we don't have LTE. So I bought Nexus via my career (Vodafone group) VIP and everything was great until yesterday.
When I entered Nexus Toolkit, I found out that I have Verzon LTE build number of my Nexus. It was IMM76K, and my device was toro (?) insted of maguro (gsm version that I was supposed to have as I understood?).
Ok, that's not big deal, I don't really care if I have toro or maguro, but when I flashed CM or any other ROM for Toro, I got unknown baseband problem. And I can't flash maguro ROMs, only toro ones.
I tried to flash gsm radio via CWM (XXLF1), but baseband is still unknown. I can't make calls, sms or any other career action.
Then I flashed JB following THIS thread, and I made it. I have stock JB that works, but again I can't flash any other custom ROM on my Nexus. I can, but then I can't make calls or sms. Everything other is working normal.
Now I'm on stock JB, waiting for someone to help me solve this problem...
P.S. IMEI was also unknown if it means anything (*#06#)
P.P.S. Sorry for my bad english, I'm Croat...
Click to expand...
Click to collapse
You have a MAGURO device, NOT toro. Toro means Verizon, and Verizon ONLY. You need to go back and flash a maguro radio.
P.S., as was mentioned before, the build number has NOTHING to do with whether your device is toro or maguro. There are maguro devices running IMM76K, and toro devices running IMM76K (although they are different builds: mysid IMM76K vs. yakju** IMM76K).

qube310 said:
I live in Croatia where we don't have LTE. So I bought Nexus via my career (Vodafone group) VIP and everything was great until yesterday.
When I entered Nexus Toolkit, I found out that I have Verzon LTE build number of my Nexus. It was IMM76K, and my device was toro (?) insted of maguro (gsm version that I was supposed to have as I understood?).
Ok, that's not big deal, I don't really care if I have toro or maguro, but when I flashed CM or any other ROM for Toro, I got unknown baseband problem. And I can't flash maguro ROMs, only toro ones.
I tried to flash gsm radio via CWM (XXLF1), but baseband is still unknown. I can't make calls, sms or any other career action.
Then I flashed JB following THIS thread, and I made it. I have stock JB that works, but again I can't flash any other custom ROM on my Nexus. I can, but then I can't make calls or sms. Everything other is working normal.
Now I'm on stock JB, waiting for someone to help me solve this problem...
P.S. IMEI was also unknown if it means anything (*#06#)
P.P.S. Sorry for my bad english, I'm Croat...
Click to expand...
Click to collapse
If you flashed it with a Verizon option, it won't work. You have the GSM version. Verizon is an LTE carrier in USA. Vodafone is a GSM carrier.

Thank you all for replies and help.
Ok, now I understand that I have maguro device, but why I can't flash maguro ROMs (cwm allows me to flash only toro roms)? Is it because of cwm? When I try to flash maguro rom, cwm says that error status 7? Something like 'what is maguro?'. If it's important what error it is, I could write it down?
I don't know if I'm doing something wrong?
Sent from my Galaxy Nexus using xda app-developers app

Chances are, you flashed a toro cwm since you said you used a toolkit and selected the toro option.
Go back to stock using this guide and do everything manually.

Ok, I'll try. Thank you.
Btw, I'm on stock JB right now but I'll revert to ICS and remove all to stock..
Sent from my Galaxy Nexus using xda app-developers app

I solve the problem.
Toolkit flashed toro cwm so it wouldn't let me flash maguro ROM. Now I flashed maguro cwm and it's all fine
Thank you all for tips and help!
Sent from my Galaxy Nexus using xda app-developers app

Noob question: Why flashing the wrong S3 ROM bricks your phone?

I have wondered this for a while now. How come if you own an ATT or other variant S3 and flash a rom for a different S3 variant your phone bricks?
Being a huge computer nerd I have some tech knowhow but I'm new to the Android scene. The hardware is the same right? International version aside I am aware tgat version gas different hardware. Can someone be kind enough to explain this to me?
Thanks.
Sent from my SAMSUNG-SGH-I747

djdoubt03 said:
I have wondered this for a while now. How come if you own an ATT or other variant S3 and flash a rom for a different S3 variant your phone bricks?
Being a huge computer nerd I have some tech knowhow but I'm new to the Android scene. The hardware is the same right? International version aside I am aware tgat version gas different hardware. Can someone be kind enough to explain this to me?
Thanks.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.

BCSC said:
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.
Click to expand...
Click to collapse
Thanks, So it is in fact a hardware issues. I was just wondering this for a while.
Sent from my SAMSUNG-SGH-I747

I installed an at&t romantic fine on my unlocked s3 works fine no issues with any connectivity no brick
Sent from my SGH-I747 using xda app-developers app

BCSC said:
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.
Click to expand...
Click to collapse
Indeed Part of your Information is wrong I am on rogers network and I am running T-mobile (4.1.2) Firmware on it, I used mobile odine to flash the rom without the modem. I did that because the email apk on rogers is white writing on black background but in T-mobile it's inverted which I find is more comfort on my eyes

I may have done this
BCSC said:
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.
Click to expand...
Click to collapse
I am on a SGH-I747M and I accidentally downloaded what I think is a ROM that is incompatible with my carrier (Telus). I'm a total noob when it comes to these things and this would be my first time flashing a ROM on a rooted phone, although I did put lots of prior research in (apparently not enough). Anyways, I used ROM Manager when trying to flash Cyanogenmod 10.1 by going to "Download ROM" and choosing the ROM that I wanted. I thought that it was all going smoothly because I did it exactly how they showed you in the tutorial video. It even said in the video that it would only provide ROMs that are compatible with your device. I downloaded a stable version of Cyanogenmod 10.1 like I mentioned previously. Anyways, after I went through the process of backing everything up, and then flashing the ROM, I was unable to send texts, nor was I able to recieve or make calls. However, I was still able to recieve texts strangely enough. Anyways, I noticed that in the "About Device" section of the settings, it said my device model was no longer "SGH-I747M" but instead "SCH-R530" which I believe is MetroPCS. At this point I have no idea what to do or how to fix my phone. Please any help would be amazing

Aspring4 said:
I am on a SGH-I747M and I accidentally downloaded what I think is a ROM that is incompatible with my carrier (Telus). I'm a total noob when it comes to these things and this would be my first time flashing a ROM on a rooted phone, although I did put lots of prior research in (apparently not enough). Anyways, I used ROM Manager when trying to flash Cyanogenmod 10.1 by going to "Download ROM" and choosing the ROM that I wanted. I thought that it was all going smoothly because I did it exactly how they showed you in the tutorial video. It even said in the video that it would only provide ROMs that are compatible with your device. I downloaded a stable version of Cyanogenmod 10.1 like I mentioned previously. Anyways, after I went through the process of backing everything up, and then flashing the ROM, I was unable to send texts, nor was I able to recieve or make calls. However, I was still able to recieve texts strangely enough. Anyways, I noticed that in the "About Device" section of the settings, it said my device model was no longer "SGH-I747M" but instead "SCH-R530" which I believe is MetroPCS. At this point I have no idea what to do or how to fix my phone. Please any help would be amazing
Click to expand...
Click to collapse
You can try flashing the ATT CM10 from here http://get.cm/?device=d2att. The ATT version is the one that is compatible with Canadian S3's. If all else fails, you can revert back to stock. You are not bricked, so you shouldn't have much to worry about. If it boots it can be fixed. Try flash D2ATT Cm10.1 first. Maybe also look here if all else fails. http://forum.xda-developers.com/showthread.php?t=1831898

BCSC said:
You can try flashing the ATT CM10 from here http://get.cm/?device=d2att. The ATT version is the one that is compatible with Canadian S3's. If all else fails, you can revert back to stock. You are not bricked, so you shouldn't have much to worry about. If it boots it can be fixed. Try flash D2ATT Cm10.1 first. Maybe also look here if all else fails. http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Thank you so much, when I get the opportunity I will put that to work and hope for the best. I'll post again if any issues arise. Thanks again:fingers-crossed:

Still not working
BCSC said:
You can try flashing the ATT CM10 from here http://get.cm/?device=d2att. The ATT version is the one that is compatible with Canadian S3's. If all else fails, you can revert back to stock. You are not bricked, so you shouldn't have much to worry about. If it boots it can be fixed. Try flash D2ATT Cm10.1 first. Maybe also look here if all else fails. http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
So I'm still getting more issues when trying to flash this ROM. The message I'm getting is as follows:
Verifying SD Card marker...
ROM Manager Version 5.5.3.0
August 16, 2013
Preparing to install ROM...
Formatting /data...
Formatting /sd-ext...
- - Installing: /sdcard/0/Download/cm-10.1.2-d2att.zip
Finding update package...
Opening update package...
Installing update...
assert failed: gerprop("ro.product.device") == "
d2att" | | getprop("ro.build.product") == "d2att"
E: Error in /sdcard.0/Download/cm-10.1.2-d2att.zi
p
(Status 7)
Installation aborted.
Not sure what to do here. Any help would be appreciated

Aspring4 said:
So I'm still getting more issues when trying to flash this ROM. The message I'm getting is as follows:
Verifying SD Card marker...
ROM Manager Version 5.5.3.0
August 16, 2013
Preparing to install ROM...
Formatting /data...
Formatting /sd-ext...
- - Installing: /sdcard/0/Download/cm-10.1.2-d2att.zip
Finding update package...
Opening update package...
Installing update...
assert failed: gerprop("ro.product.device") == "
d2att" | | getprop("ro.build.product") == "d2att"
E: Error in /sdcard.0/Download/cm-10.1.2-d2att.zi
p
(Status 7)
Installation aborted.
Not sure what to do here. Any help would be appreciated
Click to expand...
Click to collapse
I ha this error also when flashing a rom with CWM, I flashed the latest TWRP recovery using ODIN, never had this problem afterwards.
check this thread
http://forum.xda-developers.com/showthread.php?t=2374306&highlight=error+7

[Q] Bootloader error when flashing Sprint ROM on SCH-S960L

I recently rooted and flashed my Samsung Galaxy S3 SCH-S960L (TracFone Variation, Sprint Based) with CyanogenMod 10.2-20131102-SNAPSHOT-M1-d2mtr which is for the MetroPCS version of CyanogenMod. Along with it saying MetroPCS, I also had an issue where the landscape orientation would be inverted which is quite a nuisance. Over on CyanogenMod's website someone suggested flashing the Sprint ClockworkMod (Which I was already using but for MetroPCS) and flashing the Sprint version of CyanogenMod. Now, upon flashing the ROM I get the error of
Code:
ClockworkMod Recovery v6.0.4.3
/storage/sdcard1: Checking
/storage/sdcard1: Mounted
--Installing" /storage/sdcard1/cm-10.1.3-d2spr.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.bootloader") == "L710VPBLJ7" || get prop("ro.bootloader")
(Log is not directly copied, some symbols may be inaccurate)
From there is just continues with similar lines of error.
Can anyone provide a fix to using my phone? I have to use the MetroPCS/Sprint versions of CWM and CM since the TracFone version of the Galaxy S3 has little support. At the moment my device is a brick and I would really like to use CyanogenMod but without that orientation issue and it saying "MetroPCS"
Any support is appreciated.
With best regards,
SirBenjamin

SirBenjamin said:
I recently rooted and flashed my Samsung Galaxy S3 SCH-S960L (TracFone Variation, Sprint Based) with CyanogenMod 10.2-20131102-SNAPSHOT-M1-d2mtr which is for the MetroPCS version of CyanogenMod. Along with it saying MetroPCS, I also had an issue where the landscape orientation would be inverted which is quite a nuisance. Over on CyanogenMod's website someone suggested flashing the Sprint ClockworkMod (Which I was already using but for MetroPCS) and flashing the Sprint version of CyanogenMod. Now, upon flashing the ROM I get the error of
Code:
ClockworkMod Recovery v6.0.4.3
/storage/sdcard1: Checking
/storage/sdcard1: Mounted
--Installing" /storage/sdcard1/cm-10.1.3-d2spr.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.bootloader") == "L710VPBLJ7" || get prop("ro.bootloader")
(Log is not directly copied, some symbols may be inaccurate)
From there is just continues with similar lines of error.
Can anyone provide a fix to using my phone? I have to use the MetroPCS/Sprint versions of CWM and CM since the TracFone version of the Galaxy S3 has little support. At the moment my device is a brick and I would really like to use CyanogenMod but without that orientation issue and it saying "MetroPCS"
Any support is appreciated.
With best regards,
SirBenjamin
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/54652/ got it merged in, come tomorrow just flash the latest d2spr nightly and it should flash in d2spr recovery for you.

it works
shabbypenguin said:
http://review.cyanogenmod.org/#/c/54652/ got it merged in, come tomorrow just flash the latest d2spr nightly and it should flash in d2spr recovery for you.
Click to expand...
Click to collapse
I got it to work(this is bilyan from IRC) missed CM on my s3

wickedclown691 said:
I got it to work(this is bilyan from IRC) missed CM on my s3
Click to expand...
Click to collapse
glad to hear it

APN
make sure you back up your apn. After I installed d2spr I couldnt connect with data. I had to restore APN settings.

[Q] i9300 - I747 Frankenstein What the heck phone do i really have HELP

I just purchased a "new" Galaxy S3 GT-I9300 from a store online. It can't be new even tho it is in pristine condition. It says I9300 when it boots, its not an I9300. I cant seem to get any roms to work but then again I have no idea what model this phone actually is. Here is the info I have.
It is a dual core so it cant be a GT-I9300
In the about phone screen it has the following
Model Number GT-I9300
Android version 4.1.1
Baseband version I9300ZSEMC
Kernel version 3. 0. 31-538866
[email protected]#1
SMP PREEMPT Tue Nov 20 22:42:27 KST 2012
Build Number I9300ZSEMC1
PDA, CSC, MODEM gives me all three with the number I9300ZSEMC
If I run terminal and do
getprop ro.bootloader I747UCALEM
getprop ro.product.device D2CAN
getprop ro.build.product D2CAN
If put my phone into download mode it says I747
When I tried the cyanogenmod one click installer it identified my phone as AT&T canada it also installed clockwork recovery but it failed when installing the system because the it cant find the product properly (basically its the wrong rom for the phone.. I believe it looks for a I747 number and gets the I9300ZSEMC number and fails ). The strange thing is, if its a canadian model it should be an I747M from what I have been seeing in my research. I have since flashed TWRP (openrecovery-twrp-2.8.1.0-d2can.tar) and rooted the phone but I still cant find a cyanogenmod rom that would install from recovery.
I would really like to get cyanogenmod on my phone since the retuning and replacement of this phone will most likely result in another Frankenstein I747-I9300.
Any ideas on how to figure out exactly what phone this is and a way to make the phone actually know what it really is so I can flash a rom correctly?

JOrion said:
I just purchased a "new" Galaxy S3 GT-I9300 from a store online. It can't be new even tho it is in pristine condition. It says I9300 when it boots, its not an I9300. I cant seem to get any roms to work but then again I have no idea what model this phone actually is. Here is the info I have.
It is a dual core so it cant be a GT-I9300
In the about phone screen it has the following
Model Number GT-I9300
Android version 4.1.1
Baseband version I9300ZSEMC
Kernel version 3. 0. 31-538866
[email protected]#1
SMP PREEMPT Tue Nov 20 22:42:27 KST 2012
Build Number I9300ZSEMC1
PDA, CSC, MODEM gives me all three with the number I9300ZSEMC
If I run terminal and do
getprop ro.bootloader I747UCALEM
getprop ro.product.device D2CAN
getprop ro.build.product D2CAN
If put my phone into download mode it says I747
When I tried the cyanogenmod one click installer it identified my phone as AT&T canada it also installed clockwork recovery but it failed when installing the system because the it cant find the product properly (basically its the wrong rom for the phone.. I believe it looks for a I747 number and gets the I9300ZSEMC number and fails ). The strange thing is, if its a canadian model it should be an I747M from what I have been seeing in my research. I have since flashed TWRP (openrecovery-twrp-2.8.1.0-d2can.tar) and rooted the phone but I still cant find a cyanogenmod rom that would install from recovery.
I would really like to get cyanogenmod on my phone since the retuning and replacement of this phone will most likely result in another Frankenstein I747-I9300.
Any ideas on how to figure out exactly what phone this is and a way to make the phone actually know what it really is so I can flash a rom correctly?
Click to expand...
Click to collapse
From the firmware information on the phone, it's best described as a I9300 - the generic or international version of this device. I say 'best described' because it appears to have had some history of hardware/firmware modification like a previous J-Tag job or something. It also has the boot-loader for the Canadian version.
Flashing a custom ROM from recovery should be possible, if you can get to recovery first. I would suggest, however, you try to flash the recovery kernel for I9300. If you can successfully get to TWRP recovery, you may try to first remove all existing firmware before flashing the custom. A custom ROM will not alter the existing boot-loader but flashing an (upgraded) stock ROM probably would.
BTW ... if you are exercising your buyer protection rights with the vendor, I'd go for a refund or replacement with a carrier version only. One major problem with the so-called generic or international version of this popular device is that it is the exclusive target for knock-offs and fakes.

still have issues
Larry2999 said:
From the firmware information on the phone, it's best described as a I9300 - the generic or international version of this device. I say 'best described' because it appears to have had some history of hardware/firmware modification like a previous J-Tag job or something. It also has the boot-loader for the Canadian version.
Flashing a custom ROM from recovery should be possible, if you can get to recovery first. I would suggest, however, you try to flash the recovery kernel for I9300. If you can successfully get to TWRP recovery, you may try to first remove all existing firmware before flashing the custom. A custom ROM will not alter the existing boot-loader but flashing an (upgraded) stock ROM probably would.
BTW ... if you are exercising your buyer protection rights with the vendor, I'd go for a refund or replacement with a carrier version only. One major problem with the so-called generic or international version of this popular device is that it is the exclusive target for knock-offs and fakes.
Click to expand...
Click to collapse
Like I said, I can't flash a rom. I have TWRP installed and when I try to load the cm-10.2.0-i9300.zip I get the following error:
Code:
Installing '/external_sd/cm-10.2.0-i9300.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: assert failed: getprop("ro.product.device") == "m0" || getprop("ro.build.product") == "m0" ||
getprop("ro.product.device") == "i9300" || getprop("ro.build.product") == "i9300" ||
getprop("ro.product.device") == "GT-I9300" || getprop("ro.build.product") == "GT-I9300"
assert failed: getprop("ro.product.device") == "m0" || getprop("ro.build.product") == "m0" || getprop("ro.product.device") == "i9300" || getprop("ro.build.product") == "i9300" || getprop("ro.product.device") == "GT-I9300" || getprop("ro.build.product") == "GT-I9300"
I was looking at some threads and found something about editing build.prop or something .. I will have to find that again and see if that is what I need to do. Its looking for GT-I9300 or i9300 from ro.product.device or ro.build.product but as stated above those return d2can so the script fails.
I also stumbled upon a site that has this available:
I747UCALEM_I747ATTALEM Android ICS 4.0.4 Ice Cream Sandwich
Device: Samsung Galaxy S III SGH-I747
Country: USA
Carrier: AT&T
PDA: I747UCALEM
CSC: I747ATTALEM
MODEM: I747UCLEM
Released Date: May 2012
Stock ROM Download: SGH-I747_ATT_I747UCALEM_I747ATTALEM
Im wondering if I used oden to flash this if it would bring the system back to original factory at&t *US phone which is what it seems to be originally .. i believe because i also saw this in the failed attemp to install CM... ro.product.model=SAMSUNG-SGH-I747 and the bootloader is I747UCALEM but I'm not sure what would happen and if it was successful .. I know I would have to root it again but I dont know if I would have to unlock it again .. I dont use AT&T.

Update .. getting somewhere
Ok .. I flashed openrecovery-twrp-2.8.1.0-d2att and was able to install cm-10.0.0-d2att but thats as far as i can get because now Im starting to understand ... the 10.1 versions are looking for a newer bootloader.
now in the about section it says:
Model Number SAMSUNG SGH-I747
Android Version 4.1.2
Baseband version I747UCLEM
Im still wondering if I should try installing the stock att rom and trying to use samsung update to put the latest update on it .. then save a back up so I have a copy of the latest stock setup for the phone ...
Can anyone tell me or point me to a thread that can explain, if possible, how to back up the complete phone so if I install that stock rom and it doesnt work properly I can put what I have back on? boot loader ... recovery ... everything

JOrion said:
Ok .. I flashed openrecovery-twrp-2.8.1.0-d2att and was able to install cm-10.0.0-d2att but thats as far as i can get because now Im starting to understand ... the 10.1 versions are looking for a newer bootloader.
now in the about section it says:
Model Number SAMSUNG SGH-I747
Android Version 4.1.2
Baseband version I747UCLEM
Im still wondering if I should try installing the stock att rom and trying to use samsung update to put the latest update on it .. then save a back up so I have a copy of the latest stock setup for the phone ...
Can anyone tell me or point me to a thread that can explain, if possible, how to back up the complete phone so if I install that stock rom and it doesnt work properly I can put what I have back on? boot loader ... recovery ... everything
Click to expand...
Click to collapse
Do you mean creating a Nandroid backup? If so, you can do it in TWRP or Clockwork mod recovery.

JOrion said:
Ok .. I flashed openrecovery-twrp-2.8.1.0-d2att and was able to install cm-10.0.0-d2att but thats as far as i can get because now Im starting to understand ... the 10.1 versions are looking for a newer bootloader.
now in the about section it says:
Model Number SAMSUNG SGH-I747
Android Version 4.1.2
Baseband version I747UCLEM
Im still wondering if I should try installing the stock att rom and trying to use samsung update to put the latest update on it .. then save a back up so I have a copy of the latest stock setup for the phone ...
Can anyone tell me or point me to a thread that can explain, if possible, how to back up the complete phone so if I install that stock rom and it doesnt work properly I can put what I have back on? boot loader ... recovery ... everything
Click to expand...
Click to collapse
It now looks like you have AT&T (based) firmware on it although I still doubt very much if this was ever an AT&T official device. If it was, the only way you could have had the hybrid firmware was if it had been force-flashed directly to the motherboard via a J-Tag. Usually, attempting to flash firmware meant for the generic version onto a carrier version would result in an instant hard brick. You could do a Nandroid backup as Stoney suggested or if you are merely looking at backing up your data and self-installed apps, you could use Samsung Kies for that. There is no direct source for flashing 4.1.2 UCLEM firmware for scratch as this can only be done via upgrade from 4.1.1 so if you experience any firmware failure and need to revert to stock, you would have to do 4.1.1 (via Odin) or 4.3 via custom recovery.
Please note that most custom ROMs like CM do not interfere with your manufacturer's bootloader and rely on the stock bootloader to run. Chances are therefore, that you still have the 4.1.1 bootloader in spite of your current build information. It may, therefore, be possible to flash full stock 4.1.1 or stock 4.3 and thereafter upgrade to 4.4.2. However, if you flash either 4.3 Jelly Bean or 4.4.2 KitKat, you cannot subsequently downgrade to an older firmware without hard-bricking your phone. You may, therefore, want to play around at 4.1.1 for now until you are everything is OK

thanks for the info
I found a stock firmware for a d2att (I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5) an installed it. Now everything is a SGH-I747 ... when I plug it into my computer ... when I look at the download screen on the phone ... when I do *#1234# it shows the above. ro.bootloader now shows i747UCDLK3. so now my phone is officially a USA based AT&T Samsung S3 SGH-I747. Luckily for me because of all the problems, I did already run across the threads that mentioned about downgrading your bootloader after upgrading to a 4.3 bootloader. But as you said ... CM doesnt mess with the boot loader. So I was able to install CM11 nightly without issue with the new Baseband version I747UCDLK3, the I747UCLEM version was just too old and that's why it was failing. 4.1.1 is the only firmware I found for completely stock. I have yet to find the stock KitKat update .. since i can't deal with AT&T directly since they aren't my carrier. I also found out that AT&T released a Lollipop stock firmware for their S3's on November 14, 2014 but I can't find that stock firmware either.
If anyone knows where I can get this firmware version I would love to have a stock lollipop install to have as a backup. lol tho then I probably would have problems downloading mods again because if they check for the Baseband version ... they probably don't have I747UCUFNE4 (KitKat) or I747UCUFNJ1 (possibly Lollipop) as one of the ones they look for .. just like cm10.1 didn't have the I747UCLEM to look for.
But with this new firmware stock or with a flash to cm 11 ... I even show LTE which I didn't have when it was Frankensteined... not sure if it works yet .. haven't tested it. I still would like to have the stock firmware for kitkat or lollipop if anyone knows where i could get it. Unfortunately CM-11 is missing one of the features I really liked and that was an option to have the phone screen stay on if you are looking at it. I haven't found that option anywhere in the CM-11 firmware .. unless i missed it somewhere.
Oh well, at least I got a "stock" phone that I can actually install mods on and the company has offered to give me a partial refund (tho until I got this fixed I wasnt going to accept anything .. so we shall see what their "partial refund" will be
I appreciate the responses and again if anyone can find the stock kitkat or lollipop firmware for a US based AT&T SGH-I747 (I747U - d2att) I would be very happy.

Help! Same problem
hi JOrion
I bought a used samsung galaxy s3 .
Like yours, It says I9300 when it boots, but its not an I9300.
In the about phone screen it has the following
Model Number GT-I9300
Android version 4.1.1
Baseband version I9300ZSEMC
Kernel version 3. 0. 31-538866
[email protected]#1
SMP PREEMPT Tue Nov 20 22:42:27 KST 2012
Build Number I9300ZSEMC1
It is a dual core with 2Go de Ram and
If put my phone into download mode it says I747, so it cant be an i9300
Can you give the link of your stock firmware for s3 i747 at&t. ??
Im a beginner in flashing phones. I dont want to brick my phone.
Please, how to do this with a simple et detailed procedure?
Do you find the stock firmware s3 i747 at&t???
If yes, give me the download link and how to install this?
I am on 4.1.1 already rooted.
Thank you very much!

jordicrystal said:
hi JOrion
I bought a used samsung galaxy s3 .
Like yours, It says I9300 when it boots, but its not an I9300.
In the about phone screen it has the following
Model Number GT-I9300
Android version 4.1.1
Baseband version I9300ZSEMC
Kernel version 3. 0. 31-538866
[email protected]#1
SMP PREEMPT Tue Nov 20 22:42:27 KST 2012
Build Number I9300ZSEMC1
It is a dual core with 2Go de Ram and
If put my phone into download mode it says I747, so it cant be an i9300
Can you give the link of your stock firmware for s3 i747 at&t. ??
Im a beginner in flashing phones. I dont want to brick my phone.
Please, how to do this with a simple et detailed procedure?
Do you find the stock firmware s3 i747 at&t???
If yes, give me the download link and how to install this?
I am on 4.1.1 already rooted.
Thank you very much!
Click to expand...
Click to collapse
Hi .. I got the stock firmware from SamMobile www(dot)sammobile(dot)com /firmwares/database/SGH-I747/ATT (sorry cant post outside links yet)
this brought me back to stock 4.1.1 ... and changes all the information in the phone to the 747 and also it will be recognized as d2att instead of d2can so roms seemed more compatible. You will not be rooted but if it will still be "carrier unlocked". It wont download updates from Samsung because the flash counter has already been tripped. I believe installing this rom will reset the flash counter but it still keeps it at 1 if I remember correctly.
Not sure if you have oden set up or anything yet .. but if not .. just do a search on rooting your phone in these forums ... there are plenty of step by step posts... just follow one to the point of getting oden installed and connecting to your phone ... then put your phone into download mode .. open oden ... click the pda button and load file you download from sammobile... make sure that reboot and F.Reset Time checked and making sure that Re-Partition is unchecked. Start it up and wait.... you phone will eventually start to boot again but don't unplug it or do anything yet... wait till Oden says Passed and the little bar at top turns green. ... I just left it plugged in until it finally booted into the OS. ... it does take a while and will look like its hung with the white screen and AT&T icon... just wait .. let it go .. it will get there eventually.
If you want to root again ....
The process I followed was to download TWRP (openrecovery-twrp-2.8.1.0-d2att.tar) www (dot) teamw (dot) in /project/twrp2/104
Then I downloaded TeamEpic-Root-from-Recovery-v5 www (dot) teamw (dot) in /project/twrp2/104 and copied it to my phones sd card.
I flashed TWRP using Oden leaving reboot and F.Reset Time checked and making sure that Re-Partition was unchecked. This will void warranties but as for us I guess we didn't have any anyways .. since the flash counter has already been tripped. I believe it tries to reboot after it finishes flashing TWRP .. if so pull the battery .. don't let it boot back into the OS.
I put the battery back in and booted into recovery. Using TWRP, I flashed TeamEpic-Root-from-Recovery-v5... Did a factory reset in TWRP (Wipe button in TWRP) .. rebooted and I was at 4.1.1 stock rooted.
There are places on this forum where you can get 4.3 and even 4.4.2 installed .. Im running stock KitKat right now but I had issues with it that are big and now that I had them I found that a lot of people have problems with the sdcard not being able to be written too in KitKat .. I tried to downgrade to 4.3 and soft bricked my phone ... well not really I just didnt realize that its very hard to downgrade your bootloader and modem ... the problem I had when I downgraded is .. it left my bootloader set for KitKat and changed my modem to JB. I lost my carrier, my baseband and my IMEI I had to find a modem to flash that was I474UCUFNE4. Even then I had problems .. I'm back on KitKat right now "without the no writes to sdcard bug atm" but I still haven't installed everything.
I'm basically new to flashing too .. did it a while back for the MyTouch 3G Slide ... If I was you .. after getting the stock firmware rooted .. that would be as far as I would go ... Im kicking myself for going with 4.3 and 4.4.2 because now I'm stuck ... I can't get 4.3 to flash correctly and work .. I can't find any way to down grade my boot loader and modem and everything so it is back to the 4.3 stuff .. It doesn't look like I can flash any of my backups I made for device. I haven't tried it but I doubt I will be able to use any custom roms because they usually look for the bootloader and usually only looks up to the 4.1.1 - I747UCDLK3 so when it sees my I474UCUFNE4 it fails. So stick with 4.1.1 .. if you want kitkat try cyanogenmod CM-11 .. once you get your phone back to stock 4.1.1 it will be able to be flashed .. it doesn't update your bootloader or modem it will run off the I747UCDLK3 bootloader and is available for the d2att. As mentioned by someone else .. if you go to the 4.3 or 4.4.2 roms ..you have to update your bootloader and once that is done .. it will not be able to go back and if you try to say reinstall this stock rom to get it back you will have a brick because you cant downgrade 4.3 to any lower bootloader .. 4.3 does something to the phone that makes the older loaders even if reinstalled, completely unusable and will cause a hard brick you will probably not be able to fix yourself.
Good luck hope this helps

It will not help you any JOrion, but most of the KK roms will run off of the MJ2 bootloader. The MJ2 bootloader came from a leaked release of AT&Ts 4.3 rom, it also came with the MJ2 baseband. This may be of use to @jordicrystal because you can download from this bootloader. There were links posted to it from S3Rx by loserskater, I believe there are other links to it in the forums. What will work just as well is the MJ2-bootloader_MJB-modem combo. I have noted a number of KK roms that will run from this. Even CM may require this at some point.
On another note, @JOrion, have you enabled root access in your file manager? This may solve your issues regarding writing to the external sdcard.

dawgdoc said:
It will not help you any JOrion, but most of the KK roms will run off of the MJ2 bootloader. The MJ2 bootloader came from a leaked release of AT&Ts 4.3 rom, it also came with the MJ2 baseband. This may be of use to @jordicrystal because you can download from this bootloader. There were links posted to it from S3Rx by loserskater, I believe there are other links to it in the forums. What will work just as well is the MJ2-bootloader_MJB-modem combo. I have noted a number of KK roms that will run from this. Even CM may require this at some point.
On another note, @JOrion, have you enabled root access in your file manager? This may solve your issues regarding writing to the external sdcard.
Click to expand...
Click to collapse
thanks for the reply .. I was having issues with it writing to the internal sd .. I have KK running smoothly. I'm now able to save files on internal and external sd. Its rooted and I can customize it so I'm set. I tried cyanogenmod on the phone before I did my updates and I liked some of the extra features but .. I like the feature that stock has where you can set it to keep the display on if you are looking at it. I didn't see that feature in cyanogen so I decided that stock is more set to what I want. Now that I have KK running and functioning properly I'm ok with not having the other options ... at least for now .. and I'll probably update to a new phone before it becomes an issue. I messed with my old htc for a while, trying different roms ... but once I put cyanogenmod on it I liked how it worked so it stayed till I got this phone ... I think KK will end up the same .. I tried others ... liked stock the best ... now that it works .. I'll probably not play with roms anymore on this phone.
Thanks everyone for the help and responses. My issues have been resolved.

Thank U dawgdoc!
Finally, I did not do anything at all. I just sold the phone and bought a galaxy s4 i9505 with which I have not had problems updating to kitkat .
Thank you for your various interventions.

i9300 - I747 Frankenstein What the heck phone do i really have HELP
hello guys i had sem probleme
in bootloader i had sgh-i747
but in system info i had
i9300zsemc
please help me what i can do
flash with cyanogenmod or with stock rom AT&T 4.1.1

boziditofik said:
hello guys i had sem probleme
in bootloader i had sgh-i747
but in system info i had
i9300zsemc
please help me what i can do
flash with cyanogenmod or with stock rom AT&T 4.1.1
Click to expand...
Click to collapse
Its up to you. If you can get Cyanogenmod to work I would probably do that. I had issues trying to get Cyanogen to run which is why I flashed the stock AT&T 4.1.1 rom. Once I did that, it made my phone a SGH-I747 (d2att rather than d2can which is what it was supposed to be originally) and I was able to install just about any rom I wanted to after that.

i think to change build.prop from system change d2can to d2att and flash to cm with cwm recovery

my phone is d2tmo but it says it is d2spr

Hi xda.
I have search a lot but maybe I have no Idea what to search for solve my problem so please.
There is this problem that I was trying to install CM-10.2.1 for t999 [d2tmo] but I couldnt.
Searching in this forum I Found THIS, and I tried but it didn`t worked.
Also found another person with this problem HERE
And I made all the steps they said, but did not worked.
SO I decided to download a nigthly build of CM 11 but had the same problem and I cheked this code at /meta-inf/com/google/android/Updater-script
Code:
abort("This package is for \"d2tmo\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
The function of
Code:
+ getprop("ro.product.device") +
Should be alert me that the rom is not for my decive and this shlould tell me what kind of device is.
and whe I try to flash the rom, the error says that my device is d2spr
but I`m 101% Sure that my device is d2tmo cuz if it wasn´t I could not flash rhe d2tmo stock rom: T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5
I noticed that any rom I download has the "UVUENC2" support. and searched a way to change it but somewhere I read it was so risky and should not be done.
Also Is d2lte == d2tmo?? Things I read suggest that they sould be, but I want a simple answer yes/no before doing something stupid.
What can I do?
Any suggest of a rom?
PD: I rooted my device with towel root, also removed knox

original SIII on TMobile is **NOT** the same as the LTE version
First off, the original S3 for TMobile is not the same as the LTE version. Open the phone, take out battery, and look for exact model number on the phone. If it says SGH-T999, it is the original S3 for TMobile. If not, then it isn't.
Try going to a standard factory ROM first, to make sure it is A-OK. Then you can start to play with custom roms. I would use ODIN to reset phone pack to factory image, since trying to flash a rom when one is already installed may also be causing issues for you.
Good Luck.!