yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
Sweet, thanks guys

It looks like those are both MJ2 bootloader and modem, is there a significant difference between MJ2 and MJB modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I'm getting the LG G3 at the end of this month when pre orders come out. I've been researching this everyday and it will be the baddest phone for quite sometime. Sammy is getting lame with their iphone type releases, by just doing small upgrades and calling it the next version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Someone said MJ2 modem was better than MJB for some reason. Might've been Pwn. I've been running MJ2 for months with no complaints.

---------- Post added at 10:51 AM ---------- Previous post was at 10:49 AM ----------

Which of the new phones has the best camera? I'm really intrigued by the One plus One but camera is supposed to be just OK.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Do some searching on the G3, looks like LG is not going cheap on anything. A 13 mp camera but it has the new and improved optical image stabilization in it with a laser sensor for low light.

This is the first phone I fell very impressed about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Optical image stabilization and good low light performance are going to allow much better photos. Sounds great, but I admit something like a One+One or Nexus that runs non-bloated Android natively is a plus for me. I have been flashing ROMs for years but frankly I'd be happier not having to waste time on that. *runs and hides*

On that note, I never upgraded from Quantum 3.36 and it's been great. Occasionally will get an app/service causing bad battery drain but most of the time it's excellent, and rarely if ever reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
I gotta say, last night I dirty flashed from Slim back to 4.1 - 4/28.2 and it's been rock solid with great battery life since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I'm not worried about bloatware, when within a month there will be root access.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nope, baseband is MODEM, not necessarily bootloader.

I'm sorry I can't link you to any right now, just popping in. You can check the bootloader a few ways (device info by jphilipps on the play store for instance)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Serious problem please help ASAP

My wife's S3 has been running Quantum since early 2013... currently (was) on Quantum 2.4 and fairly stable.

This afternoon her phone hard rebooted, and was stuck at the spinning Quantum logo. I pulled the battery, booted into recovery (6.0.4.3) and wiped system/cache/dalvik... tried reinstalling Quantum 2.4 and it gave a status 7 error. ****.

I tried pulling from a backup and it said no files found. DOUBLE ****. I'm 95% sure I have at least one backup on here.

I cannot 'see' the phone from the laptop, and I cannot get into the Android OS to back up thousands of photos of our kids, etc.

I just want Quantum 2.4 or 4.1 back. I cannot afford to lose the data on this phone. What can I do?

I can get into recovery, or Download mode, but nothing else. Nothing was installed that caused this... it seems REALLY weird that it just all of a sudden started throwing this Status 7 when installing a ROM.

I don't even think I have a backup stock touchwiz to go back to... and I can't seem to sideload anything onto the device to get the right files in order to get it back up and running.

HELP, PLEASE. My wife may just kill me if it's not back up by Sunday AM!!!

Thanks in advance.

Eric
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Anyone else's root go kablooey after today's tibu update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
others have said it more eloquently than myself, but my understanding is the MJ2 boot is mjb without knox. you can downgrade bootloader from mj2 boot, but not MjB.

+1 on device info app

and the first time I asked I was clearly told......"modems are not bootloaders, and do not contain Knox." if you're reading this, I still get a kick out of that!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
No
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
Woops lol, thanks for that info guys o;

Attempting a touchwiz flash to fix my funky connection issues... hopefully that'll fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmppe3:
I have a feeling this is a stupid question but I'm going to ask it anyway! :D

If I flash a TW ROM to recover the LTE/network connection issues, can I just restore a Nandroid (data) backup of Quantum 4.1 afterwards? Or do I have to do a clean flash of Quantum?

Thanks...

---------- Post added at 08:08 PM ---------- Previous post was at 08:00 PM ----------

Same for me, I switched back to 2.6.3.1 and works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I would suggest a clean install, just due to the way the partitions went kafooey. The process was complicated, but if you can search and see if someone else did it and had no issues, then by all means try it.

Wait a little bit though... something might show up to download before the end of the night....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmppe3:
Not sure where you are/what carrier, but I got Status 7s on TWRP when I installed a d2can TWRP on my Koodo phone. Had to switch to the d2att TWRP to get it to work. You could try that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
+1, NEVER use a d2can recovery for flashing d2att ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
Oh god.... I had forgotten how painful Touchwiz was....Def not buying another Samsung until I know it's already has solid dev support x.x

Data seems to be working right now, though apparently speeds in NYC are like 1Mbps right now on 4g....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
So that's why nothing is loading and my battery is getting wrecked. Dumbass towers acting up. Every Sunday for the last month.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
It is a Canadian model. However, it has been running near flawlessly on quantum 2.4 for months. Nothing was changed... It just shut off and went into a boot loop at the quantum circle. So I pulled battery, wiped cache and system and tried reinstalling the rom... And then that damn status 7 happened.

Anyone??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Internet:
That was happening to everyone during Quantum 3.2-ish update. It seemed that we needed to update out bootloader. I updated my bootloader from LK3 to MG2 (ATT model). For your Canadian model, it looks like you'll need MK5, but be very careful to never downgrade your bootloader once you've updated to MK5 because you'll probably brick your device.

Do some research before doing anything just to be sure you are doing the right thing and flashing the appropriate files. Here's the bootloader page.

http://xdaforums.com/showthread.php?t=2321310
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atthebeach:
I think adb should work from recovery, so you should be able to backup /data with 'adb pull'.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Well... I did a nandroid backup last night before trying (unsuccessfully) to flash stock TW rom (stuck on Samsung logo). That data is on the removable SD card.

Can I somehow use stock recovery to get into the 6.0.4.3 recovery to do that now?

So stumped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atthebeach:
I think, if all you have is download mode and stock recovery, then you may have to use odin to install a custom recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
When you flash stock you need to full wipe in either custom recovery before or stock recovery after or you'll be in a Samsung boot loop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miluardo:
Hey guys since the switch to slim I've had my network signal go in and out. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
I always chalked that up to just part of running AOSP ROMs dating all the way back to Gingerbread. That would be great is there actually was a fix for this though, I never ran Quantum until everything went unified.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Just backup anything you need, jump back to stock, wipe, reflash quantum, and restore.

I had the same issue, and my understanding is it's a side effect from when everything was changed to d2lte instead of carrier specific versions (d2att/d2vzw etc.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I'm not trying to rush Pwn or anything, but I want to express how pumped I am for the next release. Even with the reboots, Quantum is the smoothest rom available, plus battery life is so phenomenal that I considered switching back to the stock battery from my 7000mAh ZeroLemon for a day just for fun. Again, that's reboots included, so I can only imagine how battery life will be once those are ironed out.

Sorry for the rant, it's late and I'm sick of studying and none of the ROMs I'm bouncing between can beat Quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Does quantum 4.1 have lockscreen notifications? That is the only thing I like from the kitkat roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Its not included on Quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Update your recovery then try the newest Quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
edited: sleep longer, read better, do it faster, nevermind me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
oh ok, I thought that error 7 was an outdated recovery but I could be wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Upon re-reading, you're probably right haha. Wasn't paying attention, if it was bootloader issue it would likely be assert failed. Move along! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Here's my question to those theories, though...

If NO updates had been done to the phone since Quantum 2.4 (including the recovery, ROM, kernel)... Why, all of a sudden, would the presence of an old recovery cause this issue? It's the same configuration that worked a few months ago and worked for months before that.

Plus, the fact the phone crashed about once a day while typing (SwiftKey), and on Friday it also crashed hard (hard enough to get into a boot loop)... wtf?!

---------- Post added at 10:40 AM ---------- Previous post was at 10:39 AM ----------

The error is something like "error: Status 7 (assert failed)" and has something to do with the getprop.

That's all I remember. The phone is at home and I'm at work right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah ha! Then it is most likely a bootloader error. You probably have a version of the bootloader that is not in the install script.

Get the complete error, someone can help you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
How would the bootloader have changed on its own between October(ish) and now? I am positive I did not update it. And, the Quantum 2.4 zip file is still the same one on internal storagte as it always was.

I have a feeling something, somehow, changed the d2att back to d2can in the getprop. But, I cannot access the phone to change it back. Ugh.

This is purely to recover photos at this point, as she got a used Galaxy S4. Although, I would love to fix up the S3 and repurpose it as a portable gaming device for my kids. :)

I'll post the exact error tonight.

Thanks,

Eric
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
With the exact error in hand, don't worry, we'll get you in working order. You can always push back a proper build.prop using ADB if needed, not that it really should.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
That's an issue I've had in the past and recently as well. If you can get into custom recovery, you'll be OK, as long as you can mount and plug your phone in the PC. There a few lines you have to edit in the update script to remove the upgrade assert and allow you to flash if indeed your build.prop has been changed from att to can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miluardo:
I'll try going back to stock and reflashing. I'll let you know. It's never happened with any other rom ever for me. Can I go back to a different custom rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
I can get into custom recovery or download mode. Neither was able to connect to PC as a drive. I was able to connect via ODIN to the phone using download mode.

Alternatively I may be able to use the microSD and transport the proper files into the S3 that way...?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You can use adb push/pull as well as microSD too. More than one way to skin a cat (psst don't do that)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
Download the update that you're trying to flash, and on the PC, browse the zip file as a normal folder(don't extract it) and go into:

(Quantum).zip

META-INF

com

Google

android

Once there, copy the updater script to a folder and the add .txt to the end of it and open it in notepad.

Select and remove all lines above the one that reads " ui_print("AnyKernel Updater by Koush.");

Save, remove .txt and copy back to the zip file(it will automatically repack), then copy the whole zip to your micro, insert into phone and attempt your flash. Hopefully that was detailed enough! Hope it helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
This is fantastic - I'll try it out tonight.

Should I go with the Quantum 2.4 in the OP (as that was the last one installed)?

What are the implications in doing this, IF:

- My d2att was reverted back to d2can somehow?

- My bootloader somehow changed or became corrupted (is this even possible?)?

Thanks again!!!

Eric

EDIT: I just checked, and 2.4 isn't in his OP anymore... can I go straight to the 4.1 version without upgrading my bootloader and/or anything else (aside from GAPPS)? I'm using an older recovery at this point too...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
To goto 4.1 you'll have to do a clean flash(wipe system, data, cashe and dalvik). About the boot loader, I'm not too sure. I haven't updated my bootloader in forever(I think). You are Prolly going to have to update your recovery at least. I use either philz or twrp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If you want v2 Final

http://d-h.st/users/TommyTarts/?fld_id=29390#files

:)

As for upgrading to v4, have the MJ2 bootloader and MJB modem flashed as well as up to date recovery prior, otherwise you'll hit a brick wall.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
Edit: d2att and d2can are the same system, just different region codes. There's no worries there.

For the bootloader, unless you did the ota update from Samsung or installed it yourself, then it should be unchanged
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Here's the error. I'm trying your edit-file method after I type this.

installing update...

assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"

E:Error in /sdcard/Roms/Quantum-v2.4.zip

(Status 7)

Installation aborted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
So I would imagine you have a Canadian S3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Yeah that's a recovery error. The recovery thinks/knows that you're a d2can. I'd flash the latest d2att in download mode and restore a nandroid (assuming you have one) start with the recovery before you wipe or flash an update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
I'm having a problem with this...

There is no: " ui_print("AnyKernel Updater by Koush.") or anything with "ui_print" in it, within that file.

I'm attempting to remove the first asserts where it calls for d2att, but I'm having issues repacking the zip (using basic copy/paste from one folder to another).

---------- Post added at 08:53 PM ---------- Previous post was at 08:45 PM ----------

Sorry, but you're going to have to dumb that down a bit for me. ;)

Download mode (via Odin I assume?) to flash a new recovery? Which one and what version?

My only nandroid that I can find on the phone was taken after this crap hit the proverbial fan. Will that still work? (assuming it's the recovery that is the issue here...?)

Then once the latest/greatest d2att recovery is in place, go into recovery mode and flash Quantum Final 2.4.zip as per normal?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
For twrp I believe it is an Odin flash, cwm and philz touch are either recovery flash or Odin. Obviously for Odin you'll be in download mode

And for my previous entries and help, I was mistakenly going thru the steps for updating the kernel like that. What you have is an outdated recovery. Just search the forums, they're usually close to the top with [recovery] in the thread name and they should be updated to the latest version
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Ok... I d/lded CWM 6.0.4.3 d2att and flashed it with Odin.

In there, I wiped /system, /cache, dalvik, installed Quantum 2.4.zip, then GApps, then wiped cache again.

Now I get past the "Gimme Pwncakes" logo and am now stuck on the spinning Quantum logo...

Getting there...?

EDIT:

Downloaded AROMA File manager. Within that (run from Recovery), I explored every folder on the phone and internal SD. No pics to be found.

Should I just do a "Wipe data / Factory Reset" within CWM and then clear caches, then reinstall Quantum 2.4 and GApps at this point?

EDIT #2: SUCCESS

I did a wipe data/factory reset in CWM. Reinstalled everything. The CAMERA directory was still there after I got back into Quantum!! Backed it up to the external SD and transferred to my wife's new (to her) S4.

THANK YOU ALL SO MUCH!!! I might actually get to sleep in the same bed as her tonight LOL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Good job! What is wrong with the S3 anyway? Are you looking to sell it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
When it crashed (for whatever reason) my wife needed a working phone. She's been complaining about battery life on the s3 as that battery is almost 3? Years old.

I went and bought the s4 used locally. But we need photos and documents off of the s3, and we will also repurpose the s3 as a gaming phone for one of the kids (daughter has my old HTC EVO 3D).

Can't get much for the s3 so I probably won't sell it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
Where do I get my hands on that aroma file manager?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
Wake lag

I'm getting a wakelag of up to 3 seconds. Is that the Quantum Rom or Ktoonsez kernel? Is there any way to stop it from taking that long?

---------- Post added at 07:07 AM ---------- Previous post was at 07:04 AM ----------

Pretty sure philz has one

http://xdaforums.com/showthread.php?t=2335527
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Right here: http://xdaforums.com/showthread.php...cct=/sitesearch.php&__utmv=-&__utmk=264529036
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Alrighty, just looking, the S3 is still a very capable phone for some gaming. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
I have the same issue would love to know what settings to use on Ktoonz if there is a way to reduce or kill it entirely.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
Try a different scheduler.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kaflex:
I got about $200 for my s3 on swappa.com
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'm using AOKP and kt747 at the moment
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kinggame992000:
Ujm. Have anyone notice the volume when making call is very small?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
tried almost all, no difference. it's not a huge deal, just annoying at times
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
Common issue. Turn the volume down once or twice then back up again

---------- Post added at 07:56 PM ---------- Previous post was at 07:55 PM ----------

Screen off max too low with semi-intese app running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aew0314:
Try this, I found the s3 was quiet on all fronts, this solved all my issues.

http://xdaforums.com/showthread.php?t=2563209
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
no apps running, and not sure about the screen off max
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Running off to the gym, new kernel up in the usual place!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
If you're using quantum kernel, there's the option in CPU settings for max CPU while the screen is off
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
QuantumKernel 5/14 - http://d-h.st/zlj

Changelog:

Gym version

Running off to it

Added Quantum

Very commit

Added

Much 7/11 pizza

Much cardio

Much Linux 3.4.9

Much one bugfix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Downloading now. Been wondering if you were still alive. Guess exams are over now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
-Much 7/11 pizza

-Much cardio

-Much Linux 3.4.9

-Much one bugfix

Today starts the hardest two days, have 3 finals and 2 papers to do before tomorrow night. Just decided to do that since I was really procrastinating last night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Yuck, that's no fun. Thanks for the hard work on the Kernel/ROM. Will report back if I encounter any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
This won't magically fix the reboots that users are having, but it should have enough to at least prevent them from happening again or as often.

I forgot I used GCC 4.10 instead of 4.9 as well. Whoops. It's a stability change, SM decided to drop 4.9 development for now.

Also now that my whole VM is set up after moving to an SSD I will finally be able to build without it taking forever, so even if I'm busy I can still pop out these kernel updates fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So did you ever determine the cause of all the reboots? The in-call ones were the most problematic for me, and they were present in pretty much ever kernel release after 4/16.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Had no time to really look at that past what I had. But now that you gave me that date, I think I figured it out. I previously thought it was modules I disabled.

https://github.com/tommytarts/quantumkernel/commit/35812c1e9c018910d1880e45ef2cd8bf7ee68629

You sir, have just contributed to this kernel. I'm almost positive that this is the issue, I'll build once I get back from gym and send it to you so you can try it out.

Seriously you're the reason why sometimes sitting around and waiting it out will bring out great results. Everyone give this man applause, and even more if it actually works!

And on top of all of this, I just got an email saying I got an extension to do one of my papers whenever I feel like it!

[MENTION=4570464]ScOULaris[/MENTION], will you marry me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Might stop the msm bam_dmux spam in the logs too. =D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
That might be something else. I used a method to disable the logging but it may have gotten undone with a merge somewhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Glad to have helped. :good:

Hopefully you're right and that fixes the problem. As you can probably understand, I had to switch over to another kernel while the call-reboot bug was still present. I'll gladly test out a potentially fixed update, however.