yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
I'm no ADB expert, but I've dabbled with it when theming my UI a while back. To move files you can use the ADB PUSH command. In order to use this command you need to have the files stored in the folder where the Android Java SDK files are stored.

For example, in my case, the location where I access ADB is at, and any files I ADB PUSH need to be stored here:

C:\Program Files (x86)\Android\android-sdk\platform-tools

Then, you would need to use the following command:

adb push <file name> <destination on device>

ex.:adb push HowToMakeFelafel.txt /system/lib/HowToMakeFelafel.txt​

Again, that is just an example, but is how you would perform the command. The file name and location are going to be unique to each push. I hope I haven't confused you at all. Good luck.
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
I did exactly what you just told when I tried before. It's weird, it said it was transferring and all but when I rebooted the files weren't there. I made sure I made remounted as row and also put it in the right location.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
When you first connect your device via USB, you can verify that you have a solid environment to use ADB with by typing: adb devices.

Upon typing this command a long number should pop up, indicating that your device is connected. I wish I could help you more.

Is there an error message indicating failure to transfer? If so, copy and paste it into your reply. Perhaps, someone more skilled than I can help you. Good luck.

---------- Post added at 02:06 AM ---------- Previous post was at 01:53 AM ----------

Also, correct me if I'm wrong, but wasn't there an issue where any changes made to the root of the device failed to stick after reboot? It could be that the files are successfully transferring but the reboot is reversing any changes you've made to the root directory.

After transferring the files, do not immediately reboot. Instead, after ADB completes the transfer, navigate directly to the directory where you transferred the files and verify the transfer.
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
I moved the files using the commands you said but as I said, they didn't transfer. I looked using root explorer and the files weren't even there before the reboot, I was hoping they would appear after reboot. I can't test right now, but I'm sure it was connected because I made sure by unplugging the device and trying an adb command and it said "device cannot be found", so it had to be recognized.

There were also no error messages either, it said it was transferring but is there supposed to be a "successful" message of some sort? Cause I didn't get any, it just said the files were transferring and the speed.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
That is the success message, but don't worry about it for now. I'll see what I can do.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
At some point, when I have some free time, I may have a go at testing the ROM and the patches Supermaster put out.

I have a Korean SGP 5.0 which has the physical home button like the international 5.0. The difference is that the Korean version has a 5megapixel camera. Any chance that the camera patch won't work with my device?

Also, is there a pre-alpha available with soft buttons enabled?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Not officially, but I'm working in building from source, so then we will.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Status update: we can't really go forward with development until we build from source. I have cm10 successfully compiling with a modified version of JackpotClavin's cm9 device tree. It boots with the libcamera_client.so from the a (Because JB has no libsurfaceflinger_client.so), but it loops due to something wrong with the graphics hw libraries. (Surfaceflinger errors out with HAL being unable to connect to the framebuffer.) on a positive note, the /system bug is fixed and it looks like the internal sd card will function.

I will upload the device tree to GitHub this evening, but until someone figures out graphics, I can't do anything more.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Are you using the new pvr libraries to match the kernel version?
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
Higgs_Boson, I transferred the files correctly (but I could only transfer them to / because /system could not rw), and I rebooted and they weren't there. It must be like you said, the reboot reverses any changes that happen.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Thats the issue I think. I've tried mixing and matching, and I have some ideas for this evening. Do you know which libraries/binaries I should take from the prealpha vs stock?

That's due to / being the kernel's ramdisk. It's not a partition, but is extracted every boot.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
You could download the nexus s binaries from Google. The latest from jellybean should be what we need. Different files go into different folders though, but the files and locations are in the .mk file once the binaries are extracted
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Make sure the new gralloc.whatever it's called now matches the old gralloc.whatever it was called before you added the new nexus binaries
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Did that work? Could you post the zip and I'll give it a go. I haven't picked up my player in a week or so, been busy :(
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
I might try the camera thing tomorrow. I was working on my comp today and this thread is getting interesting

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I'm not quite sure what you mean. Do I use the gralloc from the nexus binares? Or from stock? No, I'm still on it.

EDIT: I figured at least that part out. Removing gralloc.s5pc110.so allows gralloc to setect the screen size. But i still am getting 'couldn't find an EGLConfig'.
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
How high a priority is the sound bug? That is kind of the only thing that bugs me, I can't watch YouYube videos or even Netflix with the new hardware acceleration...
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Our first priority is getting a working device tree/blobs. That way we can build from source, and vold will stop bricking things :). (And modifying /system will work.) Then we can work on sound a lot easier, and maybe things like bluetooth and camera - but those are a ways down the road. First we have to get it booting.

tl;dr: No further work will be done on the current pre-alpha.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Remove the old gralloc.s5pc110.so that came from stock, and rename the new gralloc.something.so you took from nexus s binaries to gralloc.s5pc110.so
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Ok, doing that doesn't give me any gralloc messages, but it doesn't give any gralloc errors, either. My battery is dead right now, but i believe using the nexus gralloc also gets rid of the 'eglInitialize bad_alloc' warning.

Edit: this is my current device tree (yes, it could use some cleaning). You'll need to flash the 3.0 kernel separately after the zip. It's too big to upload to xda, so here it is: http://mevordel.usgrd.com/files/android/device.zip

Edit2: I added some tracing in the EGL initialization routine, and it turns out that eglGetConfigs() is returning 0 configs. That explains why it can't choose the right one :cyclops:

Edit3: Everything is now on my Github https://github.com/Mevordel. You'll still need to flash the kernel afterwards.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I think this deserves a bump :)

I got it to work!!! It turns out i had all of the right files, just that they were in the wrong folder (see the end of http://e2e.ti.com/support/omap/f/849/t/211841.aspx). So in a couple of hours, I'll have uploaded a new cm10 ROM, and I'll update the device tree. It only just booted, and I haven't tested things like wi-fi or bt, but I know a few system-level bugs are already fixed, and development will be much easier from now on.

Edit: I built it, and found a major bug (everything FC'd). It is fixed. Rebuilding now. In other news, through trying to flash back to a kernel with CWM, my player is now 100% bricked :( . So I may not be able to work on this any more. But I think it died just in time for me to be done :)
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
Holy crap, can't wait :D
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Will you be providing a changelog sir?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Yes, here it is:

* Built properly using venturi_usa device tree from CM10 source

* Softbuttons enabled

* Modifying /system works now

* HW acceleration still works

* Internal SD *may* work (can't test - see above)

* Wifi may possibly be broken (also can't test)

* Bluetooth is probably broken, and GPS I have no idea
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Oh no, what happened? Completely bricked? :'(
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
mmhmm. No lights, no sounds, no resurrector... I couldn't get back to recovery mode after flashing Entropy's kernel in download earlier today, so I thought I might have some partitioning/param/residual junk issues. So I flashed back to stock in Odin (with PIT), but it kept getting stuck on setting the PIT. So I tried without, and stock booted fine - recovery and normally (so I know the problem's not bad blocks). So now I've built cm10, and I'm at my linux box. I flash Entropy's with heimdall (same version I always use). No dice. I'm thinking it's a corrupt param.lfs - after all, button combo should work with corrupt /cache and whatnot. So I run my handy unbrick script (from the days where vold kept corrupting my pbl - must have used it 50 times) while in download mode to flash PBL, SBL and param. Reboot, and whadaya know? BRICK.

In hindsight, I'm pretty sure the issue is a corrupt PIT leftover from Odin that caused heimdall to write something wrong, because I know the only way to completely brick this device is to corrupt the SBL, but not the PBL. After all, if they're both fine, you have download mode, if pbl is broken, you get resurrector. So basically I'm dead until I can fix the SBL or purposely b0rk the PBL and use the resurrector.

ETA on the new CM10 build is 30 minutes to an hour. I will update the OP once uploaded. Then someone else may have to take over. Everything I have is on GitHub (https://github.com/Mevordel), and I can provide a local_manifest.xml if needed.

Also, If you all think it's useful (for kernel dev or whatever), I can upload pics of everything inside my deconstructed device. :)
[Samsung Galaxy Player 4.0, 5.0] kfirbep:
Merdovel u still can fix your device I did it when I had full brick. U need linux and some software that I can remember her name but there is a guide in this forum.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
Is it possible to overwrite the corrupt PIT with the default PIT via Heimdall or Odin? I have a PIT file handy, but I have a 32gb Korean model; not sure if that matters though.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
I've got a brick thread bud where everything should be there. If you need any file don't hesitate
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Believe me, I know about the Resurrector (used it many times). I'm past that now. Basically my only options now are JTAG or the hardware UnbrickableMod.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Here is the new ZIP: http://www.mediafire.com/?nkmvzafmhu5m8ib. I haven't tested it, and, come to think of it, it probably won't boot. But it would be immensely helpful if someone could do a full wipe, install this, and give me a complete logcat, and in addition, the output of the command 'adb shell mediaserver'. Thanks.

(There's a library issue - probably a quick fix.)
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
Whatever possible, please try. We need you, man.
[Samsung Galaxy Player 4.0, 5.0] aznflawless:
What progress have you guys gotten so far? Just wondering.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Well, bugs keep popping up, and I've already fixed some issues from the zip I posted yesterday (which bootloops, by the way). I don't have time today to post another build, but I should get one in tomorrow evening.

Considering my player's situation, I'm not sure if I can afford to JTAG it, as it's not really a device I use, except for development. If I don't, I'll still try to get one working zip, and then y'all are on your own.

Edit: if someone wants to fix the zip, all it needs is the gralloc.s5pc110.so from the Nexus S proprietary video drivers and one other library. I don't remember which, but it's the last one in the error message you get from running 'adb shell mediaserver'. I either pulled it from stock or the prealpha. One final note: after adb pushing the gralloc library, you'll need to run 'adb shell pvrsrvinit' to reinitialize the video driver. If you do all that, and you still can't get it to boot, send me a logcat, and I'll try to diagnose.
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
Thank you for everything but i would like to unbrick that player,i dont now anything about kernel development ,if you go its be provably dead (only hope JK) :D
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
You sure you can't unbrick it? I've hard bricked mine twice already and both I've been able to get it to work. First time took me three weeks though.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
It's not detected in the resurrector, so no.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Are you having the same problem that another dev had where he had to do something to the PCB to get it to work again? I want to say he had to drain a capacitor, but that doesn't sound totally correct.

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Yes
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Do you think you could do it or are you going for assistance?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I don't have the skills or equipment, so I'm going to send it to someone who can JTAG it for $40. Honestly, after I get jellybean to a stable state, I am going to sell my player anyways, as I never use it anymore.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Here's a new build: http://www.mediafire.com/?3h7s4esz73tkjli. You may still have to reflash the kernel from prealpha 2 in download mode, but I think I finally fixed all of the graphics library issues this time. :fingers-crossed: I'd still like a logcat and the output of 'adb shell mediaserver' if it doesn't boot, as that's the only way I can diagnose further issues.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Couldn't we just flash prealpha 2 and then flash this new build right after?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
No, because cm integrates a kernel, which overwrites the prealpha's. However, if you removed boot.img and the updater-script lines referencing it from the new zip, yes it would work.
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
I think after you sad that you brick player before you boot it first time now everybody is in fear to test :D
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
But, his device bricked due to a kernel error, not because of the ROM. Just be very careful when flashing kernels, and you should be fine.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
No, no, I will not post anything that could possibly brick your device. Mine bricked because I stupidly flashed bootloaders after messing up my PIT. Nothing to do with a kernel. The worst a bad kernel flash can do is leave you in download mode.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
My bad. All I remember is that something was done wrong in Heimdall/Odin. And, for one reason or another, "kernel" is what came to my mind first. Guess I should just go back and read next time. :silly:
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
I've got a stock Russian ROM with bootloaders.. should the resurrector detect the device, there's your way out. All I remember is that it took me three weeks getting the computer to recognize the device.
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
Mevordel, any hope on your Player?
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
If there isn't I have one that I would be willing to ship out to you of you want
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Thanks for the offer, but I think I need to focus on my studies, and not having a player is a great motivator. :D

No, other than sending it to someone for a JTAG, which will take about a week. (I think I'll go ahead and do it.)

I know what I did. Detecting it's not going to happen, but thanks anyways.
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
Has anyone try this rom is it booting?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
It bootloops because mediaserver fails to start due to a library issue. I need someone to install the latest zip, and then the kernel from prealpha 2, and then run

adb shell mediaserver

after it is bootlooping for a few seconds. A logcat would also be awesome. Then the next zip will probably be fully booting. Unless someone gets me this info, however, we're stuck for a week until I get my player fixed.
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
I would try it, except I hat having to re-install all my apps through Titanium Backup. It takes soooooo long. You know?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
To one of you that sent me the info: while it's bootlooping, could you please extract system/lib/libcameraservice.so from the prealpha 2 and then while it's bootlooping like before run

adb remount
adb push libcameraservice.so /system/lib/
adb shell pvrsrvinit

and tell me if the logcat changes or if it finishes booting?
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
I see no one try so i try and get error in CWM when i try flashing zip "assert failed getprop ro.product device ..and so on

I guess i need some newer cwm

Also i dont nou how to flash zimage(that from alpha 2) ..i now only in fastboot mode but mu pc dont recognize device in download mode "fastboot devices" gives me nothing, i try to create tar file and flash from odin but odin did not like my tar.
[Samsung Galaxy Player 4.0, 5.0] Higgs_Boson:
Have you gotten any results from anyone yet? If absolutely nobody is willing to do this for you, I'll try to do this in my spare time.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Yes, actually. Two people have been helping me, so no worries. We have made some progress, but it's not quite fixed yet.
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
The ROM is now booting

I got the ROM to boot. Just replace the following files to /system/vendor/lib/ from the pre alpha 2 ROM:

libpvrANDROID_WSEGL.so

libsrv_um.so

libIMGegl.so

and this file to /system/lib/ from pre alpha 2 ROM:

libcameraservice.so

Then in ADB type "adb shell pvrsrvinit" and it will start booting!

You can replace these files while it's bootlooping using the "adb push" command.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I will have a new zip by the end of the week with the fixed files (terribly busy right now). The next step after that is investigating why pvrsrvinit isn't being run on every boot. Also, I'd like some feedback to what is/isn't working in this current zip: sound, wifi, gps, etc. In fact, does the touchscreen even work?

EDIT: It's really great we can reproduce a full boot. No more fiddling in the dark :) (pun slightly intended). And, as a note, the 'adb remount' and 'adb push' will only need to be done once, but the 'adb shell pvrsrinit' may need to be done every boot. Can someone confirm that, please?
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Yes, "adb shell pvrsrvinit" needs to be run on every boot. Things that don't work: Sound, wifi, accelerometer (screen rotation), Bluetooth, capacitive button backlights (capacitive buttons work), says internal SD card is damaged, haven't tested external SD.

Things that are working: GPS (detected in location settings, I haven't really tested it), ADB, touchscreen, editing /system, capacitive buttons (lights not working).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hahmjt:
Many probably noticed that fido in canada has turned on its LTE. I jusy found out that they only have regular sized sim available at retail store. Has anyone tried putting this sim in galaxys3 rogers version? Would it work just like or sim if we cut it up to fit in the phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jimmyct:
Hey,

Just to clear things up, you'll first need to unlock the phone (obviously) .. Even if fido is a Rogers sub brand.

I contacted fido customer rep and they said it should work. And as you mentioned, they only have the regular sim size.

However, I went to the Montreal flagship fido store over the weekend, and the sales rep confirmed it will work and they are getting the LTE micro sim sometime this week.

I'll go buy it as soon as it's available, and I'll keep you guys posted.

Jimmyct
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hahmjt:
Thanks for reply,, as matter of fact, roger galaxy s3s works with fido sim.

Plus i just got the regular sized sim, and cut it with sim cutter. It works very well on my galaxy s3. It shows lte where 4g icon should be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Caz666:
I have also had good success cutting regular SIMs with a kitchen knife and scissor using online templates (just google Micro-SIM template).

Just print the template, put the regular SIM on the template and then cut where the lines are. I have done this 4-5 times with only 1 failure (my first...I think I used too much force).
[AT&T Samsung Galaxy Note I717] Joe_cool98:
I have just flashed over to Jellybean on my Note and now the Mic is not working on the Phone or Gtalk. I am ruining JB:CM10:HYBRD] PARANOIDANDROID [2.00] but now when i flash back to an ICS Rom the mic works, Just wanted to know if any one had this problem and also if there is a fix for it thanks.
[HTC EVO 3D] notsointeresting:
Team 420
​

Shades of by NotSoInteresting, on Flickr

Shades Of.. Series is a theme base of colours that is neither too flashy nor too minimal. It contains different shades of specific colours that will differentiate your device

.

Standard Disclaimer: Im not responsible for anything that happens to your phone, social life, marriage, etc.

Thanks to:

Bebida for his Skin to base off since it has no bad .9's

Team420 for the fun, and help with everything

Shades Of Red

Shades Of Orange

​

IF YOU DON'T KNOW HOW TO APPLY A SKIN:

Download APK file

Either click on the file from status bar, or naviagte using a File manage (eg.ES File Explorer)

Click on the file and install

Now exit to the home screen

Press Menu

Press Personalize

Press the Display tab at the bottom and Press Skin

Find "SOR"

[/URL]

Press Apply

Screenshots:

View attachment 1300195

View attachment 1300196

View attachment 1300197

View attachment 1300198

View attachment 1348799
[HTC EVO 3D] notsointeresting:
Changelog:

V1.0 : First release. Still a bit rough around some edges.
[HTC EVO 3D] notsointeresting:
Taking one more
[HTC EVO 3D] nuvens:
Very nice. _(\
[HTC EVO 3D] Bebida:
Mine. Good job.
[HTC EVO 3D] dased14:
Looks good :highfive:

(lol only a few, lol :rolleyes:)
[HTC EVO 3D] notsointeresting:
Added title image to OP to make it look a little better :good:
[HTC EVO 3D] mob68:
Downloading....

"SeXxy Virus"
[HTC EVO 3D] mob68:
::::Got it...Beautiful skin....ThnXx nonsoin... to give us a one more art of your work:thumbup:

"SeXxy Virus"
[HTC EVO 3D] mob68:
Looks Beautiful:::::::

View attachment 1302637

View attachment 1302640

View attachment 1302641

View attachment 1302642

"SeXxy Virus"
[HTC EVO 3D] notsointeresting:
So why is their a folder titled "Mob68" in my theme folders? And better yet how is it possible for someone to have made a folder in there o.O
[HTC EVO 3D] ssojyeti2:
Hmm that one confused me:confused:

:p
[HTC EVO 3D] mob68:
I've reg yestrdy to downld this skin...there was option to create folder there,so i just create one of my usr name....Now what to do bro,tell me...it can be edit...first i've created on other name...then i've changed on "Mob68"....can i change on your name..???

"SeXxy Virus"
[HTC EVO 3D] mob68:
::::.DELETED::::

I've Pressed "New Subfolder" button & folder created on that name,then i've changed on "Mob68", I thought its my folder to upload files in ma acc....Sorry for Getting Dstrbd....

"SeXxy Virus";)