yashsingh1/xdaforums huggingface dataset:
[Galaxy Camera Android Development] Jiggity Janx:
Another thing I learned while I had my ATT galaxy tab 8.9 was that Samsung likes to use the same hardware in their South Korean version of their devices with cellular and in their US devices with cellular. It's almost certainly because of the LTE requirement. Wouldn't you know that such is the case with the Galaxy Camera. The South Korean version of the camera has a Qualcomm board just like the Verizon one. Maybe the firmware for it, which can be found on Sammobile at the link below, can be helpful.

http://www.sammobile.com/firmwares/1/?model=EK-KC120S&pcode=0

EDIT: To clarify more, the Korean version uses a Qualcomm 9215 baseband board with Exynos 4412 while the Verizon version (based on Samsung own specs page) uses a Qualcomm 9615 which has it's own applications processor.
[Galaxy Camera Android Development] Jiggity Janx:
CPU Z says the Verizon GC120 DOES use the Exynos 4412 (smdk4x12). It makes no mention of the Qualcomm board on Samsungs' own specs page. They don't make this easy...

Still need any Verizon build anyone has (original 4.1.1 or 4.1.2 update which should be found in /cache).
[Galaxy Camera Android Development] twistedumbrella:
Newest JZO54K.GC120VRAMC4

Previous JZO54K.GC120VRALL2

The one in the op should then be the 4.1.2 update
[Galaxy Camera Android Development] Jiggity Janx:
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
[Galaxy Camera Android Development] twistedumbrella:
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.

Edit: Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
[Galaxy Camera Android Development] Jiggity Janx:
edited out...

You can still likely see what was written in your thread quote notification but it doesnt need to be hashed out here.
[Galaxy Camera Android Development] twistedumbrella:
It isn't about feelings, its about development.

Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
[Galaxy Camera Android Development] Jiggity Janx:
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required

XDA - development FORUM that requires HUMAN interaction

Now....

I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).

So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).

Thank you again for assisting us all with development on this device.
[Galaxy Camera Android Development] twistedumbrella:
Look at the number of developers who have left xda butt-hurt about some comment a nameless, faceless text blob made about them because of how they read it. The device suffers, the users suffer, and some kid is up in his room crying about a hobby gone wrong.

As for the rollback, it was only theory anyway so if there is any doubt about what to change its better to find an alternative. If you could get images of the partitions from stock condition, it is possible to build the install. At least that is all done off the device where it won't corrupt anything. You could root, get the system, data, cache, and boot then merge those with the Korean release to fill in the missing parts. To the best of my knowledge, the bootloader and such are not region specific. That should be verified first, though, because you can't go back later.
[Galaxy Camera Android Development] Jiggity Janx:
Rolling back the build.prop to see if it would download the update was a good thought. I am willing to try it once I get the device I will end up keeping. Need those values though and I don't know if anyone posted them in this forum. I came across some on the net in my search to find other models like this one but don't know if they would be helpful.

Mentioned to EVA it would be helpful if one of you more knowledgeable folks could write up the dd command line for adb once to make sure I have it right then list below it the adjustments I need to make for the partitions and resulting .img name. Just didn't have time yet to pull those together and check to make sure I pull something usable. Also I seem to have lost odin access to the camera I am returning but still have adb access while in the recovery. When I polled for partitions though it only gave me /dev and /system. Maybe you know what's up with that?

Merging those files with the Korean release was what I was aiming for when I mentioned the similarity. I wouldn't know particularly how to accomplish that and it may be quite a bit of work so likely a last resort. My concern with the bootloader would be whether or not Verizon locked their bootloader. This is using the Exynos 4412 like the Verizon GN2 with updates that locked their booloaders around the same time.
[Galaxy Camera Android Development] twistedumbrella:
dd if=exact/path/or/partition/of/source of=exact/path/of/output

I can post the partition paths a little later, but you will want to write to extSdCard not sdcard0 or you'll run out of space fast.

If you have dev and system it sounds like the system partition mounted, but there is an issue with the boot. You should also have /sbin and /proc

I believe the Odin OTA is just a collection of md5 signed images in a tar with a signature file. All the modifying needed would really be just changing the signature file to match the new md5 values and putting them all together. I will have to look what all comes in the Odin archive before I can say what is needed, but the only one that would be any trouble is a radio image.
[Galaxy Camera Android Development] twistedumbrella:
Partition breakdown

https://github.com/StarKissed/ek-gc...ldimg/recovery.img-ramdisk/etc/recovery.fstab

You can verify they are the same for the 120 by checking where the symlinks lead in /dev/block/platform/dw_mmc/by-name/

Example: ls -l /dev/block/platform/dw_mmc/by-name/BOOT for me returns /dev/block/mmcblk0p5
[Galaxy Camera Android Development] Jiggity Janx:
Great. Thanks. Was just about to sit down and *hopefully* pull these.

Also the 'new' gc120 I received was purchased from a different source but appears to come from the same 'warehouse' so I have the same problem. It looks as though they get in the camera and load a verizon demo model img they somehow got. Looks like this is how they are updating the cameras before sending them out.

I hope everyone else that receives one of these returns it for full refund and shipping costs like I am.
[Galaxy Camera Android Development] twistedumbrella:
It can't be disabled? I got my Apple TV in "demo mode" and it was a menu option you had to disable. It was because store staff is usually lazier than owners and wouldn't turn it on unless it was the preset.
[Galaxy Camera Android Development] Jiggity Janx:
This one appears to be a different build with a .02 at the end of the build number and the words PRE EMP in the version.

It likely can be disabled if I edit a bunch of atuff or .bak the vzw demo install system apk but I dont want to start with a device that way.
[Galaxy Camera Android Development] E:V:A:
If that is really the partition table, it seem that it would confirm that the EK-GC120 is an Exynos based device. This is bad, from a HW developer point of view, since we have very little available info on this chip including the accompanying modem chipset, which is likely the Intel XMM6360... This means no LTE telephony...

But please feel free to post a more complete partition layout, by running the tools mentioned in my signature. (You need to be rooted.)
[Galaxy Camera Android Development] Jiggity Janx:
Should be getting another another another Verizon GC120 in the mail shortly so will hopefully pick back up where we left off...

EDIT: The new (to me) camera I received is still on the 4.1.2 firmware. So I should be able to pull those partitions before the update and provide the update.
[Galaxy Camera Android Development] swjpilot:
A little late... but i reposted taht firmware update under the same link as before.

http://d-h.st/users/swjpilot/?fld_id=16995#files
[Galaxy Camera Android Development] nuke072786:
I've been trying to figure out how to root my EK-GC120 that has already been updated to android 4.1.2. It seems the best route would have been to root the device on 4.1.1 before updating to 4.1.2 and keeping root through the update. Since I failed to do this, is there an ODIN image of the 4.1.1 image?

Through reading the thread it appears not...

So in summary am I sunk, I cannot root? I am not using a sim card in this device. Should I try flashing an EK-GC100 4.1.1 image to the device and rooting? I feel like this would be a risky route to go....
[Galaxy Camera Android Development] Jiggity Janx:
I did not come across anything that would indicate 4.1.2 could be rooted. But keep looking...

BTW I dont think you can downgrade the 4.1.2 bootloader to 4.1.1 or lower without perma brick

*because I believe 4.1.2 update is right when samsung started locking bootloaders
[Galaxy Camera Android Development] TroyLeeWells:
I know it has been a while but I was able to root my ek-cgc120 (vzw) by using Kango root.

It had a hard time detecting my phone for the longest time but I kept going into Device manager on my PC and making sure all the drivers were showing as good.

After a while it showed and I was able to root with no issues.

Kango is a fickle lover...

Good luck!
[Galaxy Camera Android Development] twistedumbrella:
I just noticed this post but still don't have time to sift through all of the links to find which tool for the device I don't actually have you are referring to. Thanks for the invitation, though.
[Galaxy Camera Android Development] Hidesquadron1:
totally worked!

I can confirm that Kingo (I think you spelled it wrong :p) works like a charm on the latest official EK-CGC 120 software. (4.1.2 I believe).

Been sitting on this device unrooted for months now and the weight has finally been lifted. Very happy to at least have root access. IF anyone has some direction on custom roms/recovery for the verizon version, I'd be most grateful. Searching other threads hasn't been very helpful so far. Will I have to use special versions of custom recovery on the verizon model, or can I use the others listed here (roms as well. I'd like to get some lightweight rom on here if possible).

Thanks to Troy for the heads up. So happy this worked!
[Galaxy Camera Android Development] TroyLeeWells:
Ha...I never even looked...I thought it was a play on kangaroo. ..

:)
[Samsung Captivate Glide] suret:
Within a second my Captivate Glide will suddenly go to 0% power then slowly charge back up over time..or if I charge it, it jumps back up to about where it left off. And it happens pretty much every time I turn my phone on for more then 5 mins. It seems to happen while sending or receiving text? Any ideas what could be causing this or a solution?

I keep my data off, and theres 3 apps (Stock SMS Messenger, Handcent SMS, and the Contacts+ App) that can handle SMS on my phone, and I have locker pro that displays my notifications. And I also use the Nova Launcher, but thats the only app's I keep running. Maybe a conflict with the apps or a bug with one of the apps? I don't see how that'd effect the battery that much but possibly?

I've also changed my ROM a few times, but right now I'm back on the newest ICS update and I've rooted it. Maybe I need to change it again? I can't remember if this problem started happening before I did my last change.

Or maybe just a bad battery? I don't know much about batteries but I haven't had this phone long, I don't think it'd be the battery.

If you have any more questions feel free to ask and I appreciate any help!
[Samsung Captivate Glide] TL1170:
I had about the same problem, with it working fine with a decent charge (anywhere between 30-80%), and all of the sudden it would say "battery critically low" and shut down. Putting it on the charger would often get the charge to show what it was before it freaked out.

I noticed that the battery was starting to bulge and get somewhat "mushy"....which told me the battery was probably going to explode or leak if I didn't replace it soon :o

I have had the phone for a year and four days, and this just showed up in the last few days...fortunately I bought an extended warranty and they will pay for the replacement battery I just picked up today.

FYI, the battery should be totally flat on both sides. Mine would wobble if I set it on a table.
[Samsung Captivate Glide] suret:
Ok, TL1170, Thanks!

I already narrowed it down to my battery by the time you posted that because I factory reset my phone multiple times and changed the ROM once to see if that'd help, and it didn't..I was running out of stuff to blame it on :p..

But yeah, my battery is pretty badly deformed and I just ordered a new one.
[Samsung Captivate Glide] jester131:
Thanks, mine is doing the same thing - about once every 2 days or so. I can see in the battery life plot that it sometimes goes from 90% almost completely vertically to 0% and then right back up to 90%. I don't see any obvious bulges or "mushiness" to it, but it doesn't seem to be completely flat when put on a table. I'll see if I can get a replacement battery, this phone was not used by it's previous owner for maybe a year or so before I bought it, maybe that might have been part of the problem.
[Samsung Captivate Glide] Neuntoter:
Any time a battery is misshaped it can do the oddest things.
[Samsung Captivate Glide] roothorick:
Pull out and visually inspect your battery. If there are any visible cracks or bulges, dispose of it carefully. Damaged lithium ion batteries are incredibly dangerous; a properly pissed off LIon will produce a sizable fireball.

If your battery looks fine, fully charge it (until your phone says "100%" or "Charged"), then fully discharge it (don't connect to the charger again until your phone shuts off for lack of power). This is to calibrate the charge estimator chip in the battery itself. Don't bother with batterystats.bin, it's completely unrelated.

If the above doesn't work, you need a new battery. If the new battery behaves the same way, you need a new phone :(
[Samsung Captivate Glide] jester131:
Happening to us too

It's been happening to my phone for a while now, but I'm usually using it while at a desk so I can keep it charging. However, it just started happening to my wife's Captivate Glide also. I checked my battery and don't notice any bulging or non-flatness... but it happens about once or twice a day now - Pretty much anytime I do anything more than make a call with the battery indicator saying it's somewhere less than maybe 90% charged. I've taken to using a portable backup battery when I'm out.

If you view the battery usage screens, you can see the cliffs where it drops from 80-90% down to zero and right back up. We've only had them for about a year, so I'm going to take it to AT&T and see if they can do anything for it... probably not.
[Samsung Captivate Glide] roothorick:
If you're really desperate to get those particular batteries working, you could try cleaning the contacts, both on the battery and in the phone, with rubbing alcohol and Q-tips. But most likely you will need new batteries.
[Samsung Captivate Glide] b80m4rl:
Battery( low power) Shut Down Issue Fixed

I also was having the "critical powerl level" shut down issue over the past two weeks. My phone is about two years old, and there was a few occasions in the past two weeks where i pulled it out of my pocket and it was off. Then this past week the phone (on a full charge) would go anywhere from around 90% sometimes %40, and then all of a sudden say "battery low" and shut off. It would turn back on, but would only stay on for a few minutes.And a few times it also got really hot. It wasnt doing this when plugged into the wall so i examined my battery and there was NO visible flaws or bulging of any kind, it looked fine. But as we all know just because it looks good certainly doesnt mean it is so i odered one on ebay for about $10. It arrived 2-3 days later and instantly fixed my problem. The phone is fine now and hasnt done anything wierd. It was the battery. These batteries have a limited life span, and very often the phone may say the battery is 76% charged but the capacity of the battery under load can still draw it down to 0%. You cant always trust the level the phone says its at. So if anyone else out there is having this power issue it really isnt expensive to find a good battery out there. The one i got was $9.98 and it is a Samsung battery identical to the one that came with the phone. Except the new one has a fresh date of 2013 on it. Very happy to have my phone back. Ive never been a part of any sites like this, but im posting here now because there seems to be a lot of people having this issue, and often someone will put a very complex procedure on these sites to fix an issue when its not always necessary. If you have the power/shut off issue like i've described here and your phone does the same as mine was its probably the battery, and for the price of a new one like i got, its worth trying.
[T-Mobile Samsung Galaxy S II SGH-T989] namelessghoul:
Hey guys,

I was having trouble with a previous ROM that I was using (Paranoid Android 4.2) after several months I decided to reflash...

With a pretty full internal SD so I decided to delete some of my old files etc. I picked a new ROM (JediMindTricks 4.2), updated my CWM/Rom Manager, wiped with SuperWipe, Installed the rom, and now I am stuck in a real jam....

Of course I am boot looping and as a result of that I am trying to revert to a backup, however CWM freezes almost instantly when trying to do anything. Whether it's wiping, reinstalling, or restoring a back-up it freezes. So with a similar previous issue I decided at this point I need to revert to stock ICS using ODIN. Inside ODIN (which I have never had any issues with) when I put the phone in download mode ODIN never recognizes it and will not allow me to revert to stock...

At this point I seem to be out of options.... What do you guys think?
[T-Mobile Samsung Galaxy S II SGH-T989] jonmassot:
Did you try to boot in recovery and install CWM from internal SD? Wipe data / factory reset and wipe cache in recovery mode... I'm not an expert but it won't hurt to try!
[T-Mobile Samsung Galaxy S II SGH-T989] namelessghoul:
Unfortunately it is completely unresponsive when attempting to install any version of CWM.zip that I try to install in recovery.
[T-Mobile Samsung Galaxy S II SGH-T989] jonmassot:
Yesterday I had trouble with a bad upgrade through Kies and my cell kept telling me to plug it with Kies and do an emergency recovery. Nothing worked as the emergency recover didn't work with my cellphone and I wasn't able to boot in recovery nor download mode. I had to plug it in another computer and re-ODIN an earlier version of my stock rom... Not sure if it will helps you...
[T-Mobile Samsung Galaxy S II SGH-T989] gc84245:
Plug in your phone to your computer, open kies, select "emergency firmware recovery", enter serial number from phone (write down beforehand) then cross your fingers and hope for the best. Good luck.

Also, be careful with those wiping scripts.

Sent from XDA app
[T-Mobile Samsung Galaxy S II SGH-T989] namelessghoul:
After literally wrestling with this for the last 7 hours ODIN has finally recognized it...
[T-Mobile Samsung Galaxy S II SGH-T989] zxstyle07:
You DONT super wipe with the latest cmw recoveries. Superwipe was made for the early 5.0.x.x version, it breaks the new recoveries.
[Samsung Galaxy Player 4.0, 5.0] Mmmm-):
I have a SGP5 and am using Jackpot Clavin's CM10.1 rom.

I find that the number of volume steps is too few when using headphones. Often consecutive volume settings will change the volume too much, so that one setting is too soft and the next too loud.

The solution to this is to increase the number of steps over the same volume range.

I have successfully managed to do this using the following guide (it was quite easy actually):

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

Doing this produces a framework.jar file which needs to be placed in /system/framework with permissions "- rw- r-- r--" (ie read/write for user, read only for everyone else), and after a reboot (during which it will say it is upgrading) you should have the extra steps.

Anyway, seeing as it works I thought I'd share it here in case anyone else wants to have more steps to their volume (rather than the original 15 steps).

I've made some CWM flashable zip files to make things a bit easier.

Volsteps2-30 will give double the steps, so to increase the volume by what used to be one step now takes two steps.

Volsteps2-45 will give triple the steps, so to increase the volume by what used to be one step now takes three steps.

This theoretically should work for any rom (or even device) but it may be the case that a different zip file will be needed for each one. To make this compatible with more roms/devices I need your /system/framework/framework.jar files so I can patch them and make an install zip. But try it out before sending your file, there may be a version for you already made...

Instructions:

Remember to do a nandroid backup first!

Download the uninstall zip and one of the install zips from below.

Flash the install zip and reboot.

if it works, great...

if not, you'll probably find you're in a bootloop, get back into CWM (with the button combo) and flash the uninstall zip, (this will restore your system to its previous state), reboot and reply to this thread telling me that it doesn't work, what rom and device you are using and attach your framework.jar file (found in /system/framework/).

I'll patch your framework.jar file and make a new zip file for you to try, if it works for you I'll attach it to this post with a suitable description.

We'll see if we can get a nice collection for all the roms...

For UNINSTALL.zip and SGP5.0 mods see the files attached below

For SGP4.0 mods see post #79: Volsteps Mods for SGP4.0 Player

--------------------------------
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
nice find but this should be in the D&H section. not in general
[Samsung Galaxy Player 4.0, 5.0] TheKryptonite:
Tried it on 10.1 and it caused a damn bootloop.
[Samsung Galaxy Player 4.0, 5.0] Mmmm-):
Really? hmmmm, JC's 10.1 or iurnait's? if iurnaits, give me a copy of your framework.jar and I'll patch it for you if you like and we'll see if that works.
[Samsung Galaxy Player 4.0, 5.0] TheKryptonite:
Iurnait's. I can't because it's stuck on a bootloop, and wiping data/cache didn't work either.
[Samsung Galaxy Player 4.0, 5.0] Mmmm-):
You made a nandroid backup right? just restore that.. or if not reinstall the rom from scratch.
[Samsung Galaxy Player 4.0, 5.0] TheKryptonite:
Nope. I can't because I can't find my SD card and it doesn't exactly work correctly anyway. I'll just have to install the stock ROM and do it like that.

Edit: I found it, but my computer doesn't want to read it, so yeah...