yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
Flashing stock 4.3 then back to Quantum fixed mine too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
I also suggest reading the OP for that page as well as reading through the thread. I followed it about two weeks ago on my play with phone (which was already on MJB) and I was having problems getting it to flash. Laptop recognized the phone and so did Odin. Tried three different computers with varied results. I was getting frustrated and then decided to switch cables. The one I was using is a Samsung cable. The one I switched to is a Samsung cable. Second cable worked like a charm.

Daily driver is on MJ2. Debating whether I want to flash from the link we are talking about or one of the others that are stock but do not have the MJB bootloader in them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Flash this to remove Knox. Damn Samsung.

https://www.dropbox.com/s/rfwft0bh3pl551h/Knox_APP_remover.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Nobody flash this. Dude we aren't on touchwiz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
That's what I used to remove knox. What's wrong with it? Is it bugged by NSA?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It didn't remove a single thing....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
So other than not having the ability to downgrade if MJB is flashed what are the other negatives? I can still flash 4.4 and 4.3 ROMS correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Just flash 4.1.2 stock, same result in the end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I'm back. Rooted, although i'm still not sure how i did it. For some reason, went back to 3.27 & 2/8.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Uh.... you done ****ed up. Gotta go back to stock again when you use any build past 3.4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
Did you flash the 4.3 with Knox?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
JUST FLASH THE 4.1.2 STOCK.

Don't go to 4.3 if you don't have to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
Not going to. I'm just trying to get educated on the differences.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
4.1.2-

PROS:

Good

Cons:

It's touchwiz

4.3-

PROS:

It works, but it ****s your ****.

CONS:

EVERYTHING
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I have a nandroid of Dandroids 4.3 stock.

Will that work as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Nope.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
This worked for me as well. Completely cleared up the lte issues I was having.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
When i unrooted yesterday, it brought me back to 4.1.1. If you have the files to flash for 4.1.1, or 4.1.2, i'd appreciate it. Thanks.

Bootloader-1747UCUEMJB

FINGERPRINT-1747UCDMG2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
So if I revert to my backup of touchwiz 4.1.2 rooted will this fix my LTE issues when I reflash quantum?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Read the same page you just posted on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
Weird, had signal drop this morning, and it all of a sudden stopped, with and without wifi. So right now the only issue I have is not connecting immediately to lte, but I just toggle it if I get impatient. But going forward, it sounds like the best solution is the go back to 4.1.2 and then back to quantum. Since I'm running fine right now, will just hang out and not do anything for the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Did a nandroid of 3.54/3.9 and installed Dandroid 5.4 with the insecure MK5 kernel from the thread in order to get WiFi. Played with it for a bit and decided to restore my Quantum backup. Once I restored backup, I had instant LTE. Have rebooted a few times to see if it was an anomaly but each time I have LTE at the lockscreen. Not sure why it worked for me but it did. Canadian phone so I'm not sure if that makes any difference or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
OK - I have a question. Can you restore either a TWRP or CWM nandroid with either CWM or TWRP - ie, a TWRP nandroid with CWM and visa versa?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksd316:
Yes it did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Huh, so you guys think IntelliActive is better on battery life than IntelliDemand?

If so (at least on your devices), I might try switching over!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
i noticed that people talk about stock touchwiz for past 10+ pages, what's so special about it? lol I've always on aosp since the first day

just curious~
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
How about you read the last 10 pages?

Or just wait until I announce something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksd316:
Pwn I just took a good look at your profile picture. Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Don't - there's a simple recovery flashable MJB modem / MJ2 modem that you can flash after you odin back to LK3. it's in the S3Rx 3.0 thread, thread here and file here

AFAIK there is no benefit from updating your bootloader to MJB except that you face eminent peril if you briss yourself with a non-kosher flash.

All y'all talking about flashing stock etc etc - take it from the old folks - SLOW down. You got this far, you can figure out what you need to do, just go and read. You're taskifying Pwn.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
All y'all talking about flashing stock etc etc - take it from the old folks - SLOW down. You got this far, you can figure out what you need to do, just go and read.

https://copy.com/76m3N

Is the mj2 bootloader /modem pwn posted earlier

Not sure how Well copy app works, so Please hit thanks if it does;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I've noticed all devices are different. Weird. My friend has the same phone I do, and it gets hot all the time and he's not happy with it. Plus, I had hell upgrading it for him. Mine is fine. I've noticed everyone has totally different setting they swear by. Varies so much phone to phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Writing a guide. Back in a few.

Step 1. Check what bootloader you're on. Use Root Checker. If it says MJB at the end of your bootloader you CANNOT flash any Samsung firmware below 4.3 or you WILL brick. This is because the earlier Samsung firmware files that are flashed via Odin have earlier bootloaders, and the MJB bootloader will brick your phone when the bootloader is being downgraded. In this case you'll have to flash this in recovery: http://xdaforums.com/showthread.php?t=2658486

Step 2: If it doesn't say MJB at the end of your bootloader you can easily Odin back to stock. Download the firmware from here http://goo.gl/EQaNGn and Odin from this post http://xdaforums.com/showthread.php?t=1722686 .

Step 3: Follow the instructions from the second post of the Odin thread, but using Odin 3.07 and the firmware downloaded. You'll have to extract the firmware file using 7-zip to get a .tar.md5 file.

Step 4: You'll have to reroot/flash recovery. If you're following this guide you should be able to figure that out yourself.

Written to help out with pwncake's (and the rest of us...) sanity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
My LTE hasn't been an issue. I'm on the latest kernel and ROM releases. Of course I'm on WiFi for 22 out of 24 hours and when I'm not I'm usually on H+ because not all of my area has LTE. I'm gonna stick it out and see what pwn comes up with instead of flashing to stock then coming back to this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
I'll see if I can reproduce the results.

There's a lot of talk about flashing stock fixing locking on to LTE, but...

Can anyone confirm if flashing back to stock fixes the intermittent signal drop on LTE? I don't have any problems locking LTE, just get the consistent drops for a few seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
No. They will only restore their own backups.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
It has been mentioned by numerous people on numerous occasions throughout the last 20-30 pages or so that re-stocking helped with LTE Locking and data drops...and if I'm not mistaken, it has even been said by Pwn himself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Worked for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
My bootloader after using root checker says MG2, and under fingerprint it says MJB, am I still good to use your instructions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
Yes, there's lots of talk about it fixing people's LTE not locking on, but not so much on the consistent drops. Forgive me for seeking some clarification on the issue. Anytime Odin is involved, I find it's best to make sure your information is accurate (especially on xda).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
Thanks for the link. Upon looking in about phone to see exactly which Quantum kernel I was on, I notice that I was on the MJB bootloader on this phone too. Then I remembered that I had purposely flashed the MJB bootloader thinking that it might solve some of the problems. Plus I had already bricked my other phone once when I had taken the 4.3 OTA and then accidently flashed an older ROM that had an older bootloader. This was just when everyone was finding out about the bricking. Getting forgetful in my old age. 61 if you would like to know.

Got that phone unbricked using this http://xdaforums.com/showthread.php?t=2549068 after a JTAG didn't work.

So that being said, I just flashed enewman's 4.3 stock zip from - http://xdaforums.com/showthread.php?t=2658486. NOTE - DO NOT FLASH THIS IF YOU DO NOT WANT TO BE ON THE MJB BOOTLOADER. THIS WILL FLASH MJB. Didn't matter to me since I am already on MJB. Restored Quantum 3.36 backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
Just adding to the confirmation that flashing back to stock fixed my LTE issues as well. On another note, thank god for Quantum and custom roms. I'd probaby go back to my StarTac if I had to stare at this Touchjizz everyday!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
I think it's less about the phone varying and more about how the user uses it yes every phone is different but the different ways they react to a governor is neglible
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
For all intents and purposes, what you see in About Phone under baseband isn't the bootloader but the modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
Think of it this way.

Every part in our phones is manufactured with a range of acceptable operation. This tolerance means every phone has a lot of parts that are variables in its performance.

Some get all "bad" parts and some get all "good" parts. Mostly we get all "okay" parts.

That is why there is such variability in how each phone functions. Then add on top of that how each of us use them differently as well as load different programs, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Someone posted an adb command to get bootloader version

adb bugreport | find "bootloader"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
For all the people saying WiFi plays a part in the signal drops you're not wrong.

http://review.cyanogenmod.org/#/c/59846/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
Here is a shell script I use

#!/system/bin/sh

echo "Bootloader: " $(getprop "ro.bootloader")
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Can also use root checker in play store
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You realize Tom is pwncakes? lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
The MJB bootloader is what will brick your phone if you downgrade. You should be OK. However.. I'm not 100% sure, so wait for someone else to confirm. I don't want you to brick your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
No? Why would I know his real name? I saw this and posted it for the people who don't regularly check gerrit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's a few clues if you look around, that's all. Where's your Sherlock eye? =)

*hint* d-h.st username, see his name if you donate also *hint*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
O.K. I've finally got it through my thick Irish skull that an MJB Bootloader means i'm screwed for updates. I'm on 3.27, it's running good, but this is where i'm staying while rooted. I have amf66's zip on my SD card, ready to get me back to stock. Don't know when i'll pull the pin, but i guess i'm hoping to read about getting the bootloader back to MJ2 from some of the more knowledgeable people in this forum(God knows i'm not one of them). It's been a great ride, Pwn. Thanks for the help from you, and all the others.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm not sure what you mean as "screwed for updates". You can still flash back to MJB stock (just nothing prior) or flash other custom roms without an issue. You CANNOT downgrade to MJ2 or any previous bootloader however without bricking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I meant that i can't flash any other Quantum roms. I'm on 3.27, and i tried to go up to 3.36, but no luck. All i was able to do is reset my counter with Triangle Away. So i'm on 3.27, but the counter says NO for roms.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
Are you trying to reset your flash counter with Triangle Away after you flash Quantum? I'm a bit confused with what exactly you're trying to do.

If you ever need to send your phone back to Samsung for warranty repair, you flash to stock and run Triangle Away. You don't need to worry about the flash counter unless that happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
Currently using Quantum Kernel 3/9 with Slimkat Weekly build 3.6. All can say is WOW!! real smooth and snappy. Intelliactive+ROW 256.

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No luck meaning? It doesn't boot but shows the boot animation? It bootloops? You don't get signal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
When i tried to flash 3.36, the recovery android guy(who's supposed to be spinning green, goes red). It says rejected, or something like that, and i can't get back into 3.27 unless i go into my back-up. I guess it doesn't boot but shows the boot animation. It tries to get into 3.36, but fails. I know what a bootloop is, and it's not that.

I used Triangle Away because i had all intentions of going back to stock immediately, but backed off when i read about my MJB bootloader. If i could get the phone back to 4.1.1, i would do it in a heartbeat, but i don't think i can.

P.S. Tried Skunkape60's guide to unrooting the first time, and it worked. After i stupidly upgraded from 4.1.1 to 4.3, that's when the trouble started. After a back-up, i re-booted and found myself with 3.27. Tried to unroot again(with same guide), but no luck.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Where are you right now? If you have the MJB bootloader (it's shown in my little guide I made last night how to check) then the only thing you can do to go back to stock is to flash MJB through recovery per http://xdaforums.com/showthread.php?t=2658486 . Do not flash any stock Samsung firmware that is not MJB - these are likely to contain bootloader downgrades and your phone will brick. You can't downgrade the bootloader if you're on MJB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kinjo1023:
So I've been getting random reboots when I use Google maps, not really a big deal. Today, when it rebooted I had to sign back into CyanogenMod, set my default launcher, enable super user again. Weird, anyone else get that yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Using CWM/PhilZ or TWRP? CWM I imagine from your description. Is it up to date? That's something to check.

If you mean it says "assert failed" or something of that sort, we need the full error message. There's no reason why you shouldn't be able to update, you have the MJB bootloader which is supported by Quantum. No reason to go back to stock either (unless you're trying to fix the ongoing LTE issue).

I'm sorry if I have started to help you somewhere in this thread and stopped suddenly, there's just a lot going on lately.

---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------

Yep I got that on CM nightlies starting 0308 up to 0310 when using Quantum kernel. I'm currently testing CM nightly 0311 using stock CM kernel to see if this happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I have the A.S.I app, and i'm definitely on MJB Bootloader. I also have the file you sent me, from your previous post. At this point, i'd rather be stock, and hopefully get a 4.4.2 upgrade from AT&T. So, i guess that i just go into recovery, and flash your file? :confused:

P.S. I need stock, as i intend to upgrade to the HTC ONE, as soon as the HTC ONE 2 comes out. I can only afford one phone at a time, so the AT&T discount will be sweet.:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Yeah, I had issues with Maps on Saturday on our drive to St. Louis. I didn't have to set my launcher and such, but a few things were "forgotten." Good thing I pretty much know where everything is LOL

On the way home Sunday, I had no issues with it at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
[MENTION=1683096]PwnCakes193[/MENTION]

These are the 0308 commits regarding kernel, if that helps you regarding the "forgetting bug".

http://review.cyanogenmod.org/#/c/60776/

http://review.cyanogenmod.org/#/c/60778/

http://review.cyanogenmod.org/#/c/59652/

(and WLAN stuff prob unrelated)

http://review.cyanogenmod.org/#/c/60777/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
:crying:eek:H CRAP! I knew that. It was getting late. Guess I was more tired than I thought. Oh well, too late now. Doesn't really matter. As long as I have an easy way to at least go back to 4.3 I'll be good. Can't tell you how LTE is acting because I live just outside of an LTE area. I will however have LTE access for a few days this week and weekend. Going to visit sister-in-law in Atlanta and I'm sure she probably has LTE in her area. Also stopping over at daughter's house in DC on Thursday before we fly to Atlanta on Friday. I know I have LTE service at my daughter's house.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
That's correct. If you've got the MJB then that is the only way to go to stock since you can't Odin to anything earlier. Follow the instructions in the post and remember that you'll lose root and CWM/TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirGeraint:
I've debated whether anyone would want to hear the way that I have fixed my 2 LTE issues (LTE at startup needing to be toggled and LTE dropping out at regular intervals). It's pretty much what polobunny said he did.

I was on v3.54 with the 3.9 kernel

I had a Nandroid of v3.54 with the 3.7 kernel.

I read that polobunny did a nvrestore. I thought that I had done a nvbackup because I remembered that when I got my phone I did every type of backup I could find (I used 3 different methods to save my IMEI). So I decided to do the nvrestore.

After I did the nvrestore my phone was in a weird boot loop kind of thing, vibrating, etc. At this point I wondered if I did have a nvbackup. It never got to the boot animation. It would show the splash screen and then the screen went blank and the LED flashed blue forever (?). I let it go a while in case it was doing something productive. But then I gave up and went into recovery and restored my Nandroid. After it booted I went back into recovery. I think at that point I did a regular dirty flash of the Quantum ROM v3.54, the 3.9 Kernel and the latest pa-gapps.

Ever since then my LTE problems have been resolved.

I hope this helps someone... and doesn't hurt anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
[MENTION=4311957]polobunny[/MENTION]

I think i found the reason that i can't flash any newer roms after 3.27. My CWM recovery app is 6.0.4.7, but when i go into recovery, it says 6.0.2.3. Is that possible?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Oi that's completely my fault for not writing it down, but I installed a nightly after also ending in a bootloop after my nvrestore. Fixed everything though. Didn't need to clean flash or anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
That's completely possible and sounds like it's the cause of your problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If it says that, I'd strongly believe that's the case then. It should show the proper version number when you boot in the recovery.

I would assume you're using ROM Manager? I've never been a fan of automated software solutions, sometimes the command line just works wonders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
When you say command line, are you talking about using the "terminal". My knowledge is limited in this area, but i've got nothing to lose now. I use a MacWindows computer. 400gb Mac, 100gb Windows7. If you could give me a fix for this, i'd appreciate it. Thanks again for your help.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VanGool:
Hi guys, quick question.

I'm getting a bootloader error while trying to flash 3.36 after wiping 3.54

What can I do?

Regards.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Either Terminal or ADB shell

Download the latest recovery, either CWM or TWRP depending on your preference and place it directly in the root directory of your internal memory (/sdcard)

Open terminal emulator and type without the quotes "su" and press enter. Agree to superuser prompt

Type "dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18" once again without the quotes where recoveryfilename.img is the name of the recovery image file you downloaded and put on your phone. Press enter.

MAKE SURE YOU TYPE THIS EXACTLY LIKE IT IS (except for the recoveryfilename.img). dd is a very powerful tool. if means the source, of means the destination. If by some mistake you typed the destination wrong you could/will break things.

This step will take a few seconds, and tada! You just updated your recovery through the command line. =)

---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------

In terminal type "adb bugreport | bootloader" and tell us what is the result of this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VanGool:
If i do it on the terminal emulator i get that it doesnt recognize "bootloader". Should i do it from the ADB on the pc?

Edit: output from pc

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

List of devices attached

811dfe3b device

C:\Program Files (x86)\Minimal ADB and Fastboot>adb bugreport | bootloader

'bootloader' is not recognized as an internal or external command,

operable program or batch file.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb bugreport | bootloader

'bootloader' is not recognized as an internal or external command,

operable program or batch file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
[MENTION=4311957]polobunny[/MENTION]

Are you talking about doing this on the computer, or the phone?:confused:

Got it. I deleted Rom Manager from phone, re-installed, then the new Rom Manager gave me the option to install to recovery. Did that, rebooted, went back into recovery, and it now says 6.0.4.7. I guess now i can install roms again.