[Q]I can't installCl ockworkMod Recovery - General Questions and Answers

[Q]I can't installCl ockworkMod Recovery - General Questions and Answers

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

Related

[Q] Cannot Root the HTC Legend

Hi Guys,
I have a bit of a problem, I want to install a custom rom on my HTC Legend. But I am a kinda noobish. I followed a couple tutorials from a site called hxxp://theunlockr.com/2010/06/07/how-to-root-the-htc-legend There it says that I have to downgrade my HTC Legend to 1.31. Before the downgrading proces you have to make a goldcard, I am managed to make one. But I get stuck with the Downgrading
It says I have to follow these couple things
III. Make Phone Downgrade-able
1. On your phone, make sure that USB Debugging is checked ON in Settings > Applications > Development.
Done
2. Plug in your phone and make sure it is connected as Charge Only NOT Disk Drive or something else.
Done
3. Download the Downgrading Tools and extract them to your AndroidSDK\tools\ folder (all of the files need to be in the tools folder with adb).
Done
4. Open a command prompt on your computer by clicking on the Start button and typing cmd and hitting enter in the search box.
Done
5. In the command prompt, type the following with hitting enter at the end of each line:
cd c:\AndroidSDK\tools\
crackin.bat
Done
6. The phone will reboot 5 times, be patient.
Done
7. After it is done, you will see a bunch of error messages, that is normal.
Done
8. Look for the following line, if you see it (the date and time can be different)
you are ready to continue, if not then reboot your phone, factory reset it, and try again:
crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
This part doesnt work for me! This is what I get in CMD.exe:
Microsoft Windows [versie 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\Gebruiker>cd c:\AndroidSDK\tools
c:\AndroidSDK\tools>crackin.bat
"Copying tools"
1418 KB/s (698452 bytes in 0.481s)
1237 KB/s (76044 bytes in 0.060s)
2051 KB/s (655360 bytes in 0.312s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Jan 6 22:06 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
c:\AndroidSDK\tools>
What do I have to do? Is there anything wrong with my goldcard? Or is it something else?
PLEASE HELP!
Thanks in advance Tom

....same
http://forum.xda-developers.com/showthread.php?t=725430

[Q] Error when try downgrade htc legend

Hello,
I try to downgrade my htc legend with this tutor : http://forum.xda-developers.com/showthread.php?t=725430
But i get the next line :
cr--rw---- 1 1001 2002 90, 0 Jan 13 21:11 /dev/mtd/mtd0
how can i fix this?

Hello,
I just whiped my phone but still :
Microsoft Windows [versie 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\Administrator\Desktop\android-sdk-windows\platform-tools>crackin.bat
"Copying tools"
adb server is out of date. killing...
* daemon started successfully *
1619 KB/s (698452 bytes in 0.421s)
1190 KB/s (76044 bytes in 0.062s)
1641 KB/s (655360 bytes in 0.390s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Jan 14 00:51 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
What to do ?
mij boot loader is 1.01

You missed a step or something that's why it says no file or directory,make sure files where pushed into the Data folder
adb shell
cd data
ls
and you should see the dxdrm

Hello,
If i do that i get this :
C:\androidSDK\tools>adb shell
$ cd data
cd data
$ ls
ls
opendir failed, Permission denied

edit :
I finaly managed to roll back to 2.1 what to do now ?
Code:
C:\androidSDK\tools>crackin.bat
"Copying tools"
1256 KB/s (698452 bytes in 0.543s)
589 KB/s (76044 bytes in 0.126s)
1155 KB/s (655360 bytes in 0.554s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, Is a directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, Not a directory
rmdir failed for /data/DxDrm, Directory not empty
link failed File exists
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, Permission denied
link failed File exists
link failed File exists
"Rebooting to normal mode to downgrade ROM"
crwxrwxrwx 1 1001 2002 90, 0 Jan 14 19:25 /dev/mtd/mtd0
"Freeing links"
rm failed for /data/DxDrm, Permission denied
rm failed for /data/dontpanic, Permission denied
I Did this whit RUU Legend
but can i root now?

RUU say's i have : image version : 1.31.405.5
edit : r4-lagend-root keeps on : writing "zip"

question to ericosman
ericosman how did you managed to fix the cr--rw---- 1 1001 2002 90, 0 Jan 13 21:11 /dev/mtd/mtd0 part and get it right? iv been working on it for so long i have no idea how to fix it and cant downgrade

[Q] Root Galaxy nexus with unlocked bootloader

Hi, i saw Bin4ry .bat file that root phones like xperia s without unlocking the bootloader.
I tried with my Gnex stoc 4.1.1
Does someone know why it doesn't work?
Here's what i get:
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
3995 KB/s (1085140 bytes in 0.265s)
1399 KB/s (22364 bytes in 0.015s)
3771 KB/s (843503 bytes in 0.218s)
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Premere un tasto per continuare . . .

[ROOT/UNLOCK BOOTLOADER/RECOVERY]LG-D320/N/L70 devices

Quick guide for people having trouble rooting/unlocking bootloader and custom recovery LG-D320/N/L70 devices running 4.4.2 with a new 3.4.0+ kernel
This way is easier then any root method and NO PC is required
Simple, straight forward, takes not even 5 minutes.
First download and install these 3 apps.
CPU Benchamark
Terminal Emulator
KingoRoot.apk
Second, download this zip file and extract the "mrw" folder to your phones internal memory(/sdcard)
ReplaceKingoRoot.zip
Third, open CPU Benchtest app and press the "stress test" box, then minimize the app and open Kingo ROOT app and press the "ROOT" bubble
Fourth, Kingo ROOT says your device is rooted open Terminal Emulator and type the following
Code:
su
Your device will ask if Terminal Emulator can be granted root permissions, allow it then proceed to type the following
Code:
sh /sdcard/mrw/root.sh
Then SuperSU will automatically open and ask to update SuperSU binaries, select the "update" box and when it asks you how you want to update it select the "normal" box
Five, Restart your phone when SuperSU says you need to restart for the update to take effect
Now, unlocking the bootloader and flashing a custom recovery, fortunately i made a tool for this with the required files.
simply download this, unzip it onto the desktop and run LGTOOL.BAT by double clicking it and follow the instructions.
LG TOOL BY RICKY DIVJAKOVSKI
ENJOY GUYS
Credits:
jeffta74
wanako1
MrW0lf

updated.

I'm AndroidAddict aka MikeHoncho at AF btw. Glad to see someone post something even though we never got a forum here

AndroidAddict||AA said:
I'm AndroidAddict aka MikeHoncho at AF btw. Glad to see someone post something even though we never got a forum here
Click to expand...
Click to collapse
every device should be able to gain full flexibillity, no matter how old, how new, how popular or unpopular and device i get my hands on will gain full access
time to make a custom rom now

I think everything is done "custom ROM" wise. AOSP, cm11, cm12, carbon (by me) and other ROMs

AndroidAddict||AA said:
I think everything is done "custom ROM" wise. AOSP, cm11, cm12, carbon (by me) and other ROMs
Click to expand...
Click to collapse
ofcoarse its done custom rom wise, you can modify a rom with root access but to safely modify a rom and test recovery is mandatory

Terminal emulator not working
Thx for this guide.
terminal emulator can't install SuperSU.
Here's the log, whats wrong?
Tried also to install supersu manually, but can't update it so is absolutely useless.
[email protected]:/ $ su
l_SD/ReplaceKingoRoot/mrw/root.sh <
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
---------------------------------------
----- UPDATED BY RICKY DIVJAKOVSKI ----
---------------------------------------
Failure
Failure
rm failed for /system/app/KingoUser, No such file or directory
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[20]: cat: sdcard/mrw/busybox: No such file or directory
rm failed for /system/xbin/ku.sud, No such file or directory
rm failed for /system/xbin/su, Operation not permitted
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[33]: can't create /system/xbin/su: Permission denied
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[35]: cat: /sdcard/mrw/su: No such file or directory
Unable to chown /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
daemonsu: invalid option -- d
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
rm failed for /data/data-lib/com.kingoapp.root, No such file or directory
rm failed for /data/data-lib/com.kingouser.com, No such file or directory
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.kinguser, No such file or directory
rm failed for /data/data-lib/com.kingroot.kinguser, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
rm failed for /system/bin/.usr/.ku, No such file or directory
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/su, Operation not permittedrm failed for /system/bin/ddexe, No such file or directory
rm failed for /system/bin/install-recovery.sh, No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_INVALID_URI]
rm failed for /system/usr/iku, No such file or directory
rm failed for /dev/reportroot, No such file or directory
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
rm failed for /sdcard/Kingroot, No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
[email protected]:/ #ll

Ggcost said:
Thx for this guide.
terminal emulator can't install SuperSU.
Here's the log, whats wrong?
Tried also to install supersu manually, but can't update it so is absolutely useless.
[email protected]:/ $ su
l_SD/ReplaceKingoRoot/mrw/root.sh <
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
---------------------------------------
----- UPDATED BY RICKY DIVJAKOVSKI ----
---------------------------------------
Failure
Failure
rm failed for /system/app/KingoUser, No such file or directory
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[20]: cat: sdcard/mrw/busybox: No such file or directory
rm failed for /system/xbin/ku.sud, No such file or directory
rm failed for /system/xbin/su, Operation not permitted
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[33]: can't create /system/xbin/su: Permission denied
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[35]: cat: /sdcard/mrw/su: No such file or directory
Unable to chown /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
daemonsu: invalid option -- d
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
rm failed for /data/data-lib/com.kingoapp.root, No such file or directory
rm failed for /data/data-lib/com.kingouser.com, No such file or directory
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.kinguser, No such file or directory
rm failed for /data/data-lib/com.kingroot.kinguser, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
rm failed for /system/bin/.usr/.ku, No such file or directory
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/su, Operation not permittedrm failed for /system/bin/ddexe, No such file or directory
rm failed for /system/bin/install-recovery.sh, No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_INVALID_URI]
rm failed for /system/usr/iku, No such file or directory
rm failed for /dev/reportroot, No such file or directory
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
rm failed for /sdcard/Kingroot, No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
[email protected]:/ #ll
Click to expand...
Click to collapse
Yea i have the same problem with this i've done everything right step by step but seems cant find the location of the root can anyone help me or the topic is dead ?

[SOLVED] Restore build.prop to default: adb shell doesn't let me write

ROM: LineageOS 18.1, Recovery: LineageOS 18.1 recovery
I messed up and put my build.prop in an invalid state. I got the default build.prop from the rom zip,rebooted the phone to recovery (lineageos 18.1 recovery), mounted the system partition on /mnt/system, and tried to write build.prop to default via adb shell and then cat >/mnt/system/system/build.prop and writing whatever stuff I want. However, even after remounting as rw, I get the following error message:
Code:
cat: xwrite: No space left on device
The same thing happens if I just edit on my PC and do adb push
Code:
$ adb push build.prop /mnt/system/system/build.prop
build.prop: 1 file pushed, 0 skipped. 89.9 MB/s (2662 bytes in 0.000s)
adb: error: failed to copy 'build.prop' to '/mnt/system/system/build.prop': remote write failed: No space left on device
Now what does this even mean?? There is 3.1M free space, as confirmed by df -h. I really searched I cannot find anything on this. Any help would be really appreciated!
---
I can confirm it is mounted as rw by checking this line in /proc/mounts
Code:
/dev/block/dm-0 /mnt/system ext4 rw,seclabel,relatime 0 0
adb remount also fails with
/system/bin/sh: remount: inaccessible or not found
I'm at my wit's end, any guidance here? I feel this should really not be this difficult! I just want to rewrite build.prop from adb/recovery!
---
It might have something to do with overlayfs, as seen here https://android.googlesource.com/platform/system/core/+/master/fs_mgr/README.overlayfs.md. However adb remount merely says /system/bin/sh: remount: inaccessible or not found! How should I get this to work?
---
Finally: maybe I could just try to flash a zip containing only the build.prop via adb sideload? Will adb sideload wipe anything (e.g. system) or just overwrite the files which are present in the zip?
---
Just ended up flashing again. It worked without deleting apps or data

Database Info

welcome