yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] peterkef:
Hi all,

I have a question. I just received my T999L and I flashed wicked 10.

All is working fine after installing the right kernel and I have the latest modem.

Problem is that when I put it on LTE automatic in settings I lose data connectivity.

When I put it on only WCDMA only I have perfect connection and data but no LTE.

If I moniter in about device I see that I am connected to LTE for a short time ad then the connection gets lost but I never re connect.

The LTE srecive state is ok just the mobile network state is disconnected.

Anyone has a solution?

Thank you
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
What "latest modem" are you running? MB7?
[T-Mobile, Samsung Galaxy SIII] peterkef:
Yes, mb7 but it tried also the other one.

Thank you
[T-Mobile, Samsung Galaxy SIII] O0cynix0o:
Wanted to drop a note. CM 10.2 flashes fine with no mods to the updater script.
[T-Mobile, Samsung Galaxy SIII] Joethelegend:
WORKED
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Really, that is weird. I am running CM10.2 with MB7 and haven't seen these issues, but I also don't live where there is LTE service :(

Maybe the ROM that you are running has some build.prop settings changed that is causing it. Try a vanilla AOSP/CM ROM or [MENTION=4081205]DocHoliday77[/MENTION] PureStock w/ Root ROM.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
And when you monitored the connection were you in the process of downloading anything?

If no one else is having the same issues, it may be network related too. Does it do the same thing in a different part of town? If it works fine elsewhere, call T-Mobile.

Otherwise all I can think of is try starting over from scratch.

You may consider trying another kernel too. Which one are you using now?
[T-Mobile, Samsung Galaxy SIII] henry8668:
trying to following Root66 way/

"You should now see a COM# port listed toward the top-left of Odin (under ID:COM)"

in this step, I don't find anything under ID:COM. I did see 0:[COM3] above ID:COM. is this something wrong? how can I fix this?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Hey guys! I've got the official root66 firmware ready to go for a test flash! The difference? My original release was based on a dump of a running stock system. The only thing included is the System partition.

This new one is built from the official firmware release from Samsung, built by mrRobinson, the original root66 guy! It is the full firmware, meaning it includes kernel, modem, etc.

Be aware, this is untested! As I mention with each release I do for this phone, I cannot test as I don't have the T999L. If I try to flash to my T999, it'll brick for sure!

I wouldn't worry much at all about it causing a problem though. He has built root66 firmware for every release for the T999, plus he's done this for the other US variants of the S3, S4, and Note2. I've never heard of one not working as expected.

If you decide to test, please post here that you are about to do so. Then let us know the result once complete. This way we don't get several people testing the same thing at once. Only need one person at a time to risk a test, no matter how small the risk may be!

So here is your official root66 UVAMB7 firmware for the T999L, courtesy of mrRobinson, and delivered by yours truly! ;)

http://www.androidfilehost.com/?fid=23125694133306213
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
What version of Odin are you using? Sounds like it's showing the info you want, just in an unexpected location. If Odin can't see it, it won't let you flash it anyway.
[T-Mobile, Samsung Galaxy SIII] peterkef:
No, I'm not downloading at that time. I live in Manhattan and I tried it in different locations. I tried different kernels but the same result. I use UVAMB7 as kernel now but I tried also koontez.

I see the LTE service active, my phone tries to connect but never does. When I switch to WCDMA only it connect fine but no LTE.

Any recommendations? If not I start from scratch.

Thank you.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Start a download, something large, like a Rom, then go and check in Settings > About Device > Status > Network Type. I know for certain that on the T999, it does this by design, but with HSPA. Basically, it will drop to a 2G or 3G connection while idle, then once you start transferring any data, such as checking email, or starting a download, it will ramp up to the max available. It does this both to save battery on the device, and conserve bandwidth across the network.

I've been told by one it does the same on the T999L, while another claimed it did not. But if it is dropping down while idle, that would explain it and if you check while a download is in progress, you should see it report LTE.

If this is not the case, and even while downloading it does not get LTE, the best thing you can do, is Odin flash back to stock (rooted is ok), and test it again. If you are still having problems, I believe it would be a hardware issue and you need to do a Warranty Exchange. Or if within the time period, use the buyers remorse return (not sure if its actually called that!), instead. This way hopefully you would get a brand new device in exchange. If you do warranty, even if its only 2 days old, you will get a refurb in return.

Hope it doesn't come to that though!

Good Luck!
[T-Mobile, Samsung Galaxy SIII] peterkef:
Thank you for your quick reply! I'll try your advise and let you know.
[T-Mobile, Samsung Galaxy SIII] henry8668:
I am using Odin3 v3.07.exe. and followed Root66 way to flash file MB7system.tar.md5 into my phone (T999L). after flash is done, the phone rebooted. I didn't find any superUser or superSu app in the phone, so I am not sure if I flashed corrected or not?

after flash, I noticed the top left shows "RESET" then show "PASS"

here is the msg in the bottom left of odin

<ID:0/005> Added!!

<ID:0/005> Removed!!

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MB7system.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> system.img.ext4

<ID:0/003> NAND Write Start!!

<ID:0/003> RQT_CLOSE !!

<ID:0/003> RES OK !!

<ID:0/003> Removed!!

<ID:0/005> Removed!!

<ID:0/003> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

when I tried to volume up+home+power, the phone goes to android system recovery menu, no the cwm recovery menu.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
This is just rooting your device. You will now need to install ROM mgr for CWM or Goo mgr for TWRP, then your will be able to install a custom recovery.
[T-Mobile, Samsung Galaxy SIII] henry8668:
DJ, I am very new to root/room etc, could you point me to a guide to install either one? which one do most people install?

Thanks.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I don't really know of any since you've already done the hard part. I use TWRP and recommend it. To install it get Goo manager for the Play Store the choose "Install OpenRecovery script" from the menu. It will download and install then recovery automatically. Then reboot into recovery to enjoy/profit.

https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en
[T-Mobile, Samsung Galaxy SIII] henry8668:
tried Goo manager to install OpenRecovery script and got "no recovery were found for your device", looks some steps missing?

from docHoliday77's post #4, "I suggest you use either CWM or TWRP for the T999 (d2tmo).", by following the link in docHoliday's signature, there are many files... which one should I download? and how to flash that file into my phone?
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I forgot about that, the Goo Manager app is looking for d2tmo but is seeing d2ltetmo (T999L). Here is the long manual way to install.

Recovery install process:

1. Download and install USB Drivers from here: Thanks to [MENTION=4081205]DocHoliday77[/MENTION] for hosting

http://www.androidfilehost.com/?a=show&w=files&flid=1368

2. Download and extract ODIN 3.07 from here: Thanks to [MENTION=4081205]DocHoliday77[/MENTION] for hosting

http://www.androidfilehost.com/?a=show&w=files&flid=1369

3. Download TWRP 2.4.4.0 or 2.5.0.0 recovery image (.tar file) from here: Thanks to [MENTION=4081205]DocHoliday77[/MENTION] for hosting

http://www.androidfilehost.com/?a=show&w=files&flid=5155

4. Save all open files and reboot computer

5. Boot phone into Download mode (also called ODIN mode) by shutting down the phone and holding Vol Down & Home then pressing Power until it vibrates, still holding Vol Down & Home buttons, until the "Yellow Triangle" screen shows up.

6. Plug phone into computer and open ODIN 3.07 and make sure that only "Auto Reboot" and "F. Reset Time" are checked.

7. Click on the "PDA" button (right side about half-way down), browse for TWRP .tar file, click "Open" button.

8. Click "Start" button and watch to "Reset" or "Fail" to show in the 1st square (upper left side)

9. Phone will reboot, then power down and boot into recovery by shutting down the phone and holding Vol Up & Home then pressing Power until it vibrates, still holding Vol Up & Home buttons, until the blue "TeamWin" screen shows up.

10. Enjoy your Team Win Recovery Project custom recovery on your Samsung Galaxy S III 4G LTE SGH-T999L (d2ltetmo)

11. Profit!!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
And if you turn out to not be rooted from before, click on SU in my Sig and download whichever you prefer. I prefer SuperSU, but either is fine. Then flash the zip in your new recovery.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I also prefer SuperSU, but any Superuser app will work for root access permissions.
[T-Mobile, Samsung Galaxy SIII] henry8668:
Followed this and flashed TWRP 2.5.0.0 tar file into my phone

got the superSu and using twrp recovery to flash into my phone. after reboot, I could not find the supersu app in app drawer.

tried to run titianium backup, it stucks on start, displaying "asking for root rights..."

Did I root my phone correct? how can I verify it is rooted?

thanks very much for all the help!
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
TGlad to hear that you got TWRP installed and then flashed SuperSU, but did you open SuperSU and then reboot?
[T-Mobile, Samsung Galaxy SIII] henry8668:
I actually didn't find the supersu app in app drawer after flash it via TWRP. later I found the supersu.apk in /system/app, installed it and now I have supersu. not sure if I am doing correctly but now I have root!

thanks
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
As long as it is working that is all that matters.

It probably was installed there when you flashed it, but it wasn't added to the App drawer. A reboot probably would have fixed that.
[T-Mobile, Samsung Galaxy SIII] alexjustdoit:
Made a new thread in the Help section, but thought maybe I should post here, being a specific T999L thread.

Hi all, thoroughly read the guides in the T999L FAQ guide, rooted and installed CWM successfully (as far as I can see).

Now the hard part. Could not install Pacman Rom, even after fixing asserts. I heard there were two types of asserts. I deleted the ones at the top of the update-script, that look at the device number. Previously I had error 7, now I don't get an error number. Says "Installation aborted". Looking at the log, it says "Can't partition non-vfat: datamedia" and "Cant format unknown volume: /emmx"

Tried flashing CM10 for d2ltetmo and it was able to flash, except no signal/connection. Baseband displays T999LUVMB7 which is the correct one isn't it?

Preferably, I would like to flash Pacman Rom, but as I cannot get it to work as hard as I've searched and tinkered, I would settle for just any working ROM right now. I've been without a phone for a few days now before receiving this one today, and I really need to get it to work.\

Kinda wish my T999 wasn't replaced with T999L... all this seems too complicated than what I want to get into right now, with modems and bootloaders (never had to touch that on my T999) etc. I'm just confusing myself and at this point I've decided to ask the board instead of risking damaging anything.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
The d2tmo CM10.1/10.2 nightly builds work just fine for T999L on MB7 baseband, because this is what I am running. Did you do a complete wipe (system/dalvik/cache) before flashing CM10 or PACMan? I ask because if you went from 4.1.2 to 4.2.2/4.3 on a dirty flash you WILL have problems. I would say backup everything, then wipe everything and reflash ROM/GApps/SuperSU, then once all that is done let it reboot and sit for a couple of minutes (5-10 or more) to let the scripts finish. After all that reboot the phone again and (once everything loads) you should be good to go.
[T-Mobile, Samsung Galaxy SIII] henry8668:
post #3 provides ways to revert to stock and unroot.

If I rooted the phone, installed TWRP, but didn't install any of custom rom. Now if I want to un-root(for example, wants to have warranty claim), what steps I need to follow?
[T-Mobile, Samsung Galaxy SIII] alexjustdoit:
Yup, formatted everything except external sd, through the CWM mount and storage menu, then I did factory reset and cache.

Just tried it all again, PAC still wouldn't flash at all.

CM Flashed OK again, still no signal. The latest nightly however, did not. No error, no installation aborted, it just goes to "opening" and then black screen, and back to recovery main menu. Tried wiping everything again, same result.

Might this have anything to do with the "bootloader" as I saw mentioned in some other post? Any other ideas why this might not be working?

On a side note, must I flash SuperSU? In the past I never needed to, it was always provided with root or the ROM
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Maybe it is not formatting them correctly/completely, try TWRP instead

Redownload the ROM and GApps and try again. Also, check that your IMEI is still there. If it is not, there is your problem.

The 'assert' refers to a check for what bootloader is on the device, the MB7 one is there or you would have gotten the "Error: 7" message.

CM does not include it, they have their own (made by Koush), but in order to use SuperSU you will need to flash it or install from Play store and then choose the "System App" setting.
[T-Mobile, Samsung Galaxy SIII] alexjustdoit:
If it were not formatting correctly, then wouldn't CM run into the same problem that I am having with PAC? I will try switching to TWRP, downloading now.

IMEI is ok, just checked, thankfully that is not it.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You installed a custom recovery so you're no longer 100% stock. Just Odin the root66 firmware, triangle away and then choose full unroot from the SuoerSU app.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Man! Problems seem to have gotten quite odd lately! And not just for the T999L!

For no signal on CM, try a different kernel, like ktoonsez. Not sure on Pac man problem. Make sure /system is mounted before flashing. Try a different recovery also. And attach your recovery.log for us to look at.

Thanks DJ for all your help! I for one, certainly do appreciate it!
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Yes and no, there are scripts that run when the ROM flashes that would stop the flash or allow it to complete and the boot.

Good to hear, not sure where to go from here about that issue.
[T-Mobile, Samsung Galaxy SIII] henry8668:
need help.....

I tried to revert back to stock using first method in post #3

* use triangle away to reset counter

* reboot into TWRP recovery

* flash T999L_UVAMB7_PureStockRooted.zip

* flash 999L_UVAMB7_PureStock_Kernel+Modules.zip

* flash TMOGalaxyS3LTE_UVAMB7_Recovery.zip

* reboot recovery, factory reset, then reboot.

however, the reboot was stuck in the start screen that showing "T..Mobile. 4G LET".... and battery is hot.

pull battery and reoot, still stuck there...

what I should do now? help!

thanks!

edit:

after factory reset again in the recovery, now I can reboot. However two issues:

1) I did triangle away to reset, but in download mode, still see triangle. and show counts=1.

2) I was following the first method of 'revert to stock'. after factory reset, apps are wiped out, how can I have last change of run triangle away again and do superSu to unroot??
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Triangle away needs to be run after everything is back to stock. If you reboot and have a custom kernel or recovery still installed it'll trip the counter again.

I'll.update the instructions, maybe tonight to make that more clear. But that's why I point out that before uprooting it's your last chance to reset it.

When you factory reset it wipes your data partition. If you do so in CWM or TWRP, it'll preserve your internal sdcard, using stock recovery it'll wipe that too. If you need to rerun triangle away after the reset, just reinstall it.

Like I said, I'll update the instructions and try to make it easier to understand. Sorry for the confusion.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Anyone???
[T-Mobile, Samsung Galaxy SIII] henry8668:
Thanks DocHoliday77!

Last night, I also manually copied superSu and did the unroot. So I think currently I am unrooted but with counter=1.

Once you update the instructions, I will root it again and then try to revert back to stock. (I had some issue on the phone and need to send back for warranty)

thanks!!
[T-Mobile, Samsung Galaxy SIII] RadioActive1:
Tried flashing this version of CM on my T999L and I still receive a Status 7 error after doing a full reset and clearing all cache.:confused:

Opened the updater-script with the hopes of editing it, but not sure how much to cut (i.e. where the end of the ACCEPT section is).
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
What version of CM? The nightly builds have made the MB7 boot loader in the updater-script.
[T-Mobile, Samsung Galaxy SIII] RadioActive1:
Thanks for the reply.

I used the 10.1.2 version that DOC Holiday made available for download at the top of this thread. He edited the ACCEPTS in the script file. In doing some more reading I got the impression that I would need to be running the stock recovery for it to work with the molded ACCEPTS. I'm running clockwork recovery.

In any case, hadn't tried flashing a nightly, so the above may be a moot point. I'll try flashing a nightly.

Thanks!
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I've been running nightly build for a while with minimal trouble, but if you want 4.2.2 "stable" builds, try the 10.1.3RC from here http://get.cm/?device=d2tmo, it already has the Assert and should flash without issue.
[T-Mobile, Samsung Galaxy SIII] RadioActive1:
Sparky - what device are you running that build on? Is it a T-999L or just a T-999?

I tried flashing the nightly and got the same Status 7 Error, and again with the RC version.

IMHO the problem is in the ASSERTs that are in the script - example. When I tried to flash the Release Candidate ROM, I get the message "assert failed: getprop ("ro.product.device") == "

d2tmo

" and then the same thing is repeated.

My phone is an SGH-T999L, not a standard T999, the T-999L has the LTE feature. So, I think the issue may be (and I'm saying this as someone with a solid technical background but who is relatively new to Android.....which is to say I'm guessing) that an additional ASSERT is needed for something like "d2ltetmo". Or perhaps the d2tmo in the script needs to be changed to "d2ltetmo" - just a hunch, I could be way off in the weeds.

I'm not comfortable going in and editing the script file if I don't really know what I'm editing and what the results of making an error might be.

Seems to me that while the nightlies have included the bootloader but there still seems to be an issue with the ASSERT statement.

The red flag for me is in the CyanoGenMod Galaxy S3 support matrix where it has the following table entry:

Name Model Officially Supported Comments

Samsung Galaxy S III LTE (T-Mobile) SGH-T999L	???	Please refer to Install CM for d2tmo.

Suggestions?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Easiest thing would be to flash the d2tmo recovery. The vast majority of flashables will not work with it, if they use asserts, which many of our roms do. The d2tmo one will work perfectly fine and will be compatible with everything on our forum. I need to update my repo, but you can find the almost most recent versions by the link.in my Sig.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sorry I didn't update last night like I promised. This is my first time back on since that post though. I'll try to get it as early today as I can. Maybe early afternoon.

Sorry about that!
[T-Mobile, Samsung Galaxy SIII] RadioActive1:
Ah, OK thought I had read that flashing the stock recovery might solve this issue. I'm assuming that is what you mean when you say to flash d2dmo - under "stock" when I click on your signature?

And one last question, the recovery is a tar.md5 file - not really familiar with that format - can I flash it directly by dropping it in the root of my SD?

Thanks much for the help.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It has to be CWM or TWRP. You can't flash anything but OTA's from stock recovery.

.tar.md5 is for use in Odin or Mobile Odin only. The .md5 is really just a tag telling Odin that the md5sum is present for it to check. It's a failsafe so Odin won't flash it if the file has been corrupted.

If you want to flash from recovery, download the zip file instead.
[T-Mobile, Samsung Galaxy SIII] henry8668:
Take your time DocHoliday77! Appreciate all of the work you've done for us!
[T-Mobile, Samsung Galaxy SIII] RadioActive1:
Doc and Sparky, again thanks.

To clarify, I am running a T-Mobile T999LUVAMB7 (same as u Sparky) and CWM 5.5.0.4

Guess I was misunderstanding Docs' suggestion to flash a d2tmo recovery - now I get it. Thought the CWM I have installed was d2tmo, but based on comments here, may just start fresh and get it right.

So, gonna take a step back and make sure I have the right recovery, ROM & gapps per your script and try it again......... but I'm learning :o
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
The recoveries for d2tmo will work fine along with most ROMs for T999. My vote would be to use TWRP instead. Let us know how it goes.
[T-Mobile, Samsung Galaxy SIII] Suminigashi:
Camera on non-touchwiz roms?

Hey guys. Was wondering if anyone running a non-touchwiz rom (Cyanogen, LiquidSmooth, Pac-man, etc...) could give some insight on how to get the camera working on these roms. The only custom roms I can seem to get the camera working on are Touchwiz based and in order to get it to work on those I have to flash the rom and then flash the UVAMB7+ stock kernel from http://xdaforums.com/showthread.php?t=2308514. Some people have mentioned copying the cameradata folder from a stock setup over, but this has had no effect and I always receive the error "Could not connect to camera". Would love to hear from someone on something like cyanogen about this.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Camera works fine on CM10.2 nightly build.
[T-Mobile, Samsung Galaxy SIII] Suminigashi:
I'll try doing a fresh install again but I believe I had no luck with that one as well. Will post back shortly.
[T-Mobile, Samsung Galaxy SIII] Suminigashi:
Camera still not functioning

Just did a complete fresh install of the latest 10.2 nightly and I am still encountering the camera error regardless of what camera app I use. Attached is a screenshot of the error message. Gonna try and post a dmesg dump shortly.

* Forgot to mention I used the instructions you posted in a previous post just to be on the safe side.
[T-Mobile, Samsung Galaxy SIII] Suminigashi:
Dmesg dump

Here is a Dmesg dump that might be useful.