yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] TechSavvy2:
So just to clarify here.....

We use non-kexec recovery now right? as in use ez-recovery and flash the 6.0.1.0 or whatever the 6.whatever one is, then we use 8/15 from invisiblek from op now, correct?

Just wondering, cuz I initially tried using rom manager to flash cwm thinking it may work now.....I was wrong.........

EDIT - whoops, didn't look in the testing folder.....:p apparently that's the one I need
[Verizon Samsung Galaxy S III] jonathonparker:
Took me a min to realize this too, I just looked at the build number mentioned in the thread and didn't see it in the main download section so that's when I checked the Testing folder. lol
[Verizon Samsung Galaxy S III] hsomnus:
working for me
[Verizon Samsung Galaxy S III] TechSavvy2:
Wow, what an inconvenient time to lose my IMEI......fml.....

Going through the process of restoring it now. To those who did this also, did everything come fully back to normal? or was their the roaming issue?
[Verizon Samsung Galaxy S III] WildZontar:
What doesn't work compared to stock?

Does Netflix work?
[Verizon Samsung Galaxy S III] kabro91:
I will go to sleep tonight and when I awaken tomorrow this forum will be abuzz like a magical forest filled with custom kernels like huge gumdrops and ROMS like dainty pixies blowing their dust in wanderers faces...hehehehehe =D
[Verizon Samsung Galaxy S III] TechSavvy2:
Apparently the MMS issue was solved and implemented by CM team. It was linked in the AOKP thread on Rootz. Should be merged now or tomorrow or something I would think. Get excited!!!
[Verizon Samsung Galaxy S III] samg77:
I followed the bootloader unlock, loaded TWRP from GOO, flashed 8-15 CM10 nightly, am now Im bootlooping, Ideas? :( I can't get into Recovery or anything, keeps booting, showing TWRP screen, reboots again. ODIN TIME
[Verizon Samsung Galaxy S III] Marcismo55:
The 8/15 1920 build? I flashed the non-kexec CWM via EZ Recovery to flash the 1920 build and everything booted up fine
[Verizon Samsung Galaxy S III] samg77:
Which recovery from EZ Recovery should I flash? (Which one is non-kexec?) I used this program when I was using Kexec, and only saw the two in there (Touch and non touch). Did they update the program tonight for non-kexec? Also maybe link to me the ROM you used, but I went to OP post, and grabbed the lasted 8-15 build. So irritating having to ODIN.
[Verizon Samsung Galaxy S III] Marcismo55:
Sorry man..having to ODIN back sucks.

Here's the link (the build all the way at the bottom) http://www.androidfilehost.com/main/Samsung_Galaxy_SIII_Developers/Invisiblek/cm10/testing/

Yes, easy recovery has been updated and is available in the Playstore. This is the non-kexec recovery you want to run
[Verizon Samsung Galaxy S III] samg77:
That was the same exact one I used for kexec. Did I do something wrong? (success working now! God I was so bummed to hear the VZW bootloader was locked, only reason I even got this phone is I talked VZW into swapping all 3 of my Nexus for these for free, due to the nexus radio SUCKING BALLS at my house, lost EVERY CALL over 10 minutes due to dropped audio, if I didnt have a network extender the phone would have been useless at my house, and I live in a big city)

New question: Is NFC supposed to be broke with this ? I have not got NFC working with any CM10 build. Ive swapped batteries both stock and aftermarket(with functioning NFC), NFC works fine stock, but not CM10 :( It comes up disabled, I hit the box to enable, and it just stays grayed out. Any ideas how to fix this?
[Verizon Samsung Galaxy S III] Hilbe:
NFC hasn't worked in the past few builds. It worked before and it'll work again I'm sure.

---------- Post added at 07:46 AM ---------- Previous post was at 07:44 AM ----------

Is anyone rocking TWRP recovery from Goo Manager with the latest CM10? Curious if it's working right now...
[Verizon Samsung Galaxy S III] onpoint10101:
Using twrp with unlocked gs3 with cm10 1920. Works great !!
[Verizon Samsung Galaxy S III] Hilbe:
I read there were issues with it recognizing the internal SD card.
[Verizon Samsung Galaxy S III] Josolanes:
I haven't gone to download mode to test but I know I did it this same way and it booted quickly. I then flashed a nokexec kernel and it works well (no 3 boots and it's a custom kernel confirmed in phone status)
[Verizon Samsung Galaxy S III] onpoint10101:
I had a slight issues but was able to get it to recognize my internal sdcard properly...... then was able to see all contents on my internal sdcard and proceeded to wipe then flash 1920 and gapps
[Verizon Samsung Galaxy S III] jdubau55:
OK...so just so we are clear. What recovery are we flashing?

Looks like the process is to push the aboot.img from Terminal, then flash a non-kexec recovery, then reboot to recovery, wipe/reset/yadda yadda, then flash the 1920 version on the CM10 nightly, reboot??? This should put us on the latest nightly that is using a normal recovery and has the kernel loaded in the normal place and not some work around place right?

---------- Post added at 10:15 AM ---------- Previous post was at 10:13 AM ----------

Has always shown that. I'm still on kexec and kernel version is blah.blah.cyanogenmod.blah.blah-blahblah-blah.

Also...just went into the Play Store and there was a ROM Manager update. Is this old or did this just happen due to the unlock? Looks like version 5.0.1.5 is the newest and was posted today. No change log in the store though.
[Verizon Samsung Galaxy S III] aznxk3vi17:
Roger. Well, assuming you're not rooted, you should root first too. And remember gapps, of course. You'll know it worked when your phone boots in about 10 seconds, as opposed to a minute.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
i wanna flash this so bad but i think ill wait until they find a secure way to not lose imei cause im not too bright at following instructions and that imei thing seems complicated
[Verizon Samsung Galaxy S III] dmbfan13:
Ok, so im unlocked now. I understand I need the non kexec kernel. When I got to the CM10 nightlies page (http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies), I dont see a link for CM10 1920. Or is this it? d2vzw-CM10-invisiblek-KANG-08-15-2012-1646.zip
[Verizon Samsung Galaxy S III] tprouty:
Go into "testing" http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies/testing
[Verizon Samsung Galaxy S III] dmbfan13:
Im an idiot! Thanks!
[Verizon Samsung Galaxy S III] ruben8448:
Here is an issue i had last night. I installed TWRP and then i flashed cm10 8-15 without the kexec. I was stuck on a bootloader screen. I did it twice and same thing happened. I then had to switch to CWM with kexec and i installed this rom and it worked. It seems that with the 8-15 test build you still need cwm with kexec even though the rom doesnt use kexec.

Also, i have an unlocked bootloader. I used Adam's program.
[Verizon Samsung Galaxy S III] dmbfan13:
Interesting! Can other people verify this?

Anyone have a possible mirror?? Been sitting on 0% for several minutes!!!
[Verizon Samsung Galaxy S III] Hilbe:
I used CWM to flash 8/15 build (no kexec). I flashed TWRP 2.2.0 from Goo Manager. No issues. Took a backup. I am probably going back to CMW though.
[Verizon Samsung Galaxy S III] dmbfan13:
Yea, I'll prob just go ahead and use CWM. Now I just need to get the download to work!!
[Verizon Samsung Galaxy S III] :
i flashed the 1920 build with twrp without any issues
[Verizon Samsung Galaxy S III] Poloasis:
Do we still have to flash JB Gapps? thank guys
[Verizon Samsung Galaxy S III] loryndm:
I followed the directions to the "T". On a unlocked phone when i flashed CM10 with GAPPS when it went into recovery it began to bootloop. It would loop and loop. I could not get it back into recovery and had to restore to stock via ODIN :(

I dont think i missed a step but this is discouraging.
[Verizon Samsung Galaxy S III] Kev13Dd:
EDIT: nvm

K
[Verizon Samsung Galaxy S III] Ahodson1985:
I've also had bootloop issues with the 8/15 :crying:. Tried it with a supposedly non-kexec cwm, wiped data/cache/dalvik and bootlooped. Lost my recoveries and had to odin back to rt66. Installed TWRP, tried both a dirty flash and a clean flash with wiped data/cache/dalvik and it still bootlooped. Recovering back to stock now. Anyone having these issues with 8/15 who didnt have with 8/14? Will try that next
[Verizon Samsung Galaxy S III] loryndm:
I dont believe so. My phone was only rooted. I never flashed a rom on this phone nor went through the KEXEC method. I downloaded the rom from the link in the OP in the testing folder. Im now going to assume that the non-Kexec ROMS are not posted yet ??
[Verizon Samsung Galaxy S III] Ahodson1985:
Supposedly the rom/kernel in this thread is a non-kexec. If you never installed the kexec CWM (has a gray textured background rather than the regular black one), then you should be fine flashing regular roms/kernels like you would on any other unlocked device. Just wish it worked for me :silly:
[Verizon Samsung Galaxy S III] loryndm:
Well the only thing i can think of is that i (now looking at the file itself) flashed the wrong version (1646). I am now downloading the 1920 version so ill see if it works in an hour or so.
[Verizon Samsung Galaxy S III] lazarus2405:
Yep, that'd do it. You were trying to boot a kexec rom on a non-kexec recovery. 1920 and up.
[Verizon Samsung Galaxy S III] Kev13Dd:
Did you flash the correct 8/15 ROM from the testing folder? The only non-KEXEC ROM so far is the 8/15 ROM with a build date of 1920 in the testing folder

Your problem sounds like you flashed the KEXEC 8/15 build from a non-KEXEC recovery

K
[Verizon Samsung Galaxy S III] rossguy:
Great news! Is this fix in the 8-15 1920 Build? If so, I am going to flash. Can't wait to be rid of TW. Thanks to all the devs!

EDIT: I think I answered my own question. Seems the patch was released on 8-16 so it obviously wouldn't be in the 8-15 build. Looking forward to 8-16!!
[Verizon Samsung Galaxy S III] Josolanes:
What recovery did you use?

You'd need CWM 6.0.1.0 so that it can support kexec to boot kexec CM10
[Verizon Samsung Galaxy S III] ruben8448:
Sounds like the issue I had. Try to install cwm recovery and run it with that.
[Verizon Samsung Galaxy S III] aaronfuhrer:
The OP says to install the recovery do this:

I Recommend TWRP

Download Goo from Play Store.

Settings / Install Custom Recovery Project / Follow Steps

But inside my settings, the only options are:

Rom update check frequency

Download Path

There is no "Install Custom Recovery Project". Can anyone help? Does installing CWM 6.0.1.0 in EZ-Recovery work the same way? Can I just flash that recovery?
[Verizon Samsung Galaxy S III] tprouty:
I installed CWR from Rom Manager then I opened Rom Toolbox and setup an install queue for CM10 then GApps, selected wipe data, wipe cache, backup and its running nice!

Came from Beans 8
[Verizon Samsung Galaxy S III] aaronfuhrer:
Okay, thanks! So is Rom Toolbox just an easier way to install ROMs? Just going into CWR would work perfectly fine?
[Verizon Samsung Galaxy S III] somerandomguy1:
That's exactly what I just did and it's working fine. Had Beans before, unlocked with http://xdaforums.com/showthread.php?t=1835791

Went into EZ-Recovery, flashed CWM 6.0.1.0 from the menu. Booted into CWM. Wiped, installed the 1920 8/15 release, installed Gapps, booted up and running fine so far!
[Verizon Samsung Galaxy S III] aaronfuhrer:
Great! Thanks a lot, I feel a lot more confident about it now. Now I just have to wait for my slow ass internet to download the files...
[Verizon Samsung Galaxy S III] TheBiles:
Working very well with TWRP. :D
[Verizon Samsung Galaxy S III] incubus26jc:
I did have the wording a little wrong. Fixed now.
[Verizon Samsung Galaxy S III] dmbfan13:
So it sounds like we can use any recovery we want. I prefer TWRP, so I may just use that to flash CM10 1920 and Gapps.

Anyone know if theres an non kexec IMO kernel? I always had good battery life with that kernel and using CPU editor.
[Verizon Samsung Galaxy S III] TechSavvy2:
Several of the devs were waiting on imo's word last night to release it since he hasn't dropped it yet AFAIK. Supposedly he was off the grid last night.
[Verizon Samsung Galaxy S III] somerandomguy1:
That download isn't fast on any internet. Seeders on the torrent should make that the better option.
[Verizon Samsung Galaxy S III] incubus26jc:
but what do you know, your just some random guy. lol sorry had too.
[Verizon Samsung Galaxy S III] Flip35:
hey guys I'm reading a few posts about this I just want to make sure, right now I'm running synergy so if I want to run cm10 I can stay with the current recovery clockwork mod cuz I knw before we had to switch to the kebec recovery n now since we have unlocked bootloader is a little different so I can stay with cwm recovery, the same one I flashed synergy? Thanx guys

---------- Post added at 02:33 PM ---------- Previous post was at 02:28 PM ----------

Also do we download the cm10 under testing right???
[Verizon Samsung Galaxy S III] stkiswr:
I can verify that my coworker used ezrecovery to flash non kexec cwm. He then flashed the 1920 cm10 non kexec and Justin bean inverted 8/7 gapps. Works perfect. Still have to do the data toggle after a reboot to get mms working again but the ROM has been running for 5 hours w 0 issues for him. No soft reboots. No drama. No issues. Can't wait for next update w the merged code to fix mms completely but his gs3 is pretty slick. I run a nexus w aokp jelly bean and that's the gapps I sent him to use.

Also we used the terminal method to push aboot.
[Verizon Samsung Galaxy S III] Poloasis:
That's what its all about. Gj
[Verizon Samsung Galaxy S III] dmbfan13:
I am now also having this issue. Doesnt seem to want to activate. I hit the home button, and everything seems to work as it should. My number also says "unknown".

Also, my pictures dont show up. However, I know they're there because I can see them using the terminal. Any ideas whats going on? Anyone else have this issue??
[Verizon Samsung Galaxy S III] tekhna:
Alright, lemme see if I've got how this goes down. I'm on kexec CM10 right now.

Flash the unlocked bootloader

Flash normal CWM (either adb or ezrecovery)

Reboot into recovery, wipe, flash 1920 build

Profit?

Or will flashing cwm have to be done differently since I'm kexec booted?
[Verizon Samsung Galaxy S III] TechSavvy2:
Okay, wanted to say something earlier, but I thought I'd test it so I didn't look like a dumbass first.

Wasn't 6.0.1.0 the kexec based recovery that we used previously? Because a ton of people posting to use 6.0.1.0 from ez-recovery with the 1920 build since both are non-kexec (except they're not!)

I used ez-recovery, and flashed the NORMAL 5.8.whatever it was (touch based one) since it was non-kexec and I used previously for stock-based, downloaded 1920 from tests folder and bam, everything works perfectly.

Oh Jelly Bean, how I missed you..........(haven't picked up my GNex since I bought my GS3 :))
[Verizon Samsung Galaxy S III] Mooem7:
Same, used the 5.8 touch based recovery from ez-recovery with 1920 and it flashed fine. No issues so far outside of the MMS problem (which hopefully will be fixed in a new build soon).

Anyone have any ideas for getting picasa sync working in the gallery?
[Verizon Samsung Galaxy S III] Josolanes:
I used 6.0.1.0 and still have no kexec running by finding a nokexec kernel

Here's imo's nokexec kernel (0.4): http://rootzwiki.com/topic/32286-ke...l-minimalistic-kernel-v03-and-v04-beta-81512/

I'm using this with CM10 from 8/12 and modified a file in 8/12 to disable kexec. My phone boots up with imo's 0.4 (confirmed in status) without any reboots or anything - just a single boot straight to CM10 8/12

I'll wait until the MMS fix is implemented to reflash CM10. Right now I'm pretty happy with my setup and that's the only thing I'm really waiting on :)
[Verizon Samsung Galaxy S III] taters343:
I'm randomly dropping wifi, generally only for a second or two. I also get crashes when trying to access the keyboard settings. I tried reflashing after a factory reset and what not, and I tried fixing permissions with no luck. I've had a few more things consistently crash on me, but that's the only one I remember right now, I'll post an update if I can get any of the other ones to happen again.
[Verizon Samsung Galaxy S III] IAmPears:
installed it and it was awesome. switching back to stock just until the kinks get worked out
[Verizon Samsung Galaxy S III] taters343:
Data dropped and wouldn't come back for over an hour. Tried restarting, tried changing the data settings, still nothing. Restored Bean's Stock ROM for now, hopefully the bugs get worked out soon.
[Verizon Samsung Galaxy S III] herbiehusker2608:
Is the clock weather widgets from the op in this Rom? It's pretty cool. I could not find it in the widgets. Also is there an issues with playing videos on this to?
[Verizon Samsung Galaxy S III] knifedroid:
The stock browser keeps crashing on me. It will begin to load a page and then just close. I downloaded the ICS+ browser and it force closes on open.

Any ideas? I wanted to play around with Google Now for a few days before going back to stock for Samsung's camera and motion controls.
[Verizon Samsung Galaxy S III] ali87va:
Same thing happened to me, I downloaded the phone info app and changed settings from there because the one inside cm10 was showing differently.
[Verizon Samsung Galaxy S III] kschmidty17:
I am also getting intermittent data connectivity issues. I was wondering what settings you changed in the phone info app to fix this?
[Verizon Samsung Galaxy S III] ali87va:
Just go into phone info and change the settings to cdma/lte and you should be good to go.
[Verizon Samsung Galaxy S III] knifedroid:
I'm an idiot. It just dawned on me that there's no flash support for JB. Just had to uninstall flash.

At least I go to quote myself.
[Verizon Samsung Galaxy S III] IAmPears:
i think that clock widget is from motoblur but i cant seem to find it
[Verizon Samsung Galaxy S III] droidstyle:
If you guys want a little easier method to installing cm10 click the link in my sig and look up section 5. :cool:
[Verizon Samsung Galaxy S III] OnceAMatrixMan:
Looks like UCCW - Ultimate Custom Clock & Weather Widget
[Verizon Samsung Galaxy S III] incubus26jc:
I am using "One More Clock Widget Free"
[Verizon Samsung Galaxy S III] Fadingintofall:
The clock widget is... I believe... Rings Digital clock.

If not, it's from Motorola Atrix HD

Edit: or what the op said. I'd go with what he said.
[Verizon Samsung Galaxy S III] rushless:
Isn't that a tad presumptuous, considering just a few hours of rom existence?
[Verizon Samsung Galaxy S III] ali87va:
Meh still running on it without any issues : P
[Verizon Samsung Galaxy S III] graymonkey44:
This ROM is crazy smooth! I am 100% sure I will never go back to TW now. Thank you! Plus having AOSP is awesome after coming from the Rezound with nothing and everyone at each other's throat!:D
[Verizon Samsung Galaxy S III] herbiehusker2608:
Here it is! https://play.google.com/store/apps/...=organic&utm_term=rings+digital+weather+clock
[Verizon Samsung Galaxy S III] turbosrrgood:
While this ROM does work pretty well for such an early release, to say it doesn't have any issues is not accurate. There are many, mostly minor issues, that others have already posted in this thread.

For me the "irregular" haptic feed back is the main thing that prevents this from being a daily driver.

I understand that some get excited about the prospect of newer versions of software, and to them it "feels" like everything is working. However this is most certainly an alpha build for a reason. Something people might want to keep in mind if they are trying to decide whether to flash it.
[Verizon Samsung Galaxy S III] bobdude5:
Flash kind of works on dolphin browser but its a little buggy. Not unusual for flash though .

I'm having a problem with YouTube. It keeps force closing every time a video starts
[Verizon Samsung Galaxy S III] TechSavvy2:
I also have the issue with phone number saying unknow, it "activating" upon rebooting, and to add to this - Mobile network state is disconnected, and MEID is all zeros (unlike the MIEI problem). But just like you, my phone actually works fine.....?!?!?!
[Verizon Samsung Galaxy S III] Josolanes:
Nice! Thanks!

Question, going from 8/12 should I do a full data wipe and all or do you think a dirty flash might be alright?

I may just suck it up and do a full wipe :-/
[Verizon Samsung Galaxy S III] dmbfan13:
Anyone having these issue?? I just flashed IMO's kernel, and my number still says unknown. Just really curious about the pictures thing. When I take a pic, it saves it next to all my other pictures.
[Verizon Samsung Galaxy S III] aaronfuhrer:
I haven't changed my kernel at all since I bought the phone, so I don't need a new kernel or anything, do I?
[Verizon Samsung Galaxy S III] jdhas:
I'm no dev, but I think you're generally more likely to reap the benefits of changes such as this when you do a full wipe. That said, considering how (relatively) minor these code changes are, they should take after a "dirty wipe". I'll be testing shortly, just backing up apps and trying to look busy at work. ;)
[Verizon Samsung Galaxy S III] TheBiles:
I've noticed that the photos and ring tones on my internal storage aren't showing up in the gallery and sound menus, respectively. 1920 build.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] Josolanes:
Haha sounds good. Unfortunately I couldn't wait and already flashed -_- lol

I've gotten too used to going through the routine of installing everything and setting it up. It's interesting to see what I change every time now :p
[Verizon Samsung Galaxy S III] neyenlives:
6.0.1.0 works with kexec enabled kernels

in addition to

standard usage you've known forever. The CM10 1920 build from 8-15 is non-kexec based. I was running the8-13 kexec CM10 build with 6.0.1.0 of course last night when news broke. All I did was plug my phone in, use Casual to root and flash unsecure aboot, then straight up dirty flashed the 8-15 1920 non-kexec CM10 rom in CWM 6.0.1.0, no problems.
[Verizon Samsung Galaxy S III] Karl:
Is the mms fix still needed?, first cm10 flash
[Verizon Samsung Galaxy S III] ddggttff3:
*sigh* well took the dive into CM10. backed up my EFS so if anything went wrong, all would be good. Messed with it for a bit, and I just dont think its there yet. so I restore my stock rom, and it says im roaming. Checked my IMEI and everything, and its all what it should be. So I restore the EFS, and do data wipe, and it still is stuck on roaming :( No data or calls. What do I do?
[Verizon Samsung Galaxy S III] Josolanes:
I just confirmed that the phone number works automatically after a restart so the MMS fix shouldn't be needed any more. Haven't tested MMS but this was the cause from what I understand
[Verizon Samsung Galaxy S III] ddggttff3:
My bad, figured it out.

NOTE: Dont leave it in NV mode, then flash to stock. Phone will logcat saying it is not provisioned, thus think it is roaming.
[Verizon Samsung Galaxy S III] rossguy:
What did you think was "not there yet"? I was about to flash seeing as how the data is better and MMS is fixed. Just wondering what was still in the process of being worked out. Thanks.
[Verizon Samsung Galaxy S III] ponyboy82:
Are there any working/not-working lists out there? It's been difficult to track where things are at.
[Verizon Samsung Galaxy S III] Dcox28:
I just downloaded and installed this ROM from CVPCS. I rebooted the phone and checked status and my Phone Number and MIN are both Unknown. Either fix didn't work or it didn't work for me. Either way, I had to do the manual MMS fix again to get it back.
[Verizon Samsung Galaxy S III] WildZontar:
Noticing a small, intermittent screen flicker that you really have to look for. Anyone else?
[Verizon Samsung Galaxy S III] ddggttff3:
Just the radio problems I was having, but seems to be fixed now after my little mess-up and a data wipe. I am testing MMS atm, waiting to receive a message from a friend. if it doesnt work, then im back to stock, otherwise this build seems quite solid. also lean kernel helps it be faster :D
[Verizon Samsung Galaxy S III] neyenlives:
that's been there for a while now in every daily build since around 8-10