I Updated my HTC EVO DESIGN 4G acidently. now the super user had denied any root access request! those any boddy now how can i fix this problem now?
thanks
Manuel
did you try to root it again?
yeah but i get this
Loading root script......
pushing BusyBox...
changing permissions...
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system
Pushing su...
changing permissions...
Unable to chmod /system/bin/su: Read-only file system
Unable to chmod /system/bin/su: Read-only file system
rm failed for /system/xbin/su, Read-only file system
when i had problems with my lg optimus 2x after new updates i tried this "Unlook Root". You need to find it in google because I don't have rights to post links here))))
This tool helped me.
Hi just tryit but no luck i get this
failed to get shell root
thanks
Can anyboddy help me please
I'm having this same issue, none of the usual methods have been working.
try running:
adb remount
and then your root script.
what it does is it remounts the system partition r/w instead of read-only, so you can chmod and such
Related
Hi, any help with this one? I get as far as being able to push su and busy box but get "failed, read file system only" or "directory doesn't exist" Thanks in advance!
model PMID700
Android version 2.3.1
kernel version 2.6.32.27
build number 20110918.170336
Firmware version 2.2
I also have this tablet. The issue is the file system is cramfs which is read only so we can't move files to any /system folder. This is where every current one click root tool is failing.
On the positive side it appears we have shell root.
This is the output from doomlord's v3 root script:
Code:
...
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed File exists
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
ALL DONE!!!
Is there anyone out there that has converted a cramfs image to ext3 (or possibly something else, not sure what this supports yet)?
i got cat /proc/mounts to work in terminal emulator once and i did notice some others partitions were marked ext3 so hopefully a conversion would be possible i just don't know how and i cant seem to get the mounts again
*edit* cat /proc/mounts works in terminal emulator everytime
attached the important part of the output
Cool that's the same thing I'm seeing.
Code:
/dev/block/mtdblock4 /system cramfs ro,relatime 0 0
/dev/block/mtdblock7 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mtdblock6 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
I suppose its a little ambitious for me to try to go directly to ext3 so what i think i will try to do is to try to download the system image from the phone and then modify it with the proper files (from doomlord's oneclick v3) so it can be rooted.
I will update this thread with my progress.
Returned it...I'm all for tinkering, but not willing to go that deep good luck!
Need Help pls on hwo to root atrix 2
Dear Friend pls help me
when im trying to root my atrix 2 i getting this below but when im checking in root checcker its not rooted.
pls help if im missing anything,
[*] Installing Root Packages ...
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/bin/busybox': Read-only file system
Unable to chmod /system/bin/busybox: No such file or directory
/system/bin/busybox: not found
2732 KB/s (785801 bytes in 0.280s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
cannot create /data/local.prop: permission denied
[*] Rebooting...
* daemon not running. starting it now *
* daemon started successfully *
[*] Your Phone is Rooted !
[*] Press any key to exit.
Press any key to continue . . .
Try running server as adb root after that do adb remount and your good to go :thumbup:
Sent from my Xperia Live with Walkman using xda app-developers app
Hi Friend,
thanks for your reply, could you pls advise what i have to do here sorry im new
Sorry brother I don't know this tablet I'm a Xperia user
Sent from my Xperia Live with Walkman using xda app-developers app
its not tablet im using atrix 2 bro....
Is there any way to temporary root EVO GSM ics hboot 1.53 ?
Don't know about temp. ..... But this will help you root http://forum.xda-developers.com/showthread.php?t=1787426
invince2 said:
Don't know about temp. ..... But this will help you root http://forum.xda-developers.com/showthread.php?t=1787426
Click to expand...
Click to collapse
Tnx for rply.
I know for that tut but dont whana lose my warranty.
bump, i'd like to temp root to backup apps/data before unlocking... is this possible?
ls3c6 said:
bump, i'd like to temp root to backup apps/data before unlocking... is this possible?
Click to expand...
Click to collapse
I will try this one, as it says - it should create temp root for locked bootloader devices:
http://forum.xda-developers.com/showthread.php?t=1340255
doesn't work:
[-] Not a 2.2/2.3 Android ...
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3478 KB/s (1075144 bytes in 0.301s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
ls3c6 said:
doesn't work:
[-] Not a 2.2/2.3 Android ...
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3478 KB/s (1075144 bytes in 0.301s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Click to expand...
Click to collapse
read through that thread, there was discussion on some errors people gets, maybe will find solution there
Hi! I am trying to root my xperia mini st15i with doomlord rootting kit but i constantly get this message in the end of this procedure...Please help me!
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
Hi!
Question related to Samsng Galaxy Mini S5570.
After been using link2sd without problem, I restore the phone for cleaning propurse and I had the bad idea of update the fimware with Kies, It stop at 80% and after two hours, desesperate I disconnect the cable. Good point of that I could do an emergency recovery with Kies.
The problem now is when I try to root, I get this error log with 'Easy rooting toolkit' (and many others):
Note: I have tried also with the same Universal Gingerbread that worked with other Mini 2.3.6 like a charm.
Code:
--- DEVICE FOUND
--- pushing busybox
1590 KB/s (1075144 bytes in 0.660s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
I found a thread with a good rooting solution, http://forum.xda-developers.com/showthread.php?t=1869493
but related to Samsung Galaxy S II.
Do you know any way to resolve this?
Thanks for help!
Hello Guys!
This is my first post on the forum, I will try to make myself as clear as possible. I have got a LG Optimus L5 (known as Swift L5), which I am trying to root. But there is a problem. I have been doing a bit of research, and I have found out that the Optiums L series are read only (the internal storage). And because they are read-only, I cant push the files onto the device, in other words I cant root the device! This is really freaking me out a bit. I hope You guys can help me solve my problem. Best regards
Please help guys
Again the problem was not looking for specific device forum.
However, here's your answer
http://forum.xda-developers.com/showthread.php?t=2098550
Hi!
Thanks for replying to my thread. I have already followed that tutorial, and all I get is a message: failed to copy blablabla device is read-only.
petergood said:
Hi!
Thanks for replying to my thread. I have already followed that tutorial, and all I get is a message: failed to copy blablabla device is read-only.
Click to expand...
Click to collapse
Ok. I read the tutorial and there is no file to be pushed in /system partition. What are you basically trying to do?
Sent from my GT-S5830i using xda app-developers app
Well, basicly I wan`t to root my phone
petergood said:
Well, basicly I wan`t to root my phone
Click to expand...
Click to collapse
You aren't understanding me. I didn't see ANYTHING in guide that was to be pushed in any partition that returns with read only error.
I was asking that what you were trying to push when you got that error. I know that you're trying to root. Tell me what I need to know to solve your problem
I suggest you to read the guide again thoroughly and then tell me WHERE you are getting error.
I get the error, when I start root.bat:
Code:
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: can't create /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
/system/bin/sh: busybox: not found
/system/bin/sh: busybox: not found
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
You will notice, that I get Read-only file system and permission denied errors, as well as No such file or directory. Does that mean, that my rooting package is corrupt?
petergood said:
I get the error, when I start root.bat:
Code:
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: can't create /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
/system/bin/sh: busybox: not found
/system/bin/sh: busybox: not found
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
You will notice, that I get Read-only file system and permission denied errors, as well as No such file or directory. Does that mean, that my rooting package is corrupt?
Click to expand...
Click to collapse
My best bet would be to post in the thread I gave you. They know more than me about your device
Sent from my GT-S5830i using xda app-developers app