I'm relatively new, but have flash a couple Galaxy S2's. But I have my personal SGH-T999L that I want to flash and would like to use the Beanstalk 4.3 here http://forum.xda-developers.com/showthread.php?t=2345663, I can't afford to brick my phone and just trying to find out if anyone out there has used it on a T999L. I could only find one reference to it which wasn't very specific.
Thanks in advance
All Custom T999 Roms will be fine to use on the T999L unless otherwise stated.
Please don't double post in multiple places.
Sorry, was just trying to find someone online to answer before i tried it. Had been searching for an answer for quite awhile and running out of patience not finding much in specific in reqards to the t999L except a few horror stories related to other attempts to use t999 software on the L model. Was hoping to get an answer from DOCHOLIDAY77 (no offense) since he seems to have the most post/experience with the differences between the 2 models. But I thank you for your response and input. I presume from your answer, that as long as I only install the system software and leave the radio and bootloader alone. I'll be okay? Am I getting that right? That seems to be what the horror stories are about, people who have flashed the entire device with software from the original T999
dwgibson2000 said:
Sorry, was just trying to find someone online to answer before i tried it. Had been searching for an answer for quite awhile and running out of patience not finding much in specific in reqards to the t999L except a few horror stories related to other attempts to use t999 software on the L model. Was hoping to get an answer from DOCHOLIDAY77 (no offense) since he seems to have the most post/experience with the differences between the 2 models. But I thank you for your response and input. I presume from your answer, that as long as I only install the system software and leave the radio and bootloader alone. I'll be okay? Am I getting that right? That seems to be what the horror stories are about, people who have flashed the entire device with software from the original T999
Click to expand...
Click to collapse
You are spot on.
Related
To be specific, I'm wondering exactly how careful I need to be with my Galaxy Nexus compared to other phones to avoid bricking specifically. I make Nandroid backups regularly, so I'm not worried about losing data. But is it easy to outright brick the phone even when taking all precautions? I ask because I just recently bricked a Samsung SII within 24 hours of purchase, and I don't want to lose my new Galaxy Nexus in the same way. Most of my experience has been with the Nexus S so far, and I'd mostly be flashing Cyanogenmod and probably a custom kernel here and there, again, performing backups regularly and whatnot. Is there anything that could easily brick the phone, and are there any precautions to take against that? Thanks.
This phone is pretty hard to brick unless you blatantly flash radios or ROMs for the LTE version of the phone. Kinda surprised you were able to hard brick a SGSII. Samsung phones are pretty tough to completely brick when there are tools like Odin...
Just don't make stupid choices and you won't brick your phone. Fastboot is your friend.
I had the Telus version, which was just different enough from the T-Mobile version that a couple of basic things weren't working post-root, and I ended up being unable to connect to Odin, have the system recognize my SD card, or boot into recovery. So I'm just not wanting to have something like that happen again, where none of my tools are working. I appreciate the reply though, I figured the Galaxy Nexus would be a pretty safe bet in general. Does anyone know any particular quirks with the Canadian version, as I'm pretty sure that contributed to my being screwed previously.
feanarosurion said:
Does anyone know any particular quirks with the Canadian version, as I'm pretty sure that contributed to my being screwed previously.
Click to expand...
Click to collapse
They're all pretty much identical hardware. For example you can flash Google images straight onto any i9250, regardless of what firmware it shipped with.
Thanks, that's helpful to know. I'm definitely glad the hardware is the same with the exception of the lte version.
Sent from my Galaxy Nexus using Tapatalk
feanarosurion said:
Thanks, that's helpful to know. I'm definitely glad the hardware is the same with the exception of the lte version.
Click to expand...
Click to collapse
Yep, that's what to look out for. Don't want to flash for the wrong version.
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.
The thing is, we weren't even going to root it. I thought that Teamviewer Quicksupport supported all S3's.
I looked and he is running 4.1.1. So...I'm not sure what the big deal is, but no matter what, Quicksupport is not "supported" when we go to the Play Store. If there is a simple fix, I would love this, because he is not tech-savvy and this is why we got this model.
However -
I've only rooted one phone in my life before, when there was only really one way of rooting. It seems I have read that problem abound with these S3 models - more specifically, IMEI may be lost, and choosing exactly which way to root, since there are varying stock kernels.
I see this thread here on the IMEI backup/injection. Am I safe to assume, that is where I start? (I have read that the Bell is just a ATT version, so will the ATT version instructions work here? I will ask in that thread but not sure).
Then - once that is done - I have to pick a way to root it that works for Bell's SIII SGH-1747M. That is where I am running into a bit of a wall. I wonder if I can get someone who has done this with this model to help me out and pick a safe way to mod it? Do I need to post more info to help decide this? I can get on his device and get whatever info is needed.
I also read, that perhaps Bell's stock kernels either do or do not need unsecuring (not quite sure after a lot of reading) before doing anything else. I really am trying to learn - it's just all very daunting and when I'm reading and not understanding, I can still read til the sun explodes and never be able to do this correctly. Well, maybe if I had an unending supply of phones.
Thank you for your help...
I would just ask in the IMEI and other forums but they are not available to me (either post count too low or I'm not sure).
Sincerely,
Foxdev
foxdev said:
The thing is, we weren't even going to root it. I thought that Teamviewer Quicksupport supported all S3's.
I looked and he is running 4.1.1. So...I'm not sure what the big deal is, but no matter what, Quicksupport is not "supported" when we go to the Play Store. If there is a simple fix, I would love this, because he is not tech-savvy and this is why we got this model.
However -
I've only rooted one phone in my life before, when there was only really one way of rooting. It seems I have read that problem abound with these S3 models - more specifically, IMEI may be lost, and choosing exactly which way to root, since there are varying stock kernels.
I see this thread here on the IMEI backup/injection. Am I safe to assume, that is where I start? (I have read that the Bell is just a ATT version, so will the ATT version instructions work here? I will ask in that thread but not sure).
Then - once that is done - I have to pick a way to root it that works for Bell's SIII SGH-1747M. That is where I am running into a bit of a wall. I wonder if I can get someone who has done this with this model to help me out and pick a safe way to mod it? Do I need to post more info to help decide this? I can get on his device and get whatever info is needed.
I would just ask in the IMEI and other forums but they are not available to me (either post count too low or I'm not sure).
Sincerely,
Foxdev
Click to expand...
Click to collapse
You can root without worrying about losing your IMEI.. Give this thread a look over.. Click
BAM1789 said:
You can root without worrying about losing your IMEI.. Give this thread a look over.. Click
Click to expand...
Click to collapse
Thanks, I just added it as a part of the research I did I am not worried so much about that anymore, but the other things are like....making my mind explode. All I've ever done so far is my Thunderbolt 2 years ago and that was so easy.
foxdev said:
Thanks, I just added it as a part of the research I did I am not worried so much about that anymore, but the other things are like....making my mind explode. All I've ever done so far is my Thunderbolt 2 years ago and that was so easy.
Click to expand...
Click to collapse
this is actually a pretty simple device to root too. Just pick a method and read it over and it'll be pretty hard to screw anything up
Sent from my R800i using xda app-developers app
Also make a backup of your imei just in case something goes sideways.
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
Also make a backup of your imei just in case something goes sideways.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks, going to do that for sure
Also, does anyone know with this model if Teamviewer Quicksupport just doesn't work at all? I cant get answers from Teamviewer. If it did I wouldn't need to root the stupid thing!
i don't understand why you believe you need to root to have this app supported. i attempted to use the app and it told me i needed to download an app from here. try that before you root?
edit: also i am rooted and it still did not allow me to use the app. rooting isn't your solution here
sent from my I747
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
Some months ago I made the huge mistake of applying the OTA update to my locked AT&T G S III SGH-i747 which had a stock ROM at the time.
The result could not have been worse. The phone is barely usable now. It's very slow, drains battery faster, cannot tether for free anymore, and can't seem to be able unlock. I tried with SamMobile and lost my money because their software does not work on this phone, and they don't answer to my inquiries
So, does anyone know a method for unlocking it?
Is there a way to go back to stock? Is there a way to reset it before selling it?
My phone is encrypted and I don't know if that makes any difference, but I am afraid it becomes bricked
I have searched the threads first and can't find a definitive answer to my questions
After this terrible experience I am seriously consider never buying a Samsung Android phone ever again. In fact, I am even afraid to install the AT&T OTA KitKat update given the possibility of my phone becoming even less usable
I'm assuming you're referring to Sim unlocking to use on other networks. It doesn't have a locked bootloader if that's what you mean though.
Once updated to 4.3 the only way to Sim unlock it is to get an unlock code from AT&T or buy one online. Unlock codes MUST be entered into the stock dialer.
As for the issues you mentioned, I suspect it has something to do with your encryption, though I could very well be wrong though. I can say your experience is not the norm, so something simply just went wrong along the way. It happens.
This is what I suggest you do. Backup your important data, including what's on your internal SD card.
Flash the 4.3 MJB firmware via Odin. (Firmware is in a thread in the General section.)
Reboot to recovery and factory reset. (This will wipe all apps and data including the internal sdcard)
Reboot, setup and test to see if it's improved.
Alternatively, if you have trouble with Odin, enewman17 has a thread in development for full stock revert. I'll try to find the link in a moment. If either method gives you problems, factory reset and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
---------- Post added at 12:20 AM ---------- Previous post was at 12:20 AM ----------
http://forum.xda-developers.com/showthread.php?t=2658486
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Thanks DocHoliday77. I will try to do what you are saying
This update was a well known fiasco, and had to be pulled by Samsung:
http://www.thefullsignal.com/samsung/samsung-galaxy-s-iii/16037/android-43-update-pulled-samsung
http://www.thefullsignal.com/samsung/galaxy-s3/16050/samsung-galaxy-s3-android-43-update-pushing-att
Multiple complaint threads were created in the AT&T forum, which they conveniently folded into a single one
https://forums.att.com/t5/Android/Galaxy-s3-android-update-to-4-3/m-p/3858373
Some people tried to factory reset the phone after the update with the result being the phone bricked (you can read in the above thread and on this very same website). So, I am a little worried about that. But right now the phone it's very unusable, so I guess I have little to lose by following your directions
Question: why do I need to flash the 4.3 MJB firmware via Odin if the firmware is already in my phone? Sorry if it's too obvious to you
I suggest flashing the full firmware in case something was corrupted in yours. That's all.
The only thing I know for sure about the update issue was that it primarily affected i9300 users. Pretty much any article you find about the update being pulled will be talking about that international model. I'm not aware of any us models having an update pulled after its release. I can't say much about AT&Ts though, I'm a T-Mobile user. But on T-Mobile there were very few problems at all. Even with leaked and ported builds from other carriers. I personally didn't have a single issue, but I do recall a lot of people panicking because they thought the i9300 problems were going to affect them too, which ultimately they didn't.
As for complaints on the carrier forums, you'll find similar threads related to every update for every carrier. Its an extremely small percentage compared to the overall number who took the updates with no issues.
Anyway, I hope flashing that firmware helps to solve some of the problems you've had. Make sure your important data is backed up of course and you may need to factory reset. I do acknowledge some had some unnecessary problems though, so I can't guarantee anything. Hopefully everything goes smoothly for you.
Good luck!
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Well, it affected non-international users as well, like me. Not sure what you mean by "primarily" but if it means you mostly heard about the i9300 and you don't use AT&T so you didn't hear too much about it, that does not really sound less anecdotal than my experience
And yes, I am aware the people who complain in forums does not necessarily represent the whole universe of users. However, the absence of more people complaining in such forums does not prove in any way the problems do not affect most users. One simply can't draw conclusions one way or the other.
Thanks for your help. Based on your reputation I am sure you know what you are talking about with regards to ROMs and technical details.
I am not convinced, though, about how typical or less typical are the problems I am experiencing just based on the information on this thread.
:deleted: (with apologies)
err on the side of kindness