yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Master Cylinder:
HO! Been waiting for 2.8.7 to come out! Might solve CMUpdater issues. 2.8.6 worked for me but it would hang up whilst it was doing a backup - couldn't swipe the screen open to see what was going on. Been using 2.8.5. I just get it straight from here: https://dl.twrp.me/d2vzw/

d2 and TWRP both r/w to EXT4, at least with AOSP. There is a way to get it to work on Touchwiz, I found some instructions somewhere. There are some considerations, though. Can all apps write to EXT4? I'm looking into that and other performance issues now.
[Verizon Samsung Galaxy S III] realicet:
twrp 2.8.7

I just tried to upgrade to 287 twrp, through its new app and also falshify and they both failed on reboot I get stuck in download mode. I waited 15 min with sim, sd, and bat pulled then it would boot download mode and chose to cancel and rebooted to cm 12.1 ok. I went back to flashify and it restored the 286.... Long story short, boot into TWRP and update img to 287, not worth the scare.
[Verizon Samsung Galaxy S III] Master Cylinder:
I've never used those apps - with a .img file, you can flash it directly in TWRP! Just select install and then the images button at the bottom, the rest is self explanatory.

I just flashed it that way and no problems.

PS - If it ever gets hung up like that one can always Odin.
[Verizon Samsung Galaxy S III] Master Cylinder:
CMUpdater Woiks!!

Hot Dog! Using TWRP 2.8.7.0, CMUpdater works like it's suppose to - dloading, installing and restarting the phone! Awesome!
[Verizon Samsung Galaxy S III] noticonoclast:
flashed modem then hard bricked

after I flashed the modem as per instruction, I seemed to hard brick my phone

I was able to unhardbrick my phone, but currently i am unable to boot into any android

I am able to flash stock verizon roms using odin

I am able to flash twrp

i am able to boot into twrp

I am able to install zips from twrp

in the past after taking the 4.3 OTA update I lost the ability to odin flash earlier stock ROMs, or custom bootloaders, so I am hoping I can remedy my situation without JTAG

unfortunately for me I am still currently unable to boot into any os as I get the message with a bright yellow triangle with an exclamation point:

System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.

I am going to try a few more times to fix this, but I am thinking it might be time to send it into a JTAG service

---------- Post added at 09:31 PM ---------- Previous post was at 09:21 PM ----------

instead of custom bootloaders, i meant to say custom recovery mode
[Verizon Samsung Galaxy S III] phonetool:
After taking the 4.3 update you have lost all ability to flash custom ROMs. You are now limited to the stock OS and the very few ROMs that are based on it (such as superliterom). With 4.3 is installed also a 'q-fuse' that bricks your phone if you try to flash a custom ROM.

Your only option with the phone now is safestrap and one of the locked bootloader ROMs. Those threads are very informative, so you have a good chance to get the phone working again, but only on 4.3. Good luck!
[Verizon Samsung Galaxy S III] Master Cylinder:
Can he use a 4.4.2 TW ROM through Safestrap?

"The official 4.3 touchwiz update brought significant changes to the Verizon Galaxy S3. Once you took the update, the phone is completely stuck on the 4.3 or 4.4 base and any attempt to change the rom (unless using safestrap) will brick the device. "

From 4.4 and 4.3 Sticky Roll-Up Thead
[Verizon Samsung Galaxy S III] phonetool:
Yah, that's right. 4.4.2 is the latest OS he can use, but only one that has a locked bootloader.

We're OT now... The other threads are best for such discussion.
[Verizon Samsung Galaxy S III] LLStarks:
Hopefully the next nightly is 5.1.1_r5 (LYZ28E)

Btw, has anyone noticed that builds earlier this week were a bit flaky? All keyboards were broken at one point.

My radio is performing a bit better, but the phone is struggling to keep 3G and LTE signals. Keep getting the exclamation mark.
[Verizon Samsung Galaxy S III] AyUaxe:
Can you say why that's significant for us marginal Luddites?
[Verizon Samsung Galaxy S III] Master Cylinder:
No problems with keyboards (Other than Google Speech to Text hanging up a lot, but that's been going on awhile.)

Having the same problem with the radio, though. A reboot fixes it for me but if I'm in a wifi them I don't know is out, just unknowingly not receiving texts.
[Verizon Samsung Galaxy S III] LLStarks:
http://www.androidpolice.com/2015/0...v5-1-1_r5-lyz28e-and-its-actually-quite-long/

It honestly should be called 5.1.2 or even 5.2. It is huge.

Most notable addition would be AOSP wifi calling. Whether this will work on random phones is up in the air, but it should work on any phone that supports wifi calling with a stock rom.

Btw, no go on LYZ28E for next nightly. Hopefully this weekend.
[Verizon Samsung Galaxy S III] AyUaxe:
On 6/24, haven't seen any KB probs in the last few weeks, other than a spate of Google play services crashes mostly during txt entry and navigation, but those seem to have resolved with a couple of full wipes and reversion to a last known good data backup.

No radio problems observed. Bt, calls, lte, and MMS have been fine.
[Verizon Samsung Galaxy S III] Master Cylinder:
Turns out to have been a false alarm. Most of the commits that guy was referring to were ghosts - commits that have already been made.The author had to retract later in the same day:

Update: 2015/06/25 8:24pm PDT

Problems with the changelog

A number of inconsistencies in the changelog suggest that the script we use to generate a list of changes is not working as expected. I apologize for the confusion. I'm looking into a fix. If anybody has some helpful information, your input is welcome.

End of Update

From a comment:

From atl4ntis, a recognized XDA developer: "The changelog posted on AP is totally wrong and changes are minimal, no changes for hammerhead, mostly are for the N6 wifi calling.The majority of commits you see in that changelog are already included in r3, they just have different ids, so got caught by the changelog generator.

A bit disappoint that they didn't dig deeply and just assumed everything wrong out of a wrong changelog."

:(
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Best way I've found to get out of exclamation point mode is go to airplane mode reboot then exit airplane mode and I get data back every time
[Verizon Samsung Galaxy S III] spankiej:
Thanks that worked for me too
[Verizon Samsung Galaxy S III] MPTP:
The best way I found was to just switch APNs. It'll usually just bounce back to Verizon Internet and my data returns after 10-15 seconds.
[Verizon Samsung Galaxy S III] phonetool:
No nightly in three days... I'm going into withdrawal and the changelogs mock me by growing and growing.
[Verizon Samsung Galaxy S III] spankiej:
Someone mentioned that a few pages back, but the procedure didn't work for me. Maybe It'll work for others.
[Verizon Samsung Galaxy S III] AyUaxe:
At least when these forums go quiet, it means things are working reasonably well, unlike the cm11 forums that fell into disuse from disgust.
[Verizon Samsung Galaxy S III] Master Cylinder:
Device Mainterer: Nardholio

I've finally acknowledged our 'Device Maintainer' in the OP, the person who generously provides us our candy.

It's [MENTION=2044079]Nardholio[/MENTION].

:)
[Verizon Samsung Galaxy S III] XdrummerXboy:
By candy you mean our drugs?

Just kidding, kinda...
[Verizon Samsung Galaxy S III] Master Cylinder:
Well, I'm sure there are a number of us who are a little twitchy with "sugar" withdrawal at the moment ...

:silly:
[Verizon Samsung Galaxy S III] Master Cylinder:
Phone Crash and Burn - Literally!

Oh NO! I had a spectacular crash with my phone on a hard tile floor yesterday! One of those where you're grabbing for it and you pop it up a couple of times but it smacks down right on it's face from about 5 feet. Pretty bad, but no cracked screen.

However, it's been flaky ever since, and now I can't get it to boot! It attempts to boot by just putting the battery in, but it just loops. From a little Googling, seems like it's an inner power switch. I tried banging it and such. I found a Youtube video that shows how to fix it. If that doesn't work, I'm cooked!
[Verizon Samsung Galaxy S III] stevet86:
I had the same problem with the switch but I didn't drop it. I pressed it one day to power the screen on and it just kept looping. I banged the corner above the power switch and it took care if it. It still occurs once in a while but hitting the phone resolves it. I've seen power switches on eBay but the tricky part is installing them.
[Verizon Samsung Galaxy S III] Master Cylinder:
I should say I really don't know what's wrong with it so anybody with a good idea. Still will be searching around ...:crying:
[Verizon Samsung Galaxy S III] Deliquified:
S3s are well known for faulty power switches. I have to smack my phone above/below the power button sometimes to get it to stop boot looping
[Verizon Samsung Galaxy S III] XdrummerXboy:
It's honestly not too bad tearing the phone apart. Just have a YouTube video handy. Lucky for us the screws are basically all the same, they make it obvious when one is different. Unlike taking an iPhone apart... Those are God awful.
[Verizon Samsung Galaxy S III] Master Cylinder:
I took it apart and plied the power switch with alcohol and worked the switch for a bit - no go. I've smacked it quite a few times now around the power switch also without any luck... I got an $8 battery coming in on Wednesday just to be thorough.:(
[Verizon Samsung Galaxy S III] Doctorimpossible:
[MENTION=5519140]Master Cylinder[/MENTION] best of luck to you with that

Has anyone tried the new unofficial version of xposed 5.1? I tried it on aicp and I ended up in a boot loop, sort of. I made it all the way to being able to open an app for about 20 seconds before it restarted on me
[Verizon Samsung Galaxy S III] Master Cylinder:
I've been using it for at least 6 weeks without any problems and it works great! Got Gravity Box going and CM 12 Settings... You have to flash the framework, which will cause the phone to re-optimize all apps, then install an app. After that, you have to reflash the framework every time you update, so best to flash them one after the other, then boot. No point in always optimizing your apps twice. Cyandelta will allow you to select a second zip to flash when installing but CMUpdater does not.
[Verizon Samsung Galaxy S III] Doctorimpossible:
No, I meant the update that was released for 5.1 today. The old version worked for me but today's update put me in a boot loop or something like that
[Verizon Samsung Galaxy S III] Master Cylinder:
Oops! Um, I can't try it right now and may never be able to try it ....:crying:
[Verizon Samsung Galaxy S III] Rushead:
I read somewhere about a guy who removed his power button entirely. I never had to resort to that, but I never use mine unless absolutely necessary. New buttons are super cheap on eBay, and it looks doable if you have a good soldering iron. But you could start with removing it.
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah, I saw a video on it, and he shows how to start the phone without the button! (I have a cheap soldering iron.) If a new battery don't fix it, that will be my next step.

I hate to contemplate the step after that, though.:(
[Verizon Samsung Galaxy S III] AyUaxe:
So sorry to hear, MC! May I suggest that you try one more red neck engineering procedure? You described it landing flat on it's face as the cause of the failure. Try the converse-i.e., slam it on its back. Might sort of re seat whatever was knocked loose.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Edit: didn't realize you meant the latest, ignore the rest of this post.

Don't know which alpha I'm on for 5.1 (if there are multiple releases... I wish they'd consolidate) but it works flawlessly for me. It depends more on the Xposed modules themselves, some do not support the alpha builds, and therefore bootloop, such as XInstaller (I think is the one)
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh::laugh:

Oh, that's a good one! In fact, I've tried it but without the force of the original crash. I'm waiting on that as the most desperate last resort!

:laugh::laugh::laugh:
[Verizon Samsung Galaxy S III] CasualCore:
Time for an upgrade!

I decided now's a good time to update my ROM, seeing as I haven't in a year or more. Currently running MOAR 8.0 on ML1/4.3. Do I need the firmware included in the modem link if I'm already at MF3 firmware on the phone? Can I dirty flash this over my existing setup or should I wipe clean first? Prepping for this update soon, thank you for posting it and the nightlies!
[Verizon Samsung Galaxy S III] Master Cylinder:
I think MF3 is a firmware for an ATT S4? You're probably on MF1 or ML1.

There's no foolproof way to tell, but if you're using TWRP, you can use the TWRP command line, or adb shell into the phone while it's in recovery and run:

getprop ro.build.description

getprop ro.build.fingerprint

They give the same info in slightly different formatting.

I get "d2vzw-user 4.1.2 JZO54K I535VRBMF1 release-keys" with the first one, and

Verizon/d2vzw/d2vzw:4.1.2/JZO54K/I535VRBMF1:user/release-keys with the second one.

That comes from default.prop. You could look at that file, too, or pull it or copy it out. If you're using CWM or Philz, you'll have to look at the file directly for those entries because CWM based recovery accesses build.prop which is never accurate for the firmware either inquiring through the command line or adb shell (EDIT: I have some uncertainty on this second one.) Same is true for if the phone is booted - the command will pull from build.prop. I don't think you can see default.prop when the phone is booted.

But, that's just for fun because it won't hurt anything to flash it anyway, then the NE1 modem after, as long as you're NOT on a 4.4 base ROM and I535VRUDNE1 firmware.

Welcome aboard! :good:

PS - Oh, and best to clean flash if coming from an older JB ROM.
[Verizon Samsung Galaxy S III] CasualCore:
Based on your first sentence, I am on MF1 and 4.3 base, and I can guarantee it because I upgraded the modem to ML1 for this build of MOAR. I found it to be a nice upgrade feature instead of having to redo the ROM from a different base. So you would still recommend flashing the program that comes with the NE3 modem first, and then the modem after?

Thank you for having me and answering quickly! Just want to cover all bases before I dive into a new ROM.
[Verizon Samsung Galaxy S III] Master Cylinder:
There are 2 files in that link: "d2vzw_VRBMF1_firmware.zip", which has it's own modem, (if you say it has the NE3 modem in there, I can't argue because I can't remember) and "d2vzw_VRUDNE1_modem.zip" which is just the NE1 modem which is an upgrade to all modems, and the latest. (and probably last.)

Flash VRBFM1 first, then VRUDNE1 = Success!

Or:

Flash VRUDNE1 = Success!
[Verizon Samsung Galaxy S III] CasualCore:
Not too painful at all. After backing up files: clean reset, flash firmware, flash modem, flash CM 12.1. I think I can handle that. :D
[Verizon Samsung Galaxy S III] Master Cylinder:
You'll love it!:angel:
[Verizon Samsung Galaxy S III] Master Cylinder:
Woops! Flash some GApps!!
[Verizon Samsung Galaxy S III] CasualCore:
Oh yeah, that would be what I intended during the last step. :cool: 12.1 and then GApps.
[Verizon Samsung Galaxy S III] AyUaxe:
Def nandroid back up your last good set up, too. I'm the local heretic who also recommends flashing decimalman's dkp kernel, which you can do later, if you want. I think it provides better battery life and performance.

Also see of you like trebuchet or now launcher. I think many have found they prefer Apex or KK launcher. I like KK.
[Verizon Samsung Galaxy S III] Master Cylinder:
phhhhttt! :mad:
[Verizon Samsung Galaxy S III] Master Cylinder:
Nova Launcher Prime!! Fastest paging animation. And Material Design and Lollipop features. But, Apex for free perhaps - has gestures included. Can't live without gestures.

Another heretical suggestion: Xposed Framework with Gravity Box. But, I don't know what version I have - can't get into my phone at the moment.
[Verizon Samsung Galaxy S III] phonetool:
Even Nova Launcher free version is better than Trebuchet. Better than most launchers, actually. It's my favorite.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Off topic, so I apologize, but I've always liked apex more than nova. I have Premium for both, but I feel like apex is lighter/cleaner or something...
[Verizon Samsung Galaxy S III] Master Cylinder:
Really, considering someone coming to AOSP and cm12 for the first time, this topic can be helpful to them because it will be a culture shock. And, these 3rd party launchers add ease of use and functionality to the ROM that is head and shoulders above the stock launcher. People can get lost on how to proceed with the stock launcher it seems to me.

:):good:
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I use the Themer app. :D
[Verizon Samsung Galaxy S III] phonetool:
"Massive APN update" in the changelog for the upcoming nightly. I wonder if that will help anyone's connectivity.
[Verizon Samsung Galaxy S III] AyUaxe:
Themer is a new one for me. Just tried it and it does seem snappy and worked well with my preferred icons, etc. Installed size is 28+MB. KK is under 16mb installed and in use. Based on apk size, I assume Nova and Apex are close to KK in installed size. Is it foolish to care about 12mb difference in size? I'm curious about what others think.

---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------

Thanks for the heads up!
[Verizon Samsung Galaxy S III] ZiQn3zZ:
Sorry for staying Off Main Topic, but if you guys want customization, you should try out Buzz Launcher. It allows you to do almost anything you want from different backgrounds on every page, custom icons per app, gestures, etc. Plus, the app is in constant development and they actually listen to the community.
[Verizon Samsung Galaxy S III] Gibscreen:
Anyone having issues with the Dialer crashing? If my screen is on and I get a call the phone becomes virtually unresponsive. Can't answer the call.

If the screen is off when the call comes in it works no problem.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I definitely have quite a long delay before I can accept the call, but it's not unusable like you describe
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I had that happen to me too. I couldn't answer an incoming call. Now, I can't remember which build that was. I'm on the 06/29 build now.
[Verizon Samsung Galaxy S III] phonetool:
XDA needs a "me too" button.
[Verizon Samsung Galaxy S III] AyUaxe:
Me too. Just a delay, not unusable.

Interesting that it's a common problem. I thought it was my ham fisted under/over clocking and under volting. Things are a little slow to wake at min 54mhz/790mv. Bumped min to 805mv and that's been much better, stable, good battery, and cool. Max is 1782mhz/1175mv. Hitting it 1% of uptime and stable. Anything above 1782 immediately locks up. If anyone has guidance on mv settings for ocing, that would be appreciated.
[Verizon Samsung Galaxy S III] Master Cylinder:
Phone Works, Sort Of

Ola All!

Got my phone to work again from a stuck power button! Resurrected!

I had the logic board out maybe 20 times working on that switch to try to get it functioning, with alcohol, canned air, WD 40, different kinds of force on it, repeat. It's working but it is a little flaky, like it activates twice frequently when I push it, meaning it turns the screen off and immediately back on, or I can't get to the Power Menu.

However, it turns out you can run your S3 without a power button! You can set a double press of Home Button to turn screen off (and/or the double tap the status bar, which doesn't always work.) I put a ROM Toolbox widget on the home screen that is the 'Rebooter', which gives access to all power menu options plus some.

The only thing is turning the phone on from a power off, but you can do it by putting in the charger and when the battery icon appears, immediately pull the cable and pull and reinsert the battery (back off first.) BAM! It's booting.

Now I'm back in business and waiting for the next nightly!

If that power button continues to give me problems I'll just have to amputate it!

:):):):)
[Verizon Samsung Galaxy S III] Deliquified:
The symptoms with mine are predictable. If the power button is stuck on boot, it won't boot past cyanogenmod screen. If it sticks during use, it will bring up the advanced reboot screen and reboot about 5 seconds later. Smacking above/below the power button fairly hard will get it to boot again until the power button decides to trigger again.
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah, probably most of what I was doing didn't help. Just got to whack it harder next time!
[Verizon Samsung Galaxy S III] AyUaxe:
http://m.youtube.com/watch?v=rL9-Va6_SVY

Go to @ 3:10 for the relevant "instructable."
[Verizon Samsung Galaxy S III] NeoTrantor:
Same here. Any suggestions on what's wrong there?
[Verizon Samsung Galaxy S III] Master Cylinder:
That's out of control!!!

I can't even comprehend the neuronal connections that ended with that link up.:silly:

Love it, though. Sword was a cakewalk compared to Omaha.
[Verizon Samsung Galaxy S III] AyUaxe:
I'm all about "Anything mechanical, give it a good bash!" If it worked for a tank, it can't be far off for a d2. The bulldog is also key. On yours, are you able to see any broken solder connections to the switch? Might need a magnifying glass to see, but if so that could be a slightly delicate but pretty easy fix with a small soldering iron, instead of a shaleighly. Eagle Rare Bourbon is an excellent neural transmitter.
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh::laugh:

LOL! Oh man. Well, that is probably why my fix is not quite 100%: I have neither a bulldog nor any Bourbon.

PS - I examined that dang thing over and over again, WITH a magnifying glass. It looks perfect from the outside. It clicks perfectly, even when it ain't workin'.

See the last post on this page for a postmortem autopsy on the switch under a microscope. (Proof that phone geeks like us really need to get more varied activity in our lives ...)http://forums.androidcentral.com/t-...roken-power-button-galaxy-s3.html#post4033209

EDIT: shaleighly - totally missed that the first time I read it. So, that's what a sheleighly is? I need to get me one of those for my tool collection. (sorry to be so off topic, but this is tooo much fun! Shillelagh)
[Verizon Samsung Galaxy S III] bmeek:
FYI, if you've had to remove your faulty power button (as i did), the idea of having to pull the battery while turning on the phone is a myth.

If the phone is powered off with the battery inserted, simply plug in a live power cord and then immediately press [home] & [down-vol] simultaneously. This will bring up the download screen which says to press [Volume up] to Continue (downloading a custom OS), or [Volume down] to "Cancel (restart phone)". Just press [Volume down] and it starts/boots normally.

I'll have to check out your mod for dealing with the lack of a power button, but I've been very pleased with an app in Play Store called "Button Savior": https://play.google.com/store/apps/details?id=com.smart.swkey
[Verizon Samsung Galaxy S III] Master Cylinder:
Ho! I had tried the Download mode method but I guess I didn't get the instruction to do it immediately after plugging it in. That does work! Thanks!! However, the battery trick works on my phone anyway. I just did it again. Put the cable in, as soon as the battery image shows for the first time, pull cable and battery out-in. But, not necessary because your method works better.

As for the Button Saver app, I'm gonna give it a try! :good:
[Verizon Samsung Galaxy S III] bmeek:
Huh... I've never had much use for ROM Toolbox, but i didn't know it had such widgets...

For this need, I noticed that the AICP ROM, unlike the cm12.1 that it's based upon, includes an optional Quick Settings tile for bringing up the Power Menu and another for turning off the Screen.