yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Ahh, my apologies: if you open the zip file itself and click through the metainf folder, through com, google, android: you will find an updater-script (just a text file), in there you'll find the line (assert<device info>) just remove it and rezip the file. (as I mentioned before you do generally want to be careful removing asserts, etc from there but being that you have confirmed the device already that shouldn't be a problem: just don't go trying to flash it on another device ;) )
[AT&T Samsung Galaxy S II SGH-I777] igayan1991:
Thanks bro! Got it!

As i Have a backup through CWM, there won't be anyrisk? Isn;t it?

So if anything happens I can restore?
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Well you should always be making a backup before flashing any rom. Otherwise the only risk when removing an assert from an updater script is if you are trying to flash that on a device other than the one it is intended for; if you did that it really wouldn't matter if you had a backup or not in a lot of cases as you probably wouldn't be able to get back into recovery (being that recovery is wrapped in boot at least on this device), that's why I was stressing the point of making sure your device was the right one.
[AT&T Samsung Galaxy S II SGH-I777] igayan1991:
Thanks for all the help bro.

I installed Siyah 4.3.3 kernal and then the ROM without any issue.

Only problem after that is it requested network lock PIN:eek: I got this through ebay and it was unlocked by them.

So I restored the backup! No still it requests SIM network unlock PIN:mad:

I found a zip named galaxyS unlock on my internal memory. Anyway I can unlock it by that?
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Hehe, yeah; I activated mine on straight talk and it required a sim unlock pin as well. I just called ATT the rep was very nice and gave it to me in a matter of minutes (do to recent legality changes (around the beginning of this year) unlocking via exploit is no longer something we can assist with).

Edit: just to be clear, rooting your device is still OK of course. Sim-unlocking however is considered a federal offense without a proper unlock code from the original provider.
[AT&T Samsung Galaxy S II SGH-I777] igayan1991:
:good:thanks. Solved all the problems and installed the new ROM.

All good:D except it heats the devices than previous rom.
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
We are now Official!​

Thanks to [MENTION=3973140]Sblood86[/MENTION] and [MENTION=4209428]bluefa1con[/MENTION] the i777 is now officially supported by Pacman! I have updated the OP with [MENTION=3973140]Sblood86[/MENTION] buildbot. We have been having some issues getting it to boot correctly; I'll leave it to him to explain what's up with that though.

Expect a 4.3 build soon!
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Yeah, basically there's an issue booting 4.3 on exynos4 devices; while it boots fine the first boot getting it to boot after the initial configuration is a bit hit and miss (this is occurring on the i9100 and several other exynos4 devices), generally if you do a factory reset a second time after the initial config then reboot and do it all again it works, I just consider this to be a little less than user friendly and have been disinclined to update the dependencies for 4.3 until after this is resolved. If enough people want to fiddle with it anyway I may be willing to push the updates to the pacman gerrit but in my opinion that's a pretty decent reason not to release a build ;)

Goo.im is more or less done as far as pacman builds are concerned so don't expect any GooManager notifications, there is a new OTA platform for pacman but I've yet to read up on it too much (being semi-lazy on account of the stability issues) so there should still be some form of update notifications in the relatively near future but not until after manually updating to the newer builds (after they are released).

Questions, comments, etc; let em fly :D
[AT&T Samsung Galaxy S II SGH-I777] AJ Newkirk:
Thanks for picking this up Sblood86!

Is there a reason that the maintainer did not start a thread of his own?
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Well I had discussed the matter w/ [MENTION=4516744]IconRunner[/MENTION] before even pushing my initial changes for 4.2 to the PAC-man gerrit, not wanting to step on any toes or anything and he said he would like to continue to maintain the thread to keep device history etc (I did in fact offer to create a different post as to do full maintenance myself but this was only an offer as I did not want to usurp anything).

To that end I won't be taking over all the thread maintenance (need to [MENTION=4516744]IconRunner[/MENTION] to the contributors list for PAC-man as well, figured I would when I pushed the 4.3 changes) though it is likely I will be handling most (if not all) of the code changes (updates) for the i777 (not that their are a lot of changes the dependencies, etc are nearly identical to that of the i9100 (right down to the kernel the only difference is the primary device tree itself).
[AT&T Samsung Galaxy S II SGH-I777] AJ Newkirk:
I feel like that is going about things in the wrong way, as this is no longer IconRunner porting an i9100 ROM to the i777. The developer should be the thread maintainer. But I will respect your decision and hope that you might revisit this down the road.

Thanks again for picking this up :good:
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
Yea, it's still sort of in interim. We might end up switching over still, depending on how [MENTION=3973140]Sblood86[/MENTION] wants to handle pushing updates. I had expected to update links in OP and push thread updates to let people know when new major updates come through, freeing up [MENTION=3973140]Sblood86[/MENTION] to focus on the Rom instead of dealing with thread maintenance.
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
I'm just happy to see my favorite ROM still alive and kicking

Sent from the second to last Galaxy

PACman Rom 23.0

STI kernel 2.38
[AT&T Samsung Galaxy S II SGH-I777] SkVergil:
I'm looking forward to install this ROM. But I see two links, the PAC i777 23.0.2 IconRunner and the milestone 1 RC1. Which one is the latest one? I'm taking a guess that it's the 23.0.2 one...
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
The ones that are not "Official" are Deprecated and will only be left until we have two Official builds. They are there only as a fallback in case a fatal bug shows up in the Official build.
[AT&T Samsung Galaxy S II SGH-I777] SkVergil:
Thank you. Went with the "Official" one.
[AT&T Samsung Galaxy S II SGH-I777] bluefa1con:
cm started nightlies with that bug, thats why i started mine on i9100

as for thread just wait for devDB to hit i777 forums and more than 1 person can control the thread, its up to the maintainers who wants to maintain the thread, users please dont discuss this as its between them

[MENTION=4516744]IconRunner[/MENTION] can u make a gif for pacman 4.3 like the one in OP? it looks amazing
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
Cool deal! Looking forward to the new stuff!

And yea, I can put together a gif for 4.3, just PM me any images or logos you have and I'll whip something up.
[AT&T Samsung Galaxy S II SGH-I777] bluefa1con:
I am really bad a taking catchy screens shots lol because my phone keeps running experimental patches and i have to wipe

Users submissions are always welcome
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
does the officiak require a full wipe if coming from the old ported one?
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
I'll take the screenshots (needs to fit my .psd template), just if there're any Pacman logos or decals you're using it'd be nice to get them from the source.
[AT&T Samsung Galaxy S II SGH-I777] jaysix79:
I would recommend a full wipe. And don't forget to flash the new gapps.

P.A.C 4.3 ALPHA
[AT&T Samsung Galaxy S II SGH-I777] dashrendar:
Hi guys,

I tried this ROM a couple of nights ago. Even though I thought it was very cool, I had to switch to something else (4.1.2-based) because of a Bluetooth dialing issue. I noticed this in two 4.2.2-based ROMs so it seems to be a common bug.

Reproducing the symptom:

Pair and connect a Bluetooth headset. Long-press the Call button on the headset. This will bring up the Voice Dialer. Normally, it would ask you to speak and then display Listening. In this defect's case, it hangs on Starting Up. Then when I press the Call button again or the Back button on the phone, it shows "Error Initializing" or something to that effect for a brief time before disappearing.

I have a Plantronics Voyager PRO+ Bluetooth headset.

It's worth noting that this does not happen if Bluetooth is turned off. In other words, if you click the Voice Dialer icon when Bluetooth connectivity is off.

Also, this has nothing to do with Bluetooth audio. I can hear audio through my Bluetooth phone if I dial the contact manually using my fingers. A few reported that disabling Call or Media in the Bluetooth settings fixes this issue, but prevents the ability to either use the headset for calling or controlling media (i.e. a workaround that de-features the phone)

Voice dialing is something I need because I drive 2 hours every day and it's much safer for me to do that.

Sorry for not providing a logcat for this.
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
I wish more people reported bugs like you do :)
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Sounds very much like a kernel issue, all my builds will be using the CM kernel unless I come across a reason to change this but I'm curious if flashing a different one doesn't resolve that for you; if you feel like testing, you might try flashing [MENTION=577081]AJ Newkirk[/MENTION]'s kernel and try again (incidentally there have been quite a few changes to the 10.2 branch of the CM kernel, I'm debating going ahead and pushing our gerrit commits and linking 4.3 builds with a massive red warning about startup issues...)
[AT&T Samsung Galaxy S II SGH-I777] jaysix79:
If you guys decide to use AJs kernel use 4.5 and up or else you'll come across with status 7 error

P.A.C 4.3 ALPHA
[AT&T Samsung Galaxy S II SGH-I777] asderxsdxcv:
Is this still 4.2.2 or 4.3?
[AT&T Samsung Galaxy S II SGH-I777] SkVergil:
It's 4.2.2
[AT&T Samsung Galaxy S II SGH-I777] asderxsdxcv:
Thanks been away from the android scene in months. Just making sure what gapps to download.
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
I've been running the RC1 and it's been awesome so far. Smooth. I've been getting a small error system ui crashing when on a call or missed call but i haven't been able to pin point to where it's coming from. I uninstalled the newest app I added after the upgrade but still happens. But other than that, runs smooth... Thanks for keeping this project going. I've been on pacman for a few months now and it's great. Once 4.3 gets a little more stable I'll jump on it. :thumbup:

Sent from the second to last Galaxy

PACman Rom MS1 RC1

AJK 4.5 "the boss"
[AT&T Samsung Galaxy S II SGH-I777] elkinjp:
ok, im going to try this rom http://xdaforums.com/showthread.php?t=2140110 with the kernel and if the problem continue i flash http://xdaforums.com/showthread.php?t=2110542!

thanks for the help!
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Re: [ROM] [PORT][JB 4.2.1][PA2.99][AOKP-MR1][CM10.1]P.A.C True All in 1 ROM[09/02][V1

No Lol stop flashing kernels! Just the ROM! I dunno if he's getting it.
[AT&T Samsung Galaxy S II SGH-I777] elkinjp:
i had not flashed any kernel! just the rom! im using this rom and its working amazing! no problems!
[AT&T Samsung Galaxy S II SGH-I777] projekt1:
Found three bugs so far not sure if its just on happening on mine phone.

Bug 1. Time reverts to 3-4 hours behind. "Automatic date & time" and Automatic time zone" are both checked. I have to reboot for it to receive the correct time. However, it reverts back to the wrong time an hour or so after reboot.

Bug 2. After reboot, the volume adjusts itself as if I was lowering then raising it. It goes down 3 times then back up twice. This bug is freaky lol.

Bug 3. When trying to set pattern lock there is no "Next" option visible. It says " Ready to start? Touch Next" but there is no "next button visible".

No DPI settings have been changed from stock. I did and have done again 3 clean wipes through TWRP.

If I'm the only one experiencing these bugs please let me know. I'll keep wiping lol
[AT&T Samsung Galaxy S II SGH-I777] dandrumheller:
Re: [ROM] [PORT] PACman: Paranoid-AOKP-CM TrueHybrid [Feb 9, version 19.9]

#1. Known bug on all 4.2.1 ROMs on this device. Disable automatic timezone and set it manually is the work around.

#2. I believe this is caused by (and is the solution for) the low volume bug fix in the siyah kernel. Try disabling that in stweaks and see if it goes away.
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
Dandrumheller's got the first two covered. The third looks like a thing with your DPI settings. I'm at 180 and I can see (and click) about half of the "Next" button at the bottom of the screen. Looks like a UI error.

Regarding no DPI change, make sure ParanoidSettings is granted SU permissions. SuperSU and Superuser have the "Grant" buttons on different sides so it's easy to accidentally hit "Deny".
[AT&T Samsung Galaxy S II SGH-I777] barnes26:
Re: [ROM] [PORT] PACman: Paranoid-AOKP-CM TrueHybrid [Feb 9, version 19.9]

Been running for 24hrs and not a single issue to report.. Running great
[AT&T Samsung Galaxy S II SGH-I777] Aayush_13:
Notification Bar alongwith Full Pie controls

I have noticed that whenever i enable the expanded destkop, the notification bar disappears........and when the expanded desktop is disabled, I cant see the time and the status of the phone in the pie(only the buttons of the pie can be seen)....Thats where my question arises - Is there a option via which I can keep my notification bar......and also keep all pie controls??? Any Help will be appreciated.....Thanks!!!
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
That's the purpose of Expanded Desktop; replace the notifications bar with Pie. Regarding your not being able to see pie date/time. Go to Pie Settings and set the "Pie Style" to Quick. Enable expanded desktop, activate pie and give us a screenshot of what your screen looks like after being in Pie for 5 seconds.

If you want "Pie" while keeping the notifications bar - install LMT Launcher. I'ts pretty similar to Pie but without the notifications stuff.
[AT&T Samsung Galaxy S II SGH-I777] Aayush_13:
Will give it a try

Well, I'll certainly try out your settings.....but the problem is after 3-4 hrs after i flashed, the phone started to misbehave...i couldn't type , unlock or even scroll proplerly......like someone said earlier, the volume would adjust itself automatically, and random apps would open without me pressing any button.......with much hardwork was i able to finally go to cwm and flash another rom.........Well I read in earlier posts taht it might be the kernel problem, so im currently d'loading your rom with the cm kernel which you mentioned a few posts ago.......will try to run that and update you how it goes.......normally i would have settled for my earlier rom after so much trouble, but i REALLY liked Pacman Rom (I'm not flattering :P)

Will post the screenshots with the new settings after the rom has benn d'loaded.......

ANYWAYS THANKS FOR YOUR INFO....I'll try out the new settings as quickly as possible, thanks again.....!!!!!!
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
Yes, definitely give the CM version a try. It doesn't have Stweaks but I'm getting WAY better battery life, no glitches, and it connects to USB properly. Planning to either support both, or possibly switch to using CM as the main base and providing a link to the latest Siyah kernel for people who like that.

Actually while I'm here, would anyone object to that? Using a CM kernel instead of Siyah until it gets fixed?
[AT&T Samsung Galaxy S II SGH-I777] asderxsdxcv:
Re: [ROM] [PORT] PACman: Paranoid-AOKP-CM TrueHybrid [Feb 9, version 19.9]

I think going for cm is a good idea. It brings it closer to the original and people can always just flash siyah if they want. Keep up the good work :D
[AT&T Samsung Galaxy S II SGH-I777] Aayush_13:
I always prefer a stable kernel, over an experimental one.......If I get better results using CM, I will prefer CM.......U can either fix siyah, or permanently include CM in the roms, and add a link for siyah...(for people who want to try out siyah)
[AT&T Samsung Galaxy S II SGH-I777] Aayush_13:
Here's your Screenshots!!!!

Well, the CM kernel rom is definitely more interesting as well as stable.....having no problems here.....and as asked by you, here are some pie screenshots
[AT&T Samsung Galaxy S II SGH-I777] dandrumheller:
Re: [ROM] [PORT] PACman: Paranoid-AOKP-CM TrueHybrid [Feb 9, version 19.9]

I agree with this completely.
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
Alright, I'll switch to CM and keep the link to the Siyah thread for people who prefer that.

Aayush_13, looks like everything is working with your Pie. Hopefully the CM build fixed whatever problems you were having.
[AT&T Samsung Galaxy S II SGH-I777] Aayush_13:
No problems!!!!

No problems whatsoever......I really like CM now.......phone's perfect.....excellent battery(better than the siyah one) NO BUGS AT ALL.

EVERYTHING'S PERFECT!!!!!! I would also love the option for you to permanently switch to CM.......and give a link for siyah :cool:
[AT&T Samsung Galaxy S II SGH-I777] nuuits:
omg now I'm going to have to stay up all night configuring this after I flash it.

Curse you and have a nice day.
[AT&T Samsung Galaxy S II SGH-I777] IconRunner:
New version ported. This has Paranoid 3.0 but they're still working on getting AOKP fully merged. See the Original i9100 thread for a full changelog.

Note that this and all future versions will be using the latest Cyanogenmod Nightly kernel until Siyah has been fully fixed.
[AT&T Samsung Galaxy S II SGH-I777] MonFrayr:
Re: [ROM] [PORT] PACman: Paranoid-AOKP-CM TrueHybrid [Feb 14, version 19.9.1]

I flashed the update and no wifi. Then I fully wiped and reflashed, still no wifi. May be I had bad download. Will let you know after I give it another go. Really liking what I am seeing from the ROM so far.

EDIT* Redownloaded and same issue. MD5 was fine.
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
If you have these problems post a logcat (try using the CatLog app) - devs generally can't help you otherwise.
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Just a little heads up...

You guys should see 4.3 builds showing up on the basketbuild server soon (just waiting on dibs to run another autobuild). So far everything seems relatively stable once it's booted but there is still the data wipe issue (common to all exynos 4 devices so I'm hoping CM will find a fix soon); do NOT perform a data wipe when updating to 4.3 (the system will fail to load after the initial configuration, you may be able to force this by running another data wipe and configuring it a second time).

The safest, most reliable method if coming from another ROM is going to be to install the rc1 build from 4.2 then update to 4.3 (dirty flash) from it.

If you are already running 4.2 pacman you should be safe to update to 4.3 as a dirty flash.

As I said the builds aren't there yet, but you guys will probably want 4.3 gapps when the builds post; so noone asks which ones, I've been using the 4.3 gapps posted to goo.im : http://goo.im/gapps/gapps-jb-20130813-signed.zip
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
View attachment 2013-08-27-17-15-10.zip
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
Above are my logs for these issues here. Sorry i couldn't figure out how to do it all at once lol. I'm out on the road.

Sent from the second to last Galaxy

PACman Rom MS1 RC1

AJK 4.5 "the boss"
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
Did you get a chance to look into the logs? Let me know if they are good or you need something else. I still have the issue

Sent from the second to last Galaxy

PACman Rom MS1 RC1

AJK 4.5 "the boss"
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Sorry meant to respond sooner, those logs don't provide anything other than basic device info. We'll need you to perform a logcat to be able to provide any real answers.
[AT&T Samsung Galaxy S II SGH-I777] ronron6665:
I can't find the 4.3 ROM download just a log ???
[AT&T Samsung Galaxy S II SGH-I777] alerionn:
same problem as above, really want to try this out :c
[AT&T Samsung Galaxy S II SGH-I777] SkVergil:
Today will be a happy day with this release c:
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
It would appear someone broke something on the pacman buildbot, we were talking about it earlier, I thought it had been fixed but apparently not (going by the most recent log from tonight's unpresent nightly) It's broken for multiple devices, so hopefully should be sorted soon.
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Ahh, logcat only showed in the one post I thought your attached file was the same one. I'll have a look through this other.
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
Thank you for looking into it.

Sent from the second to last Galaxy

PACman Rom MS1 RC1

AJK 4.5 "the boss"
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
Have you been able to review the log? i did a clean wipe and new install and i'm having the issues. I did notice it started happening when I started changing the "system" are playing with the quick settings and what not.

Edit: it appears to be related to the phone apk or something. Every time i get a phone call, the "system ui" crashes.
[AT&T Samsung Galaxy S II SGH-I777] Sblood86:
Yeah sorry I read through it a bit last night and nothing jumped out at me, having said that I'm not generally the greatest for reviewing logcats in the first place lol... Definitely not an issue I've seen/had so I'm disinclined to blame the phone apk itself (should be the cm phone.apk iirc) did you try making any phone calls before you started cahnging settings? (I'm wondering if it's a setting you are using taht I'm not)
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
I did make calls but the problem is when I get a call. Even a text message so it has something to do with the notification bar or something. The only thing I did was changed around the quick settings. But when I was running the old i9100 ported version I had the same settings but no issues. I got a new log today when I saw the issue but I myself can't figure this out. I wish I could figure it out.
[AT&T Samsung Galaxy S II SGH-I777] hoopas:
Am I missing something here? I can't download this ROM from the link, all I get is to view the log of it. Any different links or am I just blind/dumb haha. Really want to try this one:D
[AT&T Samsung Galaxy S II SGH-I777] r_diaz13:
The new build is 4.3 already I think. A couple of pages back it mentions there is something wrong with the compiler I think. The thread owner and maintainer will be doing it soon.
[AT&T Samsung Galaxy S II SGH-I777] asderxsdxcv:
I dirty flash the new nightly i keep getting androir.process.acore has stopped blame. How to fix this? Also Is the data wipe bug still present?

Edit: tried complete wipe and ajk kernel and it worked great. thanks so much. This is a great update.
[AT&T Samsung Galaxy S II SGH-I777] NJD316:
Coming from CarbonRom 831 nightlt I flashed the latest Pacman nightly (did complete wipe), flashed AJ 4.5 kernel before booting and cwm backup worked fine. Great ROM!!!!
[AT&T Samsung Galaxy S II SGH-I777] BInspirinG:
Don't dirty flash. Just clean wipe and install the new 4.3. Works great so far!
[AT&T Samsung Galaxy S II SGH-I777] Butchr:
As soon as you installed a custom kernel you left the brick bug behind you. I never flash dirty. I also always take the extra step to go into mounts and storage and format the system partition in order to clear up any kernel remnants that may be hiding in there to reek havoc with my flash.
[AT&T Samsung Galaxy S II SGH-I777] asderxsdxcv:
I dirty flash cause its mentioned a few page back. But all well that's end well. The 4.3 update is amazing.