yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
This is from the phone.

If you know how to use adb then you can use adb shell, then do the commands outlined.

---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------

Derp, my apologies. Forgot the command after the pipe.

Type "adb bugreport | find "bootloader"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Possible fix coming in tonight's CM nightly for LTE problem. We'll see.

http://review.cyanogenmod.org/#/c/60871/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VanGool:
From the phone I get

find: bootloader: No such file or directory.

error: device not found

I'll try from the pc and post again.

From PC I get

Command line: androidboot.hardware=qcom user_debug=31 zcache sec_log=0x80000@0x

8d00008 sec_dbg=0x40000@0x88d90004 sec_debug.reset_reason=0x1a2b3c00 etb_buf=0x

000@0x8fffb9c0 androidboot.debug_level=0x4f4c sec_debug.enable=0 sec_debug.enab

e_user=0 androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_debug=0 cordon=e

fcf37acecdc8734200b78ee2f9b61a sysscope=0xee000000 loglevel=4 samsung.hardware=

GH-I747 androidboot.emmc_checksum=3 androidboot.bootloader=I747UCDLK3 androidbo

t.nvdata_backup=0 androidboot.boot_recovery=0 androidboot.batt_check_recovery=0

level=0x574f4c44 sec_pvs=0 androidboot.emmc=true androidboot.serialno=811dfe3b

ndroidboot.baseband=msm

<5>[ 0.000000] Kernel command line: androidboot.hardware=qcom user_debug=31

cache sec_log=0x80000@0x88d00008 sec_dbg=0x40000@0x88d90004 sec_debug.reset_rea

on=0x1a2b3c00 etb_buf=0x4000@0x8fffb9c0 androidboot.debug_level=0x4f4c sec_debu

.enable=0 sec_debug.enable_user=0 androidboot.cp_debug_level=0x55FF sec_debug.e

able_cp_debug=0 cordon=e0fcf37acecdc8734200b78ee2f9b61a sysscope=0xee000000 log

evel=4 samsung.hardware=SGH-I747 androidboot.emmc_checksum=3 androidboot.bootlo

der=I747UCDLK3 androidboot.nvdata_backup=0 androidboot.boot_recovery=0 androidb

ot.batt_check_recovery=0 level=0x574f4c44 sec_pvs=0 androidboot.emmc=true andro

dboot.serialno=811dfe3b androidboot.baseband=msm

<3>[ 6.132275] init: Found bootloader id I747UCDLK3 setting build properties

for d2att device

[ 15.142255] init: Found bootloader id I747UCDLK3 setting build properties fo

d2att device

[ro.boot.bootloader]: [I747UCDLK3]

[ro.bootloader]: [I747UCDLK3]

C:\Program Files (x86)\Minimal ADB and Fastboot>

What im seeing now on the error on clockworkmod while trying to flash the rom is that the bootloader that I have is not on the list of the bootloader that I think the rom accepts. Which is really weird because i've been using quantum for the longest time and never had any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
PwnCakes193 is already in the discussion.

You can update your bootloader to MJ2 and your modem to MJB using this ZIP

http://invisiblek.org/sgh-i747/d2att_I747_MJ2-bootloader_MJB-modem.zip

Flash in recovery. Then you can update your rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VanGool:
Question:

Why do i need to change my bootloader to downgrade a rom?

Im trying to go from 3.54 to 3.36 not the other way around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
[MENTION=4311957]polobunny[/MENTION]

Everything up and running after recovery upgrade. Installed 3.36 rom, and it went right in. Thanks again.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Because these are the supported bootloaders by 3.36. Pwn didn't have LK3 in there.

assert(getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747UCUEMJ2" ||
getprop("ro.bootloader") == "I747UCUEMJB" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MVLUEMK5" ||
getprop("ro.bootloader") == "I747MUMUEMK3");
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Cause I think LK3 is an ICS bootloader lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
Flashed quantum kernel 3/9 this morning on slimkat weekly build3.6 and I've been on LTE for a 8hours straight. No dropped signals. 20mb/so download and 10.5md/s upload.

Using mj2 bootloader and modem. Att i747. In addition, LTE coverage in area is not that great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It doesn't *really* matter per se, just that some CM devs suspected the bootloaders might be the cause to some glitches we've saw on d2 phones before. So a line had to be drawn. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
There really is no problem with LK3. I used it for months with Kitkat ROMs. You can edit out the bootloader check and you'll be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I already looked at it... I already stated what the fix was as well, no commit will fix the LTE issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NJD316:
Exactly the same situation for me, LTE working great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xsever:
I tried Task's 4.4.2 ROM since I was getting frustrated with the CM camera issues. Am running Quantum Kernel though and have had zero camera trouble since Sunday while benefiting from all of Pwn's optimizations.

Anything we can learn from that pertaining to the camera? Seems AOKP is more stable than CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodfart:
can i just say.....NAVBAR!!...ok im done
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Any signal issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
Are you running quantum kernel on task's kitkat rom?? Is your wifi working??

I thought I read somewhere that the wifi from aokp roms will break if a aosp kernel is used. Because of different wifi drivers....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rofflayo:
Is it cool to run the 3/9 kernel on v3.36?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xsever:
Nope. But I never had any with Quantum neither. 3.50 was the last version I ran.

Am running MG2 btw.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I am. Smooth as silk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
I've been using the 3/9 kernel with the pac rom nightlies and everything is nice and smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Everyone should get their backups and everything ready for the next release. It's gonna be a pretty large release to be honest. Lots of little fixes and some new testing stuff. Expect it tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
You give me a tingling sensation man. No homo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jakers1991:
Can't wait to see whats new in the new release lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Based on d2att or d2lte? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Ditto here - 6% left on 15h of battery - 1:42 screen time - working great. Excited for it to hit the fan when the Next Big Thing™ comes to town :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
Looking forward to it!

Saw your comments on the mobile network commit that went live on 0312 regarding LTE being FUBAR. If there's anyway I can assist in trying to figure out what's going on, let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit68:
I must be one if the lucky ones I'm running 3.54 and the kernel that comes with it and I have great battery and not dropped signal LTE works great... Only thing I changed was row to deadline and using intelliractive (what ever the new one is).

Let me know if you want logs or anything.

Oh I've also dirty flashed over last few builds

And I'm on a d2can (rogers 747m) running latest modem and boot loader that came with 4.3 if that helps any
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
That commit was merged a long time ago, not yesterday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Having a problem with the screen shutting off randomly. I think it may have occurred after the dlte fiasco, but even installing a datt version doesnt fix it. Hopefully it can be fixed in next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
+1, very excited. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Help needed.

I was switching between kitkat builds last 6 months or so. Other issues but no signal drop. I was in India for 3 weeks. Wanted stable build. Flashed CM 10.2 stable. No issues while in India. Since I came back on AT&T signal drops frequently ( on same CM build).

Then thought it could be issue with switching Sim. So wiped everything and flashed CM latest kitkat nightly. Still same issue.

And surprisingly. I am seeing same issue being discussed in several forums.

What is this new signal drop issue. I am seeing on jellybean as well as kitkat.

Why is it happening all of sudden. AT&T issue ?

What can I do to prevent.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
99% of the time Pwn already merges the commits even before they are published and go live.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's no signal drops on Jellybean, you have a different issue or 2 issues combined.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Apparently, the new d2lte breaks something deep in the internals that even a restore of a previous version won't help. The only thing that has been found to rectify this so far is a complete restock, then a clean flash (probably better to use d2att instead of d2lte). Plenty of people in this thread have restocked, then flashed Quantum 3.36 for ROM and QuantumKernel 3.9 for the Kernel, and are loving it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
So. There is new signal drop issue with kitkat in the last 3 weeks ?. If so. If I flash a kitkat build Prior to that will it be gone ? Also you are saying if I flash any 4.3.1 or prior this issue doesn't exist ?

Ant idea when/how it started with kitkat. And when can it be fixed

Thanks

---------- Post added at 06:25 AM ---------- Previous post was at 06:21 AM ----------

Dang. Then this is what might have happened. Using international sim might have caused initial signal drop issue for me even on jellybean. Then I picked d2lte build. And I an seeing same issue.

But I am on MJB bootloader. What are my options of going stock and fixing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It started with the d2lte merge from CM. Previous builds are 101% unaffected, but for some reason those early d2lte builds broke something deeper than just the rom and the "easiest" way to recover from that glitch is to flash back to stock ROM and then flash to CM. Current builds seem unaffected though for most if not all people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
So is Odin only way or just picking some stock ROM and flashing thru recovery and getting back to non d2lte also OK ?

Reason for skiing this. I am on MJB and can't use Odin (possible hard brick)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You're confused, just as everybody else it seems. You just can't flash any package containing a previous bootloader. Doesn't matter whether it's via ODIN, Kies or CWM/TWRP. If it contains a bootloader older than MJB, you'll brick your device.

But back to your question, you can just pick a stock ROM. Flash it, let it boot, test LTE (should work yay), then flash a non d2lte build (or latest d2lte builds, which don't seem to be affected anymore) and there you go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Can you please give one such stock rom link.

In fact I am on latest cm build last nightly. Still I have signal issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Since he is on MJB, I would suggest he ODIN the stock 4.3 that Pwn himself flashed a few pages back, and then continue from there.

DO NOT FLASH ANYTHING PRIOR TO MJB!!! YOU WILL BRICK!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
New kernel is up. ROM borked so I had to rebuild. Going to class though so it won't be until later.

New kernel is nice :)

For those wondering, here are some of the picks from CM that will be in the next build.

58164 60900 60146 60817 60816 59707 60734 60747 60838 60835 60839 60829 60912 60735 60844 60845 60846 60847 60848 60849 60850 60851 60852 60853 60854 60855 60856 60975 60748 60958 60959 60960 60961 61011
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I think I won the lottery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Looking forward to the gps tile fix, I use it alot and that drives me crazy that it only toggles accuracy instead of on/off.

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's already in 3.54. That's the only thing it does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] winga45:
[MENTION=1461885]pwncakes[/MENTION] whats the changelog for new kernel whatts change since last one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Linux 3.4.83 and tweaked intelliactive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Everyone should start doing their restore processes soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
You're a tease, Pwn. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Not anymore :) Remember everyone, LTE WILL WORK as long as you just go back to some sort of stock and then back.

Old users should feel free to upgrade to this one, network stuff is finally all good and a LOT of stuff is changed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'm so excited! My phone's been a hunk of crap lately corrupting on me because it's as if the power button is perpetually held down...!!!!

So no matter what my experience is tarnished. Just happy for another fresh start! I'm gonna go read the past few pages before I ask what it's gonna have, lol!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
This may be of no value to you, and you may have already BTDT (been there done that)....but, I had a phone acting like that at one time, and it turned out to be my charging port (micro USB). It was evidently shorting out. One time, after removing the battery, I scrubbed the port out with a small brush and alcohol (isopropyl not something from the fridge ;) ) and it helped a lot! Make sure the port is good and dry before putting battery back in (I blew it out with canned air).

Again, this may not be at all related, but just thought I'd throw it out there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
This is only for d2lte correct? I don't see it in the d2att folder.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
Yea I'm not sure what you mean by "LTE will work". Are you saying that we would have to do some sort of stock flash and then flash quantum over it in order to actually get LTE working, or just like, an LTE toggle? I didn't think that I had been missing LTE since I've been dirty flashing the last Quantum builds but I haven't had much time with classes lately to pay that much close attention... ._.

EDIT: Went back a few more pages and it looks like it is some sort of LTE problem people were having then...

Welp I haven't had any issues so far so I'll just cross my fingers and hope for the best :D

I'll make a nandroid, and then dirty flash it. I'll post if anything goes catastrophically wrong :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Can this be dirty flashed over 3.54?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
It might be the power button. This may sound strange, but try whacking the power button against the edge of a table a few times and then see if the problem stops. I was having a similar problem and found a post (not sure where, it was last fall) that mentioned doing this. I thought oh well it isn't working now so what can it hurt. Surprisingly it did work. I have only had a problem once since then and whacked the power button again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Is there a stock ROM that you recommend for Canadian users to flash back to? I formatted my SD card by accident a while back a lost my backup :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
For those not taking the advice and flashing stock and then flashing the ROM, do not post any LTE issues here. They have already been covered.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Sorry, I don't see it. It keeps toggling between battery saving to high accuracy only. To turn gps off, I have to physically go into location and turn it off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
But, you posted recently that you need to flash back to stock in order to get rid of lte issues O_o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Harshpatil:
I am using this rom in India where LTE is a distant dream(seldom get good 3G coverage) so I have never had any issues with signal drops for LTE like other users had, so do I need to go back to stock before flashing this new build? I mean will it provide any benefits other than getting LTE signal? I might just clean flash it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
I think that's what he means by "already been covered" ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
So, there's this LTE issue I've heard about... (ducks and runs for cover) ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dynas7y:
I had this same issue and the same solution worked for me! Haven't had the issue since
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Don't be fooled by the changelog, this is a MAJOR update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
And if this doesn't work... Just get a bigger hammer! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
can't wait
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
just wait about 10 minutes.... and ill give you the link. its uploading now.. (:

EDIT: i hate how google drive always takes long on large files. almost done though.

---------- Post added at 02:47 AM ---------- Previous post was at 02:19 AM ----------

Mirror is up guys. (; and also for you man.. [MENTION=4602487]ps3kev[/MENTION],

https://docs.google.com/file/d/0Bw_421-rC97lZ21XQm9VZk9fd0E/edit?usp=sharing

:highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Sweet, thanks for the 1.11 update - is this for the Camera app or Focal?

Also, I'm not even sure if I should be running the dkp kernel with this, how is the kernel included in this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
camera app.

and also dkp kernel i great. but also great as well. personally i like dkp. i get the best battery life. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Anyone else having to flash gapps on every update?

Sent from my sexy Android 4.3 thanks PWNCAKES
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Devhux:
This is usually the case for AOSP and CM-based roms as Google doesn't allow GApps to be bundled with them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
yep, normal as far as I know. I also have to flash Super SU update as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Ok cool thanks. There for a couple updates some reason I didn't have to until it switched to quantum

Sent from my sexy Android 4.3 thanks PWNCAKES
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
You definitely shouldn't have to do this for CM-based dirty flashes. When you install gapps it'll make a file in addon.d and so it'll keep the Google APKs across flashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I did for 1.10 but I had also lost other apps. About to install 11 so we'll see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
I had to on all quantum based flashes so far

Sent from my sexy Android 4.3 thanks PWNCAKES
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah I had to for .11 also. Not sure why they are being lost.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I do it everytime as a habit. Got tired of having to re-reboot into recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trippmcnealy:
I modified this to run on my T-Mobile S3 and it is running great, thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theyurtingyeti:
I see a lot about the DKP kernel and it's got me interested enough to give it a try. However, I can't seem to find it anywhere (by that name)... is there a better name to search for it? I've come across similar hits on the Bionic Sheep kernel... are they the same?

Thanks for any help/links you provide.

And this ROM is really nice. I'm still on the 8.14.2 version, but Quantum is getting some crazy love. I just wish someone was able to replicate Samsung's BT drivers... 4.3 doesn't want to play nice with my BLE device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trippmcnealy:
See the link in the post below.

My mistake.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
http://xdaforums.com/showthread.php?t=2226889 this is the at&t thread, the one linked above is T-Mo. No differences in the kernel itself but just for support / questions go to this one or T-Mo one depending on your device. And no they're not the same
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxSTEROIDxX:
Doesnt work. I dont know why either. When I switched back to my other rom it worked fine. Im gonna download this update and try it and see what happens. I know it was stated earlier in this thread that there were issues with some but not all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Do we have a fast charge option? Seems like it's taking a very long time to get a charge on last few builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rs3freak:
Guy at the cell phone repair store tried to tell me that my sequence of reboots was software issues...umm no buddy I clearly showed u my power button not acting properly. Smh.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
And for anyone like me that was trying to figure out WHAT stock to flash... :D

Won't have time until maybe the weekend though, so I guess I might just hold out on updating at all with such a grim warning of what may occur without a stock flash lol...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
If you already have LTE issue it won't matter lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Anxiously backing up my download, pictures, and alarms folder because I have no idea if flashing back to stock wipes /storage or not... I'd assume it doesn't, but I don't know if it's linked to /data/media or not. Probably just me being stupid to be honest xP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
If I don't have it (or at least don't think I have it), am I likely to contract it upon flashing the update? That's what I've been the most unclear about with recent posts lol... wasn't sure if it was something that happened to some people at some build along the way and has stuck, or just something that has been happening to people with recent builds in general.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
So, if I don't have any lte issues, can I just clean flash 3.6?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Harshpatil:
:eek: confused reading these last some pages. I am going for a clean flash if anything bad comes up will flash back to stock and try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Same thing happened to two of my friends, one with an S3 and one with an S4, a few weeks ago. If hitting the power button doesn't fix the problem you'll have to get a new one soldered on. It costs $30-50 at most shops.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
If you experience LTE issues- Flash Stock and then 3.6

OR if you have the LTE problem and you want to just deal with the current issues until later, upgrade to 3.6 and then do stock later.

If you aren't experiencing any issues then feel free to update to 3.6 freely.