I have unlocked with htcdev and am wondering if there is a perm root option for me.
Sent from my ADR6425LVW using xda premium
im wondering about this as well
Please Read The Threads Already Posted In The Development Section.
http://forum.xda-developers.com/showpost.php?p=20776953&postcount=80
Permission denied
Sent from my ADR6425LVW using xda premium
What are the steps to use that once I download it ?
Sent from my ADR6425LVW using XDA App
You can't run it. Windows files
Sent from my ADR6425LVW using xda premium
You can perm root with MacOSX. Get the Android SDK for Mac, then all you need to do is edit the batch file(to use mac/linux convention) and supplement the command file(s) from the Mac SDK. It's actually not as bad as it sounds.
The only Windows files in there can be replaced with the Mac equivalent. The actual important part(s) are android files. Matter of fact...I just did the script for you. Now all you need to do is drop your Mac version of ADB in the "tools" directory.
MrSmith317 said:
You can perm root with MacOSX. Get the Android SDK for Mac, then all you need to do is edit the batch file(to use mac/linux convention) and supplement the command file(s) from the Mac SDK. It's actually not as bad as it sounds.
The only Windows files in there can be replaced with the Mac equivalent. The actual important part(s) are android files. Matter of fact...I just did the script for you. Now all you need to do is drop your Mac version of ADB in the "tools" directory.
Click to expand...
Click to collapse
i put adb in the tools folder in one click root run your script and it get this
--- WAITING FOR DEVICE ---
--- Device Connected ---
Checking for previous attempts...
, No such file or directory
Pushing Zergrush...
2037 KB/s (23060 bytes in 0.011s)
Setting Permissions...
: No such file or directory/tmp/zergRush
/Users/kevinbarry24/Android/OneClickRoot_1.1/OneClickRoot.sh: line 10: syntax error near unexpected token `('
/Users/kevinbarry24/Android/OneClickRoot_1.1/OneClickRoot.sh: line 10: `echo Gai'ing Perm Root (Aka running zergrush)...
i rooted with this method
http://forum.xda-developers.com/showthread.php?t=1418653
thanks for the help
Related
I'm attempting to root my Thunderbolt on a Mac. I've followed the instructions from the dev section, but whenever I try to "./adb push XXX" it tells me it "cannot stat 'XXXX': no such file or directory." How can I fix this?
It would help to know exactly what XXX is.
Pope of Eruke said:
I'm attempting to root my Thunderbolt on a Mac. I've followed the instructions from the dev section, but whenever I try to "./adb push XXX" it tells me it "cannot stat 'XXXX': no such file or directory." How can I fix this?
Click to expand...
Click to collapse
Sounds like you don't have the files in the directory you're running from. It can't find them with the information you've given it hence it reports they don't exist.
Change to the dir of the files then run or add the location in the filepath.
Xxx could be psnejter or any of the exploits that I'm trying to push.
Sent from my ADR6400L using XDA App
Pope of Eruke said:
Xxx could be psnejter or any of the exploits that I'm trying to push.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
It's either what the previous post said or you are pushing to the wrong directory. Most likely it's what he said though.
I'm not on a MAC, but my directory is c:\android-sdk-windows\platform-tools>
**You can always hit <tab> to jump to the directory you're looking for after entering in a couple characters of the folder you want.
I agree it sounds like your programs are not in the file/directory they should be located in.
I've rooted my HTC Amaze. The rootedness persists across reboot. Here's how I did it.
1. Copy the zergRush temp root to the phone. I put it in /data/local
2. Run zergRush on the phone via adb shell.
One you have temp root do this (from the PC)
1. adb remount
2. adb push su /system/bin/
3. adb shell chmod 04755 /system/bin/su
Then you can install superuser.apk and reboot. After rebooting you should be able to adb shell and type su. This should prompt you (on the phone) to allow su. Once you allow it then any apps that need root should begin working.
You can find the zip file that contains the su binary here
NOTE: the adb daemon will not be running as root so, when you adb shell to the device you will not have root. You just run su and then you have root.
Questions? Just ask. I'll do my best to help. But, remember, you do this all at your own risk.
-xdadevelopers-user
I had some weirdness when allowing a second root app in superuser. It would consistently FC. The first root app was fine and continued to work but I couldn't get another root app to be authorized.
It turns out it's related to the permissions on the superuser databases. To fix my problem I went to home>menu>settings>applications>manage applications>superuser>clear data. Then run superuser and dismiss the startup dialog. Now adb shell and run su. It will prompt on the device and you should allow it. You should now have the root prompt in your adb shell session. From there type
Code:
chmod 666 /data/data/com.noshufou.android.su/databases/*
Now you can run more root apps without superuser FCing.
-xdadevelopers-user
Very nice work, I will probably wait until we have recovery to actually do it. This is a great start though, hopefully this works with no problems as I saw that some were "bricking" their devices using the Zerg method for temp root.
This is still temproot , it won't allow u to go into /system to delete bloat or edit framework .
Sent from my HTC_Amaze_4G using XDA Premium App
Revolution said:
This is still temproot , it won't allow u to go into /system to delete bloat or edit framework .
Sent from my HTC_Amaze_4G using XDA Premium App
Click to expand...
Click to collapse
Yes, it will. In fact, that's basically all it does. Of course if you want to change /system/ you'll need to su to root first, then remount it RW. From there you can make any changes you want. The changes you make will persist across a reboot. To test this I deleted teeter.apk and teeter.odex from /system/app and rebooted. Teeter is now gone from my phone.
So, unless I'm misunderstanding what you mean, this is permanent root.
-xdadevelopers-user
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
xdadevelopers-user said:
Yes, it will. In fact, that's basically all it does. Of course if you want to change /system/ you'll need to su to root first, then remount it RW. From there you can make any changes you want. The changes you make will persist across a reboot. To test this I deleted teeter.apk and teeter.odex from /system/app and rebooted. Teeter is now gone from my phone.
So, unless I'm misunderstanding what you mean, this is permanent root.
-xdadevelopers-user
Click to expand...
Click to collapse
Revolution said:
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
Click to expand...
Click to collapse
For the record yes it dose, but your a dev next time try it b4 you post saying it don't work because u make yourself seem like you don't know what your talking about
Sent from my HTC_Amaze_4G using xda premium
I asked a question , i could speak and ask question's. kk .
Jaywan said:
For the record yes it dose, but your a dev next time try it b4 you post saying it don't work because u make yourself seem like you don't know what your talking about
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Revolution said:
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
Click to expand...
Click to collapse
Yes, you can make changes (add/edit/delete) to the files in /system.
I added:
/system/bin/su
/system/app/TitaniumBackup.apk
and deleted:
/system/app/teeter.apk
/system/app/teeter.odex
I did not edit anything in /system but I could if I had a reason to.
-xdadevelopers-user
for what it's worth...
I used the UOT kitchen to modify the battery to include percent. Since we don't have recovery yet I manually pushed the framework-res.apk and SystemUI.apk and then manually deleted the dalvik-cache. Now my status bar has the modified battery. Woohoo!
I was going to build a recovery today but android.git.kernel.org is STILL DOWN. Since the instructions I have require it I guess I'll wait for someone who already has the sources or until android.git.kernel.org comes back (I'm starting to wonder if it ever will).
-xdadevelopers-user
This is ****ing GENIUS work! Good job man. Pioneering for our amaze!
Not sure what I might be doing wrong but my su disappears after a reboot.
Try pushing to both xbin and bin
Sent from my HTC Sensation Z710e using xda premium
I did... No dice.
can you guys tell me what phone says when rebooting into hboot when its searching for a .zip, .nbh etc
its something like this
Example Sensation): PG58IMG.zip
It's not working for me.
C:\Users\Administrator\Desktop>adb push zergRush /data/local/
20 KB/s (21215 bytes in 1.000s)
C:\Users\Administrator\Desktop>adb shell
$ chmod 755 /data/local/zergRush
chmod 755 /data/local/zergRush
$ /data/local/zergRush
/data/local/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.
[-] Cannot copy boomsh.: Permission denied
$
Click to expand...
Click to collapse
EDIT
I removed the files in the tmp directory and it worked!
BUT
It's not consistent. When I reboot the su file disappears.
I've unlocked my bootloader. This may be required. Can anyone confirm that this works/fails on a locked bootloader?
-xdadevelopers-user
Finally, you sir are a genius
Sent from my HTC_Amaze_4G using Tapatalk
xdadevelopers-user said:
I've unlocked my bootloader. This may be required. Can anyone confirm that this works/fails on a locked bootloader?
-xdadevelopers-user
Click to expand...
Click to collapse
I'm on a locked bootloader. It doesn't work.
cmenard said:
I'm on a locked bootloader. It doesn't work.
Click to expand...
Click to collapse
Confirmed, same result for me on a locked bootloader. On reboot, it all goes away (or comes back).
Hey,
So a few months ago, I installed either an older version of Busybox, or the newer version I installed never stuck. Basically, I have two folders that contain the busybox commands: /sbin and /system/xbin. In Terminal Emu., when I enter a Busybox command, it seems to only acknowledge the older folder (/sbin). eg if I type in "busybox ifconfig..." or "busybox ipconfig...." I'm told that there's no such command, in so many words. How do I go about fixing this?
Would it mess anything up if I moved the contents of the newer folder (/system/xbin) into /sbin ?
Also, should there be a busybox file located anywhere (ie a file in root that's executed when "busybox" is typed into Term. Emu?) I can only locate the one in the internal sdcard directory ("busybox-stericon")
Thanks
bump
Alot of people are having the same issues on the reviews on gapps. Might be an error with gapps
Sent from my YP-G70 using xda app-developers app
alljokingaside said:
Hey,
So a few months ago, I installed either an older version of Busybox, or the newer version I installed never stuck. Basically, I have two folders that contain the busybox commands: /sbin and /system/xbin. In Terminal Emu., when I enter a Busybox command, it seems to only acknowledge the older folder (/sbin). eg if I type in "busybox ifconfig..." or "busybox ipconfig...." I'm told that there's no such command, in so many words. How do I go about fixing this?
Would it mess anything up if I moved the contents of the newer folder (/system/xbin) into /sbin ?
Also, should there be a busybox file located anywhere (ie a file in root that's executed when "busybox" is typed into Term. Emu?) I can only locate the one in the internal sdcard directory ("busybox-stericon")
Thanks
Click to expand...
Click to collapse
All files in /sbin are part of the kernel. Changes to this folder will be lost after a reboot. The only busybox you need is the one in sbin. It will be run when you type commands in terminal. Any other busybox should be deleted to avoid conflicts
Sent from my Galaxy Nexus using xda app-developers app
and I'll assume, then, that copying over the files from /system/xbin to /sbin won't cause any conflicts, since the files in sbin are like a subset of /system/xbin. thanks a bunch!
edit: blerg. apparently, I just learned to read. changes to /sbin will be lost
is there anyway that you're aware of to modify that folder? sbin's is missing a few useful commands eg ifconfig, iplink, etc
alljokingaside said:
and I'll assume, then, that copying over the files from /system/xbin to /sbin won't cause any conflicts, since the files in sbin are like a subset of /system/xbin. thanks a bunch!
edit: blerg. apparently, I just learned to read. changes to /sbin will be lost
is there anyway that you're aware of to modify that folder? sbin's is missing a few useful commands eg ifconfig, iplink, etc
Click to expand...
Click to collapse
It's the initramfs in the kernel, so you'd have to recompile it.
Sent from my Galaxy Nexus using xda app-developers app
Mevordel said:
It's the initramfs in the kernel, so you'd have to recompile it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
thanks for all the support. i suppose the initramfs is a file. Will decompiling/recompiling it w/ apkmultitools do the trick? I realize that this question's mad noobish, but hey- it is what it is.
thanks again
alljokingaside said:
thanks for all the support. i suppose the initramfs is a file. Will decompiling/recompiling it w/ apkmultitools do the trick? I realize that this question's mad noobish, but hey- it is what it is.
thanks again
Click to expand...
Click to collapse
I mean it's integrated into the kernel when the kernel is compiled. you'd have to recompile the kernel.
Sent from my Galaxy Nexus using xda app-developers app
figures.
ok- so when you type in a busybox command (eg ifconfig), does it respond? Busybox, when installed, adds commands and links it when you type it in in the terminal, so, I suppose my follow up question is - how do i re-link the commands to the proper path?
on second thought, this problem may have occurred roughly when I flashed paranoid android, reverted (no camera=not a daily driver) and re-flashed Entropy's kernel. additionally, root in terminal emulator, ever since, has shown "sh-3.2$" at the prompt. (PATH=/data/local/bin:$PATH)
for some reason, I'm starting to think it wasn't always this way.
Hey there! About 2 months ago I first rooted my HTC Legend and unlocked my bootloader and ugraded it to hboot 1.02
I installed cyanogenmod 7.2 and all worked great. I have CWM 5.0.2.8 installed too. And supertool worked for me (zergling rushes commenced . I was also able to use eclipse for android to view my root files via the computer.
Well I cant do this anymore. I can only see my root files via the phone using Root Explorer Lite which I downloaded from the play store.
And supertool is giving me errors of read-only file system (see attached screenshot) and says pushing Superuser.apk, so it appears on my phone, I also opened it but I don't know what im supposed to do in there??
I just want to be able to access my root files via my computer. do I have to use eclipse or is there another program? what am I doing wrong here?
ATM im using a workaround where I copy files to my SD card and then using Root Explorer Lite I copy for instance ringtones to the system/media/audio/ringtones folder and that works. But I need a simpler method like drag and dropping files into this folder via my computer. How can I do this?
Thanks for you help!
You can try qtadb.
Sent from my Legend using xda app-developers app
Curious as to actually know the need to use supertools when your already using a rooted rom?
I am so sure supertools was only needed to root a non rooted Rom, perhaps supertools stuffed it up....
Have you simply tried just using adb commands from cmd?
Perhaps your issue is the pc itself.
Maybe first is to try this:
Adb devices (proves phone and pc are connected).
Adb shell
Then type "su"
Then type "ls" (this gives file listing on device)
This is assuming you know anything about windows cmd, Adb and stuff like that.
Just some basics to get you started in trying to diagnose.
Hey, why not try restoring a nandroid backup you did earlier, you did do a backup yeah?
Sent from my HTC Desire HD using xda app-developers app
jazib360 said:
You can try qtadb.
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
thanks this actually worked! i dont even know how/why but it did
i tried other programs like Droid Explorer or Android Commander but it didnt let me copy files to system/media/ or wutever. and it would say my phone isnt rooted.
i tried the cmd promt as ranger said with adb shell
i did the su and ls thing and it works (displays dir/files list) but thats not the problem, the problem is when i type something like this:
chmod 777 media/
and it says it cant change permissions cuz its read-only file system, the same reason supertool didnt want to work. i wan my zergling rush!!!
seriously this is weird
I am testing to make sure I can push files into my device when in recovery.
I was able to successfully push a file when the device is up with adb push test.txt /sdcard/ROMS
It was there and able to open
Now in Recovery (New file test1.txt)
adb devices showed my device in recovery
I entered adb push test1.txt /sdcard/ROMS
adb shows it completed successfully but I do not see the file once I boot back into my OS.
What am I missing?
that is odd you should now see your file. what program did you use to make the file?
is the file perchance in a 0 folder in sdcard0?
Try adb push test.txt /sdcard/ROMS/test.txt
Hope that helps.
Sent from my HTC6435LVW using Tapatalk 4 Beta
I used notepad to make the file. The file isn't anywhere else. I have even done a search. And I tried putting the name of the file at the end of the command. I'll try again in a bit.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Download notepad++ and make a file then see what u have
Sent from my HTC6435LVW using XDA Premium HD app
Still nothing
t1gartist said:
Download notepad++ and make a file then see what u have
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I have installed notepad ++ and created a txt from there as recommended. Still no change. Here is a print out of what I have done. Also note that I made a new directory in order to avoid any possibly directory conflicts.
C:\android-sdk-windows\platform-tools>adb push new2.txt /sdcard/ROMS/new2.txt
16 KB/s (258 bytes in 0.015s)
C:\android-sdk-windows\platform-tools>adb push new2.txt /sdcard/newfolder/new2.t
xt
20 KB/s (258 bytes in 0.012s)
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
FA33AS504665 recovery
C:\android-sdk-windows\platform-tools>adb push new2.txt /sdcard/newfolder/new2.t
xt
77 KB/s (258 bytes in 0.003s)
rockfreak101 said:
I have installed notepad ++ and created a txt from there as recommended. Still no change. Here is a print out of what I have done. Also note that I made a new directory in order to avoid any possibly directory conflicts.
C:\android-sdk-windows\platform-tools>adb push new2.txt /sdcard/ROMS/new2.txt
16 KB/s (258 bytes in 0.015s)
C:\android-sdk-windows\platform-tools>adb push new2.txt /sdcard/newfolder/new2.t
xt
20 KB/s (258 bytes in 0.012s)
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
FA33AS504665 recovery
C:\android-sdk-windows\platform-tools>adb push new2.txt /sdcard/newfolder/new2.t
xt
77 KB/s (258 bytes in 0.003s)
Click to expand...
Click to collapse
you've likely installed a 4.2 based rom recently (like cm10.1). these virtual paths get all jacked up when you do that, especially in recovery.
A few options
1.) don't do that
2.) push things to /data/local/tmp/ instead
3.) push things to /data/media/ instead
beaups said:
you've likely installed a 4.2 based rom recently (like cm10.1). these virtual paths get all jacked up when you do that, especially in recovery.
A few options
1.) don't do that
2.) push things to /data/local/tmp/ instead
3.) push things to /data/media/ instead
Click to expand...
Click to collapse
Thanks. I will look into the other two options. I had a feeling that may have been it, but no grounds for why. I have a 4.2 rom installed and I'm prepping to format my sdcard because I have crazy loads of old data that I don't need and don't know what is what, so I'm going to format insternal SD and push the backup of my current rom back in. I'm using 6.xGb of the space already. No good.
rockfreak101 said:
Thanks. I will look into the other two options. I had a feeling that may have been it, but no grounds for why. I have a 4.2 rom installed and I'm prepping to format my sdcard because I have crazy loads of old data that I don't need and don't know what is what, so I'm going to format insternal SD and push the backup of my current rom back in. I'm using 6.xGb of the space already. No good.
Click to expand...
Click to collapse
So I pushed the test txt file to the specified locations. My struggle is that on the phone with the native file manager I can't access the data folder, though I have it root access. I downloaded Astro and it shows there are no contents (with show hidden contents selected).
So my thought is what am I doing wrong or what can I do?
Sideload?
So. If I so desired. I could wipe my internal memory, and sideload the install of the OS, or a backup?
You could but you might need to ruu first if you do that, I'm not sure as recovery stuff is in your internal storage like database files. It might just recreate those though.
Sent from my VIPER DNA
beaups said:
you've likely installed a 4.2 based rom recently (like cm10.1). these virtual paths get all jacked up when you do that, especially in recovery.
A few options
1.) don't do that
2.) push things to /data/local/tmp/ instead
3.) push things to /data/media/ instead
Click to expand...
Click to collapse
I love option 1... made me lolz