hi all, sorry for my bad english. i've a problem with my note 8. when i enter recovery mode there are some strange message in the white line under SUPPORT SINGLE SKU
unfortunatly i can't post an image because i'm a new users but those line are:
-E : ensure_path_unmounted failed to unmount /efs (Device or resource busy)
and
-deleting selective files remove failder dir '/system/app/IQAgent'(No such file or directory)
can someone explain what those it means or how to solve?
thanks to everyone
imSh0w said:
hi all, sorry for my bad english. i've a problem with my note 8. when i enter recovery mode there are some strange message in the white line under SUPPORT SINGLE SKU
unfortunatly i can't post an image because i'm a new users but those line are:
-E : ensure_path_unmounted failed to unmount /efs (Device or resource busy)
and
-deleting selective files remove failder dir '/system/app/IQAgent'(No such file or directory)
can someone explain what those it means or how to solve?
thanks to everyone
Click to expand...
Click to collapse
no one? :/
It's forbidden to bump your thread in less than 24 hours.
People are not just sitting here waiting to answer your questions. That, or nobody knows the answer.
Sent from my Galaxy Note8 using XDA Labs
Related
Hi,
I get through this with my eye's closed but when I have to type in the chmod line,and hit enter, it says, "unable to chmod : / Read-Only file system / I've asked this on many different forms, and researched it and tried a lot of code to fix it, none of witch worked, so now I'm just asking strait out if anyone knows how I can fix this, It's done this on 2 separate computers so It's doubtful that it's a PC problem.
Thanks for reading this and perhaps helping me, I'm about to rip my hair out, lol,
Kn0t
Wait what?
So it's rooted tab yeah and your? Terminal or abd? Into the system. So you have super user rights huh? And the system files are mounted as read/write? If you said yes to these questioned which I assume you will as it sounds like you are savvy with permissions and how android mounts its system files from the "eyes closed" part then its a new one on me, I have never heard of this problem?
Oh and what kernel you running? is it gingerbread or froyo?
Sent from my GT-P1000
Don't forget to grant superuser its permissions. Check if the app is asking for it. Perform adb with tab on, superuser will pop up.
I felt for that couple of times.
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
speldenaar said:
Don't forget to grant superuser its permissions. Check if the app is asking for it.
I felt for that couple of times.
Click to expand...
Click to collapse
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
And lastly I'm thinking this doesn't qualify to be in the development section bud .. its a little cause and general and should be in General section not Here.
Sorry but its out of control on these boards.... these threads shouldn't be in the development section unless you are developing something or are replying to a development thread about, well.... a development ... or finally, ahhhhh....ummm, bah... development... just had to say it one more time and couldn't get a third reason... I don't want to be harsh or you think I'm flaming you its just my 2 cents....
Sent from my GT-P1000
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
it's adb,, and I have super permissions, yes and it says it's a Read-only file system when I go to write my chmod. The "eye's closed" part of my post was just me being sarcastic about the amount of phones I've done this too and the amount of time I've done it with zero problems.. that's all.
Yup, I did that.. thanks a lot for the advice..!!
nobleskill said:
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
Click to expand...
Click to collapse
Yes I agree but I don't know how to fix it that way.. thanks for helping
Sorry man. It was supposed to be moved to Q and A some time ago and it just never happened. My fault, my mistake. sorry to all that this bothers, and thank you to all that are helping me out.
~k~
nobleskill said:
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
Click to expand...
Click to collapse
Thanks a lot for this advice, I tried it and got a message that says, "System permissions cannot be changed because the file system is Read-only"
Thanks again, it was worth a try.
~K~
quick question....
When do I enter that into my command prompt? right before I try to chmod or right after????
thanks a lot
~K~
mchampeli said:
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
Click to expand...
Click to collapse
I think you have to put on a new rom that does that. try http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
good luck
~K~
GldRush98 said:
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Yea I tried that and it said "system permission cannot be changed becausethe file system is Read-Only" so I don' know. But I do really appriciate you trying to help me out.
knotrkr said:
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Click to expand...
Click to collapse
Whoops, I thought the file you were chmod'ing was in the system partition.
The data partition is already mounted with read/write.
Your chmod command is incorrect... there is an extra space in there.
It should be:
chmod 755 /data/local/bin/flash_image
I don't think the data partition is mounted as read only (I could be wrong, but I didn't think it was)
Herro
By request I have (hopefully) ported the European O2X touch recovery to the SU660. I don't have one of these to test, so on your own head be it etc etc
Other ports I've done have worked (O2X => G2X, SU660 => P990), so I don't see why this shouldn't, but you know the drill.
Thanks Rusty!
Just to be sure before I dive in...are the backups made in prior CWM version (e.g. 5.0.2.7) compatible with this version?
As far as I know, yes.
But I've never tried
Hi Rusty,
Wanted to report back. I haven't got a chance to test it out myself because of my usb cable giving up its spirit and dying.
BUT, I did have some friends try it out on theirs and they are having issues. Installed fine but have "cannot mount" errors.
EDIT:
Got myself a new cable and flashed it. I also get the same errors. I cannot access the log file either. The error messages are hidden behind the recovery menu, but the lines I do see are as following:
Code:
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
When attempting advanced--report error, I get
Code:
E:unknown volume for path [/data]
Sounds like cannot mount because of wrong partition assignments. Any thoughts?
Interesting, I've had a look and I've used the right partition layout. Only other changes were default.prop (which doesn't contain any references to partitions) and the kernel (which should be interchangeable as I've used the SU660 on on P990 recovery and used a P999 one to get the touch recovery working).
Colour me confused (for now).
If i sent you the latest working cwm image file (5.0.2.8), would that help?
Sent from my LG-SU660 using xda premium
It might, it might not lol
But I can stick bits from it in the touch version and see if it makes any difference.
here's the img file. I think wkpark and others put it together for the su660 based on your earlier work.
I also noticed that the fastboot.bin that I used for my su660 may be different than what you posted before. I'm attaching that as well in case it might help too.
Thanks!
Any luck Rusty??
Sent from my LG-SU660 using xda premium
I had forgotten
Rusty! said:
I had forgotten
Click to expand...
Click to collapse
Thanks, but still no luck. Similar mounting errors as before. This time, the Advanced-Show log did manage to give an output:
Code:
event: 228 451
event: 228 451
up
failed to open /sys/class/android_usb/android0/state: No such file or directory
Does that mean anything to you?
Not a thing I'm afraid.
Well, too bad but thanks anyway. Appreciate your kind attention and help!
Sent from my LG-SU660 using xda premium
i not undersent to use it
Hello guys,
I have serious problem with my Samsung Galaxy Mini. I rooted the phone with Root_Exploit_OneClick and everything went fine. Then I installed a bad ,corrupted custom Rom and the phone was not working properly,(white screen everytime i was pressing the power button)..
With Odin if I remember well , I flashed the phone back to the original Rom.
Since then some months passed, and I wanted to try again. I tried 1000000 times to root it again with SuperOneClickv2.3.3, Root_Exploit_OneClick and other tools like this and i ALWAYS get the same message...
I also attach a picture of my error message. I dont know what to do. I dont know what is the problem. I also read somewhere in the forum, that it could be the firewall that is blocking something, disabled it,tried again,always problem...
Could you help, or do you have any idea what this is happening ?
I want very much to change my rom from cyanogenmod 2.3.6 to something newer !!!:cyclops:
Thank you very much
Error message
Trying to write qemu value to prop-file
cannot create /data/local.prop: permission denied
Rebooting
Waiting for device to reboot again
Try to remount /system
remount failed: Operation not permitted
Pushing su and Superuser.apk
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/app/Superuser.apk: No such file or directory
Cleanup of the Stuff created while running
rm failed for /data/local.prop, No such file or directory
Press any key to continue . . .
Can you just root with Stock Recovery ?
I hope this will work
I will try now and I will write again my result
I hope this will work !!!
F4uzan said:
Can you just root with Stock Recovery ?
Click to expand...
Click to collapse
I tried to find it online, but i found for other devices like HTC i didnt find something for Galaxy mini..This tool you write about roots the phone or forces a new Rom to the phone?
thanks
nefeli89 said:
I tried to find it online, but i found for other devices like HTC i didnt find something for Galaxy mini..This tool you write about roots the phone or forces a new Rom to the phone?
thanks
Click to expand...
Click to collapse
Just search "How to root samsung galaxy mini", and take the zip file, and then flash it.
Done.
try this http://dl.dropboxusercontent.com/u/45768197/Galaxy Mini Stuffs/gingerbred-2.3.6-root.zip
flash it on recovery like what @ F4uzan said
hi i try to install xposed app on my karboon A7 rooted mobile but the following message appearing on screen
system writable...segmentation fault could not mount /system writable trying to contunue anyway...segmentaion fault
failed to create backup of/system/bin/app_process
Sounds like your phone is write-protected. Have you searched for this error message?
Tried to install Xposed by recovery?
Sent from my black pearl using Tapatalk
vishiwashi said:
hi i try to install xposed app on my karboon A7 rooted mobile but the following message appearing on screen
system writable...segmentation fault could not mount /system writable trying to contunue anyway...segmentaion fault
failed to create backup of/system/bin/app_process
Click to expand...
Click to collapse
Don't you get a red warning text on the main window of the installer? Read it and follow the link it provides.
Help.
Mi3 rooted. Followed everything in This Internal memory recovery to PC Guide.
Stuck at 0 Byte file getting created.
Tried whole partition blk0 and data part p28.
Quote:
$ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p28.raw
0 B 0:00:00 [ 0 B/s] [<=>
It seems few guys already faced this error. Any workaround? Please help.
I'm thinking of try and mounting PC drive on Mi3 and check if that works. Suggestions?
Edit: Tried Win 7 Folder Share mount with cifs.ko Mount Manager etc.. Invalid argument error Totally stuck.
Bump
Someone anyone? Please reply! Is this bug in Mi3 or ? I'm able to run this method on Samsung phones.
Bro, Visit a service center, You applied more than required brain in this.
I am not sure, but actually Mi3 is sharing 2 systems by default, so this procedure might not work as usual.
Btw what exactly you are trying to do with this?
Sent from my MI 3W using XDA Free mobile app
It worked for me, so I made a thread in this forum:
http://forum.xda-developers.com/showthread.php?t=2900304
USB drivers are maybe missing on your computer. Can you access adb?