This is probably really a dumb question, but can I flash the Sprint ND8 bootloader and modem safely on a TracFone S3 (based on the Sprint variant)?
Whoareyou said:
This is probably really a dumb question, but can I flash the Sprint ND8 bootloader and modem safely on a TracFone S3 (based on the Sprint variant)?
Click to expand...
Click to collapse
I don't think so, ND8 is for L710, your model is probably S390 or S960
The FCCID for it is L710 I bricked it trying to flash it with dd though since Odin wouldnt work, need to get a 16gb sdcard for unbricking...
Whoareyou said:
The FCCID for it is L710 I bricked it trying to flash it with dd though since Odin wouldnt work, need to get a 16gb sdcard for unbricking...
Click to expand...
Click to collapse
Under the battery it says L710? Because the TracPhone branded S3 is not L710
I'm aware of that, but it is a rebranded L710 , as made clear in the FCC ID
Whoareyou said:
I'm aware of that, but it is a rebranded L710 , as made clear in the FCC ID
Click to expand...
Click to collapse
The FCCID doesn't matter, what does it say for model?
It's the S960L, but I remember back when I actually used an S3 I was able to convert my T999 to a I747 by flashing the ODIN package for it, it just seemed logical that since these were essentially the same device, (at least according to the US FCC) then they aboot should be interchangable
Whoareyou said:
It's the S960L, but I remember back when I actually used an S3 I was able to convert my T999 to a I747 by flashing the ODIN package for it, it just seemed logical that since these were essentially the same device, (at least according to the US FCC) then they aboot should be interchangable
Click to expand...
Click to collapse
ROMs should be fine, but the bootloader may be an issue
Well, the thing is as Straight Talk and TracFone failed to update the device to kitkat, so no Roms higher than CM10.2 can boot and function properly, so I was simply hoping that it could be converted to a L710 in a similar way how I can convert my dev edition M8 to GPe or the I747/T999 example I used before...
Whoareyou said:
Well, the thing is as Straight Talk and TracFone failed to update the device to kitkat, so no Roms higher than CM10.2 can boot and function properly, so I was simply hoping that it could be converted to a L710 in a similar way how I can convert my dev edition M8 to GPe or the I747/T999 example I used before...
Click to expand...
Click to collapse
Only real issue I could see is that if ND8 flashed ok, but didn't work with your service, you would have no way to go back, as if you try to flash anything lower than ND8 after you have ND8, it's brick city
Related
Ok so I like playing around as much as the next guy but is there a way to Odin a STOCK international ROM thats not rooted and make it just think its a international phone that will still work on AT&T s network with LTE. My Galaxy Nexus was pretty much that without the LTE
azfxstb said:
Ok so I like playing around as much as the next guy but is there a way to Odin a STOCK international ROM thats not rooted and make it just think its a international phone that will still work on AT&T s network with LTE. My Galaxy Nexus was pretty much that without the LTE
Click to expand...
Click to collapse
Why is NON-root an issue?
Jade Eyed Wolf said:
Why is NON-root an issue?
Click to expand...
Click to collapse
I think he wants to know if a pure factory Samsung kies released ROM for the N7015 will work... as opposed to one here we have removed kernel, modem plus rooted and added busy-box.
Gillion said:
I think he wants to know if a pure factory Samsung kies released ROM for the N7015 will work... as opposed to one here we have removed kernel, modem plus rooted and added busy-box.
Click to expand...
Click to collapse
If that the case, then no. Flashing international firmware onto the i317, and then un-rooting it for the sake of obtaining official Samsung update via Kies is just a bad idea. Assuming it works in the first place, Kies will (sometimes) overwrite the kernel, and if that happens, you could at least have no working radios, or worst case scenario, soft brick. If you have an i317, and you want the international firmware on it, you're better off just following the instructions laid out in the dev section.
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
So first off I know I messed up bad. I had 4.4.2 bell s3 i747m. I was able to go from 4.1.2 to 5.1 with cwm. I wanted 4.1 to unlock sim. I saw the warnings but they were a cpl years old. Nothing new. And it said 4.3 and above only. Since I could get to 4.1.2 I thought maybe it wasn't still ongoing. I downgraded the bootloader. Phone went black from recovery and now nothing. The tuts are for 4.3. What works on 4.4.2? Does the sd card boot work for 4.4.2?
The phone was running a stock 4.4.2?
Did you try using the 4,3 de-brick image?
I did. It doesn't boot. And yes stock 4.4.2
I need the 4.4.2 bootloader
Also is it Knox bricking the phone? And if so will removing it (if I can boot it) stop future bricks? Anyone out there got a bell s3 they can get the bootloader and debrick from on 4.4.2
godkingofcanada said:
Also is it Knox bricking the phone? And if so will removing it (if I can boot it) stop future bricks? Anyone out there got a bell s3 they can get the bootloader and debrick from on 4.4.2
Click to expand...
Click to collapse
It's not Knox, it's just the newer bootloaders. Disabling Knox doesn't make any difference. You still can't downgrade the more recent bootloaders.
They might be somehow related. The bootloaders that produce bricks when downgraded emerged at the same time as Knox when Samsung started their corporate device push. Better to brick a phone than risk it running on a downgraded bootloader, when the bootloaders are all unlocked and will run unsigned code anyway It always seemed a little half-baked, but I'm sure there's something I'm failing to grasp.
Me as well. And I've only got mild understanding about this brick. I'm thinking with the right 4.4.2 bootloader and whatnot I may be able to use my 16 gig sd card to boot the phone. Is there any way to connect it in raw data mode? I remember older phones had to be off and have a button held while plugging it in to flash firmware.
I'm really stuck here
Also does anyone know where the extra hidden files internally are? I know it won't boot the phone because the phone knows the bootloader is invalid. Maybe if I just reinstall the right one I may revive it. But I assume I need sd boot for that to get to cwm
You should try different sd cards. Some members had to try a few different cards.
Has anyone out there successfully debrick the s3? On 4.4.2? Or should it let me force 4.3 rom and bootloader to work? I'm not sure if the method posted works for kit kat
I gotta locate a member with a bell s3 for the 4.4.2 debrick img. I can't just flash any 4.4.2 I wouldn't imagine. Maybe at&ts will work since that's i747 and this is i747m? I'm fine having to fix the modem and all that good stuff manually. I just need to get it on n I can fix the rest. Never bricked a phone before
godkingofcanada said:
I gotta locate a member with a bell s3 for the 4.4.2 debrick img. I can't just flash any 4.4.2 I wouldn't imagine. Maybe at&ts will work since that's i747 and this is i747m? I'm fine having to fix the modem and all that good stuff manually. I just need to get it on n I can fix the rest. Never bricked a phone before
Click to expand...
Click to collapse
did you check here
http://forum.xda-developers.com/showthread.php?t=2549068
sorry , that's all I got. good luck.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Yeah that's not going to work thanks tho. Anyone know how to flash to the boot sector while device off? Like raw data read/write?
so to clarify where im at. im at the dreaded QHSUSB - DLOAD with my s3. meaning there is hope. its hard bricked but it still connects in fast download mode. is there a program i can use to connect to it at this point? im not able to find usb drivers for that. so it must be an app that reads it
What do you mean fast download mode? You mean you see the android guy with the shovel?
No I mean even tho the phone doesn't turn on or do anything it pops up on the computer.
You will have to have the phone repaired via jtag if you can't get it to work using a de-brick image.
I can. I just need a 4.4.2 bell debrick img. It's got to be the exact same no? Isn't 4.4.2 a different bootloader? Also does it matter if I flash a non bell bootloader and rom? Say at&t? It's i747 instead of i747m but I've used an at&t rom n it worked fine. I just don't know what works at bootloader level. Anyone out there got a bell s3 they can take the files from?
godkingofcanada said:
I can. I just need a 4.4.2 bell debrick img. It's got to be the exact same no? Isn't 4.4.2 a different bootloader? Also does it matter if I flash a non bell bootloader and rom? Say at&t? It's i747 instead of i747m but I've used an at&t rom n it worked fine. I just don't know what works at bootloader level. Anyone out there got a bell s3 they can take the files from?
Click to expand...
Click to collapse
might be one in here.
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Hello,
I'm relarively new to the Galaxy S3 realm, and after a brief experience with a defective SGH T999 that I returned for a refund (which I'm pretty sure shipped with an unlocked bootloader out of the box since T-Mobile is usually good with doing that with their devices), I'm thinking of getting an SGH i747 new and networked unlocked on Amazon for use with T-Mobile since the SGH i747 is the least expensive S3 variant out there with LTE capabilities. I don't want to actually make the purchase until I know these two things:
1) Can the bootloader be unlocked on the latest official firmware (which I believe is 4.3 according to my research)? If so, how?
2) If I can unlock the bootloader on the latest official firmware, what ROMs will I be able to use? I read somewhere that using a ROM designed for an different stock firmware can lead to problems (like how 4.0 firmware users can't use 4.1 firmware ROMs)
I'm hoping I can get this since it has great features for the money, but if I can't install ROMs on it, I'm going to have to look for a different device to purchase.
Thanks ahead of time!
EDIT: I found an article stating there was an All In One toolkit that would root, bootloader unlock, and install recovery for US variant galaxy S3's, and it linked to me to an XDA thread. However, after reading the XDA thread, it seems that it is only able to unlock bootloaders of Nexus devices. Can anyone confirm for me that this all in one toolkit can unlock the bootloader for the latest firmware of the ATT S3?
Link to the toolkit thread:
http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my LG-D415 using XDA Free mobile app
jasonmerc said:
Hello,
I'm relarively new to the Galaxy S3 realm, and after a brief experience with a defective SGH T999 that I returned for a refund (which I'm pretty sure shipped with an unlocked bootloader out of the box since T-Mobile is usually good with doing that with their devices), I'm thinking of getting an SGH i747 new and networked unlocked on Amazon for use with T-Mobile since the SGH i747 is the least expensive S3 variant out there with LTE capabilities. I don't want to actually make the purchase until I know these two things:
1) Can the bootloader be unlocked on the latest official firmware (which I believe is 4.3 according to my research)? If so, how?
2) If I can unlock the bootloader on the latest official firmware, what ROMs will I be able to use? I read somewhere that using a ROM designed for an different stock firmware can lead to problems (like how 4.0 firmware users can't use 4.1 firmware ROMs)
I'm hoping I can get this since it has great features for the money, but if I can't install ROMs on it, I'm going to have to look for a different device to purchase.
Thanks ahead of time!
EDIT: I found an article stating there was an All In One toolkit that would root, bootloader unlock, and install recovery for US variant galaxy S3's, and it linked to me to an XDA thread. However, after reading the XDA thread, it seems that it is only able to unlock bootloaders of Nexus devices. Can anyone confirm for me that this all in one toolkit can unlock the bootloader for the latest firmware of the ATT S3?
Link to the toolkit thread:
http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
all s3i747 should already be bootloader unlocked. i bricked my first one trying to "unlock" the bootloader.lol. kind of.
as far as firmware i am assuming you mean bootloader/modem. once you are on NE4 and above firmware , trying to downgrade ,i.e. mj2 firmware will give you a nice looking paper weight.
custom ROMs ; flash away (after making a backup of course). i have never seen a custom ROM include the bootloader/firmware. although you need to always read the OP to make sure it is compatible with whatever your current firmware is.,i.e.(again) if its a ROM for nj2 your ne4 firmware may need to be upgraded to match. @audit13 or @dawgdoc can confirm/deny/provide more info i am sure.
hope this helps at least some.
good luck.
"all i can really do is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
all s3i747 should already be bootloader unlocked. i bricked my first one trying to "unlock" the bootloader.lol. kind of.
as far as firmware i am assuming you mean bootloader/modem. once you are on NE4 and above firmware , trying to downgrade ,i.e. mj2 firmware will give you a nice looking paper weight.
custom ROMs ; flash away (after making a backup of course). i have never seen a custom ROM include the bootloader/firmware. although you need to always read the OP to make sure it is compatible with whatever your current firmware is.,i.e.(again) if its a ROM for nj2 your ne4 firmware may need to be upgraded to match. @audit13 or @dawgdoc can confirm/deny/provide more info i am sure.
hope this helps at least some.
good luck.
"all i can really do is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Are you SURE they are all unlocked out of box, regardless of firmware? I have seen guides as to how to unlock the bootloader for the i747 on 4.1.1 firmware, which would lead me to believe they aren't unlocked out of the box.
jasonmerc said:
Are you SURE they are all unlocked out of box, regardless of firmware? I have seen guides as to how to unlock the bootloader for the i747 on 4.1.1 firmware, which would lead me to believe they aren't unlocked out of the box.
Click to expand...
Click to collapse
OK. if you've read different then no , i'm not SURE. but i thought they all were.
"all i can really do is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
OK. if you've read different then no , i'm not SURE. but i thought they all were.
"all i can really do is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Well too late now, already ordered one...
jasonmerc said:
Well too late now, already ordered one...
Click to expand...
Click to collapse
well i'll tell you the honest truth. nevermind bootloaders and whatnot. i gave my S3 away to upgrade to the htcm8. to do all over ; i would have kept it or ordered one like you , or off swappa ,etc. i miss it.
good luck
"all i can really do is stay out of my own way and let the will of heaven be done"
Looking in the all in one toolkit, it gives the user the option to root, busybox, and install custom recovery on a 4.3 ATT S3. From my knowledge, one needs an unlocked bootloader to install custom recoveries. Unless this is some sort of special recovery, it seems to me that this is in fact unlocked. Perhaps another user can confirm this.
thats why i mentioned audit13 and dawgdoc earlier. both more knowledgeable than me and i was hoping they would chyme in. or @DocHoliday77.
"all i can really do is stay out of my own way and let the will of heaven be done"
The bootoader is not locked. If you try to unlock it using software tools, you will brick it. I have never come across anyone on xda with an att s3 with a locked bootoader but I have come across a few that bricked their phone trying to unlock the bootoader.
Although att often locks the bootoader on their phones (e.g. note 3, s4, lg g2), they did not do this on the sgh-i747.
Once the phone is running the mjb or higher bootoader, you cannot flash an older bootoader.
Alright, thanks to both of you guys for the assistance. Just let out a huge breath of relief, I was scared my money went to waste. Can't wait for this to come in, and I'm eager to be a part of the i747 community on XDA!
Plus I got the red one
If you decide to flash anything to the phone, make sure you verify the bootloader version before flashing anything.
When you receive the phone, boot into download mode to confirm the model # as well.
audit13 said:
If you decide to flash anything to the phone, make sure you verify the bootloader version before flashing anything.
When you receive the phone, boot into download mode to confirm the model # as well.
Click to expand...
Click to collapse
Yes, I do recall reading something about only being able to flash ROMs made for the specific bootloader of the phone. But if I were to flash a ROM for d2lte (designed to work with ALL Galaxy S3 models), I would assume it would work alright regardless of bootloader version?
Sent from my LG-D415 using XDA Free mobile app
For stock ROMs, only flash for the d2att. For custom ROMs, only flash ROMs for the d2lte.
So no CM9 then eh?
Sent from my LG-D415 using XDA Free mobile app
jasonmerc said:
So no CM9 then eh?
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
Well, d2lte and d2att roms.
There are a few quirks about particular roms, do not hesitate to ask more questions as they arise. Sometimes you will contradicting answers, or typos causing incorrect answers.
Just an update, the S3 arrived. Looks beautiful physically.
But beyond that...
(I happycried for a good 3 minutes after seeing this)
Sent from my LG-D415 using XDA Free mobile app
jasonmerc said:
Just an update, the S3 arrived. Looks beautiful physically.
But beyond that...
(I happycried for a good 3 minutes after seeing this)
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
That's a nice state to receive an i747. Before doing any updates to bootloader and modem or flashing any ROMs I would suggest doing the free sim unlock found in the forums. (Yes, even though the bootloader is unlocked the sim card does not come unlocked out of the box.) If you upgrade to the 4.3 bootloader or newer you will no longer be able to do the free sim unlock. Although there are always paid unlocks.
dawgdoc said:
That's a nice state to receive an i747. Before doing any updates to bootloader and modem or flashing any ROMs I would suggest doing the free sim unlock found in the forums. (Yes, even though the bootloader is unlocked the sim card does not come unlocked out of the box.) If you upgrade to the 4.3 bootloader or newer you will no longer be able to do the free sim unlock. Although there are always paid unlocks.
Click to expand...
Click to collapse
Already flashed a ROM. Despite the seller claiming it was unlocked out of the box, it was not. I'll be flashing back to 4.1.1 stock to do so.
EDIT: This is the firmware I'll be flashing, I assume it's correct
http://forum.xda-developers.com/showthread.php?t=2161667
man 'o man. 4.1.1. heck yeah !! happy for you (and envious). enjoy. :sly: @audit13 & @dawgdoc :thumbup:
(IF you were thinking about hitting the "thanks button" for this post ; please do not). this is for you guys. :thumbup::thumbup::thumbup:
"all i can really do is stay out of my own way and let the will of heaven be done"
As long as you didn't flash 4.3 or newer bootloaders you should be good.
I747 sometimes restarts itself and gets stuck on the custom rom boot screen. I have tried multiple ROMs and multiple kernels by now but the problem persists. The only thing that gets it out is that I have to manually remove the battery and put it back in. Also sometimes the WiFi stops connecting and when I try to turn it off and on again, it gets stuck on "WiFi is turning on".
The only thing I want to do now is go back to the original firmware however the because I have a ROM installed, I don't know exactly what the VERSION (the version shown in the settings doesn't match any of these). I also don't remember the exact carrier. Can anyone help regarding this?
Did you make a nandroid backup before installing the custom ROM? If not, I suggest using ODIN to flash the stock NE4 firmware. You can find the NE4 4_file tar file thread in this forum.
StoneyJSG said:
Did you make a nandroid backup before installing the custom ROM? If not, I suggest using ODIN to flash the stock NE4 firmware. You can find the NE4 4_file tar file thread in this forum.
Click to expand...
Click to collapse
No backup at all. I was also thinking of the Odin way however as I mentioned in the post, I can't find a version of the software that matches that on the phone. I also don't know the phone carrier (it is from Canada i747m with 2gb RAM, thats all I know). Is it okay to just do any version of the firmware or do I need a specific version?
Boot into download mode and confirm the model # there.
sCell_ said:
No backup at all. I was also thinking of the Odin way however as I mentioned in the post, I can't find a version of the software that matches that on the phone. I also don't know the phone carrier (it is from Canada i747m with 2gb RAM, thats all I know). Is it okay to just do any version of the firmware or do I need a specific version?
Click to expand...
Click to collapse
If it's an i747m then you need firmware for that model. Firmware for the i747 won't work on i747m.
sCell_ said:
No backup at all. I was also thinking of the Odin way however as I mentioned in the post, I can't find a version of the software that matches that on the phone. I also don't know the phone carrier (it is from Canada i747m with 2gb RAM, thats all I know). Is it okay to just do any version of the firmware or do I need a specific version?
Click to expand...
Click to collapse
If it's a Canadian i747m, it may be a Telus, Bell, Rogers, [email protected], or SaskTel phone. Check the back --- oh wait, Telus doesn't have custom backs (I have a S3 from Telus).
It doesn't matter what VERSION, it matters what MODEL it's for. I could flash CM10 and it would run, BUT it has to be for the EXACT SAME DEVICE! (d2can if you wanted to know.)
Rogers, Telus, bell, fido, Koodo all use the same stock base rom with slight customization for each carrier. You can install the rogers rom to a Telus phone and bell phone. I've done this many times.