Hi
I have problem with using AdAway on my Z3TC.
I have successfully rooted my device. Now I'm on stock KK with root and locked back BL.
I installed AdAway but it doesn't want to work. There is problem with hosts file.
I found that I have to change permissions for /system to -rw-rw-rw and for file host too. But the problem is I can't. When I'm trying to change permissions I got info: Changing permissions was not successful. And it doesn't matter what Explorer I use.
Any ideas? Of course there is root permission for explorer... May the locked Bootloader be the problem (I doubt...)
To write in system you have to install from the recovery ricdefeat
https://github.com/dosomder/SonyRICDefeat/blob/master/RICDefeat.zip
I didn't installed TWRP after relocking BL.
I tried now and there is another problem (looks similar)
Code:
##########################################################
#
# Installing XZDR version 2.8.3 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': Read-only file system
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: No such file or directory
chmod: /system/.XZDualRecovery/busybox: No such file or directory
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event3!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
ADB asked for root permission during installation, I agreed.
And after all recovery is not installed...
I see where the problem is. You can not write in system because you need ricdefeat, but to install XZDualRecovery and flash from there ricdefeat need to write in "system"
I'm afraid you have to start over. Is necessary Flash Ricdefeat from the TWRP recovery before it is erased.
Read here (where it says "To install rooted Stock"):
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534 (relatively speaking there nicely explains the steps to take and what order , replace firmware sgp621 -> sgp611)
or my tutorial in Spanish I did not know if you know the language:
http://www.htcmania.com/showthread.php?t=966040 (Part B)
---
I will try to explain what I would do, I'm using google translator if not understood:
1- unlock bootloader
2- install advanced stock kernel
3- Now there are two options:
** 3A) Create pre-rooted firmware. Copy firmware pre-rooted and ricdefeat.zip on the tablet. Login to TWRP and flash firmware then ricdefeat, and restart at the end.
** 3B) Copy to tablet the ricdefeat file. Go to TWRP recovery, flash ricdefeat and restart. With flashtool , install on the tablet only the kernel, using the original firmware.
4- Start android and restore TA
5- Install XYDualRecovery to have a custom recovery
Related
ORIGINAL THREAD AND CREATOR IS DOOMLORD
http://forum.xda-developers.com/showthread.php?t=1320350
[ Info ]
(WINDOWS ONLY)
WILL WORK ON BOTH LOCKED & UNLOCKED BOOTLOADER DEVICES!
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
[ Credits ]
Credits go to all those involved in making this possible!
zergRush Binary from: http://forum.xda-developers.com/showthread.php?t=1296916
Inspired from: http://forum.xda-developers.com/showthread.php?t=1312859
[ Donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc http://forum.xda-developers.com/donatetome.php?u=2784807
DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
DooMLoRD_v1_ROOT-zergRush-busybox-su.zip
[ UnRooting ]
want to unroot? Read this
Im just sharing
can android vrsion 2.3.4
4.0.2.a.0.42 root using this method?
mrfarhatadib89 said:
can android vrsion 2.3.4
4.0.2.a.0.42 root using this method?
Click to expand...
Click to collapse
Yes.
Sent from my MT15i using Tapatalk
unfortunately root not working on the new 4.0.2.a.0.62
which phone?
my device is xperia neo ... also arc, play, and other phones have received the update
unfortunately the only way to root after updateing to 4.0.2.a.0.62 is to flash the 4.0.2.a.0.42 Kernal with flashtool, Im pretty sure you don't need unlocked bootloader to flash original SE Kernals... so just flash the old Kernal and you should be able to root again..
Otherwise if its not too late for other users I would just stay away from the new update until there is an easy rooting method, the update doesn't offer any real advantages.. AFAIK only a few minor bug fixes.
Have a great Christmas!
Kiwi
Update seems to be out for Middle East and Africa only atm
Croatia (Europe) still have .42 we dont have new updates.
And yes, new version still not rootable
xperia active
yesterday i rooted the xperia active of my wife (0.42).
i have a question: if sony will upgrade the phone (maybe 0.62) or later this year
to ics, i will lose the root access?
fire-warrior said:
unfortunately root not working on the new 4.0.2.a.0.62
Click to expand...
Click to collapse
just flash RootXperia.zip, works always....
Marcell96 said:
just flash RootXperia.zip, works always....
Click to expand...
Click to collapse
hi
i have same problem
how can use it?
Just download the RootXperia.zip file to your sd card,
boot into recovery and install the zip file...
easy way to boot into recovery (Bootloader needs to be unlocked)
Works great......
Sent from my MT11i using Tapatalk
Root toolkit is v4 now.
Unable to root using the above method ... this is the issue i am facing ...
busybox: /system/xbin/tr: Read-only file system
busybox: /system/xbin/traceroute: Read-only file system
busybox: /system/xbin/traceroute6: Read-only file system
busybox: /system/xbin/true: Read-only file system
busybox: /system/xbin/tty: Read-only file system
busybox: /system/xbin/ttysize: Read-only file system
busybox: /system/xbin/tunctl: Read-only file system
busybox: /system/xbin/udhcpc: Read-only file system
busybox: /system/xbin/udhcpd: Read-only file system
busybox: /system/xbin/udpsvd: Read-only file system
busybox: /system/xbin/umount: Read-only file system
busybox: /system/xbin/uname: Read-only file system
busybox: /system/xbin/unexpand: Read-only file system
busybox: /system/xbin/uniq: Read-only file system
busybox: /system/xbin/unix2dos: Read-only file system
busybox: /system/xbin/unlzma: Read-only file system
busybox: /system/xbin/unlzop: Read-only file system
busybox: /system/xbin/unxz: Read-only file system
busybox: /system/xbin/unzip: Read-only file system
busybox: /system/xbin/uptime: Read-only file system
busybox: /system/xbin/usleep: Read-only file system
busybox: /system/xbin/uudecode: Read-only file system
busybox: /system/xbin/uuencode: Read-only file system
busybox: /system/xbin/vconfig: Read-only file system
busybox: /system/xbin/vi: Read-only file system
busybox: /system/xbin/vlock: Read-only file system
busybox: /system/xbin/volname: Read-only file system
busybox: /system/xbin/wall: Read-only file system
busybox: /system/xbin/watch: Read-only file system
busybox: /system/xbin/watchdog: Read-only file system
busybox: /system/xbin/wc: Read-only file system
busybox: /system/xbin/wget: Read-only file system
busybox: /system/xbin/which: Read-only file system
busybox: /system/xbin/who: Read-only file system
busybox: /system/xbin/whoami: Read-only file system
busybox: /system/xbin/xargs: Read-only file system
busybox: /system/xbin/xz: Read-only file system
busybox: /system/xbin/xzcat: Read-only file system
busybox: /system/xbin/yes: Read-only file system
busybox: /system/xbin/zcat: Read-only file system
busybox: /system/xbin/zcip: Read-only file system
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: Read-only file system
--- correcting permissions
Unable to chmod /system/bin/su: Read-only file system
--- 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!!!
Press any key to continue . . .
Click to expand...
Click to collapse
---------- Post added at 08:36 PM ---------- Previous post was at 08:30 PM ----------
Marcell96 said:
Just download the RootXperia.zip file to your sd card,
boot into recovery and install the zip file...
easy way to boot into recovery (Bootloader needs to be unlocked)
Click to expand...
Click to collapse
===============================================
Unfortunately download link is not working on that thread for CWM .. .. do you know any other way to get into CWM >> ??
---------- Post added at 08:39 PM ---------- Previous post was at 08:36 PM ----------
kiwiBratwurst said:
unfortunately the only way to root after updateing to 4.0.2.a.0.62 is to flash the 4.0.2.a.0.42 Kernal with flashtool, Im pretty sure you don't need unlocked bootloader to flash original SE Kernals... so just flash the old Kernal and you should be able to root again..
Otherwise if its not too late for other users I would just stay away from the new update until there is an easy rooting method, the update doesn't offer any real advantages.. AFAIK only a few minor bug fixes.
Have a great Christmas!
Kiwi
Click to expand...
Click to collapse
========================================
will try this rite now
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....
OK, here's what I've done. I downgraded and rooted my SK17 several hours ago, and then removed some bloatware. everything went great, but then I decided I want to replace stock camera app with this one. as I didn't know how to do it, I thought "hey, why don't just delete the SemcCameraUI.apk from system/app and replace it with downloaded one"? so I did it, but it still didn't want to work. so I tried to reboot the phone. the app still wasn't working [by then I guessed it's not the way it's done], and then Root Explorer decided that it doesn't want to work with such a stupid human and told me that it can't delete the apk nor change the permissions because it's a read-only file. and the SuperUser app was force-closing.
so I flashed the phone with .58 again, I learnt that I lost the root, so I tried rooting it again, and then I got the message from the zergRush script:
failed to copy 'files\SuperUser.apk' to 'system/app/./SuperUser.apk': Read-only file system
Click to expand...
Click to collapse
any suggestion what should I do to root it again?
note: every time I flashed .ftf file, I was unchecking "wipe data", "wipe cache" and "wipe apps log".
najodleglejszy said:
OK, here's what I've done. I downgraded and rooted my SK17 several hours ago, and then removed some bloatware. everything went great, but then I decided I want to replace stock camera app with this one. as I didn't know how to do it, I thought "hey, why don't just delete the SemcCameraUI.apk from system/app and replace it with downloaded one"? so I did it, but it still didn't want to work. so I tried to reboot the phone. the app still wasn't working [by then I guessed it's not the way it's done], and then Root Explorer decided that it doesn't want to work with such a stupid human and told me that it can't delete the apk nor change the permissions because it's a read-only file. and the SuperUser app was force-closing.
so I flashed the phone with .58 again, I learnt that I lost the root, so I tried rooting it again, and then I got the message from the zergRush script:
any suggestion what should I do to root it again?
note: every time I flashed .ftf file, I was unchecking "wipe data", "wipe cache" and "wipe apps log".
Click to expand...
Click to collapse
check this thread for rooting http://forum.xda-developers.com/showthread.php?t=1709880
er, yeah. that's how I rooted. I did it once, and then, as I said in post #1, lost it.
Nj, post the entire Rooting log.. That might help in knowing the problem more precisely..
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- 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
2837 KB/s (1075144 bytes in 0.370s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 178304 bytes
--- no cleanup required
--- 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
at first I realized the antivirus removed the ZergRush file so I disabled it and unpacked the archive once again, but still no result.
najodleglejszy said:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- 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
2837 KB/s (1075144 bytes in 0.370s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 178304 bytes
--- no cleanup required
--- 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
at first I realized the antivirus removed the ZergRush file so I disabled it and unpacked the archive once again, but still no result.
Click to expand...
Click to collapse
There's your fault.
As I had suspected it..
The anti-virus removes the ZergRush file even from the .zip or .rar file..
Disable anti-virus, download the rootingkit files again and the unpack and root your phone..
NOTE: While rooting, using flashtool, flashing kernel, please disable anti-virus temporarily.
And also while rooting your phone close flashtool if it's open.
all done, thanks! turns out I'm too dumb to remember that antivirus can peek inside zipped files.
btw, can anyone hint me how to replace the camera app with the one I was trying to?
najodleglejszy said:
all done, thanks! turns out I'm too dumb to remember that antivirus can peek inside zipped files.
btw, can anyone hint me how to replace the camera app with the one I was trying to?
Click to expand...
Click to collapse
NP
And flash the MDPI-GB-CamExtreme.zip file using CWM..
It's only for stock ROM I guess.
And don't forget to backup first using CWM.
thanks once again! thread can be locked now.
I have tried to root my micromax a25 using Motofail Exploit and zergrush exploi but both says an error... This is it......
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Why is it so (Bold) Why my file system is read only... please help me on rooting this phone... i am trying to root it last two monts but unable to do....... I have an Unsecured Boot.img and its scatter file But I cant flash boot.img using SP Flash Tool. Also Flashboot doesn't work as bootloader is disabled.... I tried all possible key combinations and also tried to get it into flashboot mode by pc command but it starts normally.... So is there any other tool to flash boot.img please help me........... i m dying here..... also i have tried all the well known softwares like gingerbreak, z4root, Superoneclick, Unlockroot and many more...... but i think we have to make boot.img unsecure firest because all gave errors..............plleeeeeassssssseeee helpppppppppp meeeeee.... My android Version is 2.3.6.....
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