OK I want to get a back up of my existing stock rom (of course since there are now mod roms for this beast yet).
I know I can use dd as root and get a clone, (copy) of my entire system.
However not sure where to begin my if= statement in my linux box it would be if=/dev/sda ... I know from pwd that I am in / but what is my mount point for my dd if=?
Related
After having some major speed issues using Touchdown on my new Vibrant, I was directed to this thread discussing issues with the way Samsung stores app data on the phone. Apparently the app data is stored on the internal SD vs. NAND and that is considerably slower. Here are the two methods to fix:
*Both Methods require ROOT*
*Method 1 limits the space of app data, which can possibly cause issues*
*Method 2 requires writing a new Kernel, which comes with it's own possible issues*
*READ THE THREADS!*
Method 1: http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
Method 2: http://android.modaco.com/content/s...ed-real-fix-for-the-stalling-lagging-problem/
Hopefully this will be helpful moving forward with the development of this phone!
Note: I have used method 1 which moved the app data from the SD space to the NAND space which significantly increased the speed of my phone, but PLEASE read the links and associated discussion. You are limited to 130MB app space on NAND, which can be limiting depending on which apps you use. Method 2 purports to fix this limitation...
How to check how much app memory you are currently using:
Code:
adb shell
su
cd /data/data
busybox du -h|busybox grep M
How to apply Method 1:
Code:
adb shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
How to undo Method 1 (no loss):
Code:
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
How to undo Method 1 (restore to point of application):
Code:
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot
Awesome, thanks for doing the parsing and putting out a procedure. Works great. No more lag.
Thanks, just tried it out on mine.
BE WARNED you will run into issues if your application data goes over 130MB. There is a better way to do this which includes a custom kernel with ext3/4 support and symlinking to the ext partition instead of the small NAND space.
Find it herehttp://android.modaco.com/content/samsung-galaxy-s-s-modaco-com/313365/updated-real-fix-for-the-stalling-lagging-problem/
I havent felt the need to perform either of these ATM. Please warn people of the consequences especially if your just telling them "Hey this will make your phone faster!" I do notice its explained in the article you linked from but not everyone will read that and then when they start having issues they will have no idea what to do. For those that completed this method you might want to revert it and go a better route. 130MB isnt enough room.
Agreed...I figured people would read the link, but you never know. Will update accordingly. THX!
I am trying test out method 1 but I keep getting stuck. I type in cp -rp /data/data /dbdata into adb but it comes back with cp: not found. Any ideas what I am doing wrong here?
Add busybox before the cp command; i.e.: busybox cp etc...
Krycek said:
Add busybox before the cp command; i.e.: busybox cp etc...
Click to expand...
Click to collapse
Thanks, figured it was something simple like that. Still new to this Android stuff after years of custom WinMo roms and hybrid Blackberry roms.
i'm a little sketchy about applying method 2...will installing a modified kernal have an effect when samsung rolls out the update for 2.2?
I concur, but that is also probably the "right" way to do it. The nice part about method 1 is it is easily reversible. I will update post 1 in a minute with how to check what your current usage is to see if you are close to the 130MB limit.
Thanks, just checked my usage and was only using 21MB thus far. I figure the 130MB limit should suit me fine until Samsung issues a fix. It looks like the European devices already have a new firmware that speeds it up quite a bit so probably won't be too much longer here in the US either.
Im not going to do either. Im going to wait for an official fix.
I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).
anomalous3 said:
I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).
Click to expand...
Click to collapse
i doubt it...it's the reason you need to install the modded kernal so that it recognizes the ext3 or ext4 partition. without it the partition is useless. i personally wouldnt use method 2 as there is no way to revert as of now.
Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!
I'm not infront of my PC atm, but try this.
adb mount
adb shell
su
If mount doesn't work try remount.
Let me know if this works for you, once i'm home I can double check.
Already tried that. I have a Nexus One and adb remount works on that but for this phone it says 'remount failed: No such file or directory'
Digitalthug said:
Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!
Click to expand...
Click to collapse
You might have already tried this, but make sure the phone is unlocked (at home screen) when you run the su command from your workstation... superuser will then prompt and you can allow it to run.
I've noticed that if the screen is locked it won't prompt and just give the permission denied message.
Sent from my Vibrant (with lag fix and loving it)
just did method 1 and the difference is incredible. as far as method 2 goes, will custom roms have this ability from the get go or do we need the official samsung update?
I just want to confirm that this fix works for the US version of the Galaxy S (Samsung Vibrant) right?
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.
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'm trying to wipe and format a microSD card that I have plugged in via OTG and already have it wiped with this;
Code:
dd if=/dev/zero of=/dev/block/sda
Now I'm looking into how to recreate a MBR and partition table and it says to use the parted command, which I'm glad about as I'm familiar with the command from using Ubuntu but it's not installed and I can not find any instructions on how to get it. Can anyone explain how to install it? I know I could just plug the SD card into a computer and do it but I'm having fun doing all this on a tablet. Lol
Bump
Anyone?
I have got the same question, any other solutions?
This is the most complete information I have found yet, but it doesn't work. Either from me messing something up or it not being correct for the Nexus 7 being that it was made two years ago. http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
I pushed all six files to /sbin/ with no errors and changed their permissions with no issues but I restart the tablet and none of the six files are in /sbin/
Just for the heck of it I extracted the six files to the SD card in the tablet, CD'd to it and used chmod 0755 on all six files then tried to run it and this is what I get.
Code:
[email protected]:/storage/emulated/legacy/folder # parted
sh: parted: not found
127|[email protected]:/storage/emulated/legacy/folder # ls
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
... how can you NOT find that?
herqulees said:
... how can you NOT find that?
Click to expand...
Click to collapse
Depending on how your PATH env var is set, the current directory might or might not be being searched for program load(s). So indicating the current directory explicitly with a leading "./" such as
$ ./parted
will certainly work (if a read & execute bit set on file, and the filesystem is not mounted -noexec ) .
But...
...if those files are dynamically linked rather than statically linked, and the appropriate link-libraries they reference come up missing during run-time linking it is possible to still see a "not found" message. Sort of a red-herring error message, but there you go.
I just looked in TWRP's /sbin (ramdisk) just now. Don't see parted in there.
[Edit] I do see the string "fdisk" inside the busybox executable though! - maybe boot into recovery and see what
busybox fdisk /dev/block/sda
gets you? (I suppose result depends on whether or not TWRP kernel plumbs the device into place.)
Perhaps the quickest solution is to simply use a PC and media reader to do the partitioning from a PC instead of the N7. You might even want to boot a "Live CD" version of Linux to get at the tools you need. (BTW, I think that Ubuntu's Live CD mounts a fuse FS over the top of the RO DVD/CD, so you can even download and install packages as needed).
I managed to get everything to work by doing this:
1. Using this app https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en I remounted /system as RW
2. Using the CyanogenMod File Manager I copied the parted file to /system/bin (from the root of the SD card)
3. Then using the File Manager still, go to the Properties of the parted file and go to Permissions and under R, W, and X put a check mark in the three boxes bellow each. (I don't know which ones it needs permissions for so I just give it permissions to everything, kinda frowned upon to do but I trust this program so...)
By doing this you can completely stay out of command line, but at the same time you're installing a command line program so you shouldn't be afraid of the command line in the first place. Lol.
Note: After this you can go to a terminal window and type su to get root access then type
Code:
parted /dev/block/sda
you will of opened your external memory card, now use parted as you would normally.
Hello guys,
Would it be possible to create an image of an android tv box like creating a windows image? Thanks..
I assume you have one of those cheap, often prerooted Android TV boxes. If you connect the device to your computer using adb, you can type adb shell, then su, and google how to use the Linux tool that is also in android called dd to copy the boot, system and so on partitions to .img files. Most android roms will have the partitions listed in /dev/block then look around with ls for a directory called by-name to find them all listed by name. For example on my device I typed dd if=/dev/block/by-name/boot of=/sdcard/boot.img to copy boot. As far as I know, this will work for all of them.