Related
okay so I have tried installing clockwork too many times to count and it flat out will not install. i have gotten a series of errors, but have just today been able to keep a consistent error. I downloaded one click clockworkmod 2.5.1.0. plugged in my device, extracted to my desktop and ran both bat files. This is a copy of the cmd prompt window:
remove stock recovery patcher
mount: operation not permitted
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system-recovery-from-boot.p, Read-only file system
copy kernel and flasher
2043 KB/s <313888 bytes in 0.150s>
failed to copy 'zImage' to '/sdcard/zImage': Permission denied
flashing kernel
RedBend Update Agent 6,1,14,1
and then it goes on through there... bottom line, it looks like i don't have permissions for the install. and i have already tried remounting rw through adb shell, it comes back and say remounting and then thats it. and ideas? i can give the reset of the scripting in cmd prompt if needed. Thanks in advance.
4nic8
dude theres like 10 other threads on this page about the same exact thing... and this doesn't go in this forum!
Download rom manager from the market and. ...that would do it for u automatically....... and yes pls next time try to search all the forums before posting
Sent from my SPH-D700 using XDA App
I have rooted - flashed KB5 Rom - All bloatware removed ....
Now, i want to add a few bloatware apks back on ... i can't
adb commands .. push " " -- "failed via Android Commander
also, i have to keep using Superoneclick to gain root when using android commander ..
so, do anyone have any ideas how to push or why i am unable to push .apks back into /system/app/
" failed ...... read-only file "
Without knowing all your steps, I'd guess that /system is still mounted read-only
jeffsf said:
Without knowing all your steps, I'd guess that /system is still mounted read-only
Click to expand...
Click to collapse
i followed the main steps to root then flash using odin .. just cant get pass the read-only
adb push file.apk /system/app/file.apk
EXPLOIT NO LONGER WORKING DUE TO OTA UPDATE. BE WARNED.
Thanks to beaups for his exploit!
Download the zip file below, unzip it somewhere, run root.bat with your phone plugged in and usb debugging enabled. Currently this is for windows only.
Includes a fully working su binary and Superuser.apk, make sure to update the su binary the first time you run SuperSu!
Follow the instructions on the screen, they are very simple, only one thing to do!
Download:
http://www.gigashare.in/738af
HELP SECTION:
After you are rooted, I strongly suggest you unlock your bootloader immediately!!
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Make sure Wifi is enabled and connected! (seems to help, but not required)
If you are stuck at "waiting for device to reboot" for a long time or you get "/data/local.prop was not created, exit the script, try again." followed by lots of junk, reboot your phone and push your clock forward two days, reboot, and try again.
If the update fails to check for updates, reboot your phone and push your clock forward two days, reboot, and try again.
usb drivers, if you need them: http://binary100100.googlecode.com/files/HTCDriver3.0.0.007.exe
You're the man and you know this...
Sent from my HTC One X using Tapatalk 2
Damn. I'm already rooted yet disappointed I can't be part of this . Lol well Friday I will be donating like I said I would. Good job
Sent from my HTC One X using xda premium
Great work! Wonder how long this will last.
Sent from my HTC One X using xda premium
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Pumpiron579 said:
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Click to expand...
Click to collapse
should only reboot twice
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
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/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
StrykerGT said:
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
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/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
Click to expand...
Click to collapse
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
designgears said:
should only reboot twice
Click to expand...
Click to collapse
Is that taking into account the unstableness and the potential for it to spontaneously reboot on its own?
Mine doesn't get past "waiting for device to reboot"
Thanks for the script sir!
skatin707 said:
Mine doesn't get past "waiting for device to reboot"
Click to expand...
Click to collapse
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
designgears said:
should only reboot twice
Click to expand...
Click to collapse
mine rebooted once after checking for update, but when it ran all the code, prior to rebooting, i got errors in the code. looked and no SU on my phone. not sure what i did wrong. didn't reboot the first time, so i pushed the date ahead two days and then it did with the code that everyone is reporting.
designgears said:
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
Click to expand...
Click to collapse
I'll keep waiting, it hasn't even been 10 minutes.
hahaha...that was magical!!!! works!!!!
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
did you run the updater on the phone? if it is completed or still spinning after a few min just reboot and try again.
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
I set my date ahead and turned on my WiFi, checked for updates and it rebooted right away.
love you guys.
designgears said:
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
Click to expand...
Click to collapse
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
beppomarx said:
heres what i get... i did get the reboot after checking for updates though.
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
32 KB/s (334 bytes in 0.010s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
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/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse
reboot and try again! push your clock up two days.
StrykerGT said:
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
Click to expand...
Click to collapse
YUP! but there is a one click for that too
HTC Inspire 4G - AT&T
Android - Stock GB 2.3.5 + HTC Sense 3.0
Build - 3.20.502.52
PC OS - Windows XP Pro SP3
Method - Easy Ace Root Tool
Noob - Yes
Problem - Bootloader unlock successfully achieved, but installation of BusyBox, Clockworkmod, and SuperUser interrupted during process.
Text from Post-Unlock on shown below. Trouble Areas Colored Red
Summary of Problem according to Tool - "Parameter Format not correct," "Read-Only file system," and "No such file or directory"
USB Debugging and Unknown Sources enabled when errors occur
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
< waiting for device >
sending 'recovery' (3554 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 0.953s]
finished. total time: 1.594s
rebooting...
finished. total time: 0.297s
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Make sure that USB debugging is enabled and charge only is set as default
Achieving Temp Root
cannot stat '/tools/tmp/fre3vo': No such file or directory
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
/data/local/tmp/fre3vo: not found
Pushing Busybox, SU and Superuser
1 KB/s (536 bytes in 0.312s)
1829 KB/s (380532 bytes in 0.203s)
1906 KB/s (1372660 bytes in 0.703s)
Trying to gain Perm Root
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'tools\su\su' to '/system/bin/su': Read-only file system
failed to copy 'tools\su\Superuser.apk' to '/system/app/Superuser.apk': Read-onl
y file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
FIND: Parameter format not correct
rm failed for EasyAceRoot.cmd, No such file or directory
Perm Root achieved...
I too am looking for the answer. I'll edit this post if I find something
If CWM would install, that wouldn't be a problem
Scozzar said:
I too am having this issue at the moment. The bootloader is unlocked, but I will not get perm root, even though it says it was achieved...
EDIT: Turning off Fastboot yields different results. But still no SuperSU.
EDIT2: I GOT IT! Basically, I downloaded the latest SuperSU .zip off XDA, put it on the phone, then flashed it in CWM. SuperSU now appears as an app!
Click to expand...
Click to collapse
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Prestige0813 said:
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Click to expand...
Click to collapse
What have you done? Also, you can't turn off fastboot; it's a mode selected from the bootloader. Do you mean ADB? Turning that off won't do anything either, other than making your phone's system inaccessible from the computer.
Scozzar said:
Fastboot, as in the check box in the stock ROM. You can't get into bootloader with it on. Also, if I was able to flash a new ROM, does that mean busybox is installed?
Click to expand...
Click to collapse
Depends on the ROM.
Scozzar said:
V2 Oxygen JB is what I'm using.
Click to expand...
Click to collapse
Er, I don't know for every ROM. If it's a custom ROM, probably. If you're rooted (and again, if you're using a custom ROM, you probably are), you can always install it from the play store.
Update:
First off, I've already downloaded the SuperSU App from Google Play, and it's failed to obtain root abilities, so a perm root is not being acheived.
Also, I've downloaded the latest SuperSU via PC, and it's ready to go once I manage to successfully install CWM (however, if the Ace Root Kit succeeds, then using CWM to install root isn't a needed method)
I've tried continuing the process with the Fastboot setting disabled, and I didn't see any difference in the end result. It seems that recovery is successfully written, but it doesn't succeed in installing SuperSU, CWM, or busybox.
On another note, I've downloaded the busybox installer app from Google Play, and it states the phone is rooted; but runs into errors when I attempt to install (regardless of the version I select). I've run two root checking apps, and both say that the phone is not rooted.
In short, All I've been able to achieve is getting the Boot Loader unlocked.
Can you flash recovery manually from fastboot?
New Update
I just found that CWM is in fact installed. I did not realize until just now that from the HTC bootloader I had to select recovery to access it.
I placed the SuperSU.zip on the phone and installed it via CWM, as scozzar had suggested, and the phone is now rooted (verified by two root checking apps)!
From there I installed busybox via Google Play with no hiccups.
I apologize for not trying this sooner I hope that others find success. The Inspire's a great phone, and now I've made mine even better!
Yess
bananagranola said:
Can you flash recovery manually from fastboot?
Click to expand...
Click to collapse
Yes! here is the tutorial
1- Download Android.zip and unzip it
2- make a folder called "Android" in C:/ like that: C:/Android.
3- put inside of the folder Android the files: adb.exe, fasttboot.exe, AdbWinApi.dll and the recovery.img
4- go to cmd and write:
cd \Android
fastboot flash recovery recovery.img
READY! now you have a CWM Recovery
Sorry for my bad english
i need this file System/bin/debuggerd from the 4.4.1, i tried using the krt16m stock image, used this to extract it and get the debuggerd file, used es file explorer and even total commander to replace it, change its permissions to chmod 755 and root shell, but this ota just doesn't install, in twrp still getting error debuggerd file problem, i use stick mount and i dont know why but i deleted the debuggerd.backup file:crying::crying::crying:
Update: I used this which I extracted from 4.4.2 odexed rom from here, I can confirm it is working, just check the sha1sum which should be 1A008709F0945E8EACA2166D143622EB8D94C3D0
Also i used adb commands to push the file from here
Hi,
If that helps: https://www.dropbox.com/s/eu2x01fkr11x9rh/debuggerd.
Don't forget to set the correct permissions, like this:
viking37 said:
Hi,
If that helps: https://www.dropbox.com/s/eu2x01fkr11x9rh/debuggerd.
Don't forget to set the correct permissions, like this:
Click to expand...
Click to collapse
Thanks a lot for the quick reply, it still doesnt work, i dont freaking undrerstand what the problem is, i double checked the md5 checksum through adb command even of the file, it matched but it the ota still shows
"system/bin/debuggerd" has unexpected contents.
E:Error in /tmp/update.zip
(status 7)
Installation aborted
imrock said:
i need this file System/bin/debuggerd from the 4.4.1, i tried using the krt16m stock image, used this to extract it and get the debuggerd file, used es file explorer and even total commander to replace it, change its permissions to chmod 755 and root shell, but this ota just doesn't install, in twrp still getting error debuggerd file problem, i use stick mount and i dont know why but i deleted the debuggerd.backup file:crying::crying::crying:
Update: I used this which I extracted from 4.4.2 odexed rom from here, I can confirm it is working, just check the sha1sum which should be 1A008709F0945E8EACA2166D143622EB8D94C3D0
Also i used adb commands to push the file from here
Click to expand...
Click to collapse
Thank you, it works! Although I had the debuggerd.backup file, renamed it to debuggerd and still failed. But with your file, I upgrade to 4.4.2 successfully. BTW, I use Root Explorer to change the right.