yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsntrenkler:
I did not. Just flashed the zip. I cleared dalvik several times as well as performed wipe before and after install. I couldn't get it to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I tried it as is and with Ktoons 10-31 AOSP kernel. No go either way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsntrenkler:
Okay quote isn't working in tapatalk, I wiped cache and dalvik cache several times as well as wipe / restore before and after the flash. I couldn't get it to do anything. Just black screen after the Samsung logo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amzi:
wait what... hes saying its 4.2 and he uploaded it for us didnt dare himself to flash it and still doesnt know if it works.. dafuq??

edit: kinda think hes trolling now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
ktoonsez's kernels dont like working with ports a lot... they didnt work for the wickedsensations one either

try cm's boot.img

in case u dont know its

download both roms

unpack mine

extract the boot.img from cm to mine

pack mine

flash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
why? look at the lg dump

and my portscript
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amzi:
god damn this 292 mb bs lemme wait till it finishes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmjlabelle:
Did you try a factory reset after installation? That's what I have to do every time. Not sure why though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsntrenkler:
If you put something together for me I will give it a try. Haven't restored my CM10 yet just installed tapa talk. Let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
did it get to saying samsung galaxy s iii?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsntrenkler:
Yes just initial splash screen then went black and nothing happened.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meleii:
I am assuming You will need to have a new kernel for 4.2. Same as an ICS kernel won't work on jb a jb one won't work on 4.2.

That's just my .02
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
it works but half the things would be broken

and 4.1 and 4.2 are a lot more similar
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amzi:
seems legit although i agree with the other dude.. im pretty sure there is a s**tload different rom 4.1 and 4.2 linking you on this thread just to get some popularity more then it already is xD

-http://xdaforums.com/showthread.php?p=33494744#post33494744

just getting the happy 4.2 people in a big happy group :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
So what's the word. Anything new
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
nope nothing other than I got smartguy to "see if i can do anything with it"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
What's he thinking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
idk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
We basically need a kernel that has some universal qualities don't we.. kinda like tamcores ICS kernel ran jellbean on the sensation.. that kinda deal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
i could just get someone to port the nexus 4 kernel to this...

i asked ron amadeo frot the kernel, still waiting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Flashaholics unite!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
Well let's hope
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
So we use the cyanogenmod boot image? Because i was wondering if we could use liquidJB's boot image. or do none of the boot images work?

EDIT: Just saying because I have limited monthly bandwidth.

EDIT #2: Flashing this won't cause any bricks right? Even if the boot image screwed up I can still get into DLOAD Mode. Right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You guys do know that in 11 days source for 4.2 will be released don't you? I never understood why people would risk ruining their expensive devices for a couple days of waiting. :cyclops:

P.S- This from the OP "Oh yeah, and if anyone knows, what is recovery-from-boot.p supposed to do?" Probably means that you shouldn't post these types of things to the public. Don't take that the wrong way. I'm not trying to come down on you or be rude. But I'm not sure why anyone would release things that they do not know what they are.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
Let the kids have their fun.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsntrenkler:
I didn't have any issues with mine, was able to flash back to my previous ROM. Actually just flashed to the Galaxy Note 2 ROM for S3 while I am waiting on this one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I definitely didn't plan on stopping it. Just making sure others who don't know any better understand that we will have 4.2 in as soon as 12 more days without them taking any risk of damaging their devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
Impatience :)

I just found the file there which was not in 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you look at some of the touchwhiz leaks and releases you will find something similar to it. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
Great to know 11 days. Really excited!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Finally, been searching all over the place for a release date of 4.2 to AOSP. Now I have an answer, will be waiting patiently :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
Aosp releases usually come with the devices....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wavrunrx:
wait, whaa ? link ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsntrenkler:
Here you go ... So far works great, I did however add the 4.2 keyboard as I felt the Sammy keyboard was laggy.

http://xdaforums.com/showthread.php?t=1951115
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
It's about a week later from now. So I was debating on flashing some other roms but I can just wait it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Don't flash this.

1st Reason: It doesn't boot. No matter which kernel you use, it doesn't.

2nd Reason: It creates another folder in your internal sdcard called 0, and transfers all your files there. So you can't restore your nandroid as all known recoveries to me do not support locating the backup location, and you'll have to flash a new ROM, and go about transferring every single file back to its original location. Thanks for your effort OP, but I'm just warning people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
any one have a mirror?

forget it, worked fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsntrenkler:
I deleted the 0 directory and have no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plays2:
Wait, so if you flash this ROM and delete the 0 directory the rom boot up and work? Like on 4.2... Or...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrakifa:
Can u post pics...kinda scared to try this out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Read about 7 posts behind yours :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jammol:
Rani, cwm supports look up directory of backup. I use it all the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rener78:
From personal experience it does create the 0 folder and it's actually a copy of the regular storage folder i usually use on my internal SD card. I deleted it without a problem.

It does not boot so I went into recovery.

I wasn't able to see/access my internal SD but able to see my ext SD card in recovery and restored from there.

Deleted the 0 folder after.

Envoyé depuis mon SGH-T999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
Doesn't all your internal data get deleted when you delete the 0 directory?

I think it should, or does all the data come up out of the directories.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c0ns0le:
Guys looking at the updater script I think the '0' is from the format cmd. I believe it should be changed to

format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0", "/system");

Instead of

format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0");
[Code]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aquethys:
Guys,

Android 4.2 source has not been released. That means that this is just simply LG System Dump packaged into a flashable zip. The OP modded the build.prop to look like Android 4.2. So patiently wait for your poison in only about a week for sources to be updated :) As of right now, I repeat, code hasn't been released so it's impossible for any device other than the Nexus 4 to have true Android 4.2. Don't flash this, there's been problems and...yeah.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tommrazek01:
I actually tried porting the ROM and I don't think OP is lying (Well, he could be trolling us, but that is a different one). After porting everything the way you would port any other ROM and put everything into /system and created meta-inf with all its files, I still get the thing to be stuck just a bit after the Samsung Logo (Google logo for my gnex), whitout the boot animation. There is a boot animation in this ROM, therefore there is something critical going on. Since it seems everything is written to the 0 directory, the system has nothing to boot from. Removing this would fix the problem. If someone can post a working script and actually do the porting, I believe this can boot fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nopcodex90:
You cannot port a different system dump like a traditional ROM. It is possible to boot this, though I doubt it will have much use. I have ported Gingerbread dumps in the past using heavily modified froyo kernels, and yea it worked, it was not worth using. IT is fun to play with though, you might be better off looking into the kernel source and determine what is different from the JB kernel to the LKP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
This ROM made my phone grow legs and wander off and now I can't find it anywhere. Be careful if you flash this, put a leash on it first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
So hows development going

Havent seen much happen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Nexus 4 gets released on Monday which means source is very shortly after which means this thread will be dead soon. Not much needs to happen really. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
From what my friend told me, is that 4.2 Aosp has been released
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
your friend needs to find another source from where he/she gets their information then. lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
His friend is 4.2 AOSP source. That's his source. :silly: :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mu3g:
This is to assist the OP:

The stock ROM will automatically replace TWRP (or any custom recovery) with the stock recovery. To prevent the stock ROM from replacing the custom recovery, boot into the custom recovery, go to the mount menu and mount system. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak or delete it.

This is basically a fail-safe measure by a few ROMs (especially stock Google ROMs) from having the stock recovery overwritten by a custom recovery. Hence, we need to go through the process of deleting them or saving them with a random file extension.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
its out, 4.2 is out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] REDFOCZ:
Well the source was dropped yesterday, but it will take a few days or weeks before we start to see it on are devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
I wouldn't be surprised if Task releases soon. Just my guess with the great work he does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] REDFOCZ:
I believe that we could have a vannila version up and running soon. But both AOKP and CM10 have a lot of custom code written on top that will have to be ported over to 4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryuken11221:
So from this stand point this ISNA super beta ROM then but just throwing this out the since we have cm10 running wouldn't it be a sintch to get 4.2 running it is just asop am I correct or do we have to wait for cm team to have at it for us to receive the 4.2 update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hampsterblade:
It's hard to say. Part of the problem with having a proprietary device is the OS updates tend to break things in the kernel. If the 4.2 update didn't do this there would probably already be a build up. The developers are working on it (trust me, they want it as bad as you do). Just give them time and remember the XDA rule "don't ask for etas". Until then enjoy all the great roms we have now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryuken11221:
Oh I wasn't asking for an eta but I was just asking if the process was something worth doing or if the its just better starting from scratch.

From my Galaxy S III unlocked and rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
They posted on Google Plus today that they are still working over it. Sounds like it could be a bit yet.

Sent while hanging with that really hoopy frood Ford Prefect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
me with all the tech sites saying that there alot of bugs with 4.2 I would not be so ready to get it. I still have not flashed it on by nexus 7.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
This has become like a JB 4.2 discussion thread, as the ROM doesn't work :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
This should probably be moved to General or just closed up. Some poor sap is gonna see this, not read anything, bork their phone, and then come crying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I made the mistake of flashing 4.2 on my nexus 7 lol, very buggy. Not to mention 99% of android apps are broken on 4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stone_phalanges:
This entire statement is 99% false
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iwasaperson:
Anyone here mind building me a 4.2 ramdisk for the d2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WattB006:
I have been running 4.2 on my Nexus 7 for a few days and I haven't had any issues at all. All of my apps work like they used to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daveyian:
Please remove the links to save the unlucky from killing their phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Kill is a strong word. But it will cause people to go crazy, fixing it is time consuming.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
is anyone working on 4.2 for the d2att?

this is kind of sad, a flagship hasnt gotten 4.2 yet an old phone like the Desire HD has, damn
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
what do you think?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
Maybe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BaconStep:
:banghead:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erandhawa:
As the op posted its experimental if you are not familiar don't flash it there's no holding your hand as you cross the street.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Nope. No one is working on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
Lol sorry just was really excited
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey! I love the look of the new 4.2 ROM, very shiny and dark. So cool with those folders on the home screen. When will we be seeing it, Task?

[/sarcasm]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
u serious =D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr.devman:
We can be a lil patient...maybe not ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Note the sarcasm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nopcodex90:
Maybe your browser doesn't implement the newer HTML 5 standards, The sarcasm tag was introduced there, i dunno if its backwards compatible with dumb. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
Day 15 of flash withdrawal. I'm getting raging headaches and extreme sadness.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
OK

So I built aospjb for the tf101

I'll try to make a device tree for our device and maybe get a build out before cm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hampsterblade:
CM10.1 test builds are starting to come out on the galaxy tab. I'll take a look and see if our device tree will build on them tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Stay strong brother
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
It won't

u need a 4.2 config

Just compare the 4.1 and the 4.2 and make the changes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryuken11221:
Will someone get this going lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
Where can I find this device tree, have heard people talk about it. But never have I looked into it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Papa Smurf151:
Locking this due to OP stating that it is dead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Papa Smurf151:
Unlocked per op request

XDA Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PearsonDKA:
Anyone give this a whirl yet?

If anything, I could be the guinea pig :o

Sent from the Bacon Powered S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BaconStep:
Cyanogen said nightlies for d2 would start in a couple of days. So if I were you guys I would just wait it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryuken11221:
OK I'm kinda confused what's d2 or did you mean s3 either way so would that mean we are going to get nightlies of cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
ugh... d2 is the code name of the north american galaxy s3..... *sigh*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
D2's are the start of the name of our device as well as all North american GS3's (ie. d2ATT, d2TMO). And nightly builds of CM10.1, rom updated nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryuken11221:
Thanks for the clarification that's all I needed to know
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BaconStep:
the us galaxy s3 models

https://plus.google.com/u/0/117962666888533781522/posts/gdXUqktgXXr
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] keredini:
d2att is the device id of the at&t S3 ... SGH-i747 is the model number
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ima.monstaaa:
Alright, at least four people have already answered the question. One was enough. Two was a mistake. The rest are just wasted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] white00gt:
D2 is the sequal to the mighty ducks (D1)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
And he didn't "thank" any of them :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Can someone compile latest nightly for cm10.1 they fixed GPS Bluetooth and external SD =D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Why do you come into this thread and ask this? Please post in the appropriate place please. There is a CM thread dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ima.monstaaa:
I didn't ask the question. It was just obvious it had been answered. I use "Thanks" when someone posts something useful to me.

EDIT: Just to be clear. Not trying to troll or be rude in any way. We've already cluttered/derailed the thread enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RegBuckley:
I was going to say R2's last name.. lol..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
I was talking about the guy who asked the question. He didn't "thank" anyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ima.monstaaa:
My apologies, then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sonymsam:
That was like a one tight slap :D:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sid_wisc:
Apologies accepted... I suppose... LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Everyone is a little uptight fighting their flashing addictions. We've heard rumors of some really good stuff to flash that's supposed to be better than anything before, but we can't find it lol :)

It'll be a miracle if this forum survives the drought of flash

Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plays2:
so tmobile just got cm10.1, and by my understanding we have basically the same hardware right? if i changed some stuff in the build.prop file could i get it running on my att gs3? or am i misunderstanding...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zehlek:
I have Rogers. Can I flash it and then just flash tge proper modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plays2:
Well this is exactly what I wanted to try. I will test and reply in a few
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xspartany:
Did that work for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plays2:
Not quite I forgot to edit one line of the build. Prop so it doesn't boot. I will try again later. If you want to try and help out the download is at d-h.st/UhH unzip and change the build . prop to fit our device. Theoretically this should work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zehlek:
What do you edit in the build prop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plays2:
anything that says "d2tmo" should be changed to d2att...i believe we may also need a different boot.img, i am not an experienced developer at all haha so i'm pretty much going off of what i've read. if my memory is correct i should be able to get this booting but we will see. if i get it booting i will upload.

EDIT: some users have gotten thishttp://www.mediafire.com/?9wt2acv8wuoq0ll to work, you may need to flash/wipe/format /system multiple times to get it booting. (Thanks to user madMack for the link...all props go to him i DID NOT make this rom)

EDIT (12/8/12 8:00pm EST): so i just finished modifying the t-mobile rom and am about to send it to my phone and boot up...wish me luck!

EDIT (12/8/12 8:40pm EST): yea it didn't work, Sorry guys!

EDIT (12/8/12 8:55pm EST): i figured out that i cant get it to work because i was modifying the files and re-compressing them using a mac, so when you compress files on a mac it add a bunch of crap files like DS_Store and crap and i'm not sure how to fix it, so um yea if anyone knows how to fix it then tell me but i'll probably just re-do it all tomorrow on my ubuntu IF official 10.1 hasn't been released yet which i'm sure it will be. well this was fun haha.

---------- Post added at 02:16 AM ---------- Previous post was at 02:05 AM ----------

I have taken down the old link (d-h.st/UhH) and am uploading a newer version which should work....haven't tested it yet but am in the process haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] munchkers13:
Trying now!

Edit:

Tried with a full wipe and everything including the kitchen sink installed with 4.2 gapps - no dice... Went to Samsung splash then went blank until reboot

Tried with a dirty install over pkd1.4 - no dice... Same as wiped
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sid_wisc:
And what happened.... Very curious...:confused::confused::confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plays2:
Well if it makes you feel any better i couldn't get it to work either :( oh well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
when building on a mac download betterzip and compress using that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plays2:
Thanks for the tip! I got it to install but not boot. Unfortunately I think we will just have to wait for the cm team to get it done.