yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Dalvik one seems a bit low. Usually score around 5300 with Dalvik, 5600 with ART. Quadrant is crap though, multiple runs can yield you quite different results. Usually do 3 runs and take the 3rd run score.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
I wanted to play it safe. Also, just in case I need to go back to stock directly to fix my warranty, I wanted to have everything i needed beforehand

Sent from my Quantum-powered SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
hey guys,

planning to go back to stock and then to quantum 3.6

i've spent a couple hours reading and just wanted to run through my steps just to make sure. i'm on i747m rogers, LK4 bootloader, MK5 modem/baseband).

1) Odin 3.09 to stock rom (LK4) (i downloaded a rooted version of stock rom from: http://xdaforums.com/showthread.php?t=1739426

2a) boot, open maps to get GPS lock (per pwncakes)

2b) boot into stock recovery and wipe data/factory reset

3) reboot, download ROM manager, flash CWM

4) reboot into recovery, nandroid

5) wipe system, cache, dalvik cache, data, flash rom/gapps, wipe cache and dalvik again

am i missing anything? thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Sounds about right. That's what I did last night except the maps step.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brobinson2102:
Factory reset!!! Derp. Okay, nothing to see here.

Back to the S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
Guys I messed up. I went to do a "full" wipe and format internal storage, now i cant get into recovery. It only gets to the twrp screen then bootloops. I do have backups etc on my ext sd card. Any ideas how to get recovery back? I know this might be the wrong thread, but im a die hard quantium user, and you guys are pretty smart and helpful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Just a theory. Download the Odin version of twrp, the tar file. Boot into download mode, power+home+vol down and reflash twrp. You might have to Odin to stock, if you don't have the mjb bootloader, to rebuild the file system. I'm not 100% sure. This happened on my Captivate, and that's what I did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Or install via fastboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
thanks for the reply. I am on the mjb. Have to use my work computer, as i have Mint on my home computer and not familiar with heimdall.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
3.6 is working flawless for me, don't care about LTE.

Quantum = Speed + Best Battery life.

Quantum provides the best battery life with unbelievable speed. This ROM had made my S3 = S5

Thanks pwn for the awesome work..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheShamsMan:
Hey guys, sorry if this has been asked, but anyone else getting crazy network drops? Not just LTE, but full complete drops. It happens to me once every 5 minutes. It's been like this going back at least last 2 releases. Wifi isn't affected. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
not myself, but this issue has been discussed at some length for the past few weeks at least (complete signal drops and/or LTE connection problems).

only fix is to go back to stock and then flash quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheShamsMan:
Hey! Thanks for the reply. Must have been a while back, because I wasn't able to find any information on it latest 10 pages or so.

Do you know if it's a modem issue? What was the reason behind the drop? Would it fix if I just flash a different ROM? I did a clean flash on 3.6 and figured it would fix the issue, not sure how flashing stock would be different?

Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
from what i gather, problem occurred during the switch from d2att ROMs to d2lte ones. the last d2att was quantum 3.36 and after that people started having issues. I don't think flashing a different ROM or flashing a previous d2att will fix the issue. many have flashed back to stock and say that's the only way to resolve it. apparently flashing back to stock will reset something deep in the phone (not sure exactly what).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheShamsMan:
Thanks man. I'll try it out!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
so which all ROMS got affected with this. I had this issue with CM latest nightly. i went back to stock and flashed Task kitkat build. no issue.

I am planning to go to slim kat. any idea, whether this signal drop is only with those roms using d2lte instead of d2att ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
http://xdaforums.com/showpost.php?p=51034388&postcount=12811 - 8 pages ago :p

and

http://xdaforums.com/showpost.php?p=51051450&postcount=12870 - The reason it happened (he's a CyanogenMod device maintainer for us)

With all d2lte ROMs, but restoring to stock will fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
Now I was able to get into download mode and reflash recovery via odin, but im still bootlooping. I have this rom and my backups on my ext if i could just get into it:( I'm on the dreaded MJB bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I think that you might have actually erased a whole partition. A full wipe from internal storage is what I do a few times every week!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
So, Am I out of luck?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Don't know. You can't get into recovery at all? Flash stock and see if that restores everything, then try to get into stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
If there's no Odin file of MJB available have someone create you one of an earlier version with the bootloader removed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
People keep saying you must Odin to stock. Just slash any touch jizz based room and gives LTE. At least from my experiences.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You guys know you can flash any TW based rom, right? Not absolutely necessary stock ODIN rom or anything, just stock based. Could be Hyperdrive, S3Rx, Wicked Sensations, StockMod, Grievous, Dandroid or any other really.

Or if you have a CWM/TWRP backup, this works too. Which you all should have anyway. :p

But you know, enough posting in Quantum thread about that. There's more than enough information about the forum about this LTE issue right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] |flyte|:
Surprisingly enough, I'm still running Quantum 3.45 from February 21. My LTE works just fine, but the LTE issue was introduced in a CM nightly build from early March.

Would I get infected with this LTE issue by flashing the latest, or because i didn't flash the suspected build from early March that I should safe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
Oh had no idea. This seems like much less effort. Will have to research. Ideally, I'd like to use can recovery and flash ev Ruth and not need Odin.

---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------

Think everything after 3.36 had the lte issue as pwn mentioned above. Maybe you're just one of the lucky ones!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
I said a couple pages ago and didn't see you reply - can you get to fastboot? What happens when you try to go to download mode instead of recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
Thanks for the help. I just flashed an earlier version of twrp and it worked! Dodged a bullet. Thanks again to all:cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
Edit: didn't realise it was answered
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yeah you should be fine. It started at builds that you are on so you may be safe.

That's bizarre I wonder what even happened?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
Don't know, that's the first time I've formatted my internal on my s3. Did so many times on my s2, but that's a whole different deal. I'll hold my breath next time. Quantum up and running smooth... Thanks guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
sorry for the dumb question, but I haven't flashed a custom kernel in ages

How do I go about it on CWM? is not explained in the op
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
There are no dumb questions, only dumb people. ;) Seriously, you flash a custom kernel from CWM the exact same way you flash a custom ROM from CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I usually do clean flashes with roms, pretty sure you don't need to wipe data and format system for a kernel. Also I remember there was a fixing permission step with kernels, but don't remember if it was at the beginning or the end :confused:

do you mind spell it out for me in steps, thanks for your answer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Saaahweet. :good: we've all dodged bullets before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Interestingly enough I haven't had the signal loss issues that have been arising since forever.. Until the latest build. If I can recall I think I know the solution...lol. I'm so lazy I was hoping my phone was immune. Smh. Also random soft reboots have come back to haunt me. I did a clean install from the previous build. Other than that all is running buttery smooth and battery life is still awesome even given the soft reboots and random signal loss. Thanks a lot for the bleeding edge updates! I know they can come at a cost but it's worth it! I love my phone and rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Flash kernel. Profit. No wipe anything, no fixing permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
come on man are you trying to make my phone explode like a fragmentation grenade? :D

I remember there were a few steps when flashing from CWM, anybody in this thread kind enough to cough up the steps?

looking in google take me to odin stuff wtf frustrating

any good samaritan?

---------- Post added at 01:28 AM ---------- Previous post was at 01:15 AM ----------
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aew0314:
When I use root checker and look at my bootloader it says I747MVLDMF1, I don't see any reference to being able to downgrade from this bootloader to stock. Anyone familiar with the I747M bootloaders?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
that's weird, you don't need to fix permission since it's built in?

when i did that, every process crashed continuously and i went back to reflash + fix permission, that fixed for me (3/12 kernal)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I suggest to check it out, but if I remember correctly, I believe the non-downgradable bootloader for the I747M is MK5 and anything before that should be fine to downgrade.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Getting ready to move from 3.36 to latest d2lte built. Need help understanding:

Is using backup and restore within TWRP the same as nvbackup and nvrestore, and are they the same as nandroid backups?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sewermike:
delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You can thank me later. ;D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CheateR92:
Hello! I just wanna ask you which combination is going to be better for battery life. I am using the phone mainly for FB Messenger soo I don't care that much about performance :D

1) Interactive + Row

2) Interactive + Deadline

3) Intelliactive + Row

4) Intelliactive + Deadline

Thanks for the great ROM is so buttery smooth! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
Everyone's phone and use-cases are different so there is no "right" answer. Your best bet is to try different combinations to determine what works for you.

In my case, Intelliactive + Deadline (128) works well. Start there, then try different combinations to arrive at an optimal configuration for your phone and usage pattern.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
As said, different phone, different usage, different settings. I'm a fan of the "classic" interactive + row setup. Works well. If you don't care much about the performance, you can limit your screen off frequency to something lower than the default setting. You can also limit your screen on max frequency to something lower than 1.5GHz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
<br />

<br />

I suggest to check it out, but if I remember correctly, I believe the non-downgradable bootloader for the I747M is MK5 and anything before that should be fine to downgrade.[/QUOTE]

You are correct sir. I didn't realise back in October when I was flashing a modem that a older boot loader was in with it and it attempted to downgrade. Thought I had a full brick! But after a little research and a lot of headache, I was back in the game!

Summary, watch what you flash! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
I used to use Interactive and ROW at 1028, but I switched to Intelliactive and Deadline at 128, works a million times better with amazing battery life!

Sent from my Quantum-powered SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmcneil:
Hi everyone. I wanted to know if it is allowed and possible to build this kernel for the i337 platform? I loved this kernel when I had a SG3, especially since the bluetooth bugs seem to have been resolved. Can you let me know.

Thanks,

Mike
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
well, I couldn't fix permissions even if I wanted because the last version of CWM doesn't have it(downloaded straight from rom manager)

I'm now running pacman with 3/13 quantum kernel, the rom is running smoother(no fcs) , we will see about battery life, but I like what I'm seeing so far...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Because fix permissions is remnants of an ancient time where you needed to do that. Not necessary anymore, hasn't been necessary since ICS.

Meant to answer you earlier but had some rush at work.

They're not the same, but I imagine you're having LTE issues you're trying to fix.

nvbackup/nvrestore is only good if you did an nvbackup while you were on TW. If not, forget about it. It's not a nandroid backup, it's a special integrated backup that copies modem/efs/nvdata to partitions you've never knew existed. :)

The shortest path:

-Backup current setup with TWRP/CWM then factory reset in the recovery

-Install any TW based rom. Doesn't need to be ODIN or absolute stock. Dandroid, Hyperdrive, Wicked Sensations, S3Rx, stock TW, they all work.

-Verify LTE/data is working

-Restore TWRP/CWM backup

-????

-PROFIT!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Thanks! Actually, my phone is completely untainted by d2lte as I never went past Quantum 3.36. But I'm still anxious about trying d2lte even though the signal issues seem to be resolved. So I wanted to do a proper backup before I flashed the latest Quantum.

Since you're so knowledgeable, can you explain concisely how the three different backup methods I mentioned compare? Would be nice to just use TWRP, but if it's not as "deep" a backup as nandroid or nvbackup then I'd prefer to do one of those. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
God no. Two completely different phones. You can make your own kernel and just cherry-pick the features from my git though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
TWRP/CWM is what is commonly referred as nandroid nowadays. The process over the evolution of Android to make a backup of the NAND changed, but essentially it's compromised of backing up one or multiple partitions in expectation of being able to restore their state.

Most often, /boot, /system, /data and /misc are the partitions backed up by the recovery Backup option when settings are unchanged.

nvbackup/nvrestore is a special solution by Samsung integrated in the Galaxy S3 (and other phones maybe, I do not know) to backup modem and connectivity related partitions/files to hidden partitions. For the sake of keeping this related to ROM flashing, you can read more here. It's not usually *necessary* but it's never a bad idea to have a nvbackup from the first time you booted your phone in the rare event you broke things REALLY bad.

So, what you can do right now, is make a Titanium Backup of your apps, backup your setup from within your favorite recovery, ideally factory reset from within the recovery then install latest Quantum ROM then restore your apps with Titanium Backup.

You most probably will not encounter issues with LTE connectivity, but if you do, we'll walk through that when/if it happens.

The d2lte builds aren't atrocious, they're just a bit rougher around the edges than d2att were.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Thanks for clearing things up, Polo. I will do nvbackup from Terminal Emulator for good measure, and then use TWRP to backup. TiBu for apps. I think I'm going to hold off until people are in agreement that d2lte is mature enough. If it ain't broke, don't fix it....

Any reason to think d2lte would open up T-Mobile data coverage? I get great LTE here since TM has been "refarming" but I know I'm missing some of the T-Mobile data coverage that was not in the d2att's modem capabilities...I never did figure out whether the i747 and the i999 had different radio hardware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
How did you reset the NV?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
See the second link in polobunny's post (2 posts above).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Remember, even just flashing any TouchWiz ROM will restore and backup your NVRAM for you. If you are weary of d2lte, try it first and if it gives you LTE issues then just have any TW ROM handy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
I downloaded an LK4 stock rooted ROM which is what my phone came with, tried to flash but got status 7 error (expected 5 args, got 4). I googled and think it is because my CWM is 6.0.4.7? I didn't want to downgrade CWM, so then I downloaded an MK5 ROM, but same error. Do you think this is because my bootloader is too old (LK4)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No problem. I agree with if it ain't broke don't fix it. Been in the loop for a while now and while it's fun to be bleeding edge sometimes it's just painful.

I don't believe d2lte would open up T-Mo data coverage. AFAIK they have different radios and some efforts have been made to get coverage. There's a thread somewhere in the General section I believe, there was even a bounty at some point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
How would everyone feel about Google Dialer being added in by default?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allrockedout:
If you think its smoother and more user friendly, or more efficient I wouldnt mind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Even though I use my own dialer, I'd still feel better if it were only offered as a flashable option. The biggest reason why I'm into Quantum is that it's basically "a better CyanogenMod," basically stock CM with fixes and tweaks. Call me an old fuddy-duddy, but I'd prefer to see Quantum stick to that philosophy. Just my opinion. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Hate it. Clumsy, shows my "fav contacts" as well as history right there instead of a separate tab. Does not make handing your phone to someone to make a call very private. Don't want them to know I've been 1-866-SEXHOTLINE biggest customer of the month.

---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------

CM has moved to Google dialer I believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
They haven't moved to it yet, just a messy merge error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheShamsMan:
Hey guys,

I'm still stick at the whole losing network connectivity issue. I know I'm supposed to flash stock first and then Quantum, but 4 hours later, nothing is working for me.

I've downloaded and flashed ATT_I747UCDLK3 and BMC_I747MVLUEMK5.

The AT&T one wouldn't even Odin. It would keep giving me some "auth" error, so I tried the later one, which works just fine, but when I attempt to flash Quantum, I get a fail.

I look at the update script and doesn't look like the d2CA isn't on that supported list. I tried removing the lines, which has worked for me with a different ROM in the past, but not this time.

Am I flashing the wrong stock ROM? Why am I not able to get it to install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmcneil:
Thanks for getting back to me Pwn.

Mike
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
YES! (Please)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
I kinda like the CM dialer myself. I still have the problem of when I click the dialer button all I get is a white space, then click it again and I get the dialer. Using gravity box right now to just have the dialer open from jump street.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
ok, i've tried the following while trying to flash a touchwiz rom through cwm 6.0.4.7 for i747m

- flash 4.1 stock (LK4) - status 7 error (expected 5 args, got 4)

- flash 4.3 stock (MK5) - status 7 error (expected 5 args, got 4)

- updated bootloader to MK5 from LK4, still didn't work

- flash Dandroid 4.3 - - status 7 error (expected 5 args, got 3)

any ideas what I'm doing wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I

Get an older recovery. I had the same problem. This is for the i747. Flash it, then you can flash stock and re update recovery. Again, this is for i747. I have the US model. https://www.dropbox.com/s/ynlsfvgra0v71n2/philz_touch_6.00.8-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
I've downloaded and flashed ATT_I747UCDLK3 and BMC_I747MVLUEMK5.

I am not sure this is correct. Lk3 is for att and I don't recognize mk5. Double check just to be safe

Per Google dialer......I don't care if it is added or I have to flash it. But I would prefer it work with no FC's. I like the black inverted stuff too but if if is not working It just messes up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
MK5 is the new s**** bootloader with KNOX for I747M that CANNOT BE DOWNGRADED.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Yes!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Doesn't work here in Israel, so I would personally be indifferent about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
Excellent, this worked perfectly, thanks! Flashed an ATT version of CWM 6.0.4.3 and was able to flash stock 4.3 (so ugly). Restored my nandroid and LTE is instantly connected. This was a super easy fix (flash stock with CWM and restore nandroid), thanks to [MENTION=4311957]polobunny[/MENTION] and the other users for the clarifications as well!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Great. But, you're further showing how deep this LTE break was. I assume this Nandroid had the LTE bug. Further shows that it's NOT in the ROM, kernel, etc. If it were your Nandroid should recreate the LTE problem. What the hell did d2lte break? :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
I would enjoy that. I always flash the Google dialer zip after I flash the rom. It would save me a step.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
True. Yep, my nandroid had the bug for some time now, it wasn't a signal drop just delayed LTE connection so it wasn't a deal breaker. I've restarted three times now just to test and the LTE is locked already.