Why is the LTE version of our phone merged with our thread? The few ROMS it provides confuses me into thinking I can use them for the original S3. Can we not divide them and give it it's own thread?
The roms are interchangeable. Just like the T999V that's been part of this forum since the beginning.
I don't see what there is to be confused about though. If you're not sure about it, don't flash it! Or ask.
I have the original T999. But I'm running the T999L rom. Several T999L users are using T999 roms. If you gave it its own forum, everyone would just wind up here anyway. Theres just no reason for it that I can see.
Sent from my SGH-T999L using xda premium
I am using CM10.1 Nightly for T999 (d2tmo) on my T999L, works just fine.
I have read your threads about the ROMS for that phone and yes I'm impressed but even you said inside the thread that flashing the T999L will provide a few bugs if it's not the LTE provided device. That's the only reason I made a statement about dividing them as to avoid problems. I know you can flash ROMS that are not particularly for your device but all devices are different.
Your OP said you were confused into thinking that you could flash the lte roms onto your S3. As I said at the top of the T999L thread, you can.
The Root Explorer "bug" was a simple scripting error on my part (which will be fixed soon), the others are not rom related as they are that way out of the box (and one of those was only reported by one user). And even so, I wouldnt really say they are truly bugs as they do not in any way affect the functionality or experience.
One or two extremely minor glitches do not warrant another separate forum. If this were the case, you would literally see a dozen or more S3 forums! (US Cellular, Straight Talk, mobilicity, wind, videotron, etc, etc, etc.) And several of them would be T-Mobile S3 forums. THAT would make things waaaaayyyy more confusing and you would probably see a whole lot more of the bricked device threads.
Also, for the most part, the T999, T999L, and T999V are identical. Its mostly just the radios that are different (yes, i know there are other minor differences, but for the most part, they are the same)
In the end, the roms and kernels are interchangeable so that should be enough. And if you are still confused or worried about it, just don't flash it.
Again, even if a change were warranted, everyone would still wind up here anyway.
I hope that helps to clear it up a bit better for you.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Your OP said you were confused into thinking that you could flash the lte roms onto your S3. As I said at the top of the T999L thread, you can.
The Root Explorer "bug" was a simple scripting error on my part (which will be fixed soon), the others are not rom related as they are that way out of the box (and one of those was only reported by one user). And even so, I wouldnt really say they are truly bugs as they do not in any way affect the functionality or experience.
One or two extremely minor glitches do not warrant another separate forum. If this were the case, you would literally see a dozen or more S3 forums! (US Cellular, Straight Talk, mobilicity, wind, videotron, etc, etc, etc.) And several of them would be T-Mobile S3 forums. THAT would make things waaaaayyyy more confusing and you would probably see a whole lot more of the bricked device threads.
Also, for the most part, the T999, T999L, and T999V are identical. Its mostly just the radios that are different (yes, i know there are other minor differences, but for the most part, they are the same)
In the end, the roms and kernels are interchangeable so that should be enough. And if you are still confused or worried about it, just don't flash it.
Again, even if a change were warranted, everyone would still wind up here anyway.
I hope that helps to clear it up a bit better for you.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I have a SGH-T999L, with a SGH-T999 AOSP ROM on it. Everything works except the camera (I get a "Can't connect to camera" error). The major difference I've encountered so far is I can't Odin to any stock SGH-T999 firmware (which seriously confused me when Odin kept failing with an aboot.mbn error though I thought I had the firmware for the right device).
Be glad it didn't work. You might have bricked your device doing that!
As for the camera, its an issue for the T999L in some aokp roms, but I don't think all of them.
Sent from my SGH-T999 using xda premium
Camera works fine on CM10.1 nightly since (at least) 6/22/13, even the HDR and Panorama functions. Try updating the ROM.
DocHoliday77 said:
Be glad it didn't work. You might have bricked your device doing that!
As for the camera, its an issue for the T999L in some aokp roms, but I don't think all of them.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah, after I realize I tried flashing the wrong firmware, I felt very lucky... Fortunately I had read somewhere (if I remember correctly) that one possible cause of an aboot.mbn Odin error is that the device model in the bootloader in the image being flashed doesn't match with the model number in the device. (Hope this helps any other SGH-T999L owners!)
DJ_SpaRky said:
Camera works fine on CM10.1 nightly since (at least) 6/22/13, even the HDR and Panorama functions. Try updating the ROM.
Click to expand...
Click to collapse
Thanks! I saw your update in the http://forum.xda-developers.com/showthread.php?t=2308829&page=3 thread (as well as in the CM forum). Bottom line is that cm-10.1-20130703-NIGHTLY-d2tmo is working for me now, including camera, as you said!!! I actually had some initial trouble flashing using CWM which kept abort with a status 7 error, even after removing the asserts in the updater script. CM10.1 nightly ultimately flashed without updater script modification using TWRP.
Cool, glad to hear that you got it working. I prefer TWRP over CWM, but it is just choice, both work fine.
aokp
DJ_SpaRky said:
Cool, glad to hear that you got it working. I prefer TWRP over CWM, but it is just choice, both work fine.
Click to expand...
Click to collapse
Can I ask if I can install the AOKP rom on my t999L I only saw it for att s3 unless I missed it
imblessed68 said:
Can I ask if I can install the AOKP rom on my t999L I only saw it for att s3 unless I missed it
Click to expand...
Click to collapse
Should be OK, certain things might not work (camera, etc). I found it here: http://forum.xda-developers.com/showthread.php?t=2088764
Thank you Dj in running LiquidSmooth now and it seems to be flawless
Sent from my SGH-T999 using xda app-developers app
Related
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Maybe someone who is a little more savvy in this field could take a look?
Here is a very good article and discussion about the issue:
http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SGH-T989 using xda premium
this is kinda scary but so far I never had any problem
We don't even have any kernel source. There is a leaked kernel but that didn't cause any brick in our devices. Also note that the article does not mention sgh t989 or sgh 727 and all its sub variants. If this was the case for us you would see many more "[Q] plz halp I haz brick " threads
Sent from my SGH-T989 using XDA
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
kahm said:
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
Click to expand...
Click to collapse
Finally someone with a brain! Thanks for the post
Sent from my SGH-T989 using xda premium
Scary stuff indeed, has anyone confirmed that our devices (T989) is affected by this bug?
Back on the original Epic we used Odin to get the next version. I think it was 2.1 to 2.2 roms. I've always wondered how safe it was to revert to GB by flashing after installing ICS
Sent from my SGH-T989 using xda premium
[Q] plz halp I haz brick
Disregard. Funny how you figure out your issue just seconds after you post and open yourself up to ridicule.
DOH!
mharmon said:
I seem to have hard-bricked my SGH-T989 phone after flashing task650-aokp-Build-36. I don't know if it's a superbrick, but nothing I can do seems to make any difference. The phone does not seem to respond and does not seem to power off, power on or go into download mode. I have swapped with a known good battery and I know that's not the issue. I've tried using a USB jig and that doesn't help. I've contacted Samsung and I should be shipping it to them Monday.
If anyone has any advice, I'm willing to try anything otherwise I'm going to take my lumps and ship my phone off.
Click to expand...
Click to collapse
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Micronads said:
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
mharmon said:
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
Click to expand...
Click to collapse
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Micronads said:
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Click to expand...
Click to collapse
Yeah sounds dead to me. Send in for warranty. Oh well, stuff happens. Good luck to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Id rather risk bricking than rock without 4.04
Sent from my SGH-T989 using xda premium
Nobody has said it is necessary applicable to this device.
jim93 said:
Nobody has said it is necessary applicable to this device.
Click to expand...
Click to collapse
You're right, it doesn't say it's applicable to our device. But it also doesn't say our device is one of the safe GS2 variants. As you can see in my signature, I'm also using 4.0.4. And if you read my post history, I recommend it to everyone. I'm just saying that it hasn't been proven safe yet, but there's also no proof its dangerous either.
Sent from my SGH-T989 using xda premium
ICS has been flashed to these phones probably a half million times by now. If it was causing bricks we would have heard about it.
Sent from the iPhone graveyard.
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
Also, people should know that the listed phones in the OP are Exynos based and T989, i727/r and i717 are Qualcomm based. This has been discussed in the skyrocket forums and some devs have explained that.
Just my 2 cents.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
The brick in this thread was due to flashing an i777 rom to a t989. Flashing an i777 rom to t989 regardless of OS will brick your phone.
It seems to be all exynos based, but thanks for the heads up, man.
Can anyone tell me if you can run the same ROMs for these two phones. I will be getting the SGH-T999V on Wind Mobile in Canada. But I'm a little concerned for developer support for this phone, in which case I may get the SGH-T999 instead. But it would be much cheaper and easier to get it from my own carrier. So if anyone can let me know typically if the Canadian version of T-Mobile Galaxy S series phones are able to run the same ROMs, it would be much appreciated.
Hey. I just got my s3 from Videotron, it is also the v model. Personally, I would wait until the Canadian versions are out. Just this noob's opinion.
I'm also wondering this, but I've seen some posts saying how the modems of the SGH-T999 and the SGH-T999V are incompatible which means that a lot of ROMs won't be shared from the T-Mobile version to the Videotron version
Does anyone know the answer to this? pls and thanks.
adslee said:
I'm also wondering this, but I've seen some posts saying how the modems of the SGH-T999 and the SGH-T999V are incompatible which means that a lot of ROMs won't be shared from the T-Mobile version to the Videotron version
Click to expand...
Click to collapse
You are wrong. I got my T999V from Wind canada, wiped and flashed TMOUS stock ROM right over it. Its been working solid so far.
Tried a couple of other TMO ROMs also but am a stock ROM kind of guy.
Average speed of 8Mbs download and 2.25Mbs Upload in the DC area.
I intend to flash TMOUS stock modem this weekend and see if the speed would crawl into the upper 2 digits.
IMO it is essentially the same phone w/ same internals. Only reason for getting was to stick with my grandfathered $5.99 T-Zones which works PERFECTLY with the thing.
djide said:
You are wrong. I got my T999V from Wind canada, wiped and flashed TMOUS stock ROM right over it. Its been working solid so far.
Tried a couple of other TMO ROMs also but am a stock ROM kind of guy.
Average speed of 8Mbs download and 2.25Mbs Upload in the DC area.
I intend to flash TMOUS stock modem this weekend and see if the speed would crawl into the upper 2 digits.
IMO it is essentially the same phone w/ same internals. Only reason for getting was to stick with my grandfathered $5.99 T-Zones which works PERFECTLY with the thing.
Click to expand...
Click to collapse
I never said they weren't the same phone. I only said that I've seen people posting around saying that if you flash a T999 ROM that changes the modem on a T999V, then you'll run into problems. Am I wrong about seeing posts by other people that the two phones have different basebands?
Next time you post something, let's not try and sound like a douche in the first three words.
adslee said:
I never said they weren't the same phone. I only said that I've seen people posting around saying that if you flash a T999 ROM that changes the modem on a T999V, then you'll run into problems. Am I wrong about seeing posts by other people that the two phones have different basebands?
Next time you post something, let's not try and sound like a douche in the first three words.
Click to expand...
Click to collapse
I have a Videotron GSIII (Québec) and I have no issues at all. I think the added V is just for Videotron.
I used a T999 Root method, a T999 CWM and I currently use the CM10 from these forums.
Bonne chance !
adslee said:
I never said they weren't the same phone. I only said that I've seen people posting around saying that if you flash a T999 ROM that changes the modem on a T999V, then you'll run into problems. Am I wrong about seeing posts by other people that the two phones have different basebands?
Next time you post something, let's not try and sound like a douche in the first three words.
Click to expand...
Click to collapse
How do I sound like one? Saying one "is wrong" Take it easy cowboy. All I stated was my experience with the phone. No need for name calling.
On a lighter note, it seems the modem are totally different thus a Tmobile modem baseband would definitely not work on a wind or Mobility variant and would render the phone unusable. In conclusion Roms could be shared but modem/radio files can't be shared. Again I am stating my experience, "no need for anyone to wet their pants"
Sent from my iPad using Tapatalk HD
djide said:
How do I sound like one? Saying one "is wrong" Take it easy cowboy. All I stated was my experience with the phone. No need for name calling.
On a lighter note, it seems the modem are totally different thus a Tmobile modem baseband would definitely not work on a wind or Mobility variant and would render the phone unusable. In conclusion Roms could be shared but modem/radio files can't be shared. Again I am stating my experience, "no need for anyone to wet their pants"
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
You could've stated your experience without starting the post with "You are wrong", period and all. Try responding to someone else stating his/her experience in a real life conversation with those three words before anything else and let's see how many people would think you sound like a douche. Not wetting my pants here or anything man, just sayin' that you came off sounding like a real total douche right off the bat.
But back on topic here, as soon as someone pulls the modem files off the T999V model, I'm sure a lot of the devs will update their ROMs to be completely compatible with the WIND/Videotron variant.
The majority of roms you run into will not include a radio. So when you flash the rom your radio will remain untouched.
It will be noted in the OP for the rom if the radio is included. If its not mentioned its generally safe to assume its not included.
Sent from my SGH-T999 using xda app-developers app
djide said:
You are wrong. I got my T999V from Wind canada, wiped and flashed TMOUS stock ROM right over it. Its been working solid so far.
Tried a couple of other TMO ROMs also but am a stock ROM kind of guy.
Average speed of 8Mbs download and 2.25Mbs Upload in the DC area.
I intend to flash TMOUS stock modem this weekend and see if the speed would crawl into the upper 2 digits.
IMO it is essentially the same phone w/ same internals. Only reason for getting was to stick with my grandfathered $5.99 T-Zones which works PERFECTLY with the thing.
Click to expand...
Click to collapse
Good to hear that T-Zones works on the T999V GS III. I have T-Zones myself and was looking at the T999V. Where you able to flash a T-mobile radio and get better speeds? You would think the T999V would hit double digit download numbers on the regular.
NardVa said:
Good to hear that T-Zones works on the T999V GS III. I have T-Zones myself and was looking at the T999V. Where you able to flash a T-mobile radio and get better speeds? You would think the T999V would hit double digit download numbers on the regular.
Click to expand...
Click to collapse
No no no please don't flash a tmobile radio. I did that on Friday and phone became a $500 ipod, imei was null/null and baseband was unkown. Couldn't connect to a network. Finally restored it yesterday. Currently I hit speed of about 8-11mpbs not bad for my everyday use.
djide said:
You are wrong. I got my T999V from Wind canada, wiped and flashed TMOUS stock ROM right over it. Its been working solid so far.
Tried a couple of other TMO ROMs also but am a stock ROM kind of guy.
Average speed of 8Mbs download and 2.25Mbs Upload in the DC area.
I intend to flash TMOUS stock modem this weekend and see if the speed would crawl into the upper 2 digits.
IMO it is essentially the same phone w/ same internals. Only reason for getting was to stick with my grandfathered $5.99 T-Zones which works PERFECTLY with the thing.
Click to expand...
Click to collapse
How were you able to flash it? I tried and ODIN wouldn't let me
if you are talking about flashing roms. Try using cwm or twrp
Sent from my SGH-T999 using xda premium
Sgh t999v Québec also
Zotak said:
I have a Videotron GSIII (Québec) and I have no issues at all. I think the added V is just for Videotron.
I used a T999 Root method, a T999 CWM and I currently use the CM10 from these forums.
Bonne chance !
Click to expand...
Click to collapse
♡I've got also the same problem with my sgh t999v impossible to install cm10 did you find how to fix this issue?
Doumaye said:
♡I've got also the same problem with my sgh t999v impossible to install cm10 did you find how to fix this issue?
Click to expand...
Click to collapse
if you are using cwm, make sure you have the latest version which I believe is 6.0.1.2
older versions of cwm fails to flash cm10 on sgs3 with jellybean baseband
Just install TWRP and use that instead. Not saying CWM is bad but TWRP for me has been a much more pleasant experience
I plan to purchase a Wind Mobile galaxy s3 tomorrow and I was wondering about the compatibility it will have with ROMs.
I have heard many different things but from what I gather it is that Wind phones are compatible with T-Mobile Roms except for the ones that include things to do with radio. I don't fully understand what this means but I hope I can get a further understanding from the community's response to this thread.
I am not sure if the Nightly even comes with a radio. If it doesn't I heard people saying it would work as long as the rom does not come with the radio. I have no idea what all this means. I hope someone can clarify
The plan I have is to buy the Wind S3 and flash CM10 Nightly straight away with the Lean Kernel. Will it work? If not, is there a way for me to fix it?
Thank you :fingers-crossed:
hey
BUMP!
Looks like people need some encouraging to answer my question
Yes the CM10 nightly will work for you ROMs and radios are mostly kept separate so you don't have to worry about that.
Sent from my SGH-T999
Patience! Its only been a few hours. Ive seen threads go for a day or two before getting answered. Just a matter of when the right person comes across it.
To answer, yes you can flash our roms, but no you cannot use our radios. I'd recommend backing up your current one in case of accidents.
Cm10 should be fine but unless its been addressed expect somewhat slow data speeds and a few other bugs.
Stock on this phone is fantastic believe it or not! So give that a fair run too.
As far as kernel, just make sure the one you use is compatible with CM.
CM roms dont include radios. Most roms dont if they are flashable in cwm or twrp. Be careful if you're using an odin flashable as many do include the radio.
Sent from my SGH-T999 using xda app-developers app
.
joshnichols189 said:
Yes the CM10 nightly will work for you ROMs and radios are mostly kept separate so you don't have to worry about that.
Sent from my SGH-T999
Click to expand...
Click to collapse
Thank you for answering me. I cannot locate the thank you button though
wonker51 said:
Thank you for answering me. I cannot locate the thank you button though
Click to expand...
Click to collapse
Haha by the quote button. No worries though, here to help
Sent from my SGH-T999
.
DocHoliday77 said:
Patience! Its only been a few hours. Ive seen threads go for a day or two before getting answered. Just a matter of when the right person comes across it.
To answer, yes you can flash our roms, but no you cannot use our radios. I'd recommend backing up your current one in case of accidents.
Cm10 should be fine but unless its been addressed expect somewhat slow data speeds and a few other bugs.
Stock on this phone is fantastic believe it or not! So give that a fair run too.
As far as kernel, just make sure the one you use is compatible with CM.
CM roms dont include radios. Most roms dont if they are flashable in cwm or twrp. Be careful if you're using an odin flashable as many do include the radio.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
"Cm10 should be fine but unless its been addressed expect somewhat slow data speeds"
Could you go in to more details about this subject? I do not understand why the data would slow down.
Thanks
Im not sure what the cause is but ive heard a lot of people complain about slow data with cm10, mostly in the modem threads. Udated modems helped for some but not much I dont think. Only other thing ive heard is that its a known issue but the cm team had no plans to address it until they have a stable release.
I haven't kept up with development on cm so you will be able to find much more and up to date info in their thread.
Sent from my SGH-T999 using xda app-developers app
wonker51 said:
I plan to purchase a Wind Mobile galaxy s3 tomorrow and I was wondering about the compatibility it will have with ROMs.
I have heard many different things but from what I gather it is that Wind phones are compatible with T-Mobile Roms except for the ones that include things to do with radio. I don't fully understand what this means but I hope I can get a further understanding from the community's response to this thread.
I am not sure if the Nightly even comes with a radio. If it doesn't I heard people saying it would work as long as the rom does not come with the radio. I have no idea what all this means. I hope someone can clarify
The plan I have is to buy the Wind S3 and flash CM10 Nightly straight away with the Lean Kernel. Will it work? If not, is there a way for me to fix it?
Thank you :fingers-crossed:
Click to expand...
Click to collapse
That is exactly what I am running, but you should be prepared for bugs, if you think you are going to get a perfect running rom, your not, if you can't handle, then you better stick with the stock roms.
.
TheAxman said:
That is exactly what I am running, but you should be prepared for bugs, if you think you are going to get a perfect running rom, your not, if you can't handle, then you better stick with the stock roms.
Click to expand...
Click to collapse
Could you name some bugs that stand out? I would like to know which bugs bothered you the most.
Thanks
TheAxman said:
That is exactly what I am running, but you should be prepared for bugs, if you think you are going to get a perfect running rom, your not, if you can't handle, then you better stick with the stock roms.
Click to expand...
Click to collapse
are you experiencing problems with receiving text messages as well?
wonker51 said:
are you experiencing problems with receiving text messages as well?
Click to expand...
Click to collapse
For me, everything works, but keep in mind I DO NOT USE THE STOCK APPS...worthless email/gmail/message. I use Handcent, and K9 email. They work perfect. I uninstall all stock apps on every rom I load, the only bug I see is screen flicker ( which has a fix), the only thing I do not like is when charging and screen is off, no led, so I never know when it is complete on the charge other than using a prog that sounds when charge is complete....I like the nightly's. I flash update every night. Also using AnTuTu speed test, I get high 9000's on the benchmark, my friggin phone IS FAST!!!!
Just a question. My brother bought a bell s3 but he's leaving bell and paying his contract. If I flash a t-mobile modem to bell s3 would it work with wind/mobilicity? I know it works when you do it with bell note.
Sent from my SGH-T999 using xda premium
It doesnt work, it has different hardwares.
Sent from my SGH-I747 using xda app-developers app
the Bell/Rogers/Telus/Sask S3 is the i747M, meanwhile the mobilicity/wind model is the T999
cross flashing the modem, may brick your phone or do other damages/problems. DO NOT DO IT.
The Bell note is able to cross flash because they did a workaround for it. Not that you can do it up front, but you still have to do it in a special way. People are working to see if they if they can make the i747M access the special band that the wind/mobi/tmo T999, but so far they haven't done much progress, as far as to what I've read.
I've already encountered and answered this question more than enough times to make my mind ignore it nearly everytime I see it. So this would probably be the last time I would answer this question.
NO, you simply can't. Go and buy their phone model if you really want to use it for win/mobi.
I mean, if it works, they would have had simply merged the tmo/wind/mobi threads with the ATT/rogers/bell/telus thread... BUT NO, they did not, because of the difference in the hardware.
I sound like an ass, because I am simply getting frustrated by how many times this question has been asked. It seems users don't even use some slight initiative to use the search. This question has been answered several times in various forms. I'm sure one way or another using the search for "bell phone for wind" would yield some answer in the first few results.
there's even that sticky thread here on the general forums about canadian carriers: http://forum.xda-developers.com/showthread.php?p=28287042
zaghy2zy said:
the Bell/Rogers/Telus/Sask S3 is the i747M, meanwhile the mobilicity/wind model is the T999
cross flashing the modem, may brick your phone or do other damages/problems. DO NOT DO IT.
The Bell note is able to cross flash because they did a workaround for it. Not that you can do it up front, but you still have to do it in a special way. People are working to see if they if they can make the i747M access the special band that the wind/mobi/tmo T999, but so far they haven't done much progress, as far as to what I've read.
I've already encountered and answered this question more than enough times to make my mind ignore it nearly everytime I see it. So this would probably be the last time I would answer this question.
NO, you simply can't. Go and buy their phone model if you really want to use it for win/mobi.
I mean, if it works, they would have had simply merged the tmo/wind/mobi threads with the ATT/rogers/bell/telus thread... BUT NO, they did not, because of the difference in the hardware.
I sound like an ass, because I am simply getting frustrated by how many times this question has been asked. It seems users don't even use some slight initiative to use the search. This question has been answered several times in various forms. I'm sure one way or another using the search for "bell phone for wind" would yield some answer in the first few results.
there's even that sticky thread here on the general forums about canadian carriers: http://forum.xda-developers.com/showthread.php?p=28287042
Click to expand...
Click to collapse
well oddly enough this is the first topic that comes up after a search. Thx for clarifying this gain.
Oddly enough, when I opened my T999v, what I saw stamped on the motherboard is i747M, which leads me to believe that the difference between a bell or Rogers phone and wind is mostly software.
LiquidSmooth 4.2.2 ROM is available for both the ATT and Verizon S3's. I have the ATT and I regularly flash my Cousin and his wife's phones for them. But they're four hours away and I won't see them again for a couple months.
What I've done in the past with my ATT Skyrocket was to flash a TMobile Hercules ROM on it and customize it the way it needs to be, then just sent it to them to restore from CWM.
But, the Skyrocket & Hercules were essentially the same phone. So now that we all have the S3, and they are on Verizon now, I'm not sure how well I'll get away with this.
Basically I flash the ROM on my phone. Install all their apps. Set up all little tweaks & customizations. Then do a Nandroid for them to restore on their phone. Makes it a nice and TIGHT phone. They love it, and I get killer BBQ & Beer & Pool fun when I go visit every few months.
The Wife's phone has been having issues, so it's time for a new flash. And they're still on 4.1.1 ROM's.
I know the TMO & ATT S3's can share the same ROM. But I don't want to brick my ATT S3 with a Verizon S3 ROM flash, even if it's just for a couple hours while I set it up. Wondering if it's absolute trouble waiting to happen?
Its different. I had to root my friends vzw s3 and the whole process is different, and I'm sure the partitions are different.
Sent from my SGH-I747 using xda app-developers app
They are already rooted (TWRP). But that's a good point about the partitioning.
Definitely not going to do something unless someone else has already leapt from this bridge before me....
Nope. I wouldn't try it either.
Sent from my SGH-T999 using xda premium
Don't do it. You will brick their phones. The system files are very different. with different hardware as well. The antenna mainly. As well as a special dialer app and files to work on the out dated cdma network
Wayne Tech S-III
It might work, you wouldnt have signal.... I wouldnt try it though.
Sent from my SAMSUNG-SGH-I747 using xda premium
Bootloader is different. Kernel is different. The partitions may be even set up differently. Different radio bands, RILs and other items will cause it to brick.
Maybe it's the allergy meds I'm on, or maybe I just felt like testing the boundries.
Just flashed AOKP's Verizon 4.2.2 3/5/13 release on my D2ATT.
Phone still boots & works.
Well, data doesn't work (as you guys said it wouldn't). But WiFi does work.
Rebooted and installed gapps. Set up a bunch of settings. So far, so good. Though Play Store does crash. Can't get past that so far.
EDIT:
I just flashed the Verizon version of Slim Bean 4.2.2.
It had an option for me to not only add an APN, but also to select GSM. The AOKP did not.
After setting up these two things, data is working fine. Made a phone call too.
Playstore working also.