After updating to the newest leak that came out on 08-01-10.. I am not able to adb to my phone anymore since apparently it is not recognizing my device. I am trying to copy the ringtones and notifications sound directory from my sd card to the system/media/audio directory.
I am using Terminal Emulator on the phone.
I am able to get rw access to the ROM by typing in..
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
then I am trying to copy the file by typing..
cp -r /sdcard/download/ringtones /system/media/audio
It gives me an error saying "Cannot allocate system memory"
does anybody know what that means? How can do this?
Can't write to the system folder when the OS is booted. Just adb shell into the phone and make sure system is mounted in CWM, and you can run that same cp line and do what you want.
partizan81 said:
Can't write to the system folder when the OS is booted. Just adb shell into the phone and make sure system is mounted in CWM, and you can run that same cp line and do what you want.
Click to expand...
Click to collapse
yea, thats what I wanted to do first.. but my computer no longer recognizes the phone in adb mode (even though I am able to get access to the internal drive and sd card under My Computer).
don't know what to do right now.
is there a way to adb shell from the phone without using a PC, say in recovery mode or something? Any terminal app available to use in recovery mode?
As far as accessing while the phone is booted: Pull down your notification bar, click on where it says "Disk Drive." Change to "Charge only."
If your phone has your drives mounted for the computer, as a drive, they're not mounted for the phone, and therefore, adb.
As far as the rest, we currently have no access to /system while the phone is booted. You'll be able to mount the partitions in RECOVERY and interact with them.
Anybody with a clearer answer, feel free to correct me.
morbos said:
As far as accessing while the phone is booted: Pull down your notification bar, click on where it says "Disk Drive." Change to "Charge only."
If your phone has your drives mounted for the computer, as a drive, they're not mounted for the phone, and therefore, adb.
As far as the rest, we currently have no access to /system while the phone is booted. You'll be able to mount the partitions in RECOVERY and interact with them.
Anybody with a clearer answer, feel free to correct me.
Click to expand...
Click to collapse
whether your disks (internal and sdcard) are mounted or not.. adb should still be able to recognize a connected device.. which is where my PC all of a sudden has stopped doing after I installed the 8/1 leak.
adb shell with write access on the other hand is only possible in clockwork recovery and that too only after mounting the system.
We are still pushing to soon release soff safely for everyone. That is, permanent nand unlock which will give you the ability to do what you are asking. It's coming, we are getting close.
Shadowmite said:
We are still pushing to soon release soff safely for everyone. That is, permanent nand unlock which will give you the ability to do what you are asking. It's coming, we are getting close.
Click to expand...
Click to collapse
I'd do a happy dance, but I got a pair of unrEVOked blue balls that could double as curling stones. If soff ain't here soon, I'll be risking road rash just walking around...
Sorry... tmi, rite?
cantare said:
I'd do a happy dance, but I got a pair of unrEVOked blue balls that could double as curling stones. If soff ain't here soon, I'll be risking road rash just walking around...
Sorry... tmi, rite?
Click to expand...
Click to collapse
Ummmm. I am pretty sure unrEVOked has delivered the goods consistently. If they say its coming, i believe them. At least they aren't using Valve Time.
Fretless said:
Ummmm. I am pretty sure unrEVOked has delivered the goods consistently. If they say its coming, i believe them. At least they aren't using Valve Time.
Click to expand...
Click to collapse
Oh, agreed...I'm talking about anticipation here, not reliability
ETA Valve Time...lol
i've recently found a program that actually simplifies the entire adb process since most people in this forum shouldn't even have a rooted phone
http://forum.xda-developers.com/showthread.php?t=597098
Shadowmite said:
We are still pushing to soon release soff safely for everyone. That is, permanent nand unlock which will give you the ability to do what you are asking. It's coming, we are getting close.
Click to expand...
Click to collapse
ooohh.. can't hardly wait!
Related
Here's one for the genius'
1. I rooted my phone successfully
2. I edited the settings.db file to allow side apps
3. I copied to copy the original settings.db file (that I think I may have corrupted) back and when I restarted my phone, I get a blank screen.... it will not boot into android.
I have a backup of the original settings.db file, but I need to know if there is there a way that I can copy this file back from recovery mode so that I can boot. I do get command line access in through adb, but it will not let me gain su access. Any help would be great.
I would say just hard reset the phone. It'll restore the settings.db back to the factory one.
masterofthebass said:
I would say just hard reset the phone. It'll restore the settings.db back to the factory one.
Click to expand...
Click to collapse
is it possible to do a hard reset without booting into android? I didn't know about that drats!
systoxity said:
is it possible to do a hard reset without booting into android? I didn't know about that drats!
Click to expand...
Click to collapse
I'm fairly sure there's a way to completely reset the phone while in recovery mode. Haven't done it, but I read about it somewhere.
I did a reset, but the phone still goes blank after the Galaxy logo. If I can mount the sdcard in recovery I think I can fix it. But I can't get it mounted.
take it back and ask for a replacement. Use your imagination.
If this fails and you have a brick phone that you cant do anything with, then i personally would try to open it up and see if that internal microsd card can be removed and hooked up to a card reader. Ofc this is very risky, and i am in no way telling you that you should follow in my theoretical footsteps. Be careful and good luck.
Is there a way to mount the internal sdcard. I have adb access in recovery mode, but not root. I have removable sdcard, but it does not seem to access that one from the recovery mode.
Also, I see the drives in "My Computer", but when I click them they ask me to insert a card. Is there a way to manually mount it from the ADB shell?
you have adb access? So when you have it plugged in and you go to cmd and type adb devices, the phone pops up as connected?
Yes... I have shell access, just can't get root or mount anything. I had already rooted the phone before all this began.
Try this.
Boot into recovery and type this into your computer
"adb shell"
"mount /sdcard"
"exit"
"adb push <whateverfile> /<path>/<whateverfile>"
"adb shell"
"umount /sdcard"
"exit"
I haven't tried this on my phone, but it should work. Please post back if you have any problems.
That will fail because /<path>/<whateverfile> isn't readable/writeable by non-root users (aka adbd). It's /dbdata or something like that, if memory serves.
For the record, booting into recovery mode and clearing all user data will NOT restore a working settings.db. I think the OP is SOL, although I'd love to learn that I'm wrong! :-(
Yeah I tried "mount /sdcard" already.... No luck, it just tells me "usage: mount [-r] [-w] [-o options] [-t type] device directory"
I forgot that you can't get root. The only thing i can tell you is to wait for the dump of the original rom whenever that comes out or take it to your ATT store and tell them it broke.
Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?
If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.
centex99 said:
Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?
Click to expand...
Click to collapse
tbae2 said:
If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.
Click to expand...
Click to collapse
both posts +1
If you can access the phone in adb shell, then you might be able to access the recovery console by going to your computer's command line, getting into the SDK tools folder, and typing "adb shell reboot recovery"
Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.
just tried mine and it worked fine. I first tried it with pushing a file from my sdk dir, and tried it with pushing a file from another directory on the drive. worked both times, not sure what to tell you.
p.s. I'm running the desire z rom
Yeah for some reason its only on the sdcard I cant write to.. USB Debugging is checked. Anyone have the slightest idea as to why I'm unable to write to my sdcard with this Read-only File system error?
Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]
luis86dr said:
Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]
Click to expand...
Click to collapse
Are you making sure that you don't have media mounted? That would screw up /sdcard. For me, it's "umount /media/*; eject /dev/sde" then on the G2 disable USB storage, wait for it to remount the SD card.
If that still doesn't work, what does "adb shell mount" tell you?
Normally, like with /system, it's "busybox mount -o remount,rw /system", but I've never seen /sdcard mounted readonly, unless there are I/O errors (it's mounted to remount ro on failure). Have you tried rebooting your phone?
luis86dr said:
Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.
Click to expand...
Click to collapse
Is it possible that you are writing the command wrong? I noticed the slash is opposite on the second half of your command code.
C:\Android\android.jpg /sdcard/android.jpg
Click to expand...
Click to collapse
Figured it out. Had usb storage on. So it wouldn't push turned it off and I was able to push. Thx foe the info
[G2/HTC Vision]
Okay, it will be kinda noob-ish but I searched but couldn't find anything. I have latest liberated rom rooted with unrevoked and I cant push anything to /system/customize or wherever on the phone storage. Cant adb push, when I try to remount with write access phone restarts. Any suggestions?
Code:
C:\Users\Evan\Desktop\New folder\sdk\tools>adb remount
remount succeeded
C:\Users\Evan\Desktop\New folder\sdk\tools>adb push widget.txt /system/customize
failed to copy 'widget.txt' to '/system/customize/widget.txt': Out of memory
There is memory!
all i can say is try booting into clockworkmod and mount system there.
joachim123 said:
all i can say is try booting into clockworkmod and mount system there.
Click to expand...
Click to collapse
Correct. Since our phone is nand locked, to edit/push/etc the phone would have to be booted into clockwork (without usb cable attached) - mount /system partition - and then attach cable. From there, remount in adb and push / pull / explode (explode isn't really a command... lol)
Oh yeah. Thanks for the answers, clockwork worked lol. Stupid me
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.
you know, I've had the same problem lately. --curious to know what's causing it.
decalex said:
you know, I've had the same problem lately. --curious to know what's causing it.
Click to expand...
Click to collapse
Its good to know I am not the only one out there with this issue maybe someone can chime in with a fix. or some insight at least to what the problem may be.
Still no response.... Bump?
watermoore said:
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.
Click to expand...
Click to collapse
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
DevinXtreme said:
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
Click to expand...
Click to collapse
Hey man thanks for your input, I really appreciate it. That didnt work either, on ADB or on Terminal Emulator. It responds correctly from both sources with:
Code:
remount rw
Remounting /system </dev/st19> in read/write mode
I am wondering if it has anything to do with the fact that the 64bit drivers dont install totally. this module called the "Abstract Control Module" hangs forever and doesn't install. However I ran over to my wifes 32 bit vista laptop where the drivers will install totally with no success either.
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.
DevinXtreme said:
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.
Click to expand...
Click to collapse
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
Bump again
Sent from my Epic
Okay since I'm not getting much love from the forum I'm guessing this is an uncommon occurance, in which case I am going to try one more thing before I send it back for a replacement. I am planning on going back to DI18 via odin then one click rooting. Then flashing the modem and other nessecary files to run 2.2 epic experience. Its the only possible thing I can think of that I haven't tried to address my problem. Thanks for the feedback I have gotten thus far.
Sent from my Epic
This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2
The e0pic and hero are way differentwhen it comes to adb
I was the same way lol I don't think adb works
Like I think the only way is to cp things
Sent from my SPH-D700 using XDA App
watermoore said:
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
Click to expand...
Click to collapse
That last one appears to have worked. Check and see if movetest.txt is in /system/fonts. If so, then you're in business. Just copy stuff across as root instead of pushing.
Well now I can use ADB fully. I odined back to stock then used the one click clockwork 3.0.0.05 ext4 batch then flashed Truley Epic Rebirth 1.2 and was able to remount correctly, push and pull all the way down to the root dir. I am not sure what changed but it just all of the sudden started working.... I'll take that lol
mirth18 said:
This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2
Click to expand...
Click to collapse
Well my issue was a bit different. I could get it show up with the "devices" command. When I tried to "adb remount" it would deny me. It would reply with "device not found". Which is really wierd because I could ADB shell with root access any day of the week. I just had to change my process to accommodate the limitation.
I would just ADB push files to the sdcard, mount into shell to gain full root permissions then finish my work.
Kind of a strange round about way of going about it but I learned quite a bit more linux commands that way lol
Fyi.. I am using ubuntu 11.04
Sent from my SPH-D700 using XDA App
Hi expert,
Has anyone successfully JB PS3 using the following link?
http://psfreedom.com/wiki/HTC_Droid_Eris
I cannot get it to work, just curious if anyone successfully done it would like to share how you accomplish this. There are 2 steps that I have question on, they are:
Fastboot should say < waiting for device >, I don't get this message, I only received boot image loaded OK
insmod /sdcard/psfreedom.ko returns error message "cannot insert psfreedom.ko file exists"
I've been reading the last 3 days and still unable to get this loaded, is there a more up to date instruction for eris? TIA.
psfreedom.ko
Did you copy psfreedom.ko file to your sdcard
sangweb said:
Hi expert,
Has anyone successfully JB PS3 using the following link?
http://psfreedom.com/wiki/HTC_Droid_Eris
I cannot get it to work, just curious if anyone successfully done it would like to share how you accomplish this. There are 2 steps that I have question on, they are:
Fastboot should say < waiting for device >, I don't get this message, I only received boot image loaded OK
insmod /sdcard/psfreedom.ko returns error message "cannot insert psfreedom.ko file exists"
I've been reading the last 3 days and still unable to get this loaded, is there a more up to date instruction for eris? TIA.
Click to expand...
Click to collapse
do you have fastboot on? make sure you have the right root
wonder if having clockwork or RA recovery makes a difference...
Why not just use psfSM from www.klutsh.com
Works on my Eris.
Sent from my Droid Eris using XDA App
Retrogress said:
do you have fastboot on? make sure you have the right root
wonder if having clockwork or RA recovery makes a difference...
Click to expand...
Click to collapse
Yes, I have the psfreedom.ko on my root of sd card and I think I do have fastboot on because the command fastboot devices return my phone id.
Chevelle1768 said:
Why not just use psfSM from www.klutsh.com
Works on my Eris.
Sent from my Droid Eris using XDA App
Click to expand...
Click to collapse
I went to the site but not sure what am I suppose to look for, I've downloaded the img file for eris, what am I suppose to do with it? TIA.
For what it's worth, very soon you won't be needing any device to jailbreak the PS3, the master key was discovered and most if not all future developments will be signed code making the jailbreak method obsolete.
There's already a working 3.55 custom firmware, though many homebrews still need to update to use it.
Its a recovery img just like Clockwork and Amon_Ra's. Its actually based off of Clockwork. So just flash it to your recovery.
Chevelle1768 said:
Its a recovery img just like Clockwork and Amon_Ra's. Its actually based off of Clockwork. So just flash it to your recovery.
Click to expand...
Click to collapse
To verify, I have to run the following commands except replace the recover-ra with the image I've just downloaded:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
Am I right? Thx.
sangweb said:
To verify, I have to run the following commands except replace the recover-ra with the image I've just downloaded:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
Am I right? Thx.
Click to expand...
Click to collapse
Just these
adb push recovery-ra-eris.img /sdcard
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
Click to expand...
Click to collapse
Thanks Chev, looks like I can see it on the recovery menu. I'll test it out once I get home. The only thing I see is I get the following error when I flash the image:
mtd: read error at 0x00000000 (Out of memory)
Are you running Vista or Windows7? If so, run the command prompt with Admin rights.
Otherwise do this:
adb push recovery-ra-eris.img /sdcard
adb shell
cd sdcard
flash_image recovery /sdcard/recovery-ra-eris.img
Click to expand...
Click to collapse
Chevelle1768 said:
Are you running Vista or Windows7? If so, run the command prompt with Admin rights.
Otherwise do this:
Click to expand...
Click to collapse
No, I ran it on XP but I can see the PS3 jailbreak option now, there are 3 JB option right? PL3, PSFreedom, or Hermes, so I can just select any to boot my ps3 in JB mode, do you know if these payloads has spoof on them?
sangweb said:
No, I ran it on XP but I can see the PS3 jailbreak option now, there are 3 JB option right? PL3, PSFreedom, or Hermes, so I can just select any to boot my ps3 in JB mode, do you know if these payloads has spoof on them?
Click to expand...
Click to collapse
I don't believe any of them do. But you can download the other PL3 payloads from the same site also. Then just extract them to you sdcard.
Hi Chev, thanks for all your help, I think I got enough information to go home and mess around with my ps3, I hope it'll work.
Marisa said:
For what it's worth, very soon you won't be needing any device to jailbreak the PS3, the master key was discovered and most if not all future developments will be signed code making the jailbreak method obsolete.
There's already a working 3.55 custom firmware, though many homebrews still need to update to use it.
Click to expand...
Click to collapse
anywhere we can read up on this?
FYI, I was able to run the JB last night and it works great, test out some games and got GT5 working so far but it does take a long time to load my GT5 to the HD. I am happy now that I don't have to switch games out for my kids any more .
Retrogress said:
anywhere we can read up on this?
Click to expand...
Click to collapse
The place is psx-scene, psxnews, psgroove, or best is google it, many useful sites out there. Good Luck.