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
Related
Hi everyone, new android user here! I'll try to make this as brief as possible:
Recently purchased a used Unlocked Galaxy S3.
Currently using Bell Carrier on it and it works fine.
I noticed that even after restoring SuperSU was installed.
Checked download mode -> odin installed with custom binary
Checked to see if the phone has root access -> it does not
I wanted to try and flash it with a official ROM to completely restore factory settings but I don't know what the original carrier is so I don't know what ROM to download. I called a couple carriers but they have no record of the IMEI.
I'm fairly new to android and my past two days of google searching hasn't accomplished anything relative to my problem (although I know a lot more about the rooting community!) so I thought I'd ask here.
Is there any way to know what's going on here?
Can I restore the phone to factory firmware/ROM/etc.?
Here is some phone information:
Model: SGH-I747M
Android Version: 4.1.1
Baseband: I747MVLDLK4
Kernel: 3.0.31-538866
Build Number: JRO03L.I747MVLDLK4
Any help would be greatly appreciated!
Just go and download this program http://www.samsung.com/ca/support/usefulsoftware/KIES/JSP
Go to Tools > Firmware Install and Initialization
It will ask you for your model number and Serial number. It will use those to determine what stock ROM is correct for your phone.
It will then flash you to stock, just as Odin would, including the stock recovery.
theXact said:
Hi everyone, new android user here! I'll try to make this as brief as possible:
Recently purchased a used Unlocked Galaxy S3.
Currently using Bell Carrier on it and it works fine.
I noticed that even after restoring SuperSU was installed.
Checked download mode -> odin installed with custom binary
Checked to see if the phone has root access -> it does not
I wanted to try and flash it with a official ROM to completely restore factory settings but I don't know what the original carrier is so I don't know what ROM to download. I called a couple carriers but they have no record of the IMEI.
I'm fairly new to android and my past two days of google searching hasn't accomplished anything relative to my problem (although I know a lot more about the rooting community!) so I thought I'd ask here.
Is there any way to know what's going on here?
Can I restore the phone to factory firmware/ROM/etc.?
Here is some phone information:
Model: SGH-I747M
Android Version: 4.1.1
Baseband: I747MVLDLK4
Kernel: 3.0.31-538866
Build Number: JRO03L.I747MVLDLK4
Any help would be greatly appreciated!
Click to expand...
Click to collapse
It definitely looks like you are on the stock Jelly Bean firmware from Samsung. I747M is the Canadian model (747 is ATT). Your build number also looks to be the stock 4.1.1 based on the DLK4 build number! Just as the last guy said, grab kies or use Odin to go back to complete stock if you are not happy with what you have now. If your phone is showing custom binary flashes and you want to get rid of that, give Triangle Away a try! Good luck. :good:
Lumixz said:
Just go and download this program *link removed since I'm a newbie*
Go to Tools > Firmware Install and Initialization
It will ask you for your model number and Serial number. It will use those to determine what stock ROM is correct for your phone.
It will then flash you to stock, just as Odin would, including the stock recovery.
Click to expand...
Click to collapse
Thank you! That worked like a charm! The device is now in a "normal" state and the binaries are "official".
BAM1789 said:
]It definitely looks like you are on the stock Jelly Bean firmware from Samsung. I747M is the Canadian model (747 is ATT). Your build number also looks to be the stock 4.1.1 based on the DLK4 build number! Just as the last guy said, grab kies or use Odin to go back to complete stock if you are not happy with what you have now. If your phone is showing custom binary flashes and you want to get rid of that, give Triangle Away a try! Good luck.
Click to expand...
Click to collapse
Thanks for the advice! I'm not too concerned about the flash count, that's only really important your warranty to to be valid, right? But I'll look into it, it may be worth it anyway.
Thanks again everyone!
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed
ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.
Did that modem fix some of the problems?
If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .
I am not very much familiar with all intricacies of Android system but i have played around rooting and putting customer firmwares on few devices.
I have AT&T Galaxy S3 with following detals:
Baseband: I747UCUEMJB
Version: 4.3
I had the device rooted in the past but recently un-rooted it and reset the flash counter as well and did factory reset. Did all that since i wanted to use ISIS and couldn't make it work on a rooted S3. Seems it used to work before till they updated ISIS app to patch it.
Now AT&T got 4.4 update and my phone detects it, downloads it but while installing fails at 32%. I have seen many threads where people faced similar issues due to their phones being rooted. Seems something on my phone didn't reset to default.
I found one post which mentions that i can download UCUEMJB_to_UCUFNE4_Firmware_update.zip and load it to phone using TWRP. As i understand, this will update the baseband but android version still remains at 4.3 (?). Is that the path i should be looking for or i am shooting in wrong direction? I want to stay on default firmware since i like to use ISIS till they keep running those cashback promos
Would appreciate some feedback.
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
DocHoliday77 said:
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
Click to expand...
Click to collapse
Thanks for the reply.
Just to confirm so that i don't mess up, i will apply the following(is modem same as firmware?) and then try OTA.
I747UCUEMJB: modem_CWM_I747UCUEMJB.zip
No. The modem is only one part of the firmware. Firmware includes bootloaders, kernel, system, modem and more.
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.!
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882
I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
SuperGoober said:
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882
Click to expand...
Click to collapse
SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse
lvpre said:
I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
Click to expand...
Click to collapse
Thanks it worked.