Related
WARNING: DO NOT TRY THIS! IT'S A WORK IN PROGRESS AND WON'T WORK AT THIS STAGE!
A lot of people in this forum would like to try flashing custom ROMs or just de-branding their phone to an unbranded stock ROM but are concerned about voiding their warranty. I'm one of those.
Information on how to backup and restore back to original condition seems difficult to find so I thought I'd create a post that could be updated to form an easy-to-follow guide. There's a lot of gaps to fill in so please contribute if you can. Progress so far...
1. Backing up your original hboot, boot and recovery. I think this script should do it (modified from sfjuocekr's post /showthread.php?t=835746). Run from ConnectBot or similar terminal emulator on your phone (or ADB - just drop 'busybox' from the md5sum command):
Code:
#!/system/bin/sh
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_orig0.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_orig1.img
dd if=/dev/block/mmcblk0p21 of=/sdcard/DHD/recovery_orig0.img
dd if=/dev/block/mmcblk0p21 of=/sdcard/DHD/recovery_orig1.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/DHD/boot_orig0.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/DHD/boot_orig1.img
busybox md5sum /sdcard/DHD/*.img
echo ""
echo "IF THE ABOVE MD5 SUMS DO NOT MATCH"
echo "SOMETHING IS WRONG WITH YOUR BACKUP"
2. Permroot with VISIONary r12.
3. Load Clockwork MOD Recovery and make Nandroid backup. I need help with this section.
[Questions: Does it require S-OFF? Can you load the current test Clockwork recovery using 'fastboot boot' and run Nandroid from that?]
4. To restore, use the normal Nandroid restore procedure and then dd your backup files back to their original locations.
[Questions: Is it better to use 'fastboot flash boot boot.img'? I'm assuming I'll still have to use dd for the hboot and the phone will have to be in bootloader mode?]
Finally, will this work? Is this more complicated than it needs to be? Can you simply use dd to backup/restore the system and userdata partitions too?
Sorry if this is out of place. I thought I'd put in the initial effort and people who actually know what they are talking about might be so kind as to fill in the blanks.
I'm sorry to post this in the Fascinate forum, but as you all know Cellular South's version the "Showcase" is identical in hardware as is the Mesmerize, but there isn't a forum for either of them..
I see there's plenty of kernels and etc.. But is there just a simple lag fix that I can do to my Showcase that will make every day use better and less laggy?
A simple yes or no is fine with me.
if there is a way a link post or explanation would be VERY appreciated.
Thanks,
Elijahblake
(PS)Sort of on the same subject, but I read that gingerbread is going to support ext4 file system. I know the Galaxy S uses the RFS file system which I believe is where we get the lag in the first place.. Will it be possible to switch file system formats?
I'm not real familiar with all these Linux formats. Would it be similar to reformatting like from FAT32 to NTFS?
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app
elijahblake said:
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app
Click to expand...
Click to collapse
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum
jt1134 said:
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum
Click to expand...
Click to collapse
will do.. May take me some while to get all this info gathered..
quick question? I've read of some people not being able to see certain apps in the market after rooting.. Is this still the case?
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?
elijahblake said:
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?
Click to expand...
Click to collapse
To get the upgrade, you shouldn't have to un-root, but you should probably disable voodoo first as the update will almost certainly have a new kernel, and applying the update without disabling voodoo could cause quite a headache.
If you do apply the update right away, you could quite possibly loose root, so you may want to wait until the devs re-root the update. This could make things easier for you as the rooted update will also likely be cleaned up some.
To disable voodoo, you'd just need to create a file called "disable_lagfix" in /sdcard/voodoo and then reboot your phone. See the thread in the dev forum about removing voodoo for more details if you want.
ok well it looks like I'm rooted.. Now I tried to open the ADB that came in the fascinate root zip but it's not opening for more than a split second... you have a download link?
Also can uninstall all this bloatware now??
edit.. thought I had Android SDK on this laptop.. Downloading it now
jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake
elijahblake said:
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake
Click to expand...
Click to collapse
I have c:\androidsdk
I put ADB inside tools and it sees my device when I run ADB devices
But on the commands you listed nothing happens, I'm not sure if that's the entire commands or if I'm supposed to add something to them..
Try to run the following
Code:
adb shell cat /dev/block/bml7 > /sdcard/zImage
adb shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
adb shell mount
or just typing "adb shell" and entering the commands at the new prompt, and typing "exit" to get back to the normal command prompt.
here's what happened..
the first two commands didn't work. DO i need to create a folder name zImages?
The second command said access denied..
You tell me if the mount worked haha..
jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
well, it granted me SU rights.. but still a no go...
i figured since i was in shell i shouldn't type that.. still got no directory found...
imnuts said:
jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
Click to expand...
Click to collapse
would root explorer make this any easier?
I just tested out all of the commands on my Fascinate and they all worked, so I'm guessing that the Showcase is putting stuff in a different place. jt will have to help you out further as I'm not sure of where else to look for the info he needs.
elijahblake said:
i figured since i was in shell i shouldn't type that.. still got no directory found...
Click to expand...
Click to collapse
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.
GeekMouse said:
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.
Click to expand...
Click to collapse
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
It doesn't need shell at the beginning.
elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
This is how it should be typed
Code:
adb shell
su
cat /dev/block/bml7 > /sdcard/zImage
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
Hi!
The GPS - issue (GPS searching forever, no fix, status bar does not even show the gps-icon) can be fixed by wiping the efs data.
This data is stored in partition 13 and partition 14 on the G2/DZ/DHD/MT4G.
Update 18.04.2011:
Given the tragic end of a phone because of a mistyped dd-command (see this post) i decided to create a tool to replace the original instructions. I leave the original instructions for people who are confident with dd and don't want do download something to get the job done.
So just to make this clear: Method 1 and Method 2 are alternative ways to do the same thing. I would recommend that you do it using Method 1 but anyways, don't do Method 1 and 2.
Method 1: Removing the efs-data using vision_wipe_efs:
Download vision_wipe_efs from vision_wipe_efs_01.zip (md5sum 7bced5385509a58a7c8b0a54d38a6897)
Remark: The program vision_wipe_efs will create backups of the partition 13 and 14 on the sdcard using the name "/sdcard/part13backup-<time>.bin" and "/sdcard/part14backup-<time>.bin" so make sure that the sdcard is mounted to the phone.
Unpack the zip file to a directory on your PC. Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute this command (as always: do not type the # it only indicates the root prompt in the shell or the $ as the prompt in a non-root shell):
Code:
# adb push vision_wipe_efs /data/local/tmp/
You can also use other ways to copy the file to this directory but the following instructions assume that it is there.
Get a root shell on your phone (either using adb shell or a terminal app) and then use the following command:
If your prompt is not # but $ then first do:
Code:
$ su
and answer the question of Superuser. (Well you should all know this by now )
Code:
# stop rmt_storage
# chmod 777 /data/local/tmp/vision_wipe_efs
# /data/local/tmp/vision_wipe_efs
# reboot
Method 2: Removing the efs-data using dd (BRICK RISK):
To do this you have to get a root shell on your phone (either using adb shell or a terminal app) and then use the following command (as always: do not type the # it only indicates the root prompt in the shell or the $ as the prompt in a non-root shell)
If your prompt is not # but $ then first do:
Code:
$ su
and answer the question of Superuser. (Well you should all know this by now )
Code:
# stop rmt_storage
# dd if=/dev/zero of=/dev/block/mmcblk0p13
# dd if=/dev/zero of=/dev/block/mmcblk0p14
# reboot
After you followed Method 1 or 2 should have your GPS back working.
To wipe the efs is general a good idea if you switched radio-firmware or the ril-libs (which might happen when you switch from one rom to another)
have fun - Guhl
guhl99 said:
Hi!
The GPS - issue (GPS searching forever, no fix, status bar does not even show the gps-icon) can be fixed by wiping the efs data.
This data is stored in partition 13 and partition 14 on the G2/DZ/DHD/MT4G.
To do this you have to get a root shell on your phone (either using adb shell or a terminal app) and then use the following command (as always: do not type the # it only indicates the root prompt in the shell or the $ as the prompt in a non-root shell)
If your prompt is not # but $ then first do:
HTML:
$ su
and answer the question of Superuser. (Well you should all know this by now )
HTML:
# stop rmt_storage
# dd if=/dev/zero of=/dev/block/mmcblk0p13
# dd if=/dev/zero of=/dev/block/mmcblk0p14
# reboot
After this you should have your gps back working.
To wipe the efs is general a good idea if you switched radio-firmware or the ril-libs (which might happen when you switch from one rom to another)
have fun - Guhl
Click to expand...
Click to collapse
please be careful with dd. (this isn't for you, op, but for the other hamfisted folks that try to fix things)
why are there HTML backets in your post ?
Perhaps it should be mentioned to do the inverse beforehand.. just to play it safe.
dd if=/dev/block/mmcblk13 of=/mnt/sdcard/p13backup
dd if=/dev/block/mmcblk14 of=/mnt/sdcard/p14backup
I'd still stop that service beforehand..
although I must say.. my gps is ****ing awful after this.. but meh.. it could just be the time/place/conditions.. and by awful.. I mean.. it locks on.. with an error of 305 ft.. sorta screwy.. nothing is as bad as when I tried to modify the gps.conf to use other servers (like my hd2).. i got a 2-3 mile error with 10 sat locks..
oh.. but this DID fix erratic gps behavior. and I'm betting that the accuracy will even out after a couple reboots/gpslocks.
ohgood said:
please be careful with dd. (this isn't for you, op, but for the other hamfisted folks that try to fix things)
why are there HTML backets in your post ?
Click to expand...
Click to collapse
Of course you are right. Be carefull to write the dd commands correctly. Later i will put a tool on my wiki that wipes the partitions without the use of dd.
Sent from my HTC Vision using XDA App
Did anybody use gps status app to download new gps data after trying this?
Sent from my HTC Vision using XDA Premium App
Alright, it worked, thanks. The notification even shows up in the notification bar now!
Sent from my SilverBullet "HTCDesireZ running CM7"
Just out of curiosity, what is the EFS data?
All I did to fix mine was update the kernal.
theSpam said:
Just out of curiosity, what is the EFS data?
Click to expand...
Click to collapse
Temporary (in our case) radio configuration data.
Nonentity018 said:
All I did to fix mine was update the kernal.
Click to expand...
Click to collapse
Lucky you. Sometimes updating, downgrading radio or kernel can lead to the effect that the systems re-initializes the temporary radio data.
Thanks for the tip but I am still unable to have my GPS work in CM after using this. I had no GPS problems with sense roms but have yet to get GPS working on any of the CM ones. I have tried reflashing numerous times with complete data, cache and system wipes alongside multiple radio/kernel reflashes but this just never works for me . Hopefully future releases of CM somehow get it working otherwise I will have to get back to sense
EDIT: Wow, as soon as I post this I decide to try reflashing my kernel one more time and lo and behold the GPS starts magically working! I did nothing different than what I hadn't already been doing but whatever I'm not complaining
What should be the output of the dd commands?
I got something about not enough space on the device error. I still continued with inputting the codes mentioned in the first post. Upon reboot GPS stopped working on me, it was working previously but really spotty. Ill give it some time until I flash CM7 final.
boost3d23 said:
What should be the output of the dd commands?
I got something about not enough space on the device error. I still continued with inputting the codes mentioned in the first post. Upon reboot GPS stopped working on me, it was working previously but really spotty. Ill give it some time until I flash CM7 final.
Click to expand...
Click to collapse
The errors messages that there is no space left on the device are OK.
The dd commands just writes 0's into the output partition until it is full.
Hello to all,
I've read several posts and tried several things now with no success.
I'm currently on CM7 Stable
Radio 12.28h.60.140fU_26.06.02.27_M
Kernel 2.6.32.28-cyanogenmod_g4f4ee2e [email protected]#1.
GPS symbol shows when launching navigation, but no result. It keeps looking for the location. I wiped the Radio data several times as suggested.
Last thing on my list would be flashing a new radio. Since I've read that it can brick the phone I'm quite cautious.
Any other suggestions?
This is how you tell if your GPS is gonna work or not even before booting the os. If you get that small vibration after the normal bootup vibration, your GPS will not work. Been doing research on this.
Staudamm said:
Hello to all,
I've read several posts and tried several things now with no success.
I'm currently on CM7 Stable
Radio 12.28h.60.140fU_26.06.02.27_M
Kernel 2.6.32.28-cyanogenmod_g4f4ee2e [email protected]#1.
GPS symbol shows when launching navigation, but no result. It keeps looking for the location. I wiped the Radio data several times as suggested.
Last thing on my list would be flashing a new radio. Since I've read that it can brick the phone I'm quite cautious.
Any other suggestions?
Click to expand...
Click to collapse
Changing radio solved my GPS issues, check my sig for the one I'm using.
I have changed my radio a few times since getting my DZ and have never had any problems. Just make sure you read the instructions a couple of times and check the md5 sum of the download and you will be fine.
I fixed it by uploading the gps.vision.so to /system/lib/hw/
But I used ADB instead of root explorer by using the following commands:
adb remount
adb push gps.vision.so /system/lib/hw
adb reboot
Originally Posted by slashjiang View Post
I tried to solve this issue by myself.
I extract the nightly build #34 (which GPS works in my G2), and compare it with #38 (GPS doesn't work), I found the file /system/lib/hw/gps.vision.so is different in both ROM. so, I tried to replace this file in my G2 with the same file which is from #34 by using Root Explorer, after reboot, GPS works. The icon in the notification bar appears.
Run GPS status, satellite signal found.
Run Google Maps, working too.
The gps.vision.so file from #34 is attached in ZIP format. Just download it, extract, and copy it to /system/lib/hw/ and replace original one. Have fun.
Hopes Cyanogen Team solve this issue. Thanks.
Click to expand...
Click to collapse
Just wanted to add that these commands didn't work for me. I replaced the kernal with pershoots and it fixed the problem.
Thank you. This worked for me after replacing gps.vision.so and I'm a total n00b. Much appreciated!
Thanks this worked for me.
Sent from my HTC Vision using XDA App
Hello there guys, i have owned three different galaxy variants namely : m110s,m130k and gt-I9000. So far, its been a wonderful experience flashing and modifying except for the korean variants. ever since i softbricked my m130k, finding resources for it has been a headache, and all the people, including some guys here in xda are not that interested in the other lowly variants of galaxy s, even if they're also using korean variant like m110s. i have compiled some resources and links and i will post them one by one as i have the time. for now, im just asking all of you guys out their to help in making posting and helping out people using the said korean phones.
up until now, i haven't fixed my phone yet, i badly need the other files missing in the roms available in the internet, like dbdata.rfs and the likes.i know many guys using the same phones have also encountered such problem. anyway i would like to post this link, for those guys willing to use ADB or Heimdall and post some of their own phone files. thank you
>>>>>link for instructions in extracting phone files<<<<<<<<<<<<<<
http://www.freeyourandroid.com/guide/building_roms_for_odin
ill also upload my own collected files as we go along.Thank you all. Attached here is a pit for m130k extracted using Heimdall.i have already used it and it can successfully repartition your device, note however that we cannot use the roms found in the internet because they only contain factory,zimage and modem file, so repartitioning will indeed BRICK your unit unless you use a complete rom fil for m130k.
e:/ cant mount /efs (shw-m130k)
hello guys. just giving an update on those persons having problems with their m130k. specifically the e:/cant mount issue. so far ive always been in the wrong direction. my phone was already working but it just keeps on resetting the settings on power up, as well as i cannot save anything on internal sd (it was detected as 0 bytes). so i searched and found possible solutions in pit. so i downloaded pit using heimdall, and used it to repartition my system. however, as worse comes to worse. this caused my phone to not go past the recovery screen, not being able to use my phone again and the cant mount error still occurred. in short, it made my problems worse. so i did some research and out of frustration, i tried using the EA20 revision for m130k. after flashing, all the cant mount error vanished. however, because i used repartition earlier, i still cannot go past the recovery console and the galaxy k logo is gone, replaced by anycall talk-love logo.
so for those who are in the same position as me and haviong cant mount problems,
i suggest using EA20 first to fix your phone and PLEASE do not REPARTITION. and for those who can give me a hand, ill appreciate that. thank you
pulling data from ADB for possible recovery
dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096
dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096
dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
adb pull /sdcard/boot.bin
adb pull /sdcard/pit.pit
adb pull /sdcard/efs.rfs
adb pull /sdcard/Sbl.bin
adb pull /sdcard/param.lfs
adb pull /sdcard/zImage
adb pull /sdcard/factoryfs.rfs
adb pull /sdcard/dbdata.rfs
adb pull /sdcard/cache.rfs
adb pull /sdcard/modem.bin
some ADB commands i saw for pulling files and possible creation of recovery rom
mms.apk
can you sirs provide me a stock mms.apk and tw.launcher for the m130k plsssss
i accidentally uninstalled it and have no backups for it
check this out guys... m130k.blogspot.com
shwm 130
hello guys. im using a LG shwm130L anycall. it was factory reset by accident now its in korean languages. Im really really badly needed your help. My sis gave this to me and its very valuable.
ryenneinaho said:
hello guys. im using a LG shwm130L anycall. it was factory reset by accident now its in korean languages. Im really really badly needed your help. My sis gave this to me and its very valuable.
Click to expand...
Click to collapse
just press menu button, press settings and scroll down to keyboard letter "A" icon press it and press the top most menu to switch to English.
Check this out! Links to useful Guides and " Banned " Documentaries
I initially took the OTA to ZVC download thinking that I could just boot into recovery and cancel the download before it started so that the message to update wouldn't appear anymore in my notification bar. I took the download then when the phone booted into recovery I cancelled the download, but now my phone is stuck in bootloop. I am trying to restore using the LG software updater tool found in this thread (http://forum.xda-developers.com/showthread.php?t=2471370&highlight=upgrade) but it keeps giving me an error that there are "No upgrade items to fix" and it won't proceed with the update. Are there any other ways I could try that will work for me?
Can someone please help? I need my device back in working order for work.....
haoleflip said:
Can someone please help? I need my device back in working order for work.....
Click to expand...
Click to collapse
I will pay someone to help me out pleeeeaaaaasssseeeeeeeee
haoleflip said:
I initially took the OTA to ZVC download thinking that I could just boot into recovery and cancel the download before it started so that the message to update wouldn't appear anymore in my notification bar. I took the download then when the phone booted into recovery I cancelled the download, but now my phone is stuck in bootloop. I am trying to restore using the LG software updater tool found in this thread (http://forum.xda-developers.com/showthread.php?t=2471370&highlight=upgrade) but it keeps giving me an error that there are "No upgrade items to fix" and it won't proceed with the update. Are there any other ways I could try that will work for me?
Click to expand...
Click to collapse
Is it booting you back into Recovery each time? Do you have root (#) when you adb shell? If so, maybe you can clear the OTA by doing the following dd command...
[email protected] ~/adb $ adb shell
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/fota': No space left on device
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 2.656541 seconds, 12.0MB/s
~ # [email protected] ~/adb $
daryelv said:
Is it booting you back into Recovery each time? Do you have root (#) when you adb shell? If so, maybe you can clear the OTA by doing the following dd command...
[email protected] ~/adb $ adb shell
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/fota': No space left on device
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 2.656541 seconds, 12.0MB/s
~ # [email protected] ~/adb $
Click to expand...
Click to collapse
Sorry, but what is adb shell? and how do I run that command?
I just want simple step by step instructions on how to get my phone restored. I have tried countless threads and none of it is working for me. I am running into issues like no other. Please, I will be more than happy to pay someone to help me out here. I have paypal....