Hello!
So I recently stumbled upon some information that while flashing all kinds of Roms, you might lose your IMEI, thus being left over with a nice paper weight.
To my understanding this information is stored in the EFS folder (though according to this thread it is actually stored in modemfs).
I googled around and saw many options: PC software, terminal commands, apps etc.
Since each phone utilizes this option in different ways, which would be a good way to backup these folders in case of emergency on the S Advance?
Thanks!
SOLUTION:
These are the commands from the ADB shell, but can also be used within the terminal.
Backup Process:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/efs_backup.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemfs_backup.img
exit
exit
adb pull /sdcard/efs_backup.img efs_backup.img
adb pull /sdcard/modemfs_backup.img modemfs_backup.img
Restore Backup Process:
Code:
adb push efs_backup.img /sdcard/efs_backup.img
adb push modemfs_backup.img /sdcard/modemfs_backup.img
adb shell
su
dd if=/sdcard/efs_backup.img of=/dev/block/mmcblk0p7
dd if=/sdcard/modemfs_backup.img of=/dev/block/mmcblk0p2
exit
exit
Thanks to @mr.harsh and @KINGbabasula for help and KINGbabasula for making the script!
Please note that the restore commands haven't been tested out, but theoretically its supposed to work.
If someone has made a backup and wiped his EFS folder, he wont mind testing it out
YMatrix said:
Hello!
So I recently stumbled upon some information that while flashing all kinds of Roms, you might lose your IMEI, thus being left over with a nice paper weight.
To my understanding this information is stored in the EFS folder (though according to this thread it is actually stored in modemfs).
I googled around and saw many options: PC software, terminal commands, apps etc.
Since each phone utilizes this option in different ways, which would be a good way to backup these folders in case of emergency on the S Advance?
Thanks!
Click to expand...
Click to collapse
in the terminal type:
Code:
su
cp /dev/block/mmcblk0p7 /sdcard/efs_backup
cp /dev/block/mmcblk0p2 /sdcard/modemfs_backup
check that efs_backup is 10MB and modemfs_backup is 16MB.And this is for JB.I don't know about GB but most probably they'll be same...
Thank you for your quick reply.
I tested it out and got the sizes you said.
The restore process, if ever needed, is the same cp command only changing the source and destination?
Whats the difference between the CP command and the DD command?
Any way to do this from recovery or ADB?
Sent from my GT-I9070 using Tapatalk 4 Beta
YMatrix said:
Thank you for your quick reply.
I tested it out and got the sizes you said.
The restore process, if ever needed, is the same cp command only changing the source and destination?
Whats the difference between the CP command and the DD command?
Any way to do this from recovery or ADB?
Sent from my GT-I9070 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Via adb:
Code:
adb shell
$ su
# cp /dev/block/mmcblk0p7 /sdcard/efs_backup
# cp /dev/block/mmcblk0p2 /sdcard/modemfs_backup
# exit
$ exit
adb pull /sdcard/efs_backup %cd%\efs_backup
adb pull /sdcard/modemfs_backup %cd%\modemfs_backup
KINGbabasula said:
Via adb:
Code:
adb shell
$ su
# cp /dev/block/mmcblk0p7 /sdcard/efs_backup
# cp /dev/block/mmcblk0p2 /sdcard/modemfs_backup
Click to expand...
Click to collapse
Thank you!
Why use the CP command and not the DD command? Or in this case it doesn't really matter?
YMatrix said:
Thank you!
Why use the CP command and not the DD command? Or in this case it doesn't really matter?
Click to expand...
Click to collapse
cp=copy dd=copy, convert, format. See my reply. I updated
KINGbabasula said:
cp=copy dd=copy, convert, format. See my reply. I updated
Click to expand...
Click to collapse
Still don't get the difference DD / CP
As for the commands you posted, I was asking for the restore process, so I am guessing it will look like this:
Code:
adb shell
$ su
# cp /sdcard/efs_backup /dev/block/mmcblk0p7
# cp /sdcard/modemfs_backup /dev/block/mmcblk0p2
# exit
$ exit
Is there a "push" command also (to be used like the pull command)?
YMatrix said:
Still don't get the difference DD / CP
As for the commands you posted, I was asking for the restore process, so I am guessing it will look like this:
Code:
adb shell
$ su
# cp /sdcard/efs_backup /dev/block/mmcblk0p7
# cp /sdcard/modemfs_backup /dev/block/mmcblk0p2
# exit
$ exit
Is there a "push" command also (to be used like the pull command)?
Click to expand...
Click to collapse
I'm not sure but i think that you need to use dd to restore because you are going to flash 2 partition like flashing kernel.
You can do this (i repeat Im not sure)
Code:
adb push efs_backup /sdcard/efs_backup
adb push modemfs_backup /sdcard/modemfs_backup
adb shell
$ su
# dd if=/sdcard/efs_backup of=/dev/block/mmcblk0p7
# dd if=/sdcard/modemfs_backup of=/dev/block/mmcblk0p2
# exit
$ exit
Pay attention cause if you dd to a wrong partition you may brick
KINGbabasula said:
I'm not sure but i think that you need to use dd to restore because you are going to flash 2 partition like flashing kernel.
Pay attention cause if you dd to a wrong partition you may brick
Click to expand...
Click to collapse
Hmmm, so this is a pickle.
Wrong partition is always a problem, but since I also checked a thread by @frapeti, I am assuming the partition numbers are correct, though I don't know about the commands. Since we saved using CP shouldn't we also restore using CP? Otherwise I would say save using DD and then restore using DD.
YMatrix said:
Hmmm, so this is a pickle.
Wrong partition is always a problem, but since I also checked a thread by @frapeti, I am assuming the partition numbers are correct, though I don't know about the commands. Since we saved using CP shouldn't we also restore using CP? Otherwise I would say save using DD and then restore using DD.
Click to expand...
Click to collapse
No because cp copy the content of the partition. dd format the partition then copy in the partition
KINGbabasula said:
No because cp copy the content of the partition. dd format the partition then copy in the partition
Click to expand...
Click to collapse
Oh, alright, so to sum up so people can use this for future reference:
Backup Process:
Code:
adb shell
$ su
# cp /sdcard/efs_backup /dev/block/mmcblk0p7
# cp /sdcard/modemfs_backup /dev/block/mmcblk0p2
# exit
$ exit
Restore Backup Process:
Code:
adb push efs_backup /sdcard/efs_backup
adb push modemfs_backup /sdcard/modemfs_backup
adb shell
$ su
# dd if=/sdcard/efs_backup of=/dev/block/mmcblk0p7
# dd if=/sdcard/modemfs_backup of=/dev/block/mmcblk0p2
# exit
$ exit
YMatrix said:
Oh, alright, so to sum up so people can use this for future reference:
Backup Process:
Code:
adb shell
$ su
# cp /sdcard/efs_backup /dev/block/mmcblk0p7
# cp /sdcard/modemfs_backup /dev/block/mmcblk0p2
# exit
$ exit
Restore Backup Process:
Code:
adb push efs_backup /sdcard/efs_backup
adb push modemfs_backup /sdcard/modemfs_backup
adb shell
$ su
# dd if=/sdcard/efs_backup of=/dev/block/mmcblk0p7
# dd if=/sdcard/modemfs_backup of=/dev/block/mmcblk0p2
# exit
$ exit
Click to expand...
Click to collapse
Now i make a script to automate it
Here is the script
I'm not sure that it will work
KINGbabasula said:
Here is the script
I'm not sure that it will work
Click to expand...
Click to collapse
That was fast
Guessing the only way to test out the restore option is if someone that made a backup and wiped his efs/modemfs folders, to test the script out.
YMatrix said:
That was fast
Guessing the only way to test out the restore option is if someone that made a backup and wiped his efs/modemfs folders, to test the script out.
Click to expand...
Click to collapse
Yes please can you change the title to [SOLVED] How to backup EFS and Modemfs folders. And in the op write the solutions? Thanks
KINGbabasula said:
Yes please can you change the title to [SOLVED] How to backup EFS and Modemfs folders. And in the op write the solutions? Thanks
Click to expand...
Click to collapse
Already did
Hi, I just wanna ask. Can I just copy the efs and modemfs folders to ext sd, then to restore I just copy and replace both files to its actual location using any root explorer (ie: es file manager)? Just asking as I read this guide on backing imei part.
arffrhn said:
Hi, I just wanna ask. Can I just copy the efs and modemfs folders to ext sd, then to restore I just copy and replace both files to its actual location using any root explorer (ie: es file manager)? Just asking as I read this guide on backing imei part.
Click to expand...
Click to collapse
Yes you can
Sent from my GT-I9070 using Tapatalk 4 Beta
KINGbabasula said:
Yes you can
Sent from my GT-I9070 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I see. Thanks man.
YMatrix said:
Oh, alright, so to sum up so people can use this for future reference:
Backup Process:
Code:
adb shell
$ su
# cp /sdcard/efs_backup /dev/block/mmcblk0p7
# cp /sdcard/ /dev/block/mmcblk0p2
# exit
[/QUOTE]
Thats wrong, to backup using cp use something like cp [original efs] [sdcard/backup folder]
I guess it's better to use dd command for this purpose:
dd if=/dev/block/mmcblk0p7 of=/sdcard/efs_backup.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemfs_backup.img
To restore just switch if with of (input file / output file)
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Related
So as the title says, I pushed an apk to "system/tools" on my phone on accident instead of apps. How can I remove this push. I have tried rm -r /system/tools/__.apk but its telling me it doesn't exist. Is it possible it did nothing? I got a file transfer after doing so. I've also tried finding that folder (tools) in astro, but its not a folder and gives me the mesage file type not found. Thanks
barnacles10 said:
So as the title says, I pushed an apk to "system/tools" on my phone on accident instead of apps. How can I remove this push. I have tried rm -r /system/tools/__.apk but its telling me it doesn't exist. Is it possible it did nothing? I got a file transfer after doing so. I've also tried finding that folder (tools) in astro, but its not a folder and gives me the mesage file type not found. Thanks
Click to expand...
Click to collapse
Get andExplorer and browse to the /system/app folder to see if it is there, of on a computer use Android Commander.
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Kcarpenter said:
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Click to expand...
Click to collapse
rm -r is a recursive deletion. For a single file leave off the -r. Why?
Because if you accidentally forget to put in the file name it will delete everything in the directory and below it.
Kcarpenter said:
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Click to expand...
Click to collapse
Correct, but when I try this it says its not a valid directory. And when I navigate to that folder with astro is not an openable folder. Which led me to believe it didn't transfer, or just wouldn't allow it. However, cmd showed the transfer data and time after pushing. Thats why I was confused
smw is correct, -r is for directories only, so the proper command would be:
Code:
adb remount
adb shell
rm /system/tools/XYZ.apk
gu1dry said:
smw is correct, -r is for directories only, so the proper command would be:
Code:
adb remount
adb shell
rm /system/tools/XYZ.apk
Click to expand...
Click to collapse
I've tried this too I get
"rm failed for system/tools/app.apk, Not a Directory"
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then cd to the right directory and type
rm xxxx.apk
since their is no tools directory it clearly didn't autmoatically create one. Instead it just made a file called /system/tools which is your apk file. to remove it just "adb shell rm /system/tools"
alexthearmo said:
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then cd to the right directory and type
rm xxxx.apk
Click to expand...
Click to collapse
after the command "
alexthearmo said:
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
" I try a cd /system/tools/" and get a can't cd error. hmm
Click to expand...
Click to collapse
darchstar said:
since their is no tools directory it clearly didn't autmoatically create one. Instead it just made a file called /system/tools which is your apk file. to remove it just "adb shell rm /system/tools"
Click to expand...
Click to collapse
Ah ha. So there is no such thing as /system/tools on the phone? This is what I was curious about. So deleting the file will /system/tools altogether should be ok?
cd into /system & then ls to make sure there is tools folder.
sorry for the recursive thing, wasn't thinking about what I was typing.
-r is not needed.
Thanks for the great job done by developers. However, I noticed mediascape was removed after root. Personally I think mediascape is nice but failed to install it from the app folder on sdcard. Searched the whole thread but didn't find a method.
I tried manually copy the mediascape.apk to /data/app, reboot, then mediascape is restored in the application drawer and can be run functionally.
Here is the details.
Connect the X10 to PC using USB debug mode.
Get the adb.exe ready (you can run it from the root step4 folder directly)
0. Copy mediascape.apk to the step4 folder.
1. Start command prompt as administrater.
2. Change to the step4 folder.
3. Run "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" without quotes.
4. Run "adb shell chmod 777 /data/app" without quotes.
5. Run "adb push mediascape.apk /data/app" no quotes.
6. Run "adb shell reboot" no quotes.
BTW: I have copied all the mediascape related files back to /system/app as well, by running "adb shell chmod 777 /system/app" and using adb push.
Seems it's not ideal as the apk is not installed but added to the X10 directly.
Any better ideas?
Try RealPlayer for Android, it's a new app, really good!
w w w.real.com/realplayer/android
Nah, nothing can beat mediascape.
anyway, how can one get timescape back?
Fuzalert2k said:
Nah, nothing can beat mediascape.
anyway, how can one get timescape back?
Click to expand...
Click to collapse
you mean timescape? or mediascape?
shvyue said:
Thanks for the great job done by developers. However, I noticed mediascape was removed after root. Personally I think mediascape is nice but failed to install it from the app folder on sdcard. Searched the whole thread but didn't find a method.
I tried manually copy the mediascape.apk to /data/app, reboot, then mediascape is restored in the application drawer and can be run functionally.
Here is the details.
Connect the X10 to PC using USB debug mode.
Get the adb.exe ready (you can run it from the root step4 folder directly)
0. Copy mediascape.apk to the step4 folder.
1. Start command prompt as administrater.
2. Change to the step4 folder.
3. Run "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" without quotes.
4. Run "adb shell chmod 777 /data/app" without quotes.
5. Run "adb push mediascape.apk /data/app" no quotes.
6. Run "adb shell reboot" no quotes.
BTW: I have copied all the mediascape related files back to /system/app as well, by running "adb shell chmod 777 /system/app" and using adb push.
Seems it's not ideal as the apk is not installed but added to the X10 directly.
Any better ideas?
Click to expand...
Click to collapse
done this and mediscape still dont apear and cant install it through astro file manager
Can you see mediascape.apk in the /data/app folder? If yes have you copied 4 mediascape files back to /system/app?
Sent from my SO-01B using Tapatalk
hmm I don't seem to have the app folder in my data folder, in my memory card can someone help me out
The data/app folder is not on your sdcard. Up one level.
Sent from my SO-01B using Tapatalk
shvyue said:
you mean timescape? or mediascape?
Click to expand...
Click to collapse
I mean timescape
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
hey is der ne way i can get mediascape running on ne othr device than x10??? just asking
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
How exactly do you do this? What do you edit... siggh
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
This worked for me. Thanks!
Fuzalert2k said:
How exactly do you do this? What do you edit... siggh
Click to expand...
Click to collapse
Turn on USB-debugging mode. Run command prompt (start->run->"cmd"). Change to your step4 directory. Enter those commands line by line.
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
op's method did not work for me but this one worked perfect
it worked now.
thanks so much for the instruction
thanksss it works
would anyone please upload *.apk and *.odex files please, since i cant find em on my x10 anymore. thanks
*.odex files
can some one please share mediascape.odex and MediascapePluginManager.odex files
Both the stock 2.1 gallery and for example doubletwist or poweramp kicks mediascapes ass when it comes to usability, I installed Z's 2.2.1 ROM a week ago and must admit that I dont miss media/timescape one bit Bottom case is that I'll rather use a semi-stable 2.2 ROM than a slow SE rom ;-)
I managed to break my micro sd card in half today and I wasn't able to pickup a class 10 or 6 replacement locally so I thought I could use some of the 6gb of internal memory as a virtual filesystem to get me out of trouble.
So, after quickly looking at the android docs and the supported busybox commands I created a 2gb sdcard.img in /data and mounted to /sdcard. I copied some files to it with astro filemanager and fired up raging thunder 2 and it went ahead and downloaded the game data to /sdcard/ and worked correctly.
But, a few apps won't recognise it as an sdcard (Motorola SD card and phone storage settings applet) as well as things like PlayPro (states I have no sdcard present). I thought perhaps I could modify the /etc/vold.fstab file to auto mount the sdcard.img I created using vi but I'm a bit clueless as to what I should change on the dev_mount /sdcard line to get it automounted at boot and hopefully fool the rest of the apps into thinking it is a physical sdcard.
Can anyone possibly point me in the right direction? Not sure how to invoke cmd mode in vi using the milestone qwerty either but I'll keep digging.
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
+ 1 for this, it would be great to can use internal storage for user data
Why do you let this nice post die.. so "flibbulator" found anything more out?.. I'd like to know more.. like if you got it to work with Music Players and Video players??
Try to mount /data/sdcard.img to /mnt/sdcard (/sdcard is a link to /mnt/sdcard)
or try "export EXTERNAL_STORAGE /sdcard"
I made in a different way: created a 4GB storage.img in /data and mounted it in /sdcard/storage, so internal storage is finally usable for user data
the problem was to set mount point on boot, I can't find a way to execute a script on boot (you can't permanently modify init.rc)
flibbulator said:
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
Click to expand...
Click to collapse
I have actually tried this on my Droid2Global, and I get the error "unknown operand if/dev/zero" I feel like I am missing the point or do not fully understanding how to use the "dd" command?
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
patton82 said:
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
Click to expand...
Click to collapse
Thank you bro.
Quick question I keep getting these errors. I do have a folder in "/" named "sdcard-int"
Better Terminal Emulator Pro
/ # busybox mount -o loop /data/sdcard.img /sdcard-int/
mount: can't setup loop device: No such file or directory
/ # busybox mount -o /data/sdcard.img /sdcard-int
mount: can't read /etc/fstab: No such file or directory
/ #
Sent from my DROID2 GLOBAL using Tapatalk
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Will be lost anything after reboot when use this storage?
Sent from my MotoA953 using XDA App
all the stuff in img file will not be lost, as long as you put it in /data/
on the contrary the mount point must be restored after reboot
patton82 said:
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Click to expand...
Click to collapse
Thank you, I will use the Thank you button when I login via PC.
I still get the same error, I know that I'm doing something incorrectly or maybe I don't understand "mount" comment correctly?
/ $ su
/ # mkdir /sdcard/storage
/ # dd if=/dev/zero of=/data/storage.img bs=1024 count=41943404194340+0 recordsn
4194340+0 records out
4295004160 bytes (4.0GB) copied, 339.823883 seconds, 12.1MB/s
/ # busybox mkfs.vfat /data/storage.img
/ # mount -o loop -t vfat /data/storage.img /sdcard/storage
mount: can't setup loop device: No such file or directory
/ #
I am using my sdcard also, I'm not too sure if that makes any difference?
Sent from my DROID2 GLOBAL using Tapatalk
Better terminal pro uses BASH shell, I presume
try to switch to android shell, in preferences
or to use terminal emulator (free) from market
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Sent from my DROID2 GLOBAL using Tapatalk
resource busy, you have to reboot the phone
I use Gscript lite, add a script with the string
mount -o loop -t vfat /data/storage.img /sdcard/storage
and create a shortcut to homescreen, so when I reboot, I can mount the img file in one click
Cool mod for my ROM. Could I take it??
sure, they are simple shell commands
the best would be to do what happen with Samsung Galaxy S: internal storage mounted as sdcard and physical sdcard mounted in a folder /sdcard/sd
storage.img is 3-4 times faster than my peak 8GB class 6
There is an application "Autostart" in the market, which can automatially execute a script with root after boot up.
I up because I'm now also interested in making profit of the huge internal storage. I'd like to put my wikipedia data from wikidroyd to the internal storage. Hopefully I'm skilled enough to follow the given steps...I doubt that though
fKngFtd said:
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Click to expand...
Click to collapse
Guys, I need your help! I have exactly. The same problem:
Every time I try to mount my storage.img I get
Ioctl LOOP_SET_FD failed: Device or resource busy.
I rebooted several times and also tried to mount smaller images (first I tried 3gb then I tried 1mb).
Any solution?
Edit: I solved it myself. I always forgot to punch in busybox before the command. Now it worked for me!!
I do have a question now. With help of Gscript I made a shortcut to mount the storage.img to my sdcard. But my pc wont recognise the sdcard as long as the image is mounted. What is the command to unmount the partition so I wouldnt have to reboot my phone before connecting it to the pc...?
Any help is much appreciated! Thx
(Something like busybox unmount -o loop -t vfat...?)
Sent from my MotoA953 using XDA App
This might work on other devices.
WARNING: this might brick your phone use it at your own risk.
Warning you have to have some knowlage of linux to do this kind of stuff.
WARNING: actually you have to have _good_ knowlage of linux/gnu stuff to do it.
The idea is this is to make the /system/bin/toolbox from the stock rom suid (permision 6755, it originaly has 0755)
This is how I did it. It might be simpler.
get a stock rom that you want. for me it was B5330XWALH3
it is now available at samsung-updates.
You need odin (heimdal will not work with my phone) (my was 3.07)
unpack the zip.
you get a .tar.md5 file (the tar file has broken headers so tar from ubuntu 12.04 will not unpackit).
the tar file works in sectors of 512 bytes.
take out the md5sum at the end of file. (some thing like: head -c (the size up to the last md5sum) original.tar.md5 > file1)
split the file so you will have the system.img.md5 separated (some thing like: head -c (the size upto "system.img.md5") file1 > file2;
head -c (the size upto "dt-blob.md5") file1 | tail -c +(the size upto "system.img.md5" + 1) > file3;
tail -c +(the size upto "dt-blob.md5" + 1) file1 > file4
file3 now has the system.img.md5, trim the md5sum from the tail and the tar headr from head (ex.:
head -c (upto the md5sum output from the rear of the file) file3 | tail -c +513 > file5)
file5 is a sparce image file of an ext4 filesystem. run simg2img (from ext4fs_utils (search on xda)) (ex.:
simg2img file5 file6)
sudo mount -o loop,ro file6 /mnt
look for the file /mnt/bin/toolbox (ex.: ls -l /mnt/bin/toolbox) it will give you an output like this:
-rwxr-xr-x 1 root 2000 99068 Aug 9 07:59 /mnt/bin/toolbox
sudo umount /mnt
the permisions and the size of the file yield the following hex sequence that you get in the file (we will hexedit the ext4 fs): ED 81 00 00 FC 82 01 00
in file3 edit the sequence (it should be only one in the file) from ED 81 00 00 FC 82 01 00 to ED 8D 00 00 FC 82 01 00 (practically adding the suid guid bits to the inode of the toolbox)
we are almost done, now to pack our bags and go.
verify that you have indeed put suid guid to toolbox:
head -c (upto the md5sum output from the rear of the file) file3 | tail -c +513 > file5;
simg2img file5 file6;
sudo mount -o loop,ro file6 /mnt;
ls -l /mnt/bin/toolbox
It should give an output:
-rwsr-sr-x 1 root 2000 99068 Aug 9 07:59 /mnt/bin/toolbox
sudo umount /mnt
recalculate the md5sum to the _expanded_ image: md5sum file6 > file7
overide the md5sum at the end of file3 with the one from file7
now pack the pieces in one tar: cat file2 file3 file4 > myfirmware.tar
add the md5sum to it: md5sum myfirmware.tar >> myfirmware.tar
change the name to .tar.md5: mv myfirmware.tar myfirmware.tar.md5
copy the file on a windowze machine (that has odin and the samsung drivers intalled).
update with odin the new firmware (which you should put in the PDA section) (don't forget to un check the repartitioning).
you should have now a practivally rooted device.
in order to have su and Superuser.apk on it you have to do the following steps:
push with adb su, busybox and Superuser.apk into /data/local/tmp on device (you get the files from other forums here at xda)
the next steps are on device (use adb shell)
verify that indeed we have a suid toolbox: ls -l /system/bin/toolbox should give that wanderfull -rwsr-sr-x permission.
find a rw mount that has suid (in my case a tmpfs is mounted /mnt/obb)
copy su to /mnt/obb (remember that we have suid toolbox this means that toolbox now gives you root on any command):
dd if=/data/local/tmp/su of=/mnt/obb/su
give su suid and make it owned by root: chmod 6755 /mnt/obb/su; chown 0.0 /mnt/obb/su
run su now and enjoy the #: /mnt/obb/su -
Click to expand...
Click to collapse
Ofcorse after you get # you should remount /system as rw, copy su in /system/xbin, copy Superuser.apk in /system/app, copy busybox in /system/xbin, make symlinks to busybox for all the comands in /system/xbin.
You should also upon success remove suid from toolbox so as to not mistakely do damage to the system (for instance "rm /")
And here you have it.
If you do not understand what I have done, you should read more linux / tar / ext4 / md5sum.
This method should work for any phone provided that it has odin as bootloader and there is the stock rom available.
hello
I don't have knowledge about how you have rooted the firmware for b5330, the steps you made are waaaay to dificult for me . Could you provide here an already rooted firmware, to download and install. thanks in advance
ETTT said:
This might work on other devices.
WARNING: this might brick your phone use it at your own risk.
Warning you have to have some knowlage of linux to do this kind of stuff.
WARNING: actually you have to have _good_ knowlage of linux/gnu stuff to do it.
The idea is this is to make the /system/bin/toolbox from the stock rom suid (permision 6755, it originaly has 0755)
This is how I did it. It might be simpler.
Ofcorse after you get # you should remount /system as rw, copy su in /system/xbin, copy Superuser.apk in /system/app, copy busybox in /system/xbin, make symlinks to busybox for all the comands in /system/xbin.
You should also upon success remove suid from toolbox so as to not mistakely do damage to the system (for instance "rm /")
And here you have it.
If you do not understand what I have done, you should read more linux / tar / ext4 / md5sum.
This method should work for any phone provided that it has odin as bootloader and there is the stock rom available.
Click to expand...
Click to collapse
bogdan_rize said:
I don't have knowledge about how you have rooted the firmware for b5330, the steps you made are waaaay to dificult for me . Could you provide here an already rooted firmware, to download and install. thanks in advance
Click to expand...
Click to collapse
no need to upload 400M for this little modification.
I'm unable to post links, goto samsung-updates
go and download B5330XWALI2_B5330OXXALI2_B5330XWLH1_HOME stock firmware.
and apply this xdelta patch over it.
xdelta patch sGTB5330.patch B5330XWALI2_B5330OXXALI2_B5330XWLH1_HOME.tar.md5 myfrm.tar.md5
Click to expand...
Click to collapse
after that you have the firmware that I use to root my phone.
Still... this firmware will not have "su" install, it will just be a rootable firware because it has a suid'ed toolbox.
a suid'ed toolbox in android means that you can exec chown and chmod as a root.
So. After the patching of the stock rom and flashing it. you have to have this md5sum output:
032b4344ab503c8413db9127efaa3d83 myfrm.tar.md5
Click to expand...
Click to collapse
odin will accept it (I've used Oding 3.07).
after that you push the files from the attached tar.gz to /data/local/tmp
tar -xzf superuser_stuff.tar.gz
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
Click to expand...
Click to collapse
after that you bassically have to run this commands in an android shell in order to get to a stardard rooted android:
adb shell # enter the in the phone
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nologer with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
Click to expand...
Click to collapse
have fun.
I downloaded this firmware: Samsung-Updates.com-GT-B5330_COA_1_20120913171601_pducfx5hbw.zip. Where, how, what???...i unzipped it and now how to apply the patch? The rest of the stept i think i get it....i think For you it's easy to say, for me it's hard to do. I've had sgs1, sgs2 and sgs3, and the root of those was sooooooo easy... but this piece of crap b5330 drives me crazy )
ETTT said:
no need to upload 400M for this little modification.
I'm unable to post links, goto samsung-updates
go and download B5330XWALI2_B5330OXXALI2_B5330XWLH1_HOME stock firmware.
and apply this xdelta patch over it.
after that you have the firmware that I use to root my phone.
Still... this firmware will not have "su" install, it will just be a rootable firware because it has a suid'ed toolbox.
a suid'ed toolbox in android means that you can exec chown and chmod as a root.
So. After the patching of the stock rom and flashing it. you have to have this md5sum output:
odin will accept it (I've used Oding 3.07).
after that you push the files from the attached tar.gz to /data/local/tmp
after that you bassically have to run this commands in an android shell in order to get to a stardard rooted android:
have fun.
Click to expand...
Click to collapse
bogdan_rize said:
I downloaded this firmware: Samsung-Updates.com-GT-B5330_COA_1_20120913171601_pducfx5hbw.zip. Where, how, what???...i unzipped it and now how to apply the patch? The rest of the stept i think i get it....i think For you it's easy to say, for me it's hard to do. I've had sgs1, sgs2 and sgs3, and the root of those was sooooooo easy... but this piece of crap b5330 drives me crazy )
Click to expand...
Click to collapse
I've used xdelta package.
if you are on win then you're on your own.
there is xdelta.org and it seems to have pachage for windows.
for sgs[123] was easy because are main streams. may hackers were working on it.
this device is very new/obscure.
I whould have made a script, but alas, "heimdal" firmware loader whould not work with this device.
I've used linux to patch the firmware and windowze to upload it.
So a script whould be imposible, but after you pach .tar.md5 file and load it on your phone is just about cut and paste form my previous post.
My hope is that a more android savy guy will take this concept and make it a script.
I am just happy that I can now have debian on my phone.
yes, i am on win....there is no way to patch that COA firmware (i am from romania) and upload somewhere to download???i know i am probably asking to much from you, but i dont't think i will manage by my own...this rooting busines is driving me crazyyyyy :crying::crying::crying: thank you so much for your answer!!!
ETTT said:
I've used xdelta package.
if you are on win then you're on your own.
there is xdelta.org and it seems to have pachage for windows.
for sgs[123] was easy because are main streams. may hackers were working on it.
this device is very new/obscure.
I whould have made a script, but alas, "heimdal" firmware loader whould not work with this device.
I've used linux to patch the firmware and windowze to upload it.
So a script whould be imposible, but after you pach .tar.md5 file and load it on your phone is just about cut and paste form my previous post.
My hope is that a more android savy guy will take this concept and make it a script.
I am just happy that I can now have debian on my phone.
Click to expand...
Click to collapse
bogdan_rize said:
yes, i am on win....there is no way to patch that COA firmware (i am from romania) and upload somewhere to download???i know i am probably asking to much from you, but i dont't think i will manage by my own...this rooting busines is driving me crazyyyyy :crying::crying::crying: thank you so much for your answer!!!
Click to expand...
Click to collapse
ok here it is the modified firmware.
http://dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Interesting, reading carefully
Sent from my GT-B5330 using xda app-developers app
Thank you so much, tomorow morning i know how i'll spend my time...installing and rooting my b5330, unfortunately this evening i don't have my laptop on me forgoted at work ), but i've downloaded the firmware from phone and now waiting to have it done...finally!!! I'll let you know what have i done. Have a nice day and once again thanks!!!
ETTT said:
ok here it is the modified firmware.
http://dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Click to expand...
Click to collapse
it's not working, when i'm trying to adb remont it says: remount failed: Opertaion not permited. After i flashed with odin the firmware you gave to me, i think i do not have permission to make any changes, and i don't know why
ETTT said:
ok here it is the modified firmware.
http://dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Click to expand...
Click to collapse
Can you make patch for dxlh3..? Thanks
Sent from my GT-B5330 using xda app-developers app
bogdan_rize said:
it's not working, when i'm trying to adb remont it says: remount failed: Opertaion not permited. After i flashed with odin the firmware you gave to me, i think i do not have permission to make any changes, and i don't know why
Click to expand...
Click to collapse
There commands are supposed to be given in a command line box (cmd on win).
where does it gives you error?
adb shell # enter the in the phone
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nologer with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
finally it worked
yeeeees, damn you're good!!!! i have managed to root my b5330, root checher tell me that i am rooted and busybox is instaled...the only problem is that it shows me that i do not have installed superuser and supersu. Is there a problem if i just copy paste the apk file (supersu.apk and superuser.apk -> i've downloaded the pro version of bouth of them ) straight into the directory /data/local/tmp where it should be? or to copy-paste in another directory. Thanks in advance, CMD(and adb shell) gave me headache, but i finally got it an succedeed )) :victory::good:
ETTT said:
There commands are supposed to be given in a command line box (cmd on win).
where does it gives you error?
adb shell # enter the in the phone
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nologer with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
Click to expand...
Click to collapse
bogdan_rize said:
yeeeees, damn you're good!!!! i have managed to root my b5330, root checher tell me that i am rooted and busybox is instaled...the only problem is that it shows me that i do not have installed superuser and supersu. Is there a problem if i just copy paste the apk file (supersu.apk and superuser.apk -> i've downloaded the pro version of bouth of them ) straight into the directory /data/local/tmp where it should be? or to copy-paste in another directory. Thanks in advance, CMD(and adb shell) gave me headache, but i finally got it an succedeed )) :victory::good:
Click to expand...
Click to collapse
1. I'm glad you got it.
2. You should give thanks (that button) if I helped you.
3. I'm you dont read instructions. Maybe it's a problem with us romanian engineers, or maybe engineers in general
look at item 11. from my previous post. maybe I just c&p here.
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
So, when you are in adb shell and you go root (su command, you get the promt with #) and you have the /system mounted rw.
Then any apk that you copy to /system/app folder will get intalled and when you list your application (the button with 16 squares) you should see it.
Have fun.
i was having trouble understanding adb shell and cmd from the begining. I never used this command tool...ever ) and i think from yesterday to this day i managed really ok . Anyway i think i will just copy-paste the superuser.apk in "app" folder directly in the system (it's the same thing, isn't it??). I have done that in item 11., and after a restart supersu was instaled, only superuser.apk didn't, i think i wrote something wrong in adb shell
ETTT said:
1. I'm glad you got it.
2. You should give thanks (that button) if I helped you.
3. I'm you dont read instructions. Maybe it's a problem with us romanian engineers, or maybe engineers in general
look at item 11. from my previous post. maybe I just c&p here.
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
So, when you are in adb shell and you go root (su command, you get the promt with #) and you have the /system mounted rw.
Then any apk that you copy to /system/app folder will get intalled and when you list your application (the button with 16 squares) you should see it.
Have fun.
Click to expand...
Click to collapse
hihihi
neeeah, my bad, i thought that in "superuser_stuff" is superuser and supersu files, it was just su->for superuser.apk, easy peasy, it worked and installed from the first time...it was just me verry verry dizzy and confused. Your guide is 100% OK, my phone is rooted and now i can enjoy !!!
ETTT said:
1. I'm glad you got it.
2. You should give thanks (that button) if I helped you.
3. I'm you dont read instructions. Maybe it's a problem with us romanian engineers, or maybe engineers in general
look at item 11. from my previous post. maybe I just c&p here.
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
So, when you are in adb shell and you go root (su command, you get the promt with #) and you have the /system mounted rw.
Then any apk that you copy to /system/app folder will get intalled and when you list your application (the button with 16 squares) you should see it.
Have fun.
Click to expand...
Click to collapse
can you release xdelta patch for your XWALH3 because we have the same device..
phyxar said:
can you release xdelta patch for your XWALH3 because we have the same device..
Click to expand...
Click to collapse
I've started a new more universal thread:
http://forum.xda-developers.com/showthread.php?t=1965600
There you have the shell-script that will patch the firmware for you.
If you still want an xdelta patch I'll make one for you but:
Give a man a fish and it will be full for the day, teach him how to fish and it will never go hungry again.
Have fun.
ETTT said:
ok here it is the modified firmware.
dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Click to expand...
Click to collapse
Hello, i'm new here and i don't know about scripting, so need your help..
i downloaded your firmware and install it to my b5330 and did the cmd command, and it worked, thanks..:good:
but now i've a new problem that my b5330 can't type a question mark ('?').. can you help me please..
whenever i want to type a question mark it always typed a comma (',') in the screen..:crying:
it also it change the symbol and language key to emoticon and symbol, but that's not a problem for me..
andhikarogue said:
Hello, i'm new here and i don't know about scripting, so need your help..
i downloaded your firmware and install it to my b5330 and did the cmd command, and it worked, thanks..:good:
but now i've a new problem that my b5330 can't type a question mark ('?').. can you help me please..
whenever i want to type a question mark it always typed a comma (',') in the screen..:crying:
it also it change the symbol and language key to emoticon and symbol, but that's not a problem for me..
Click to expand...
Click to collapse
That's because you have use the romanian firmware. whitch has a qwerty layout keyboard.
you have to do it the right way:
first. find the firmaware for your region:
http://samsung-updates.com/device/?id=GT-B5330
second. find a linux machine and run the script from the thread.
It is unrealistic for me to just upload all the 40 version of the firmware patched.
That is why I've made the script.
If you don't have a linux machine then look for a virtual box ubuntu and run on it.
Cheers.
I know I'm a noob.. But can someone please explain what the hell is happening. When I'm root, the sdcard folder is something completely different and its different when im not?
I tried taking backups of my efs with these 2 commands in adb shell
Code:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Can someone please check the attachment below and tell me... !!!!:crying:
maniyal said:
I know I'm a noob.. But can someone please explain what the hell is happening. When I'm root, the sdcard folder is something completely different and its different when im not?
I tried taking backups of my efs with these 2 commands in adb shell
Code:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Can someone please check the attachment below and tell me... !!!!:crying:
Click to expand...
Click to collapse
That's not what root is...
The directory for sdcard is /sdcard
The directory for root is /
Root/=sdcard
The sdcard directory is located inside the root directory