I was trying to install ClockworkMod Recovery I follow the step but for some reason I'm keep getting the following.
Code:
D:\Epic 4g\one.click.clockworkmod2.5.1.0-flasher>adb shell
$ su
su
# remount rw
remount rw
Remounting /system (/dev/stl9) in read/write mode
# exit
exit
$ exit
exit
D:\Epic 4g\one.click.clockworkmod2.5.1.0-flasher>run-try-first
one click installer and Clockworkmod Recovery v2.5.1.0 made by noobnl, skeeters
lint, and koush
Press any key to continue . . .
remove stock recovery patcher
mount: Operation not permitted
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
copy kernel and flasher
1509 KB/s (0 bytes in 313888.000s)
2458 KB/s (0 bytes in 5820868.002s)flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
wait 60 second
cleanup
rm failed for /data/local/tmp/rageagainstthecage-arm5.bin, No such file or direc
tory
rm failed for /data/local/root.sh, No such file or directory
done
Press any key to continue . . .
I've searched other thread someone did post the same issue but all they ask was "did you remount as rw?" or "Make sure your looking at your phone, superuser will ask you permission to for the process to run as root"
I did remount as rw and no superuser did not ask me anything during the install.
What should I do?
Please help!
Thank you
rooting phone soc 1.7 when it gets to this point:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
159 KB/s (5392 bytes in 0.033s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
do i wait for the last one (Running rageagainstthecage...) to say ok? it has been over 20 min and it still sit there i wanna make sure before making any move.
Djveneko said:
rooting phone soc 1.7 when it gets to this point:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
159 KB/s (5392 bytes in 0.033s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
do i wait for the last one (Running rageagainstthecage...) to say ok? it has been over 20 min and it still sit there i wanna make sure before making any move.
Click to expand...
Click to collapse
Try the psneuter option, It works fine for me.
fknfocused said:
Try the psneuter option, It works fine for me.
Click to expand...
Click to collapse
+1
Rage against the cage seemed to hang on me too when I first rooted my sgs4g. I just stopped it after it ran for a while and switched to psneuter method. Psneuter worked for me--and quickly. Good luck.
Sent from my SGH-T959V using XDA Premium App
Thanks!!
Sent from my SGH-T959V using XDA App
Psnueter works no problems.newbie here been tryin for 2 days to root. Just came from iphone so thats what I'm used to.any help greatky appreciated
Sent from my SGH-T959V using XDA App
My pc removed 1.7 because rage showed up as a virus. There is a 1.8 on cnet
Sent from my SGH-T959V using XDA Premium App
Either options work, I've tried both ways and they work, not always the first run but it's all trial and error =)
Sent from my SGH-T959V using XDA Premium App
Rooting SGS4G
I ran DoomLord v4 script. But i ran into a small problem. I am on 2.3.6 gingerbread.
---------------------------------------------------------------
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
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
562 KB/s (23060 bytes in 0.040s)
--- 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
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x0001d338
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40219cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19403 0xafd390ef
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
+++ LOG: write failed (errno=14)
+++ LOG: write failed (errno=14)
+++ LOG: write failed (errno=14)
****REMOVED 160 or so lines of this "+++ LOG: write failed (errno=14)"
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- 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
1564 KB/s (1075144 bytes in 0.671s)
--- correcting permissions
--- remounting /system
--- checking free space on /system
28 KB/s (439 bytes in 0.015s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 76744 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.280 secs (3839800 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
986 KB/s (22228 bytes in 0.022s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
1739 KB/s (785801 bytes in 0.441s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
My problem is "+++ LOG: write failed (errno=14)" and "df: /mnt/.lfs: Function not implemented" does all these errors means the script partially failed? My other error is in Root Check it says "ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1" besides a few other minor things. If you want i can post the root check log as well. I loved doomlord script. went smoothly except for those small minor bugs. Can that all be fixed or should i run SuperOneClick? Thanks for any help.
Do you have Superuser on your phone?
Yes superuser is there. Here's a Root Check log. As you can see there seems like a few errors including "ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1" so i am trying to figure out if i need to rerun the batch file, try superoneclick or if its fine left alone. I have superuser cause i opened it. But its 3.06, i used Doomlord's root v4, which uses superuser 3.06 and busybox 1.18.4. SuperOneClick uses more recent one. Thats why im not sure if it's ok or not. Thanks for the response
Congratulations! You have root access!
Superuser Application Status:
Superuser application - version 3.0.6 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: No such file or directory
Analysis: File /sbin/su does not exist.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22228 2011-11-10 12:53 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-04-14 22:28 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
You're good to go.
What about all those errors and the ro.secure=1? Do i have a lower access root or just normal to get errors? Cause i was thinking of trying superoneclick but if it seems fine i can leave it alone. Thanks for the very quick response.
What is your ultimate goal? Do you want a custom ROM or Kernel? If so, none of this matters as it will be overwritten when you flash.
I just wanted to be sure i got full root access, ATM i just want stock firmware with full root. But i did want to upgrade to a custom rom. Preferably CM9 if it ever shows up for the SGS4G. I have cyanogen on my tablet. Do you know if they will release that to this phone? Since i doubt samsung will ever release Ice Cream Sandwich for this. Thanks
CM7 will come first and we have some intelligent dedicated devs working on it for all of us. But our current custom ROM's are awesome and beat the hell out of stock I must say!
I unlocked my phone(xperia P) successfully but I can't able to root my phone, the problem is if I'm rooting, a message is popping up i.e, storage is unavailable and this program can't continue. In cmd this is the problem shown below
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
2814 KB/s (210390 bytes in 0.073s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
3744 KB/s (1085140 bytes in 0.283s)
Pushing su binary ....
1265 KB/s (91980 bytes in 0.071s)
Pushing Superuser app
4072 KB/s (996704 bytes in 0.239s)
Making busybox runable ...
.
Pushing fake Backup
4235 KB/s (73728 bytes in 0.017s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
If all is successful i will tell you, if not this shell will run forever.
Running ......
Good, it worked! Now we are rebooting soon, please be patient!
Waiting for device to come up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Made a mistake and updated my Droid 4 with the Jellybean OTA, so I needed to reroot my phone. I attempted to reroot with the script below:
http://forum.xda-developers.com/showthread.php?t=2207384
but it's failing here at the point below. My question is if I select option 1 of the script (Think it's failing because I didn't unroot the ICS version) will it wipe all data off my phone? Including the personal stuff. Or will it just wipe the root folders? Thanks a lot.
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied[*] Rebooting device...[*] Waiting for phone to reboot.[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists[*] Rebooting device...[*] Waiting for phone to reboot.[*] Phase four...
3559 KB/s (543080 bytes in 0.149s)
3597 KB/s (1867568 bytes in 0.507s)
3144 KB/s (476557 bytes in 0.148s)
2308 KB/s (63838 bytes in 0.027s)[*] Cleaning up...
/system/bin/sh: su: not found
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied[*] Rebooting...[*] Exploit complete!
Solution to fix SystemUI crash loop
Hi,
i was able to fix the SystemUI crashing loop on my moto g xt1032
via LogCat i found these two errors:
Code:
E/QSEECOMAPI: ( 6008): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 6008): Error::Cannot open the file /firmware/image/keymaste.mdt
There are just symlinks in /vendor/firmware/keymaster/
Code:
lrw-r--r-- root root 2015-03-04 14:26 keymaster.b00 -> /firmware/image/keymaster.b00
lrw-r--r-- root root 2015-03-04 14:26 keymaster.b01 -> /firmware/image/keymaster.b01
lrw-r--r-- root root 2015-03-04 14:26 keymaster.b02 -> /firmware/image/keymaster.b02
lrw-r--r-- root root 2015-03-04 14:26 keymaster.b03 -> /firmware/image/keymaster.b03
lrw-r--r-- root root 2015-03-04 14:26 keymaster.mdt -> /firmware/image/keymaster.mdt
so we need to look into /firmware/image/.. and we don´t find any of these files in there. That´s a problem.
Lucky me i found those files in my backups.. since i don´t know, what these files contain, i´m not able to upload them for you. maybe secret data.. maybe device specific data.. i don´t know..
so you have to find yourself the correct files in your backup?
as there seems to be a typo anywhere (take a deep look at the second error message!) we also need a file called keymaste.mdt..
i just copied keymaster.mdt and renamed it to keymaste.mdt
files i copied to /firmware/image/ are:
Code:
keymaster.b00
keymaster.b01
keymaster.b02
keymaster.b03
keymaster.mdt
keymaste.mdt
to do so, you have to remount the folder as writeable
adb shell "mount -o rw,remount /firmware"
Click to expand...
Click to collapse
then copy those files.. and reboot
Code:
adb push keymaster.b00 /firmware/image
adb push keymaster.b01 /firmware/image
adb push keymaster.b02 /firmware/image
adb push keymaster.b03 /firmware/image
adb push keymaster.mdt /firmware/image
adb push keymaste.mdt /firmware/image
if your device is absolutly clean installed.. you can´t connect via adb.. because you can´t accept the adb connection on your device..
to connect via adb just boot into twrp recovery.. in twrp press "mount" and disable mtp file transfer.. and now your are able to use adb in twrp
twrp does not mount /firmware.. so we have to do this manually by:
mount -t ext4 -o,rw /dev/block/platform/msm_sdcc.1/by-name/modem /firmware
Click to expand...
Click to collapse
now we are able to use adb push to copy those files like discribed above..
anyone know what these files are for?
whats inside those files?
where to get them?
why is this a problem for systemui?
why isn´t this fixed in cyanogenmod since more than a half year?
maybe anyone is able to verify this:
i downloaded another stock rom (asia xt1033 dualsim).. to extract those keymaster files of it.. and surprise.. those files have same md5 hash, as my files.. that means, those stock files are exactly the same as my files.. so its not a problem for me to upload them.. here you will get a double-click solution to repair SystemUI Crash =)
you need:
adb and adb driver on your windows system
adb access on your moto-g..
if your device is absolutly clean installed.. you can´t connect via adb.. because you can´t accept the adb connection on your device while the systemui crash hides the confirm window.. it is indeed possible.. but very painfull way to get there (usb debugging, etc. must be enabled too).. there is a better solution:
to connect via adb just boot into twrp recovery.. in twrp press "mount" and disable mtp file transfer.. and now you are able to use adb in twrp
attach your moto-g to your computer
extract the archive (attached to this posting) to whatever folder you want on your windows machine (it is nothing to install via recovery/sideload!!!)
doubleclick one of these coresponding files:
1systemui.fix.bat <- this is your choice if you are able to do adb connection in cyanogenmod
2systemui.fix.bat <- this is your choice if you are in twrp recovery
what this tool will do:
remount /firmware as writeable..
pushing all keymaster files to /firmware/image on your device..
that´s it.. nothing special.. nothing creepy..
systemUI-Crash should be fixed now..
to properly remount /firmware, just reboot device..
sometimes adb can´t recognize your device.. when this happens.. the "tool" is waiting.. and waiting.. and waiting.. stocks at this point:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
to fix this just plug the usb-cable of your device out.. and back in.. maybe several times.. untill you see something like this:
Code:
adbd is already running as root
29 KB/s (180 bytes in 0.006s)
1282 KB/s (6568 bytes in 0.005s)
1987 KB/s (16280 bytes in 0.008s)
57 KB/s (176 bytes in 0.002s)
941 KB/s (6748 bytes in 0.007s)
1647 KB/s (6748 bytes in 0.004s)
###########################################
# #
# press any key to reboot your device #
# #
###########################################
bitcoin donations are welcome =)
1EkpEyRuZqHF1Bcuv6dsUKQT9v8a43zbjc