Database Users

Lag Fix for Galaxy S "Showcase"

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

[GUIDE] How to do a full backup to /sdcard-ext

[GUIDE] How to do a full backup to /sdcard-ext
How to backup your atrix with adb
Prerequisites:
update: adb,fastboot,moto-fastboot all in one zip
1. Get adb (from one of the following) (awesome thread about adb where to get it and how to use it)
a) Android adk
b) Gladroot or many of the other older rooting methods that are script based in the stickys
c) obtain moto-fastboot for your os version
32 or 64 bit ms windows xp, vista, or 7
64 bit linux
32 bit linux
Mac osX
fastbootandfriends?​ d) Drivers for your device - windows 32 and 64 bit (motorola.com site) other os's do not need driver files.​
2. Obtain root on your device
a) look in the sticky threads (I prefer the CWM zip here)
Warnings:
Do not restore /data "/dev/block/mmcblk0p16" if your going from one rom to another. use titanium backup or another utility.
Do not restore /pds "/dev/block/mmcblk0p3" unless you have a issue with your touchscreen or unless instructed to do so by someone that understands /pds.
Do not ever share your pds.img with anyone
Backup:
adb shell
su
Then type the dd commands below to create a image file on your external sdcard for the following...
Boot
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
Click to expand...
Click to collapse
System
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard-ext/system.img
Click to expand...
Click to collapse
Data
removed use tibu
Click to expand...
Click to collapse
Osh/Webtop
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard-ext/osh.img
Click to expand...
Click to collapse
Recovery
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard-ext/recovery.img
Click to expand...
Click to collapse
PDS
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard-ext/pds.img
Click to expand...
Click to collapse
MOVE YOUR IMAGE BACKUPS OFF YOUR SDCARD!!!
Restore:
to restore use moto-fastboot (from the pudding thread)
boot
moto-fastboot flash boot boot.img
Click to expand...
Click to collapse
System
moto-fastboot flash system system.img
Click to expand...
Click to collapse
Data
removed use tibu
Click to expand...
Click to collapse
Osh/Webtop
moto-fastboot flash webtop osh.img
Click to expand...
Click to collapse
Recovery
moto-fastboot flash recovery recovery.img
Click to expand...
Click to collapse
WARNING - PDS is tricky - Do not touch pds unless you have to.
Also do not ever share your pds.img with anyone
PDS
adb push pds.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/pds.img
dd if=/data/local/tmp/pds.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse

Why not just use cwm?
Sent from my Motorola Atrix using the XDA App

thebeardedchild said:
Why not just use cwm?
Sent from my Motorola Atrix using the XDA App
Click to expand...
Click to collapse
Because CWM nandroid restore has messed up a bunch of users touchscreens

Great info in one place, thanks!

Thanks
Sent from my MB860 using XDA App

I had to change the restore process for data to use adb as moto-fastboot will not flash a image that big.
my /data was 2 gig.
do not forget to delete data.img from /sdcard after you restore.
also keep in mind that your /data will be pretty big and will take quite a long time to restore.

also do not use DD if you have fat fingers and are prone to mistyping "of" and "if" since o and i are next to each other on most keyboards.

joe ferreira said:
Because CWM nandroid restore has messed up a bunch of users touchscreens
Click to expand...
Click to collapse
Wow that's stupid...Is there a fix on the way for that? This method here seems a little more intensive than just using CWM..
Oh well, thanks for giving us something to use while CWM sucks!

can we run these backup commands phone-side via terminal emulator?

the dd commands are best ran via adb
you can run them in terminal emulator but if terminal emulater fc's while your restoring then it could cause issues.
adb is the best way to do this.
really you should all be using titanium backup for /data anyways.
to avoid fat fingers you can also copy and paste.

Great thread Joe!

Permission denied
So I'm a bit of a n00b but I feel like I do pretty well at following directions. Obviously I'm missing something here because after typing "adb shell" and getting the '$' prompt I type the "su" command and am bumped to a new line without a '$' prompt. So far so good, but as soon as I type "dd" I immediately get "Permission denied". It won't even let me enter the entire line! Any help would be greatly appreciated.

AjaxTheCleaner said:
So I'm a bit of a n00b but I feel like I do pretty well at following directions. Obviously I'm missing something here because after typing "adb shell" and getting the '$' prompt I type the "su" command and am bumped to a new line without a '$' prompt. So far so good, but as soon as I type "dd" I immediately get "Permission denied". It won't even let me enter the entire line! Any help would be greatly appreciated.
Click to expand...
Click to collapse
you need root.
you type
adb shell
Click to expand...
Click to collapse
then type
su
Click to expand...
Click to collapse
then it will prompt you on the phone if you have root access to accept the root access request.

I had to remove the /data backup part until I can work the kinks out.
I will update and repost when it is finished

Thank you for the helpful response! I was able to install and run SuperUser on the device so I thought I had successfully rooted. Having been in helpdesk and IT for years there really is no excuse. I failed to follow my own first rule which is to reboot. After restarting my phone I was able to successfully logon to su and execute those commands, but it took finding out that I did in fact NOT have root access to prompt me to try such a thing. Thanks for providing helpful info and not flaming me (sincerely!)

what happens if you are on windows and not linux? can't restore the larger files through fastboot.

y2whisper said:
what happens if you are on windows and not linux? can't restore the larger files through fastboot.
Click to expand...
Click to collapse
your host system does not have anything to do with what I was discussing about image size.
the backup of /data was something that I had to takeout until i figure it out.
as always you should take multiple backups. I use titanium backup as well as the methods discussed in this thread.

i see. so how do I use moto-fastboot? to restore? (where to put the files etc)

y2whisper said:
i see. so how do I use moto-fastboot? to restore? (where to put the files etc)
Click to expand...
Click to collapse
correct me if I'm wrong, but I think you put the files in the fastboot folder.
if you don't put it in the fastboot folder -- you would have to type the full path of the file?
so im guessing --
fastboot flash recovery C:\MyDocuments\recovery.img
or something like that? im a noob too hehe

yeah that part i got down, but when I try to restore the system.img it doesn't let me due to the size.
EDIT
it says image is to big, use 0x10000000 bytes chunks
Failed <remote: 00000006>>
my sys files is 327680kb
Nevermind managed to find my way thanks to Magnetox!

[Q] EFS Backup?

Now that we have root is there a way to back up EFS? I'm a noob and managed to get my GS2's efs folder corrupted after flashing a ROM don't want the same thing happening to my S4

cl_l said:
Now that we have root is there a way to back up EFS? I'm a noob and managed to get my GS2's efs folder corrupted after flashing a ROM don't want the same thing happening to my S4
Click to expand...
Click to collapse
just download GSII_Rapair form playstore... gl

Or... do it yourself.
Download and install Android Terminal Emulator from the play store. You will need to get to a root prompt (su enter).
The following assumes that the partition information posted by mohan_kr in the Android Development forum is accurate.
Code:
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.img
Also, since I don't have the s4 yet, I am assuming that the path to internal storage is /mnt/sdcard/ as it is on the s2 with 4.1.2. But use a file explorer to verify the path to internal storage.
Store this in a safe place. To restore the efs partition:
Code:
dd if=/mnt/sdcard/efs.img of=/dev/block/mmcblk0p10

[Q][Solved] Verizon LG G2 trouble with rooting using Ioroot25

Solved. Root then back up EFS. Of course...
http://forum.xda-developers.com/showpost.php?p=48709232
So I'm trying to root my VS98024A but I'm having trouble backing up the EFS.
Step says to do this
To backup the EFS manually use the code below. It will save your two EFS partitions to the root of internal sd.
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img
Click to expand...
Click to collapse
But I can't for the life of me find where to type it. I found something that says to SHIFT+RMS and open a CMD in the IOroot25 folder. I typed adb devices and I got a serial number so I know the phone is plugged in fine.
But then I type in
Code:
adb shell
su
and it shows that su is not found. I understand that I need to be rooted to use su command but how am I suppose to back up the EFS before I root?

can I flash my efs.img via odin?

can't boot my phone cause I have deleted my efs folder becasue in one of the guides here someone said that if you had full recovery of your efs and you sure that your efs folder is damged than delete the folder and recover, well so I did... (I downgrade from lolipop to 4.4.2, lost my imei in the "process"
I had the efs.img backup on my computer and I moved it to my phone, I deleted my efs folder using root browser and than I used some adb app to type the commend "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096" and I restred my phone, but it never left samsmung logo and I can't boot up my phone I tried to go to stock channgeing roms, nothing helps, in recovery mode it says "E:/can't mount efs" something like that.. and the phone won't boot up, just stuck on samsung logo.
somone have any Idea what can i do?

After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?

audit13 said:
After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?
Click to expand...
Click to collapse
you mean when I downgrade from lolipop to the stcok rom?, if yes Than I didn't and that what cause me losing my imei and started this whole efs problem...

Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.

audit13 said:
Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.
Click to expand...
Click to collapse
yey I manged to fix ti!!!! god that was hard **** yes!! to me!
if someone will see this so this is what I did
1) I flashed to stock rom based lolipop but still had the issue of "E:failed to mount /efs" cause it didn't recvoer the folder and my phone still won't boot up, so I found a fix
right here http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
adb shell
Code:
mke2fs /dev/block/mmcblk0p3
Code:
mount -w -t ext4 /dev/block/mmcblk0p3 (this line dind't even work for me so I skipped it)
Code:
reboot
affter I did it phone boot up finally but I still had a fake Imei so next I used this guide (this time I ain't deleting the efs folder like he wrote"
2)http://forum.xda-developers.com/showthread.php?t=2392632, I alredy had efs.img as back up so all I did is install latest "su" and the latest busybox than I installed "Terminal Emulator"
and used the second method
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!

Congratulations on your success and posting your solution!

worked for me
okdark4 said:
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!
Click to expand...
Click to collapse
Hi okdark4,
thanks for sharing!
For me, I hat to use a slightly different command - just for the others to know:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3
reboot
That's it!