yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] prdog1:
My guess is when they have a Verizon S3 4.2 base available to work with. :cool:
[Verizon Samsung Galaxy S III] xoxo_xdagirl91:
Love this rom. Only thing I really wanted added was the xperia z lockscreen and I asked Arsaw if he could do it and he was nice enough to do it. So I figured I would share it with you guys. Here's a flashable zip for those who want it. Make a backup just to be safe & go thank Arsaw :) this is only made for synergy so don't try to flash it on other roms. It will also replace the aosp lockscreen with the xperia z lockscreen. Here's the link for anyone who wants it http://www.mediafire.com/?s42jsteji899r7f :good:
[Verizon Samsung Galaxy S III] Sgt Fury:
I searched pages of this forum to no avail so I apologize if this was already answered. I have been r484 with ziggy kernel some time and have had much success but only recently have not been able to get 4G. Did something change. Is there something I need to update?
[Verizon Samsung Galaxy S III] msteege:
Were do you download jelly bomb ?

Thanks
[Verizon Samsung Galaxy S III] :
Been trying to get callrecord to work on this rom but no luck

I installed modified secphone apk and I tried xspose enable call recording mod

Both do the same thing when press record button it doesn't start recording it does nothing

Mods work on MB1-MB4 built roms

not sure what rom base synergy was built off of

Any suggestions:confused::confused::confused::confused::confused:
[Verizon Samsung Galaxy S III] prdog1:
There is no call record framework in Verizon base. It has hybrid framework from Verizon K3/MB1 and Note. Skvalex's call recorder works. :cool:
[Verizon Samsung Galaxy S III] Aquila76:
Try pulling the SIM and Battery for about 30 minutes. That forces the new equivalent of a PRL update.

I wonder if this may not be ROM related. I used to get a strong 4G signal at home, but last week or so have been lucky to get 3G, falling to 1X often. I'm on 484 with BMB1. Maybe a tower update nerfed some towers?
[Verizon Samsung Galaxy S III] :
Ill give Skvalex's call recorder a try :D:D:D:D:D:D:beer::beer::beer::beer:

I have a little knowledge framework do you no what files I can add
[Verizon Samsung Galaxy S III] prdog1:
They were stripped from the Base by Verizon/Samsung due to legal liabilities. :cool:
[Verizon Samsung Galaxy S III] lord-dogbert:
Stability

After 1.5 weeks of running on the stock kernel I am fully happy with no lags, crashes or other issues that were experienced on Ziggy. I had left Ziggy with the defaults during the original install. Battery time is better now as well but I don't have specifics on this besides casual observation and i'm no longer at 50% after 4 hours of being normally used, running about 80-85% now with the same usage pattern.:fingers-crossed:
[Verizon Samsung Galaxy S III] rodstar87:
Any idea to what this might be??

http://www.sammobile.com/2013/06/19/sammobile-prepare-your-flagship-device/

4.2 JB update Finally?? Maybe??:confused:

Sent from my Galaxy. According to Verizon Ima Grandfather. :D
[Verizon Samsung Galaxy S III] Addiso:
Most likely for international models.
[Verizon Samsung Galaxy S III] DigitalMD:
The current Flagship device is the S4. It's certainly not 4.2 for Verizon since they can;t even get the latest 4.12 OTA / modem to work yet.
[Verizon Samsung Galaxy S III] prdog1:
S4 already has 4.2. It is a wait and see. If legit could be official for International as they already have leak or it is a leak for a US carrier. My guess it is probably official for International. SamMobile don't really care that much about us.:cool:
[Verizon Samsung Galaxy S III] pnyboy27:
Hey guys,

This is actually for my gf's phone. She's had this ROM for a while, and we haven't updated it so it was a little behind. Today, we decided to update the ROM. Since it was a long time ago, I don't remember which version of the ROM she had. So prior to installing it, I did a complete wipe of the phone's internal memory and proceeded to the install.

I was able to get through the AROMA installer and choose all the apps I wanted/didn't want. After it was completed, I rebooted the phone and it's been stuck on the Samsung Galaxy S3 screen. I'm not new to flashing ROMs, so I know to wait a while to see if it will boot. I left it on for about half an hour and it still didn't get off that screen. After more time passed, I decided to boot back into recovery and do a complete wipe again and try the installation. Again, the problem persisted. I tried it several times and it constantly got stuck on the SGS3 screen. I decided to give up and wipe the phone completely and just start from stock to end the day and try again tomorrow.

Unfortunately, that was even a fail. I wiped it clean, and rebooted the phone, and it's still stuck on the SGS3 screen. Currently, it's been on there for about 15 minutes. If someone can please help me, that would be greatly appreciated! I recently switched to this ROM on my T-Mo GS3 and am loving thus far. So I know this ROM works, and would love for it to be on my gf's Verizon GS3. Please help!! Thanks in advance!!
[Verizon Samsung Galaxy S III] speedingcheetah:
U sure u selected VZW in the installer....

also, u try selecting stock kernel and not ziggy in the installer...?

u should be able to odin back to rooted stock rom, then flash this rom from there....if all else fails
[Verizon Samsung Galaxy S III] trook:
What recovery are you using? What version also?
[Verizon Samsung Galaxy S III] pnyboy27:
Thanks for the quick reply, but to answer your questions:

yes, I was sure to check VZW and I actually tried both kernels. at first i tried the ziggy, then next stock. still no good for me. i'm currently downloading the stock.vzw_root66 to odin back to rooted stock. then i will try again.

I have the bootloader unlocked from a previous root and rom install i did. i previously had an older version of this rom prior to trying to update to the latest version of synergy.
[Verizon Samsung Galaxy S III] speedingcheetah:
be sure to use cwr recovery...the other one(cant recall name) is not as stable
[Verizon Samsung Galaxy S III] prdog1:
If gonna Odin back might as well grab the MF1 OTA that dropped tonight while your at it. :cool:

I have to disagree. Been doing this a long time. And TWRP is far more stable than CWM on this device. :cool:
[Verizon Samsung Galaxy S III] pnyboy27:
that's actually what i used as well when i tried. i'll try again after the odin.

if i flash the mf1, would that still be bootloader unlocked and rooted? sorry, i come from a tmobile s3 where i don't have to worry about bootloader lock =P

Speaking of my T-Mobile S3, after just a regular reboot, I now don't have mobile data :confused: I checked my APN, and it's blank. I tried creating a new one, but it doesn't add. Any ideas? I'm wanting the same ROM for my gf's VZW S3 and mine so I don't have to mess around with so many different ROMs or worry about updates so much for hers. Thanks again!
[Verizon Samsung Galaxy S III] prdog1:
I have no clue on T-Mobile. Have heard of that and there is a fix but would have to search it. On Verizon I just updated to MF1 and rooted and unlocked. But I used a different method. If girlfriends phone and you are comfortable with Mr Robinsons Route 66 method stick with his MB1 root method for now till we prove out the new MF1 and pull the bootchain. This rom should work fine on Verizon MB1 with stock kernel. :cool:
[Verizon Samsung Galaxy S III] speedingcheetah:
Not from what i have read....several of the rom devs of the roms i have used since i first entered the smartphone world swear by cwr over twrp...but it has been quite a while since i have used twrp...main device i used it on was the kindle fire...hated it....cwm as never given me any issues on any of my devices...i prefer to use physical buttons anyway...

---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------

MF1?

I assume this is fixed version of the last failed update they released?
[Verizon Samsung Galaxy S III] prdog1:
I've worked for and with many devs. I'm anywhere from moderator to Admin on several sites. I have worked with Koush to make CWM work on TBolt. That is all you had. Rezound was Amon RA. CWM didn't work. TWRP was new and went down. The new versions of touch CWM are actually a collaboration of Koush and TWRP touch. It depends on device. I use what works consistant for each device and TWRP rocks the S3.

Nothing was wrong with update and from what I can see they changed the keyboard popup from 2 to one. The modem was bad. That was easy fix since a lot that aren't in full 4G like me don't use the supplied modem anyway. You use the modem that works for your tower situation. It only affected 4G so if on fringe and farther out most look at 3G performance. I noticed it the first day when I went to fringe area and it would not go on web and would not hand off to 3G. Swapped modem and tethered 4G all weekend. I keep modems on card just for that reason. :cool:
[Verizon Samsung Galaxy S III] speedingcheetah:
I had never even heard of TWRP until a year or so ago....anyway...it doesnt matter...both do the same thing....haven't used recovery since i needed to flash rom...when i first was setting everything up..as long as it does what it needs to...they both "rock"

about the update...i am told they just reverted to the mb1 modem baseband and simply released the rebuilt update...named as a new one of cource

---------- Post added at 07:10 AM ---------- Previous post was at 07:01 AM ----------

http://xdaforums.com/showthread.php?t=1768142

i assume that is the newest twrp thread...last several posts are of folks reporting issues...installed anyway...i do like it better...lol...

---------- Post added at 07:38 AM ---------- Previous post was at 07:10 AM ----------

Is there a Synergy rom for the Note 2?

...good friend of mine is fed up with bloated stock on his note 2...and my s3 runs circles around his with this rom...
[Verizon Samsung Galaxy S III] :
I installed Skvalex's call recorder and plugin it ask to install any suggestions on on how get it to record:banghead:
[Verizon Samsung Galaxy S III] Weioo:
So I realized I'm still on r44x, could have sworn I was on the latest. Now I haven't rooted back to stock for some time since around synergy r74, though I have done 'clean installs' of the latest build, including what I'm on now. I have a few questions for you guys...

1. Is the next build coming out anytime in the next few weeks (should I just wait)?

2. If I install the latest build, can I effectively install via clean install or should I at some point revert back to a rooted stock version and then move forward to the latest Synergy? I just feel like I've gone through 12 revs of synergy without ever going back to stock and I hear a lot of people saying they get a better install with fewer issues?

Please advise! :)
[Verizon Samsung Galaxy S III] pnyboy27:
So I'm back. I successfully ODIN'd back to stock and unlocked and rooted again. I tried to flash this ROM yet again, and this time, after it was completed installing, it came up with an error saying something went wrong during installation and to save the log and post in here if the problem persists. So it did, as I tried again several times, and hopefully, someone can review this and let me know what's wrong and how to fix it. In the meantime, I will leave this phone stock, rooted, and unlocked until hopefully we can get this resolved. Thanks in advance!
[Verizon Samsung Galaxy S III] Biker1:
Google the phrase:

Installer Error, Status 7

I saw this in your file.

I found this:

http://forums.androidcentral.com/ve...002-status-7-error-when-flashing-any-rom.html

ROM, Recovery. Check them both out to be sure updated and correct.
[Verizon Samsung Galaxy S III] :
Got callrecording to work on this rom with Callrecorder

Link

http://xdaforums.com/showthread.php?t=1441643

I use posted setting from this link

http://xdaforums.com/showthread.php?t=2224730

:D:D:D:D:D:D:D:D:D:beer::beer::beer::beer::beer::beer::):):):):):):)
[Verizon Samsung Galaxy S III] pnyboy27:
Wifi Not working

So I was able to successfully install and run the ROM which worked out great. Only problem now is that my wifi isn't working. It worked when I first used it for a while, then all of a sudden, it stopped working. Either when I use the quick button at the top, or even under settings, wifi won't turn on. It just automatically turns off again. So I looked in the forum, and tried several things like restarting the phone, removing the battery, and even tried flashing the KT747 for JB TW 4.1.2 Kernel for VZW. When I did that, upon rebooting, it came with the Verizon error stating that I need to take my phone to the Verizon store and show that it has a custom install and blah blah blah. So now, I'm ODIN'ing back to stock, and reinstalling the ROM. So besides flashing a new Kernel, does anyone have any ideas? Any help would be great! Thanks in advance!

Oh, and BTW, when I flashed the ROM, I used the stock kernel. Thanks!
[Verizon Samsung Galaxy S III] prdog1:
If on MD3 firmware will break camera and wifi. KT may have fixed it but that Verizon message means your bootloader was still locked and can't run custom kernels. :cool:
[Verizon Samsung Galaxy S III] pnyboy27:
I'm on the MA2 baseband. I should be fine with the KT kernel, correct? Thanks!
[Verizon Samsung Galaxy S III] prdog1:
Yes. But I would update to at least MB1 or MF1. MA2 was an unofficial leak and was trashed. :cool:
[Verizon Samsung Galaxy S III] pnyboy27:
Should I update to MB1 or MF1 first? Then update the kernel? Or does it matter? Thanks, just wanting to make sure I don't break it again and go through the time and pain to start from the beginning. And while we're on the topic, what's the benefits of MB1 vs MF1? I'm a T-Mobile user, and this is for my gf's phone. So I'm slowly learning more about Verizon. Thanks!
[Verizon Samsung Galaxy S III] prdog1:
MF1 is the modem/firmware released yesterday. MB1 is the last working Modem/firmware prior to that. MD3 was pulled by Verizon due to connectivity problems. I know MB1 will work with Synergy. Have not tested MF1. It may break camera and wifi. The TZ file in MD3 bootchain was not compatible with MB1 roms and could be same with MF1. If this is the case could still run MF1 modem with MB1 TZ. Kernel install doesn't matter they go to different partitions. :cool:.
[Verizon Samsung Galaxy S III] pnyboy27:
I just wanted to let you and other people know that that solved it! Thanks! I had to make sure my bootloader was unlocked again, and updated the firmware and kernel. Thanks again!
[Verizon Samsung Galaxy S III] sgs22012:
Any word when this might get aroma support?

Sent from my GT-I9505 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] Biker1:
:confused:

r484 already has Aroma support
[Verizon Samsung Galaxy S III] sgs22012:
No for the s4

Sent from my GT-I9505 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] Biker1:
I thought that's what you might of meant, but this is the S3 thread, which is why I wasn't sure.

I read in the S4 thread they're working on it, and I'm sure it'll be available soon.
[Verizon Samsung Galaxy S III] Digital DJ:
Hey guys, I received my GS3 back from Jtag in awesome condition! But now I'm in love with my GN2 and am selling my GS3. I have rooted it again, not unlocked bootloader yet, but plan on it. I can't seem to get this rom to take. I keep getting stuck in boot loop. I've tried formatting data, and internal storage, but still get stuck in boot loop. I have latest twrp 2.5 and synergy r484. I have it on my extSDcard. Can't think of what I'm missing... any help would be appreciated.

Edit: I tried flashing a CM10 rom for Galaxy S3 and now Im stuck
[Verizon Samsung Galaxy S III] theinvisiblemooseman:
You are getting this message because your bootloader is locked.
[Verizon Samsung Galaxy S III] Digital DJ:
Thats what I thought, I haven't unlocked it without that app before EZUnlocker. So how would I unlock now...?
[Verizon Samsung Galaxy S III] schneid:
You might try this:

http://xdaforums.com/showthread.php?t=2332825
[Verizon Samsung Galaxy S III] Digital DJ:
I've tried that, the problem is I have no way to get in and Enable USB debugging...ugh
[Verizon Samsung Galaxy S III] Biker1:
http://xdaforums.com/showthread.php?t=2046439
[Verizon Samsung Galaxy S III] Digital DJ:
I should probably note that I got this phone back from JTAG and they put Android 4.0.4. I already rooted it easily, but never unlocked the bootloader (my mistake I see now). When I tried to flash r484, it didn't work. then I tried flashing CM10 and that's when I got the triangle exclamation screen stating this system software not authorized by verizon wireless..blah blah blah... Anyway, it seems I need to have an unlocked bootloader. I'm trying to get it but I

m not sure that last link will help as it is for rooting when already on Android 4.1.2 or higher I believe. Still trying though.
[Verizon Samsung Galaxy S III] keithrich1990:
I had the same problem to get mine off the contact the nearest verizon store I used the buttom combination to get into download mode then just removed the battery restarted the phone and it booted up and I used ez ulock to unlock the bootloader.
[Verizon Samsung Galaxy S III] Digital DJ:
Hmm, well that isn't working for me either. I don't even think I have a rom on it yet. This happened while trying to flash a rom...lol
[Verizon Samsung Galaxy S III] s197:
Pull battery. Boot into download mode and load one of the stock files via Odin. Once the phone is booted you can swap bootloaders.
[Verizon Samsung Galaxy S III] keithrich1990:
The only other thing I know to do is flash back to stock through Odin
[Verizon Samsung Galaxy S III] Digital DJ:
Any way you could be a little more specific on 'stock file'? I'm following this thread http://androidfirmwares.net/Guide/Details/9 right now, but the stock firmware all looks like they're from other countries? I'm not sure if they'll work. Plus they look like they are all for the GT-I9300 I have the I535
[Verizon Samsung Galaxy S III] s197:
http://xdaforums.com/showthread.php?t=1974114
[Verizon Samsung Galaxy S III] Digital DJ:
I'm not on stock jellybean. Can anyone else help?
[Verizon Samsung Galaxy S III] s197:
It doesn't matter, all you're trying to do is get your phone to boot. You can switch to whatever ROM you like afterwards. All you need is an Odin flashable stock image. If you take the time to read the thread it walks you through the entire process.
[Verizon Samsung Galaxy S III] Digital DJ:
Ok man, I'm sorry. I'll try this method. I ran a very similar method in a link I posted a few posts back and it didn't work. I'm very frustrated with this, thanks for not punching me....yet

Edit: Question, after I do this assuming it works, do I have to flash a recovery via ODIN or could I use say Goo.im?
[Verizon Samsung Galaxy S III] keithrich1990:
after you get back to stock use this http://xdaforums.com/showthread.php?t=2332825 it will root unlock the bootloader and flash a recovery
[Verizon Samsung Galaxy S III] prdog1:
I would just run the new casual. Should fix it all. We had this originally but JB broke it. Not sure if have to be on stock OTA to work. Haven't tried yet. :cool:

http://xdaforums.com/showpost.php?p=42791826&postcount=1
[Verizon Samsung Galaxy S III] keithrich1990:
He says he does not have an OS on his phone
[Verizon Samsung Galaxy S III] prdog1:
HaHaa. Got Ninjad by a XDA newb. Don't happen often. :laugh::cool:

---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------

He also blamed his son for bricking it. If no OS have to Odin. :rolleyes::laugh::cool:
[Verizon Samsung Galaxy S III] nitric13:
Mf1 radio update borked the camera...

How do I fix the camera?

I'm on r484 with ziggy kernel
[Verizon Samsung Galaxy S III] Biker1:
Flash your Nandroid you made before flashing MF1 ;)

Or perhaps dirty flash the Ziggy or stock kernel from Aroma in r484.
[Verizon Samsung Galaxy S III] andybones:
flash back to mb1 radio..
[Verizon Samsung Galaxy S III] Digital DJ:
My GS3 is fixed, and rooted....ready for sale. thanks for your help guys....and 197
[Verizon Samsung Galaxy S III] prdog1:
It's not the Modem/radio. It is the TZ. Is gonna be that way from now on. They are not gonna back down the security to run something we are not supposed to run in first place. They will try to fix signal and that is what they did. Flash this MF1/Mb1 hybrid and you are good to go. :cool:

http://d-h.st/SzK
[Verizon Samsung Galaxy S III] nitric13:
Thanks but no luck in getting the camera back..flashed the link modem...reflashed mb1..reflashed zeggy kernel...reflashed r484 w/ ziggy..

Camera failure....

Last step is doing a complete wipe and install :(
[Verizon Samsung Galaxy S III] Biker1:
Did you flash your Nandroid that you made prior to the flash that borked the camera?
[Verizon Samsung Galaxy S III] nitric13:
Nope...didn't cause I thougjt this was a radio/modem only update
[Verizon Samsung Galaxy S III] Addiso:
Try ktoonsez kernel
[Verizon Samsung Galaxy S III] nitric13:
FML

full wipe and install of rom didn't fix camera...

time to revert to stock and go to verizon to get a new fone

the one time i don't backup ----i get shafted...

lesson learned
[Verizon Samsung Galaxy S III] Addiso:
Did you try ktoonsez kernel and a note 2 camera at the same time?
[Verizon Samsung Galaxy S III] Mystikalrush:
Just revert back to w/e radio update you have prior, i had MB1 and it fixed the camera issue.

http://invisiblek.org/sch-i535/firmware/

Pick the correct one you were using prior to flashing MF1

*edit* These files are all in one, so modem, rpm, and tz it will fix your issue garantee.

You shouldn't have wiped your entire phone. it has nothing to do with it, you updated the radio, etc. and it broke stuff, so put back what you replaced, not the whole OS
[Verizon Samsung Galaxy S III] pnyboy27:
So I finally got this ROM fixed and working almost perfectly. I don't have multi-touch working on the nav bar to reveal more of my Gmail. You know that two finger swipe to reveal more or less of the email? It doesn't work on mine. Anyone have that problem and a solution? Thanks!
[Verizon Samsung Galaxy S III] schneid:
Okay I am rock solid without issues TW kernel Synergy r484. This is okay to flash without borking my setup? Or, is it just a waste of time? And, I flash from TWRP?
[Verizon Samsung Galaxy S III] jlyle:
So if you revert back to stock ( run Odin ) your camera will be fixed .LOL :cool:
[Verizon Samsung Galaxy S III] tainle:
hey i noticed that this rom has two "Gallery" icon, one is the purple color icon and one is the yellow flower icon which is for galaxy s3 default Gallery. i cannot uninstall both. do you guys have two "Gallery" as well?
[Verizon Samsung Galaxy S III] Biker1:
Yes.|

The more, the better ;)
[Verizon Samsung Galaxy S III] Hobart!:
Ok I have been reading for days about this new firmware breaking camera and I am confused on when its ok to flash it or not.

If rom is md3 or mf1 based its ok

If its mb1 based it will break wifi and camera unless you flash a hybrid zip with mb1 tz.

So since synergy is mb1 it should break but the hybrid zip with mb1 tz is ok.

Am I on the right track here prdog? I know I can just flash but I want to understand before I do..lol

If I flash a md3 or mf1 based rom do I need to then flash the full mf1 package or will the hybrid be fine?
[Verizon Samsung Galaxy S III] Addiso:
As long as the kernel's are updated to md3 base all roms will be good, if not yes a rebase to md3 it later will fix the camera situation.
[Verizon Samsung Galaxy S III] prdog1:
You got it. Hybrid zip will work on any rom/kernel combo. :cool:
[Verizon Samsung Galaxy S III] bobcaruso:
Nope, Camera still borked on TW rom with Leankernel 2.4
[Verizon Samsung Galaxy S III] prdog1:
Been reported that kernel breaks camera. :cool:
[Verizon Samsung Galaxy S III] Hobart!:
Flashed hybrid zip from prdog and all is well. I am on baseband mf1 with stock kernel mb1 synergy 484...camera works..thanks prdog
[Verizon Samsung Galaxy S III] prdog1:
Kewl. Only custom kernels I know of that work and support exFat are latest KT and one not on XDA. :cool:

MOD Edit: Please do not discuss work from banned members