root can't write to phone!!!

lpoppe22

New Member
Joined
Aug 20, 2010
Messages
3
Reaction score
0
Ok so here's the deal, i rooted my phone, and then unrooted it. The reason i unrooted it was to teach myself the ins and outs of how to fix things if ever need be. Now, I am running in to problems as i go to re-root the device. I have tried Motofail, DroidRazrUtility, and DoomLord and still no luck. I go to root the same way i did before and now says that i can't write to phone, that it is read only, or some jazz like that. I found a root method online somewhere, but have since lost it, that ran the abd and abd shell through the cmd prompt and, i believe, changed permissions. I NEED to find out what went wrong and why it worked perfectly the first time, but now is giving me problems. I looked around on some other threads, but without an definitive answers. can someone help?


Here's an example of the problem i am encountering:



--------------------------------------------------------------- Easy rooting toolkit (v4.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 (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)

[*] 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
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- 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
1407 KB/s (23060 bytes in 0.016s)
--- correcting permissions
--- executing zergRush


[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.


[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.


[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- 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
3301 KB/s (1075144 bytes in 0.318s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
142 KB/s (439 bytes in 0.003s)
--- Free space on /system : 212760 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: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
busybox: /system/xbin/su: 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: 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!!!
Press any key to continue . . .
 
OP
L

lpoppe22

New Member
Joined
Aug 20, 2010
Messages
3
Reaction score
0
not sure if i know how i did it but i DID do it....

ok so i think my problem might have been that i was trying to execute motofail root exploit through winrar... i had not extracted the files to a folder and when i tried that litterally as my last resort, it worked. rooted perfectly. have super user and everything. so if people are having this problem like i was, try motofail, make sure to extract all the stuff to a folder first, and then run the exploit... ugh. what an experience
 

jpcalhoun

Senior Member
Joined
Dec 14, 2010
Messages
1,567
Reaction score
61
Location
PA
ok so i think my problem might have been that i was trying to execute motofail root exploit through winrar... i had not extracted the files to a folder and when i tried that litterally as my last resort, it worked. rooted perfectly. have super user and everything. so if people are having this problem like i was, try motofail, make sure to extract all the stuff to a folder first, and then run the exploit... ugh. what an experience
I'm just guessing, but I bet that is the same problem you had when trying to use the Razr Utility...you have to extract the zip to a folder then run the .bat file.
 
OP
L

lpoppe22

New Member
Joined
Aug 20, 2010
Messages
3
Reaction score
0
yup. you're right

I'm just guessing, but I bet that is the same problem you had when trying to use the Razr Utility...you have to extract the zip to a folder then run the .bat file.

I think that is correct. it was weird though. i think it worked without being extracted the first time though. im not sure, but all utilities work now. i just wish i had figured that out about 12 hours ago, lol. Now at least i have a bunch of help pages bookmarked so if i do have a problem, i can find the, now, haha :biggrin:
 
Top