hello,
my HTC amaze has been rooted for years, but somehow it recently got unrooted. busybox installer still shows it as rooted, but every other application i have that requires root tells me i need root access/superuser privileges. when i try to re-root with the zerg rush exploit, this is what happens:
bash-3.2# adb devices
List of devices attached
HT19VVP12772 device
bash-3.2# adb push zergRush /data/local/
1667 KB/s (21215 bytes in 0.012s)
bash-3.2# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
bash-3.2#
***EDIT***
i am pretty sure it got unrooted after i installed busybox, which installed at /system/xbin.
responses from adb terminal commands:
bash-3.2# adb ls /system
000041ed 00001000 515f14ed .
000041ed 00000000 53343bad ..
000041ed 00001000 00000000 lost+found
000041ed 00002000 53343976 app
000041ed 00001000 53343976 bin
000081a4 00001fd0 515f14ed build.prop
000041ed 00001000 4f7f6e47 customize
000041ed 00001000 4f7f6e49 etc
000041ed 00001000 4f7f6e4a fonts
000041ed 00001000 4f7f6e53 framework
000041ed 00002000 4f7f6e64 lib
000041ed 00001000 4f7f6e65 media
000041ed 00001000 4f7f6e72 usr
000041ed 00002000 52d9d612 xbin
adb ls /system/xbin includes this:
0000a1ff 00000014 4f7f6e73 sh
whereas adb ls/system/bin does not have "sh" listed.
so /system/bin/sh doesn't exist but /system/xbin/sh does.
how do i fix this and get my device rooted again? this is driving me nuts! thanks
FIXED (i think - i hope)
installed su binary from recovery, did cleanup in superuser app, root seems to be working again now
eudemonics said:
installed su binary from recovery, did cleanup in superuser app, root seems to be working again now
Click to expand...
Click to collapse
That's what I was going to suggest, but glad you figured it out.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Related
[FIXED] Urgent help, how to restore \efs to get lost IMEI ? "Input/output error"
Greeting,
Tonight I flashed a custom kernel to my phone, just\ lost the Singal and my phone show no sim card inserted!.
anyway, i figure it out that... the IMEI lost.
in \efs there's no nv_data.bin file!!
So i went to restore the \efs.
but something not right here!
Hope someone can help here.
i tried these commands but no chance tel now!.
here to restore nv_data.bin
Code:
su
# cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
[COLOR="red"]cp: can't stat '/efs/nv_data.bin': Input/output error[/COLOR]
and here to restore \efs
Code:
# busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
efs/
efs/cryptprop_rebootMode
[COLOR="Red"]tar: can't remove old file efs/cryptprop_rebootMode: Read-only file system[/COLOR]
#
tried to flash back to many FW but no chance,
now i'm in KF1 rooted.
tried root explorer to copy the files but \efs is read only can can't not be changed!.
Hi.
Sounds like your /efs is mounted read-only, try re-mounting for rw access:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p1 /efs
(either via adb or terminal app running on the phone itself)
and then try to copy the files back again.
If it doesn't want to work from a running system, you can also try it in recovery mode (given you have a recovery that allows you a root shell) - you have to use adb in that case ("adb shell", get a root shell ("rootsh" when you're using CF-Root) and then the above).
Maybe the actual FS on the EFS partition is corrupted, so as a very last resort maybe formatting it and then restoring the full backup might work.
here's what i got
Code:
su
# mount -o rw,remount /dev/block/mmcblk0p1 /efs
mount -o rw,remount /dev/block/mmcblk0p1 /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp: can't stat '/efs/nv_data.bin': Input/output error
will trey via recovery,
but,, how to format it ?
It's one of the mkfs commands, but at first glance I could only find the ext2 version of it - /efs is (like everything else of the internal partitions on the SGS2) ext4....
Maybe someone else can shed some light if either mkfs.ext2 can be used, or how else to format it ext4.
Also, you should use tar to write back your backup, to keep the proper permissions.
Now i see no nv_data.bin in the /efs
and I couldn't copy the file, it's read only, even with the mount!
I think this is the only solution for me.
Some have restored efs/IMEI by flashing a stock firmware .
jje
Ah, also found this command:
Code:
make_ext4fs
but I have no idea about its parameters....
Yeah, try flashing a stock FW, maybe one of the "_user_low" ones, AFAIK they clean out a bit more stuff....
I got this
Code:
su
# ls
ls
acct fota.rc res
app-cache init sbin
cache init.goldfish.rc sdcard
config init.rc sys
d init.smdkc210.rc system
data init_kernel_only.rc tmp
dbdata lib ueventd.goldfish.rc
default.prop lpm.rc ueventd.rc
dev mnt ueventd.smdkc210.rc
efs proc vendor
etc recovery.rc
# cd efs
cd efs
# ls
ls
[COLOR="Red"]ls: ./nv_data.bin: I/O error
ls: ./nv.log: I/O error
ls: ./nv_data.bin.md5: I/O error
ls: ./dmp: I/O error[/COLOR]
cryptprop_applied_result cryptprop_securewipedata
cryptprop_onetimeboot edk_p
cryptprop_persist.sys.language imei
cryptprop_persist.sys.timezone redata.bin
cryptprop_rebootMode
#
hope this help ?
FIXED...
here's the full Solution http://forum.xda-developers.com/showthread.php?p=15666725#post15666725
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....
Found a one root script. Just need to see if it'll work on the Amaze. If it does, I'll add it in my tool and give proper credits as always. If not, I'll look into it myself.
Prerequisites?
_________________________
Am I on Candid Camera?
Same as usual. S-off or unlock boot loader.
I will be able to help after work in few hours if still needed. Unless I don't need a computer, in which if that's the case, I'll help ya out now
_________________________
Am I on Candid Camera?
You need a computer, I just need a few testers. Thanks GG!
hasoon2000 said:
You need a computer, I just need a few testers. Thanks GG!
Click to expand...
Click to collapse
I'm home I'm an hour and half... I'll ccheck in then. No prob
_________________________
Am I on Candid Camera?
replacement is due in an hour or two so I will test it then.
zPacKRat said:
replacement is due in an hour or two so I will test it then.
Click to expand...
Click to collapse
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Wife says I'm busy :banghead:
Sorry 4 now
_________________________
Am I on Candid Camera?
hasoon2000 said:
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Click to expand...
Click to collapse
first attempt it hangs:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
749 KB/s (2005736 bytes in 2.613s)
640 KB/s (91980 bytes in 0.140s)
713 KB/s (570342 bytes in 0.781s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
After rebooting from power button it provided the following:
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
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/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Unlock your boot loader and try it.
hasoon2000 said:
Unlock your boot loader and try it.
Click to expand...
Click to collapse
same!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
4544 KB/s (2005736 bytes in 0.431s)
3592 KB/s (91980 bytes in 0.025s)
2978 KB/s (570342 bytes in 0.187s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
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/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Flash a recovery. Boot into recovery, run the command. Sorry for all this lol
from 4ext nothing, just hangs.
Hold on, adb is giving me issues.
Alright. Try CWM
no go from cwm
it seems that in recovery it hangs a "@adb wait-for-device"
below is what happened when I removed the wait for device command and changed reboot to reboot recovery.
I had dropped the last part of the script in manually to finish the process.
* server not running *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
788 KB/s (2005736 bytes in 2.483s)
747 KB/s (91980 bytes in 0.120s)
704 KB/s (570342 bytes in 0.791s)
mv: can't rename '/data/local/tmp': No such file or directory
REBOOT
error: device offline
AGAIN REBOOT
error: device offline
AGAIN!?
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "echo ro.kernel.qemu=1 > /data/local.prop"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>ECHO
AGAIN REBOOT
AGAIN REBOOT
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
reboot recovery
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -wo remount rootfs /"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -o remount,rw -t ext4
/dev/block/mmcblk0p30 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1
,data=ordered)
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/dev
/block/mmcblk0p33 /system"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "cat /data/local/busybox >
/sbin/sh: syntax error: unexpected end of file
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin/busybox"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 777 /system/xbin/busybox"
chmod: /system/xbin/busybox: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "/system/xbin/busybox --install -s
/sbin/sh: /system/xbin/busybox: not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/Superuser.apk
BusyBox v1.19.3-cm9 static (2011-11-20 14:44 +0100) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/app/Superuser.apk"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/su /system/xbin/su"
cp: can't stat '/data/local/su': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chown 0.0 /system/xbin/su"
chown: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 06755 /system/xbin/su"
chmod: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 644 /system/app/Superuser.apk"
chmod: /system/app/Superuser.apk: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local.prop"
rm: can't remove '/data/local.prop': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local/tmp"
rm: can't remove '/data/local/tmp': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mv /data/local/tmp.bak /data/local/tmp"
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
try this. It will reboot you in recovery
Just a heads up, I've s-offed and am upgrading to ICS because I have to get it ready for work tomorrow. let me know if there is any other way I can help.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Wait til you are in recovery, then press a button
Press any key to continue . . .
6359 KB/s (2005736 bytes in 0.308s)
6416 KB/s (91980 bytes in 0.014s)
5460 KB/s (570342 bytes in 0.102s)
mv: can't rename '/data/local/tmp': No such file or directory
mount: mounting /dev/block/mmcblk0p33 on /system failed: Invalid argument
/sbin/sh: can't create /system/xbin/busybox: nonexistent directory
chmod: /system/xbin/busybox: No such file or directory
/sbin/sh: /system/xbin/busybox: not found
cp: can't create '/system/app/Superuser.apk': No such file or directory
cp: can't create '/system/xbin/su': No such file or directory
chown: /system/xbin/su: No such file or directory
chmod: /system/xbin/su: No such file or directory
chmod: /system/app/Superuser.apk: No such file or directory
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Users\user.account\Desktop\Oneclickroot>
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
ringochan said:
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
Click to expand...
Click to collapse
His tool does have ext4... You just have to get the full version from android-dev
Sent from my HTC_Amaze_4G using Tapatalk 2
Hello,
Using adb pull to recursively copy directories skips files for me. Is this the intended behavior, and if so is there any way to fix it?
Eg,
adb pull /data \bak
Directory of C:\bak
03/22/2013 12:38 PM <DIR> .
03/22/2013 12:38 PM <DIR> ..
03/22/2013 12:38 PM <DIR> .uci
03/22/2013 12:38 PM <DIR> clipboard
03/22/2013 12:38 PM <DIR> misc
03/22/2013 12:38 PM <DIR> system
but there are definitely other directories in /data, including /data/data
adb can see these other directories
>adb ls /data
000041f9 00001000 51468752 .
000041ed 00000000 5146874a ..
000041f8 00001000 00000000 lost+found
000041fd 00001000 514cb171 system
000041f9 00001000 4d1eb514 dbdata
000041fd 00001000 5136df0c clipboard
000041ff 00001000 51468758 .uci
000041e8 00001000 4d1eb514 dontpanic
000041f9 00001000 4d1eb514 gps
000043f9 00001000 503ecdc9 misc
000041f8 00001000 4d1eb547 wifi
000041f9 00001000 4d1eb515 local
000041f9 00002000 51455838 data
000041f9 00001000 4d1eb514 app-private
000041f9 00001000 512d0ac7 app
and the weird thing is if I specificy subdirectories adb will copy them, e.g., I can do adb pull /data/data . So I take this to mean adb isn't skipping them for some reason like attributes, permissions, or their being in use. But why doesn't pulling the parent directory pull all these subdirectories if "pull" is supposed to be recucrive (and why does it pull some subdirectories)? Thanks for any tips guys.
AW: [Q] adb pull behavior
Did you already try the following:
adb pull /data/ c:\bak
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Did you already try the following:
adb pull /data/ c:\bak
Click to expand...
Click to collapse
you mean with trailing backslash and the root c specified? yeah, but no difference. still misses a bunch of files and subdirs (which it gets if I specify them directly).
Can you use the command "adb backup" (details here) to acheve your goal?
Hello,
I have one serious probleme !! When i use adb shell with root i can't remove files from one folder named clockwordmod in sdcard. I've tried chmod permissions of files and then does not work to :/ the output (name of file): permition denied . And the output of ls -l is -rw-rw---- root sdcard_r (size) (date) (name of fil) any one can help me with this situation? Thanks
Regards