[Q] parition definitions under android 4.1.2 - Android Q&A, Help & Troubleshooting

hi
I am no no-ob when it comes to linux, however I am still learning the android and the linux kernel.
I wanted one of the developers to peek at the following evolving post..
http://forum.xda-developers.com/showpost.php?p=48748094&postcount=48
I am looking into one of the unhacked devices, and need some help into looking
how I can unlock the bootloader.
I want to understand which of the partition contains the bootloader and which contains the recovery...
Is there any guide to looking at the partitions in a hex-editor or something and determining if its a
boot, recovery etc...
G

assuming the device is rooted and got busybox installed, if from windows cmd just
Code:
adb shell
mount
or
Code:
adb shell
busybox mount
or if directly from phone terminal
Code:
mount
or
Code:
busybox mount
then it'll produce output of partition names and mountpoints.

an0nym0us_ said:
assuming the device is rooted and got busybox installed, if from windows cmd just
Code:
adb shell
mount
or
Code:
adb shell
busybox mount
or if directly from phone terminal
Code:
mount
or
Code:
busybox mount
then it'll produce output of partition names and mountpoints.
Click to expand...
Click to collapse
Here are some more points...
1. Device is "rooted" however this devices does not seem to be so much popular on XDA, so there is only one "Chinese root and SU" available for the device. There is no busybox or the conventional SU
2. I have (cross)compiled busybox for arm32 and bash4.1 for arm32 and installed it on the phone using adb
3. The bootloader on the device is still not unlocked, not is there any clear cut way of unlocking the bootloader on this device (LG E-455)
4. Here are some of the outputs...
Code:
$ ./adb shell /system/xbin/busybox
BusyBox v1.21.1 (2013-12-29 07:49:16 EST) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2012.
Licensed under GPLv2. See source distribution for detailed
copyright notices.
$ ./adb shell /system/xbin/busybox mount -v
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
[email protected] on /system type ext4 (rw,relatime,noauto_da_alloc,commit=1,data=ordered)
[email protected] on /data type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=1000,errors=continue,data=ordered)
[email protected] on /cache type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
[email protected]_lg on /persist-lg type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /persist type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /mpt type ext4 (rw,nosuid,nodev,relatime,data=ordered)
/[email protected]_ro on /system/secro type ext4 (ro,relatime,data=ordered)
/dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
$ ./adb shell /system/xbin/busybox cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 0000f400 00002800 "sec_ro"
emmc_p3: 00014800 00004000 "persist_lg"
emmc_p4: 00018800 00003000 "persist"
emmc_p5: 0001b800 0000b000 "mpt"
emmc_p6: 0002b800 00005000 "swap"
emmc_p7: 00031000 0021d800 "android"
emmc_p8: 0024f000 0009a800 "cache"
emmc_p9: 002ea000 00443000 "usrdata"
emmc_p10: 0072d800 00005800 "fat"
G

Also...
I dont know the right forum to ask these android hacking questions..
The "Android Development*" forums which typically have a lot of developer presence seem to be for
the Solutions from Android Development, rather than Questions and HowTO natively hack.
The Q/A forums don't seem to have a lot of developer presence...so questions dont get answered, as most of the
Q/A viewers are no-obs or newbies.. .
G

Related

Restore efs with root explorer read only error

I instaled root explorer and am trying to replace efs files from backup but i have a problem as can not mount ir as RW it is RO
Is there any way around that?
it looks like only efs folder have this problem
Is your phone rooted?
yes i just checked again if i rooted it and i did
$ cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp: can't create '/efs/nv_data.bin': File exists
$ rm /efs/nv_data.bin
rm /efs/nv_data.bin
rm: remove '/efs/nv_data.bin'? y
y
rm: can't remove '/efs/nv_data.bin': Read-only file system
any help???
i can not get efs to be rw
mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/usb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /app-cache type tmpfs (rw,relatime,size=7168k)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data
=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (ro,relatime,barrier=1,data=ordered)
nil on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data
=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/dev/block/vold/179:11 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,
noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
#
Did you try to remount /efs in rw (instead of ro) ?
Yes and it remounts it instead of ext4 in ext3 i can delete and edit what i want no permission errors but once i leave hex editor it gets back to ro and all files I deletes reaiires and files i have changed show as unchanged and it gets RO. I feel that i am missinf some linux command to made this changes succesfull.
same problem my efs is read only and i would like to restore my efs, please help
mahatma said:
I instaled root explorer and am trying to replace efs files from backup but i have a problem as can not mount ir as RW it is RO
Is there any way around that?
it looks like only efs folder have this problem
Click to expand...
Click to collapse
Didnt try the app but have a look http://forum.xda-developers.com/showpost.php?p=16512129&postcount=73
Sent from my GT-I9100 using Tapatalk

[Q] G Tablet not seeing micro SD after root?

I've recently rooted my G Tablet and installed CM 7 rc1 and I'm running into a weird issue. If I plug my G tab into a computer the computer will make the connection noise, say it's installing drivers and say all is good. Problem is that the G tab doesn't see that it's connected and I neither does my computer. Other issue is with the microSD. The G tablet doesn't see it. I know the card is good my testing it in other devices. Recovery doesn't see it either. All I can access is the internal memory. Also on an interesting note. If I use recovery to turn on mass storage the computer see it then and I can move files.
I promise I dug trying ti find this so if a thread already exists point me there and I'll be on my way. Other wise thanks for the help.
chip17 said:
If I plug my G tab into a computer the computer will make the connection noise, say it's installing drivers and say all is good. Problem is that the G tab doesn't see that it's connected and I neither does my computer.
Click to expand...
Click to collapse
Try playing with the "USB debugging" and "USB debugging notify" settings in Settings > Applications > Development.
Other issue is with the microSD. The G tablet doesn't see it.
Click to expand...
Click to collapse
Plug your microSD in, then open a Terminal Emulator window and get me a dmesg output. Use the commands in this post.
Also include the output of the mount command. Again, in a Terminal window:
Code:
$ [B]mount | tee /mnt/sdcard/mount.txt[/B]
Only type in the commands in bold. The rest of the stuff is just there to show you how the screen will generally look.
Here's the second command return....
As you can see I tried the first one no return. Will try again see if I had a syntax error.
$ export PATH=/data/local/bin:$PATH
$su
#dmesg >/mnt/sdcard/dmesg.txt
# logcat -d -v time >/mnt/sdcard/logcat.txt
# mount | tee /mnt/sdcard/mount.txt
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mmcblk3p2 on /data type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:25 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:25 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/vold/179:17 on /mnt/emmc type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-0 on /mnt/asec/com.androirc-1 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
chip17 said:
Here's the second command return....
As you can see I tried the first one no return. Will try again see if I had a syntax error.
Click to expand...
Click to collapse
There is no syntax error. You executed the commands correctly. The output was redirected to files in /mnt/sdcard. Post those 3 *.txt files here.
chip17 said:
Other issue is with the microSD. The G tablet doesn't see it. I know the card is good my testing it in other devices. Recovery doesn't see it either. All I can access is the internal memory.
Click to expand...
Click to collapse
Actually, as the mount command output shows, both the internal SD card and the external one are recognized by the gTablet. The internal one is mounted at /mnt/sdcard and the external one at /mnt/emmc--which, BTW, is the exact opposite of the standard arrangement. Did you fiddle with the vold.fstab file to arrange it like it that or did you use the official method (Settings > CyanogenMod Settings > Tablet tweaks > switch Internal sdcard?
BTW, did you try my recommendations?:
rajeevvp said:
Try playing with the "USB debugging" and "USB debugging notify" settings in Settings > Applications > Development.
Click to expand...
Click to collapse

I need help from someone who has a WORKING rooted device.

Hey guys. I am working on a total recovery method for this device to assist you guys in making a Hard Bricked device work properly. I need to create a stock firmware package. I've been working my ass off trying to make this a reality.. I've downloaded 10 firmware packages with no success. So, now the only option left is to rebuild from a working device.
Currently we are missing the following partitions:
RECOVERY
DATAFS
USERFS
GANG
So, in this thread I'm asking for community help. I'll post the task and anyone can execute the commands:
1. use a terminal emulator on your phone and execute 'su' and 'mount'
2. copy-paste from the terminal emulator into the forums so we can locate the proper devices per partition
3. execute some commands to dump some partitions which will be determined by step 2
4. post the dumped partitions here.
Anyone can participate in any of these steps... Lets do this quickly!
Task1:
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copypasta the results of the mount command here.
Hello, I appreciate your work! Will this be able to fix a brick no matter how screwed it is?
The reason I ask is because I believe I have messed up something concerning the pit file.
I was about to send it into samsung to repair, but if this could fix it...
iJimaniac said:
Hello, I appreciate your work! Will this be able to fix a brick no matter how screwed it is?
The reason I ask is because I believe I have messed up something concerning the pit file.
I was about to send it into samsung to repair, but if this could fix it...
Click to expand...
Click to collapse
I need this information to develop a total recovery solution.
I'm breaking this down really simple. Please don't clutter this thread. I probly should have posted in development
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copy and paste the results of the mount command here.
Hope this helps
Also would you be able to create a rom for this device say ICS ?
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
AdamOutler said:
Hey guys. I am working on a total recovery method for this device to assist you guys in making a Hard Bricked device work properly. I need to create a stock firmware package. I've been working my ass off trying to make this a reality.. I've downloaded 10 firmware packages with no success. So, now the only option left is to rebuild from a working device.
Currently we are missing the following partitions:
RECOVERY
DATAFS
USERFS
GANG
So, in this thread I'm asking for community help. I'll post the task and anyone can execute the commands:
1. use a terminal emulator on your phone and execute 'su' and 'mount'
2. copy-paste from the terminal emulator into the forums so we can locate the proper devices per partition
3. execute some commands to dump some partitions which will be determined by step 2
4. post the dumped partitions here.
Anyone can participate in any of these steps... Lets do this quickly!
Task1:
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copypasta the results of the mount command here.
Click to expand...
Click to collapse
I can make this for you but do you need a US or EU version. Because I have a EU version. And for recovery it's recovery.bin? or .img?
---------- Post added at 01:16 PM ---------- Previous post was at 12:27 PM ----------
Here my mount command. Hope this helps.
Code:
$ su
su
# mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type rfs (ro,relatime,vfat,log_off,check=no,gid/uid/r
wx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid
/uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p2 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no
,gid/uid/rwx,iocharset=utf8)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,
gid/uid/rwx,iocharset=utf8)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,n
oatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codep
age=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,no
dev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utim
e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
)
/dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe
xec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,
codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k
,mode=000)
alright. Now task 2,3 and 4.. Anyone can do this.
I need a copy of working partitions from a device. You must trust me that I will perform a master clear. I will not post your personal partitions. I need a template to work with in order to get this device working.
2: execute the following code on your device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere and send me a PM. If you would like, I have a private FTP site at ftp://adamoutler.com and I will give you a login/password to log into my personal network attached storage and upload the zip file containing the partitions.
zaclimon said:
I can make this for you but do you need a US or EU version. Because I have a EU version. And for recovery it's recovery.bin? or .img?
Click to expand...
Click to collapse
It does not matter.. US, EU.. They're all fine. I think I can make a recovery.bin.
Rueben_ said:
Hope this helps
Also would you be able to create a rom for this device say ICS ?
Click to expand...
Click to collapse
That's possible. I don't own a device to work with, but a total recovery solution comes before any development. You have to have a way to get back to stock.
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
AdamOutler said:
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
Click to expand...
Click to collapse
I can't help you with this. I have an error which is said there is no such files or directory.
zaclimon said:
I can't help you with this. I have an error which is said there is no such files or directory.
Click to expand...
Click to collapse
You may have typed it wrong. Please try again.
Another method for those of you with Linux or any type of SSH terminal like the windows tool puTTY, is to use an app like SSHDroid then terminal in to your device and copy-paste the code block in.
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
I have the same error coming up ? :/
Error: cannot open for write: No such file or directory
Rueben_ said:
I have the same error coming up ? :/
Error: cannot open for write: No such file or directory
Click to expand...
Click to collapse
Do you have an SDCard in your device?
try the same lines with /sdcard instead of /mnt/sdcard.
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs
AdamOutler said:
Do you have an SDCard in your device?
try the same lines with /sdcard instead of /mnt/sdcard.
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs
Click to expand...
Click to collapse
It's not working either. I think the player don't have these blocks.
zaclimon said:
It's not working either. I think the player don't have these blocks.
Click to expand...
Click to collapse
The player has these blocks, you can't write them to the sdcard. it says can't write.
Code:
Error: cannot open for write: No such file or directory
what is the sdcard called on the filesystem?
try changing the blocksize... i belive it was 512 on this device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs bs=512
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs bs=512
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs bs=512
I can get these files directly from your device if you want to add me on google talk.. we need to get market app wireless adb installed and put your device into the DMZ on your router. *myusername* @gmail.com
AdamOutler said:
try changing the blocksize... i belive it was 512 on this device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs bs=512
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs bs=512
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs bs=512
Click to expand...
Click to collapse
I checked my mount and used the stl block instead of mmcblk0p block. Is this matter? What is DMZ? I think data will take a little more time.
Ok I have my files. What do I do now?
EDIT: My blocks and Rueben_'s are different. That's why it don't work with me.
zaclimon said:
I checked my mount and used the stl block instead of mmcblk0p block. Is this matter? What is DMZ? I think data will take a little more time.
Click to expand...
Click to collapse
DMZ on a router is where you unrestrict the IP address of a device on your network. Everything is directed to that IP. Othewise I need ports 22 and 5555 directed to the IP address of your device running adbwireless.
AdamOutler said:
DMZ on a router is where you unrestrict the IP address of a device on your network. Everything is directed to that IP. Othewise I need ports 22 and 5555 directed to the IP address of your device running adbwireless.
Click to expand...
Click to collapse
It seems difficult to configure it on my router. It would be easier to upload it no?
zaclimon said:
It seems difficult to configure it on my router. It would be easier to upload it no?
Click to expand...
Click to collapse
PM sent with my information, login and password.
I hope this works, just in case, can you ALSO get the BML blocks for this?

Online Android Backup **DO BACKUP WHILE YOUR PHONE STILL ON**

ANNOUNCEMENT:
Official version that support most (including our) device has been released. See HERE
Hi All.
Here are the modified version of Online Android Backup from ORIGINAL THREAD. I've changed some codes to make it works for our HTC Legend.
How To Install:
Through CWM
1. Download from attachment onandroidv3.7_cwm.zip
2. Copy it to your sdcard
3. Reboot into recovery
4. Flash the file
Manual
1. Extract onandroid.zip attached and use adb/root explorer to push/copy the file onandroid to your /system/bin
2. change permission to rwxr-xr-x
How To use:
From PC:
1. Open terminal/command prompt
2. type adb shell
- if using CM9, type su to gain root access after step 2.
3. type onandroid
From your phone:
1. open terminal emulator, type su
2. type onandroid
UPDATE:
If you use ogo2's ROM HERE, please download SENSE_fix_tool.zip from attachment and flash it. Mediafire link are HERE
Changes:
12.06.2012: Initial modification from original version
13.06.2012: Power checking corrected
14.06.2012: Added CWM flashable file
20.06.2012: Update v3.7 from original developer. confirm to work in cm9
Changelogs from original developer:
:: Latest onandroid fixes from v3.7
:: Made "dd" not spit results.
:: Added partition detection for boot and recovery partitions.
02.07.2012: Fix for sense ROM
screenshots and file are attached.
Credits:
ameer1234567890 Original Developer
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
vriz27 said:
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
Click to expand...
Click to collapse
Yes, download the file from attachment (onandroid_CWM.zip)
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
smithchipz said:
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
Click to expand...
Click to collapse
Thanks. I just do some simple modification to the original version, praise to ameer1234567890 for the great tools.
Restoring is working fine with me but make sure you check the backup folder after onandroid is finish running and check if all required files is there especially if you do something else during the backup process.
Fix for sense ROM attached in 1st post.
feed3 said:
Fix for sense ROM attached in 1st post.
Click to expand...
Click to collapse
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
alligator_asl said:
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
Click to expand...
Click to collapse
That is due to an issue in XDA (one of the servers crashed). Should be fixed in a couple of days!
Sense fix
Sense fix tool uploaded to mediafire. Link in the post #1.
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Click to expand...
Click to collapse
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
ameer1234567890 said:
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
Click to expand...
Click to collapse
Here is it:
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /mnt/asec/sd ext3 rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/nadsoft.physicscheatsheetsfree-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/jwtc.android.chess-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
How did you partition your sdcard? Which app2sd or link2sd version do you use?
Also, post output from below command!
Code:
echo $SD_EXT_DIREECTORY
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
alligator_asl said:
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
Click to expand...
Click to collapse
Thank you for the information. I am working on a fix.
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
Click to expand...
Click to collapse
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
feed3 said:
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
Click to expand...
Click to collapse
I have fixed this in the next version. Shall be releasing soon.
ameer1234567890 said:
I have fixed this in the next version. Shall be releasing soon.
Click to expand...
Click to collapse
Thanks ameer..

HOSTs file nightmare! Please help

Can anyone help with this...
The phone is called the n7103, It's a chinese phone and the specs can be found here: https://my.dx.com/MyOrders/OrderDetail/130421001070495638
Root: Yes
Version: 4.1
Carrier: Three (UK)
My hosts files are wrong, so I can't connect to the play store and use some apps, my hosts file currently read:
127.0.0.1 localhost
#74.125.93.113 android.clients.google.com
#74.125.93.113 mtalk.google.com
Click to expand...
Click to collapse
I presume this is correct, if not please do correct me.
Now I want to use ADB to send the to the phone, however I can't for the life of me make the system read/write, The reason being I dont know what to mount, so I found the following instructions:
Very often when you want to write files to a particular partition on ADP1, you will get a "Permission Denied" if the partition is mounted read-only.
To get around this, you need to mount the partition read-write. Typically this is done with /system partition
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts)
Click to expand...
Click to collapse
I have looked in the /proc/mounts file and get the following read out:
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected]_ro /system/secro ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:96 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:6 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:6 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
So basically I get stuck at this part as I don't know what to type:
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 .........
I have looked for other methods including using totalcommander with root to edit hosts file but to no avail.
I can't push the file as the destination is not read write. I have also tried using terminal and chmoding the system folder as 777 but no joy.
There is also an app called "HOSTS EDITOR" however it wont allow me to insert the "#" character.
I am sorry for the very long post, I'd appreciate any help!
Thanks :good:
mount -o remount, rw /system
Click to expand...
Click to collapse
This returns no errors however when i then try the follwing command it fails.
[email protected]:/ # adb push hosts /etc/hosts
adb push hosts /etc/hosts
error: device not found
Click to expand...
Click to collapse
This phone was gently placed in a bin.
Sent from my GT-I9505 using XDA Premium 4 mobile app
adb is a program in your PC, not in Android itself, so this command:
philipkroberts said:
adb push hosts /etc/hosts
Click to expand...
Click to collapse
should be typed outside of the Android shell (type exit after you remount system, then try that command again).

Categories

Resources