yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] crt60:
So are you following the instructions in the op, factory reset, format system, wipe dalvik cache?
[Captivate Android Development] robm1911:
HA!! Finally ninjed the man!!! lol

Sent from one of my "Collected" devices.
[Captivate Android Development] crt60:
I guess I need to take back that turtle comment I made, a true Ninja in da house...
[Captivate Android Development] robm1911:
Nah, the turtle stays. Guess I'm just having a better than normal day lol

Sent from one of my "Collected" devices.
[Captivate Android Development] Xenux92:
Every step followed mate, data factory, cache partition, dalvik, battery stats, wiped!

Is the problem with every ROM I'm flashing! Gb working fine!
[Captivate Android Development] topiratiko:
Did you format /system?

Android Open Collective Project

Samsung Galaxy SII

Siyah 501
[Captivate Android Development] Kyuta Syuko:
He's a Ninja Turtle!
[Captivate Android Development] startngate:
I am getting a File Not found error when trying to download from the link in post 1. Any mirrors out there?
[Captivate Android Development] robm1911:
Hmmmmm yeah I got the same, hang tight and I'll upload a mirror to drop box.

Edit: Download Mirror is up in post 2

Sent from one of my "Collected" devices.
[Captivate Android Development] crt60:
Ok, for some reason the file disappeared from the server.

I've reuploaded and the link is working now.

Have not a clue what happened.
[Captivate Android Development] 4-2ndtwin:
^ ehhh....blame it on the Mayans...

:p
[Captivate Android Development] startngate:
OK. Thanks.

Glad is wasn't just me .... :laugh:
[Captivate Android Development] :
Testing 4.2 source and looks superb.
[Captivate Android Development] kaiserXDA:
Just jumping in to say I just installed this ROM and it flashed very easy from KK4.

I will give more info in a little while because I am still getting my apps installed and learning what is what.

But Thanks To The Collective, this is amazing work.
[Captivate Android Development] :
Thank You for giving us a go. You will enjoy. But hang on as we are getting ready to release 4.2 source....even better experience as I'm on now testing for Infuse.:D

Sent from one of my Many AOCP devices.
[Captivate Android Development] :
Get ready my friends... should be very soon. I'm on the fully polished 4.2. All the cool new things and its Molon tested.....Collective approved!

Sent from my one of many Collective devices.
[Captivate Android Development] :
4.2 on the way!!!!!
[Captivate Android Development] :
Almost Time!
[Captivate Android Development] 4-2ndtwin:
Ok ok...i got my popcorn and sweet tea. Ready when ya'll r !! Lol.

And btw, appreciate the continued dev work shown to the Captivate !
[Captivate Android Development] robm1911:
Pssst, over here

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

[ROM] 4.2.1 | Jellybean | AoCP 5 | The Collective | 2/1/2013)
[Captivate Android Development] :
Right on
[Captivate Android Development] 4-2ndtwin:
Heck yeah !!!! Awesome !! Thanks again Collective !!
[Captivate Android Development] crt60:
Try flashing the ROM but not gapps and see if you have a camera then I may have posted the wrong gapps
[Captivate Android Development] jmtheiss:
That did it. As soon as I wiped and re-flashed, it was on the main screen. Thanks.

Now to get the gapps working.
[Captivate Android Development] robm1911:
Hang tight I'll post up a gapps zip just in case. Give me a few go get it uploaded.
[Captivate Android Development] 4-2ndtwin:
Lol !!

Idk...i just thought, i got to get a pic of this---a horse's ass and a jackass in the same shot :D

(and the previous conversation about the camera app/ gallery app got me dizzy lol :p )
[Captivate Android Development] robm1911:
yeah that was really funny, you actually got a pic of crt60 and me in one shot lol.

@jmtheiss here is the link to an updated gapps

https://dl.dropbox.com/u/44679379/gapps-jb-20120726-signed.zip
[Captivate Android Development] jmtheiss:
Awesome. Thanks.
[Captivate Android Development] crt60:
Yeah but who is who? I'll be the ass and you can be the horses ass.
[Captivate Android Development] robm1911:
That works, now let's hope the mods don't kick both our azzez lol.

I can say its been a pretty uneventful first 24 hours of the thread, only one real issue. I will say though its been one of the most hilarious and entertaining 24 hours I have ever seen in a thread. I love this community.

So we can try this again:

We now return you to your regularly scheduled program

And to quote Ozzy Osbourne:

Thank you good night, we love you all!!!
[Captivate Android Development] Mortem Tuam:
Use the xda app on your phone, you get unlimited thanks hits! I;)
[Captivate Android Development] m1batt1:
Downloading now... Doubt I'll get around to flashing tonight but it's next on the list :D. I would also be interested in seeing a feature list.
[Captivate Android Development] RDI:
Good News / Bad News

Square Up credit card sniper works.

Chase Bank remote check deposit, it takes the first picture of the check front and shows it to you. When you hit the "Use" button the App crashes. This App worked under v2.2

Sent from my Samsung Captivate running ICS 4.1.1 AoCP CP v3 w/KG3 Modem
[Captivate Android Development] crt60:
Dammit

Anyway you can post a logcat when the app crashes?
[Captivate Android Development] Johnsondr80:
Chances are that the app itself needs updating to support jellybean
[Captivate Android Development] DaNaRkI:
Guess it high time I went and loaded me up a Collective ROM.

-xda app, too lazy for something interesting to say-
[Captivate Android Development] Hivol:
Got a status 7 error when trying to install. Looks like it said a problem with get prop. Coming from Salty Bean with Hellybean kernel following op directions. Formatted system and cleared init.d. Any suggestions? Thanks in advance!
[Captivate Android Development] Kyuta Syuko:
Woot been waiting for this! Will flash when I get home from work!
[Captivate Android Development] Johnsondr80:
Hello DaNaRkI! Long time no see my Old Friend.

GTalk me some time today. We need to catch up!
[Captivate Android Development] Johnsondr80:
Place zip on pc

Pull out the Updaterscript from deep in the updater meta-inf folder

Remove the top three lines.

Replace the file with newly edited one

Reflash
[Captivate Android Development] Mortem Tuam:
OK robm1911

here's the updated siggy for everyone to use if they wish :cool::cool:

:eek::eek:

baraghh! I made it different from the other! I need coffee and need to wake up! I will make a new one when I get home, I'll still leave this one up though.:crying::crying:
[Captivate Android Development] tkjeeper:
Weird, not one comment on how this is running? Lots of joking around, which is good, but no comments on speed, stability etc., good or bad...strange, think I'll stick where I am.
[Captivate Android Development] robm1911:
Well here's one comment but other than that for me no bad or negative comments is a good thing. All you can do is be like Mikey, try it you might like it.

I need to stop showing my age lol...
[Captivate Android Development] ashok.antony:
Installation error due to wrong BL

My cappy shows I900 rather than I897. I guess thats a different BL that came with one of those ports but it has never bothered me before. I have used Helly Bean, Rem and other ROMs. Even now, flashed the LANIGHT and running smoothly.

My experience with AoCP was bad. It was my mistake that I didnt try to change to I897 BL (it was not suggested/recommended here. Should be added to the original post as a mandatory criteria so that it can help folks like me). I copied the ROM to my SD card and flashed following the directions. As soon as the flash started, it errored out and it never went back to previous state. I guess since we had to wipe /system, the phone doesnt have useful files to run properly. I had to go to stock and then redo everything to come back to JB.

That gives raise to a question from me. Why the /system wipe. In real sense, the installer should add all the files that it needs and then once the system is running smooth, we should be given an option to "clear" which can remove the unwanted files. Is that doable at all?

I am sad that I couldnt flash this since the screenshot was awesome and I really wanted to flash this.
[Captivate Android Development] Mortem Tuam:
the OP does say it's for I897......I think that's pretty clear that it won't work for I9000.
[Captivate Android Development] m1batt1:
Ran into the same issue during flash. Even went in and edited the Updaterscript as suggested and still get the Status 7 Error...
[Captivate Android Development] robm1911:
Try redownloading
[Captivate Android Development] richsale:
I also had a status 7 error. I simply reflashed and all went well. I have only been running CP3 for an hour or so but so far no problems.
[Captivate Android Development] m1batt1:
Redownloading now.

Yeah I tried several times before I modified the script and then tried a couple more times after that. Status 7 everytime!

I'll report back later tonight. For now I must get ready for work :P

Edit: It downloaded quickly for me so I tried it again just now and same thing. This is the error string I get in recovery...

assert failed: getprop("ro.product.device") == "SGH-I897" || getprop("ro.build.product") == "SGH-I897"
[Captivate Android Development] jmtheiss:
Interesting - the second phone identifier is misspelled (SHG-I897 instead of SGH-I897). Any chance that's the issue?
[Captivate Android Development] m1batt1:
No I would say that what you see there is me being dyslexic. Of course I've restored back to Helly Bean so I can't be sure but that was my error during typing it...
[Captivate Android Development] jmtheiss:
Ah.

Either way, the times I've seen that error is when my build.prop file had some incorrect information in it prior to flashing. You may want to poke around in that file and see if anything looks suspicious.
[Captivate Android Development] DaNaRkI:
Might not get to till tomorrow, cuz I'm in the middle of fixing my PC (my linux and windows were fighting so I ended up just wiping the whole HDD), and now I have a new ROM to learn and things to reload. Of which I never fully got settled in on CM10, cuz something I was loading would lag the phone to hell (even when installing from the market, so it's an app that is not JB ready...)

- - - - - - In other news - - - - - -

As for the ROM so far: is there a way to put calander events on the lock screen like CM10? I can't find an option. Other then that I got lots of poking around to do and things to learn. Heck it's been so long since I used the actual XDA site that I'm a little lost on how to navigate it as well...
[Captivate Android Development] crt60:
The assert in the updater-script is correct, but I wont remove it from the rom since it is a good thing to have so someone doesn't try flashing the rom on another phone it wasn't designed to.

The status 7 error is an assert error, either you didn't format your system directory like it was suggested in the op or you are not flashing the rom on an sgh-i897.
[Captivate Android Development] tkjeeper:
Wrong, I did all of that and still got status 7. And by the way, why link ics gapps in the op, them tell people not to flash it? Brutal.
[Captivate Android Development] Johnsondr80:
Why are you so argumentive?

If you spent half of that energy on reading you would see that the Gapps posted in the op is gapps jellybean version

And the gapps he stating not to flash is ICS gapps.

STOP trying to confuse users and taking stabs at the dev.

:banghead::banghead:
[Captivate Android Development] m1batt1:
Definitely formatted system per the OP and am definitely using an sgh-i897...

I guess after work tonight I'll have a look around and see what I can come up with in build.prop.
[Captivate Android Development] dman3285:
Flash cm10, don't let it boot.. do another compete wipe while in recovery then flash cp3
[Captivate Android Development] 4-2ndtwin:
...I just flashed AoCP Jellybean CP 3 per OP instructions, coming from the AoCP ICS CP 2.2, and had no errors and no problems throughout the process. And i flashed the updated gapps in post 2 by robm1911.

Lookin good guys ! Another great job done by the Collective !! :thumbup:
[Captivate Android Development] tkjeeper:
It's so easy to blame the user rather than take criticism right? The original link to gapps, was to an ics version, or I wouldn't have wondered why when I saw it. Nice to see you can admit to errors though. Atta boy!
[Captivate Android Development] crt60:
Please stop being a troll....
[Captivate Android Development] Mortem Tuam:
I'm eating some now! :laugh::laugh::cool::cool::good:​
[Captivate Android Development] robm1911:
Ignore it, it might go away..
[Captivate Android Development] tkjeeper:
That's funny coming from the guys who are two months late getting a ROM out welcome to the jellybean party guys
[Captivate Android Development] Johnsondr80:
1.

And how many Roms have you put out?

Oh yea, that's right. NVM.

2.

Let's ask everybody else.

Would you rather had it two weeks earlier while it was still lagging, buggy, busted camera, and flickering nonstop?

Or

Was it just on time, and just right?

3

We don't dish crap.
[Captivate Android Development] RDI:
Okay, I screwed up, I used the GAPPS - ICS instead of the new one, do I wipe everything and start over?

Thanks in advance...

Sent from my Samsung Captivate running ICS 4.1.1 AoCP CP v3 w/KG3 Modem
[Captivate Android Development] cliftomr1082:
The old Iron Fist, boy hadn't heard his name in a while
[Captivate Android Development] robm1911:
You should be able to reflash the ROM with no wipes and reflash the jb gapps...
[Captivate Android Development] Kyuta Syuko:
I have a question about the Status 7 error and the checking if the phone is an I897 or not. What exactly is the script looking at to see if the phone is an I897?

*edit*

Just wanted to say I LOVE the boot up animation.

*edit 2*

Anyone else having issues with this ROM and Devil Kernel?

*edit 3*

Does this ROM use the same layout as the current CM10 build?
[Captivate Android Development] crt60:
I believe it is looking at the build prop but it seems its more trouble than its worth having asserts in the updater-script
[Captivate Android Development] daskanda:
The assert failures are most likely from the kernel people are flashing from flashing a different kernel then rebooting into recovery should solve the issue
[Captivate Android Development] :
+1. Worked fine from KK4.
[Captivate Android Development] m1batt1:
First off I want to clarify that even though I'm one of those people that are having trouble getting the ROM to flash and I in no way am complaining. Just trying to troubleshoot what issues I'm running into so the overall process can be improved.

Secondly I looked everywhere in build prop and every device reference that I came across was labeled sgh-i897 so I don't know. Next step as I've read is to flash cm10 or another kernel so I'll try that.

Third I thank all you devs for your work as you feed my nerdiness lol
[Captivate Android Development] Kyuta Syuko:
That's what I thought. Now here's the issue I have with it. I just double checked to make sure, but build.prop is in /system which you say to format as part of the flash process. So the people getting that Status 7 error are the ones that followed instructions while the ones that aren't are the ones that didn't bother to format /system. I got the Status 7 error when I first flashed and thought it might be checking the build.prop file which is why I asked. I removed the check to get around the Status 7 error.

*edit*

If my Cappy wasn't my daily driver I'd flash the ROM a few more times just to make sure my findings are correct, but I'm about 92% certain they're correct.
[Captivate Android Development] 4-2ndtwin:
Sorry, but ur findings are not correct as far as the process i did to flash this rom, because i did exactly as the OP install instructions state and i had no problems flashing, no status 7, nodda.

So, i'm not sure why a few have had issues.
[Captivate Android Development] zzmomo73:
I think if your on a semaphore kernel it will give you status 7 error... try flashing a devil kernel-reboot recovery - then flash ROM?
[Captivate Android Development] Johnsondr80:
This is the most reliable and Hassel free way IMO.

And I did some checking and it looks to me that the updater script is properly and most assuredly formating system at time of flash.

With that said I do believe that unlike many of the external recovery devices that we support (that seem to have problems doing this), in the case of the i897 it is my recommendation to remove the "format system" step from the install instructions.

That is if CRT (or anyone else) can verify my findings.

One easy was to do this is to place a text file (empty or not) into the app folder. (I named my text file 01.txt so it would stay at the top of the list so I didn't have to look to hard for it) and flash the ROM.

After boot see if its still there. If it is then it is not formating system. If it is gone then of course you system was formated during installation.

:cool:
[Captivate Android Development] Kyuta Syuko:
You sure you formatted /system? As far as I know ro.product.device and ro.build.product are only located in the build.prop which is in /system and becomes non-existent if you format /system like it says to do in the OP thus giving the script nothing to check against causing it to give an error.

I know it's not the kernel unless using the kernel provided with the ROM is bad. I got a failed flash bootloop and had to boot into recovery and re-flash, but the kernel had gotten flashed.

*edit*

I take back what I said about the kernel. I just remembered it did that after I removed the check. I was originally flashing from Devil ICS 1.1.2. I think that's the right version number...
[Captivate Android Development] crt60:
Well it reads it on one of the partitions, though i have no issues with the cm10 kernel that is provided with the rom.
[Captivate Android Development] 4-2ndtwin:
^

Yep, i'm sure that i did.

Wipe data/factory reset. Then wipe dalvik. Then went to mounts and storage and selected to format /system. Then continued with the install.

I may redo the whole process tomorrow nite if i have time. If i do, i will flash back to stock gb kk4 and then install this per op.
[Captivate Android Development] RDI:
Maybe this will help. I did format /system and did not get the Status 7 error. However, when I went into the Mounting /Storage menu, I changed the unmounted /system to mounted /system BEFORE I moved lower on the menu to format/system. Hope this helps...

Edit: note that the default setting was unmounted /system. I do not think that the format command will run if not mounted first.

Sent from my Samsung Captivate running ICS 4.1.1 AoCP CP v3 w/KG3 Modem
[Captivate Android Development] Kyuta Syuko:
I find that strange. Unless it recreates the build.prop file after the format. Wish I had an extra Cappy to run tests and try to figure out what's causing the error.

Hmm I wonder how many people that didn't get the error flashed back to stock KK4 vs those that did get the error and didn't flash back to stock KK4.

RDI makes another interesting assessment. Really makes me wish I had a test Cappy...
[Captivate Android Development] bigbadwolf311:
Hey, quick question. I am about to flash this on my phone. Which gapps should I flash. The one in the install instructions or the one in the second post. Thanks for your time and great work.
[Captivate Android Development] 4-2ndtwin:
^

Go with post #2. It's updated.
[Captivate Android Development] Kyuta Syuko:
I personally flashed the one in the second post. Have been too busy reinstalling all my apps to really test anything though.
[Captivate Android Development] crt60:
I updated the one in the op
[Captivate Android Development] m1batt1:
Still Getting Status 7

Ok guys I don't know what the problem is with my phone... I've attempted changing the updater script which did no good. I tried downloading again and nothing. I checked everything in the build prop referenced in the error message and all things are labeled sgh-i897. I had Slim Bean handy so I flashed it first with no problems then tried flashing back to this since slim uses semaphore and nothing. Then since I had downloaded CM10 I tried it and got the same status 7 error. So now I'm back on Helly Bean.

The only thing I haven't tried is flashing back to kk4 as mentioned somewhere. I'm out of ideas and to clarify again I am definitely using a sgh-i897. I also tried all the combinations of flashing /system and not and mounting and unmounting. Nothing has changed my results. I'm not used to being the guy in a forum that can't figure out my issue much less being the only guy with the issue. Also all help is very much appreciated!
[Captivate Android Development] crt60:
Yeah pretty weird and the sgh i897 is spelled wrong still in the error? Which leads me to believe you have a corrupt partition, The way the rom "lands" on the partition may influence if it shows up or not. I would definitely try a flash back to gingerbread stock and start over again.

If that doesn't work, I'm at a loss.
[Captivate Android Development] m1batt1:
I apologize... I should have corrected that in my earlier post. The spelling was not part of the error... that was my fat fingers getting confused as I typed it out in the post. Either way it seems my next move will be to flash back and start over. That will have to wait a couple days though before I have the time to plant myself in one spot long enough to make all that happen.

I will let you know what I find when I have the time to work through it all though.

Edit: I went ahead and updated my previous post to reflect the proper spelling. I know it was me typing because when I did it earlier I checked to make sure the spelling was right when I got the error. Additionally I was just thinking the only thing that I've done to helly bean and the one thing is has specifically in common with Slim is a custom DPI which is auto set in slims rom and that I set in Helly using build prop editor. Though the error doesn't reflect anything with that file is there any possible way that could be my issue?
[Captivate Android Development] Kyuta Syuko:
A modified build.prop shouldn't have an affect on the check working or not. The custom DPI setting shouldn't affect the script pulling the two variables from the build.prop.

Also what did you use to modify the updater-script? I would suggest Notepad++ and search for the two variables in the error and remove the line. I believe it was 10 might have extended down into 11 as well.
[Captivate Android Development] Johnsondr80:
What are you talking about here?

I know your not saying remove lines 10 and/or 11 from the updater script.

That would be a problem.

I just ask you clarify your statement so nobody misunderstands

Edit: never mind

I just looked at it again. The lines that need removing the assert lines are in fact line 10 and 11.

I had forgot all about the ui_print lines.
[Captivate Android Development] m1batt1:
i did use notepad++ and I don't recall off hand what I removed but lines 10 and 11 sound right
[Captivate Android Development] Kyuta Syuko:
And you're still getting the Status 7 error? That's strange. When I get home I'll send you the zip I used to flash this and see if it works for you. That'll be in about 7 hours =|

On another note is anyone having any issues with some apps being slow and not responding at times? Like Google Chrome or xScope Pro? Maybe I got a bad flash reflashing it so many times trying to get Devil JB 1.4.1 to work =| Granted I think it's strange those are the only two apps causing an issue that I've found so far if it is indeed a bad flash...

*edit*

You sure you put the edited file back into the zip file? I've done that before...
[Captivate Android Development] m1batt1:
Yeah in fact I have a copy of the script still saved on my desktop. Just to clarify the script I was supposed to modify was in META-INF>com>google>android correct?

Sounds like a plan on the zip. I'm getting ready for work now so it'll be a while before I will be able to use anything you send.

Edit: Yes I replaced it. You did make me question myself so I checked.