What does "misc" do in the following line of code? My google and forum.xda-developers searches have not been fruitful.
cd /data/local
chmod 04755 *
data/local/flash_image misc /data/local/mtd0.img
Related
I am following a manual which says
Code:
adb shell chmod 755 /system/etc/init.d/95havsvdd
but his is what I get when I try to chmod on a this file I have uploaded minute before:
Code:
chmod: /system/etc/init.d/95havsvdd: Not a directory
Can anyone help?
I ran all the required commands and noticed that the chmod did not do anything. So I decided to run the temp root command abd I get permission denied.
Sent from my T-Mobile G2 using XDA App
Please anyone? I run this command "adb shell chmod 755 /data/local/tmp/*" but it does not do anything, is there something I have to change on that line?
Been trying to root for 2 days now but unsuccessful.
you're not supposed to see any return on the command prompt. Just continue with the procedure.
Thanks for giving me a reply, waited many hours. THANK you though.
When I run the temp root command, I get this.
"C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
C:\android-sdk-windows\platform-tools>adb shell
"
C:\android-sdk-windows\platform-tools>adb shell
#
#
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox md5sum /dev/block/mmcblk0p18
./busybox md5sum /dev/block/mmcblk0p18
b532ca54a073f0c4043bd7be69ebce8d /dev/block/mmcblk0p18
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
./gfree -f -b hboot-eng.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# cd /data/local/tmp
cd /data/local/tmp
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# ./root_psn
./root_psn
# sync
sync
#
Did these commands run right?
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
# ./flash_image recovery recovery.img
# ./root_psn
# sync
All looks good to me.... When yoh restart the phone do you have s off?
Sent from my HTC Vision using XDA App
i was following the procedure of permanent root-ing my DZ... There is a problem...
4.a.2. gfree, install hboot and clockwerkmod recovery
In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
./gfree -b:unknow option
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# ./root_psn
./root_psn
cp: can't stat '/sdcard/Superuser.apk': No such file or directary
cp: can't stat '/sdcard/su': No such file or directary
is this consider something wrong?
should i continue the procedure?
Try to send files to phone one more time and try again.
Sent from my HTC Vision using Tapatalk
make sure you didn't miss the star when
Code:
$ adb shell chmod 755 /data/local/tmp/*
Have you done this?
Code:
$ adb push su /sdcard/
$ adb push Superuser.apk /sdcard/
zeonion said:
i was following the procedure of permanent root-ing my DZ... There is a problem...
4.a.2. gfree, install hboot and clockwerkmod recovery
In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
./gfree -b:unknow option
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# ./root_psn
./root_psn
cp: can't stat '/sdcard/Superuser.apk': No such file or directary
cp: can't stat '/sdcard/su': No such file or directary
is this consider something wrong?
should i continue the procedure?
Click to expand...
Click to collapse
Hey all! Desperately seeking help here: I'm rooting my MyTouch 3g slide, and have successfully completed all the steps up to this point where I need to run "rageagainstthecage-arm5.bin" from the devices "/data/local/tmp/" folder. The previous steps are as follows from cyanogen's wiki page:
"On the computer, open terminal and run the following commands:"
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
/data/local/tmp/rageagainstthecage-arm5.bin
Click to expand...
Click to collapse
All of these with the exception of the last line are successful. After running chmod 755, I typed the following:
Code:
ls -l /data/local/tmp/
I get the following result:
Code:
-rwxr-xr-x 1 root root 5392 Aug 25 2010 rageagainstthecage-arm5
.bin
but finally, entering
Code:
/data/local/tmp/rageagainstthecage-arm5.bin
I get
Code:
/sbin/sh: /data/local/tmp/rageagainstthecage-arm5.bin: not found
It's there. I don't get it. Heeeelllpp meeeeeeee
Here's a log:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push rageagainstth
ecage-arm5.bin /data/local/tmp/
292 KB/s (5392 bytes in 0.018s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
~ # /data/local/tmp/rageagainstthecage-arm5.bin
/data/local/tmp/rageagainstthecage-arm5.bin
/sbin/sh: /data/local/tmp/rageagainstthecage-arm5.bin: not found
~ # ls -l /data/local/tmp/
ls -l /data/local/tmp/
-rwxr-xr-x 1 root root 5392 Aug 25 2010 rageagainstthecage-arm5
.bin
~ #
Note to moderation team: I wanted to post my contribution directly into the author's thread but I'm not allowed to do so.
If my post is right, maybe you could merge my post with the original discussion.
Hi everyone,
I'd like to to provide my feedback regarding the following tool written by Bin4ry.
Tool is available here:
http://forum.xda-developers.com/showthread.php?t=1886460
First of all, I'd like to thank Bin4ry for his job, because with the help of his tool, I have successfully rooted my noname (*) tablet, running ICS 4.0.4.
However, it did not work out at the very first try: the tool said everything went fine but after reboot, my tablet was still not rooted.
Actually, I entered the guts of Bin4ry's script, and find out this trick.
The original script contains this section:
Code:
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system && /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su && /data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk && /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
GOTO FINISH
Actually, I think that the command "/data/local/tmp/busybox" is missing at some locations.
So I rewrote the script as follows and got my tablet rooted !!
Code:
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system"
stuff\adb.exe shell "/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk"
stuff\adb.exe shell "/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox"
stuff\adb.exe shell "/data/local/tmp/busybox chown 0.0 /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 06755 /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 655 /system/app/Superuser.apk"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 755 /system/xbin/busybox"
stuff\adb.exe shell "/data/local/tmp/busybox rm /data/local.prop"
stuff\adb.exe shell "/data/local/tmp/busybox reboot"
GOTO FINISH
Note: I'm typing from memory because sadly, I erased my own modified file hope I'm not typing too much stupid things because my memory might play me some tricks. But the general idea is here.
Said differently, I simply added the command "busybox" before "chmod" and "chown" commands.
Don't ask me why but it did work. Actually, I discovered this trick by typing the aformentionned commands one a time and find out that simply chmoding a file did not actually change its properties.
I did not rewritte the entire script, but it might be necessary to add the "busybox" command prior to any other "chmod" or "chown" commands (in the ":RICSTUFF" for instance. My tablet did not require to enter this section so I did not bother modify it).
Hope this trick will help someone. If someone finds out it solves its issue, it might be useful to modify Bin4ry's script in a next version of the tool.
(*) more precisely, my tablet is a Finetech by Akor, model TG166.
Want to try to use this method to root Docomo P-02E but something concern.
If rooting is not success, it must be kept unrooted. But will it brick the phone?
Thank you and regards,