[Q] Using parted to fix corrupted partitions - Barnes & Noble Nook Tablet

I'm trying to work past an issue so that I can use Adam's Ubuntu total wipe/restore. Right now it stalls on the first step of writing zeros to MLO. In this post Celtic was able to get past it using parted but I'm having trouble using the tool. When I run it in an ADB shell it tells me "Device not found" or something similar...Any suggestions?
Facts:
1) ADB is working fine. I can get a shell and browse the NT.
2) I'm unable to mount any partitions except these:
rootfs on / type rootfs (rw)
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)
/dev/block/mmcblk1p1 on /sdcard type vfat

Thanks to Celtic, I've got this licked. It's running Adam's awesome Ubuntu recovery as I type
If anyone has trouble with this, do the following.
1) Copy parted out of snowball-mod\snowball-mod\nook-update-package.zip\nook-update-package\system-x\bin. Put it in a folder with ADB.
2) 'adb push parted /'
3) 'adb shell'
4) 'parted /dev/block/mmcblk0 print'
5) answer yes, fix, fix.

Moved To Q&A​
Please post all questions in the Q&A section​

thanks I will link this how-to to my FAQ
Sent from XDA premium using my Nook Tablet

Related

[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?

[Q]can't paste files on some partition like /data , /system and /ext_sdcard

this is weird , i try to copy some files from my internal SDcard to the external Sdcard by using Root Explorer
it keep says "the paste operation failed. it may be that there was not enough free space on the target file system "
but serious , i have 20 GB left in my external Sdcard ... and the file was only 8 MB ..
weird thing is that it happens sometime and sometimes it doesn't happen.
sometimes on /data partition , sometimes /system , like i try to replace boot animation or such .
i tried few ROMs all happens on me as well.
i tried to creat a empty text files .txt , and write something in it and it can be saved. so it just get me confused what's going on :crying:
Using any scripts?
Permissions correct?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
you should remove some apps from system folder because there is a limited space for apps in this folder
you can check it :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alfares43 said:
you should remove some apps from system folder because there is a limited space for apps in this folder
Click to expand...
Click to collapse
...and /data? /extSdCard?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
...and /data? /extSdCard?
Click to expand...
Click to collapse
I faced the same problem before in system folder
and solved it by removing some apps
i have no idea what to do for the other folders .. :silly:
Do you get the same issue if you try doing it with terminal emulator or adb? I wonder if it is some setting on root explorer that maybe limits file size or something. If you use another file explorer program do you have the same problem?
rootSU said:
Using any scripts?
Permissions correct?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Sdcard doesn't have permissions ...
alfares43 said:
you should remove some apps from system folder because there is a limited space for apps in this folder
you can check it :
Click to expand...
Click to collapse
1.5 GB left in system and 5 GB in data.. so no really the case ...
wangdaning said:
Do you get the same issue if you try doing it with terminal emulator or adb? I wonder if it is some setting on root explorer that maybe limits file size or something. If you use another file explorer program do you have the same problem?
Click to expand...
Click to collapse
I didn't try ADB, but when I failed to move around the internal and external sdcard, I can manually copy it into PC and then paste it back in...
In other words, I can access (delete, paste or such) from my PC but can't do it with Root Explorer
Sent from my GT-I9300 using xda premium
qtwrk said:
Sdcard doesn't have permissions ...
Click to expand...
Click to collapse
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
rootSU said:
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
Click to expand...
Click to collapse
This was why I say no permission...
I more think about media scan? But seems highly unlikely.
If it is not mounted or permission error ... then why I was able to create empty text files and write save it? this operation does write on it, doesn't it?
Sent from my GT-I9300 using xda premium
Try other root explorers then....
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Of course it does!, if it didn't have permissions, you wouldn't be able to use it! It is mounted with permissions. Linux basic knowledge EVERYTHING has permissions.
Hence my question "Using any scripts?"!
Since you skipped that question, I am going to assume no.
But FYI, no space errors are 1 of 2 things.
1) No space
2) Wrong permissions
So something for you to think about....
You should check output of terminal command "mount" next time you have this error
Click to expand...
Click to collapse
Code:
[email protected]:/ $ mount
rootfs on / type rootfs (ro,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,nodiratime)
proc on /proc type proc (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
sysfs on /sys type sysfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=600)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpu)
tmpfs on /storage type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
none on /acct type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=775,gid=1000)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p9 on /system type ext4 (ro,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,commit=100,barrier=1,data=ordered,noauto_da_alloc,discard)
tmpfs on /system/lib/modules type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,barrier=1,journal_async_commit,data=writeback,noauto_da_alloc,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=777,gid=1000)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ $
I can't read this... m a little help please?
Sent from my GT-I9300 using xda premium
qtwrk said:
Code:
[email protected]:/ $ mount
rootfs on / type rootfs (ro,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,nodiratime)
proc on /proc type proc (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
sysfs on /sys type sysfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=600)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpu)
tmpfs on /storage type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=050,gid=1028)
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
none on /acct type cgroup (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=775,gid=1000)
/dev/block/mmcblk0p3 on /efs type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p9 on /system type ext4 (ro,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,commit=100,barrier=1,data=ordered,noauto_da_alloc,discard)
tmpfs on /system/lib/modules type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,barrier=1,journal_async_commit,data=writeback,noauto_da_alloc,discard)
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,mode=777,gid=1000)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ $
I can't read this... m a little help please?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
This is the line you want:
Code:
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Which is normal for an AOSP ROM.
A touchwiz ROM would look like....
Code:
vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Anyway, you ruled something out there (if you ran this when you got the error)
rootSU said:
This is the line you want:
Code:
/dev/block/vold/179:49 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,noauto_da_alloc,commit=100,nobh,barrier=0,discard,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Which is normal for an AOSP ROM.
A touchwiz ROM would look like....
Code:
vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Anyway, you ruled something out there (if you ran this when you got the error)
Click to expand...
Click to collapse
Yeah... last time it shows error at beginning, and after I reboot it once and now it says error after the paste is completed, with refresh I can see the file in place and md5 checks identical.
That was the line when I got error...
I'm gonna try other files manager...
Sent from my GT-I9300 using xda premium
qtwrk said:
Yeah... last time it shows error at beginning, and after I reboot it once and now it says error after the paste is completed, with refresh I can see the file in place and md5 checks identical.
That was the line when I got error...
I'm gonna try other files manager...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
es file explorer> menu> root explorer on> grant.... then again menu> click root explorer> mount r/w and enable write permissions and you can copy/cut/paste data anywhere. this is what i always do.
:good:

[Q] parition definitions under android 4.1.2

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

mount: can't find /system in /proc/mounts

Good day,
The situation at hand:
- Samsung SM-G900F
- CM 14.1 (or what ever the last official CM Build was)
- rooted ("#" in ABD SHELL is shown)
- non-functional display (no input it seems and black. glorious spider-app)
- phone is booting normally (TWRP recovery + download mode included)
- ADB only works in recovery
So, as the phone is still working fine (apart from keeping everything for itself) I'd figure I could use programs like "MyPhoneExplorer", DDMS, or anything to use it while I'm waiting to get a new one.
Only thing that keeps me from doing so - my phone is on "charging mode" when plugged in USB and normally booted.
In order to activate the "usb debugging" (and set it as default) I tried to pull the "build.props" from /system - however, ADB keeps telling that folder doesn't exist.
I thought at first, there'd be an problem with RO/RW settings but when trying to remount /system I'm getting this:
Code:
~ # ←[6nmount -o w,remount /system
mount -o w,remount /system
mount: can't find /system in /proc/mounts
When checking with ADBFileExplorer, the folder "system" is there but completely empty.
Running #mount results in
Code:
~ # ←[6nmount
mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p26 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p26 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p24 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
I assume (or rather: I fear), I'd have to enable "system" for mounting in the TWRP screen to be able to temper with my build.prop.
Maybe someone can shed a light and show me, what I got to do to access /system and build.prop?
(Apart from getting a new display.)
Greetings
I believe you need to call "/sys" instead of "/system" so it can be found in /proc/mounts where the mount requirement are stored
Pan0ptics said:
I believe you need to call "/sys" instead of "/system" so it can be found in /proc/mounts where the mount requirement are stored
Click to expand...
Click to collapse
help!
my audio daemon services are not running in latest nitrogen pie rom.it was running before on other pie rom on redmi 3s
some bug reports generated .
i did all possible simple solution like factory reset or complete clean flash of stock rom or tried other older rom like rr oreo rom but no luck .
and i mounted system partition as rw it resets to ro after every reboot.
maybe strace is not running properly it is mentioned in bug report

Categories

Resources