[HowTo] Make temp-root permanent - HTC Amaze 4G

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).

Related

[GUIDE] Properly Setting Up Root for Your X10

Okay, so I've noticed that this rooting method is a little unconventional. It works through a compromised Fota.pkg which has setuid on /system/bin/sh as root. This is not a very safe, as any application that runs sh will gain root access to your system. Scary... :S Anyway, in order to fix this we need to take a few steps.
It is important that you do these in order, otherwise you may lose root access
Install a proper SU with whitelist
1. Download http://bit.ly/aWgALL
2. Unzip the system folder.
3.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push system/bin/su /sdcard/su
adb push system/app/Superuser.apk /sdcard/Superuser.apk
adb shell dd if=/sdcard/su of=/system/bin/su
adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
adb shell chmod 6777 /system/bin/su
adb shell chmod 644 /system/app/Superuser.apk
4. Reboot your phone.
Fix sh to not setuid to root
1.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell chmod 0755 /system/bin/sh
Properly install busybox
1. Here, it's easier to look for the busybox installer app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
chai_archer said:
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
Click to expand...
Click to collapse
If you followed the root guide you can put it in the step 4 folder.
Then hit windows key + r and in the box type CMD
A console window comes up.
in the console window type cd <path.to.your.step.4.folder>
then go from there.
zephyrix said:
Properly install busybox
1. Here, it's easier to look for the busybox app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
Click to expand...
Click to collapse
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
bcool15 said:
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
Click to expand...
Click to collapse
yep.
if you check the superuser app it should already be there.
zephyrix said:
yep.
if you check the superuser app it should already be there.
Click to expand...
Click to collapse
all i see in superuser app is titanium backup pro
that's strange. does busybox report that it's installed?
zephyrix said:
that's strange. does busybox report that it's installed?
Click to expand...
Click to collapse
nope it doesnt
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
unknown13x said:
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
Click to expand...
Click to collapse
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
bcool15 said:
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
Click to expand...
Click to collapse
use "su" to get root access... allow when the Superuser Whitelist notification pops up.
it worked for me....followed the steps, after i downloaded the busybox app i opened it and a box popped up "Superuser Request", it had discription of the busybox app and then asked whether to allow or deny the request....i then checked the superuser app and was able to see the busybox app in thr....
can anyone confirm if these steps were added in the new root method? please
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
root in adb
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
th4r said:
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
Click to expand...
Click to collapse
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Here are the answers....
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
No they were not. The reason is that many of the rooting steps rely on a setuid "sh"
gfgodoy said:
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
Click to expand...
Click to collapse
Yes
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
So what? The uid for the shell application launched after invoking "adb shell" is not going to match any of the installed applications anyways. The thing is that Superuser.apk installs a mechanism by which the user (human) can detect when an application is requesting root access. Based upon the nature of the application you may or may not want to grant root access. That is the whole point.
th4r said:
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
Click to expand...
Click to collapse
Oh yeah? I just use "su" whenever I want root access... and I didnt have to write any scripts to enable/disable it.
k1ckn1ck said:
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Click to expand...
Click to collapse
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
j4mm3r said:
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
Click to expand...
Click to collapse
easy now, it's a fair question, would be nice to be able to run cleaning scripts on a protected system. no need to be a prick
in answer to the question though, once the batch starts adb shell, it won't continue till that process ends
I did some googling for some comandline tools that might allow sending keystrokes to a process, but nothing easy appeared, looks like your only option is to use a linux friendly notepad to create some shell scripts you can execute from the sdcard. i.e. on device
su
chmod 755 /sdcard/myscript.sh
./sdcard/myscript.sh
easiest way to do scripts on a secured root IMO

New Rooting method for 2.1 | updated for 2.0.2.A.0.24 | 9/01/2011

Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.

[Q] Rooted or not?

Hi, I rooted my Vribrant, both ways (manually and with one click root). I installed terminal emulator. I tried the su command to check if I am root. The # appears normally. However I tried deleting a file with Root explorer, inside the system folder, and when I get back it's still there. I also tried deleting it manually from Terminal EMulator with these commands:
su
cd system/apps
rm Swype.apk
and I get this:
rm failed for Swype.apk, Read-only file system
I also tried:
su rm Swype.apk
and this is returned:
Permission denied.....
I also tried the exact same thing from adb shell (which I had to allow in superuser permissions program), but it gave me the exact same results. What's wrong? Am I doing something wrong? Thanks
In root explorer, try hitting the r/w button at the top and see if that works.
Sent from my SGH-T959 using XDA App
I know about the button. The strange thing is that inside system folder it grands me r/w permissions, and no matter how many times a press the r/o button it doesn't change. Still gives the results I said. However, besides root Explorer what's wrong with terminal emulator and adb?
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
rbirg said:
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes both methods installed the "Superuser Permission" app.
I7oobie said:
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
It does normally.
linuxmotion said:
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
Click to expand...
Click to collapse
I tried the first method but it didn't work. When I entered adb root, it said "adbd cannot run as root in production builds". I searched a bit and found that I must have a rooted kernel for this to work. (I guess it's different from the root method I tried in "how to root vibrant").
Anyway the second way worked, where i replaced mntblock3 with stl9 for my phone. I tried the rm command and it worked! However as soon as I exited terminal, I couldn't delete other files. I had to retype the command. I can't do this everytime I need access in System folder. Why is this happenning? Does this have something to do with the fact that root explorer cannot change r/w to r/o mode while in system folder?
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Moved to Q&A, please post in the correct section.
s15274n said:
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Click to expand...
Click to collapse
No it didn't work. I also installed the latest version of SuperUser 2.3.6.1. But without a difference unfortunately.
What works for me, is installing sgs tools, and whenever I want to do write operations on system folder, run the appropriate script from sgs and then use root explorer......
Although I think there's something wrong? Why doesn't the mount r/w button work in root explorer, and why do I have to remount the file system through SGS tools, every time for it to work?
makes no sense to me either. Have you uninstalled RE and the installed it back granting root once reinstalled?
Yes several times.....
I am giving up. I just have to go through the whole process every time. I found some other people having this issue. I am on stock JI6 firmware. Maybe when I read a little bit more I will flash a custom rom.
Download and install Super Manager. Pretty handy program to use for Root users.
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
msnuser111 said:
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
Click to expand...
Click to collapse
At least I am not the only one with this problem.... haha
I forgot to mention that I use Root Explorer version 2.12.2
When I try a custom Rom I will post the results....
^ why not get the update, .4 is the most recent build. Do you have an illegal copy?
It's not only root explorer. It happens with other file explorers too like android mate and super manager... Inside system folder whatever, I do doesn't happen unless I unmount and remount like before

Method to install root for Honeycomb

Check this thread for updated and improved information, many thanks to j4mm3r
http://forum.xda-developers.com/showthread.php?t=953110
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. Using this version of su is not as secure because it will not activate Superuser for your permission to grant root access. In fact, it can work without Superuser.apk installed at all. Hopefully we will soon have an updated su or maybe the next version of Honeycomb will be prerooted. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2
Extract the above files using your favourite program
Using adb, install all three files to /data/local:
adb push su /data/local
adb push Superuser.apk /data/local
adb push busybox /data/local
Use adb remount to open the /system directory
adb remount
Use adb shell to move files
adb shell
cd /data/local
cat Superuser.apk > /system/app/Superuser.apk
cat su > /system/bin/su
cat busybox /system/xbin/busybox
Symlink su and set permissions:
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
Typing su should now work
su
su: access granted, courtesy of www.magicdroidapps.com
Install busybox
exit from adb shell and using a terminal application (i.e Root Explorer or Better Terminal Emulator) on the nook,
su
busybox --install -s /system/xbin
That should do it, works with Root Explorer, Titanium Backup, LCD Density, Quick Boot and SetCPU.
Good Luck
really? That simple? Root was the only reason i haven't jumped on the Honeycomb train. This may change my mind.
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
anbradle said:
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
Click to expand...
Click to collapse
Check your steps, especially permissions and the symlink. Works consistently on reboot for me.
Homer_S_xda said:
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
Click to expand...
Click to collapse
I couldn't get it to work for me without installing in /system/bin and using a symlink to /system/xbin
chhaggerty said:
It wouldn't work for me without installing in /system/bin and using a symlink to /system/xbin
Click to expand...
Click to collapse
It should work anywhere in the default PATH as long as it's got the full permissions (7655) set. I've only got one in xbin wih no symlink and all has been well for the superuser app...
[email protected]:/system/bin # echo $PATH
echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
[email protected]:/system/bin # ls -l su
ls -l su
su: No such file or directory
[email protected]:/system/bin # ls -l /system/xbin/su*
ls -l /system/xbin/su*
-rwSr-sr-t root root 76232 2011-02-04 09:08 su
-rwSr-sr-t root root 76232 2009-07-31 19:08 su-magic
-rwSr-sr-t root root 26264 2010-08-10 06:52 su-new
-rwSr-sr-t root root 68340 2011-01-31 11:22 su-org
chhaggerty said:
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2.
Good Luck[/B]
Click to expand...
Click to collapse
i might take credit for gaining root, but the rest is all you
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
nswenson said:
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
Click to expand...
Click to collapse
Running busybox from terminal will install all the busybox commands in /system/xbin which should make them available when using adb.
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
You were right I tried again and now I am rooted after reboot. Thanks
jleecong said:
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
Click to expand...
Click to collapse
Okay...
I am running HC (v2) off a 8gb sd card.
So do I just do these steps to gain root or do I need to partition the sd card first?
Thanks
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
agreed, i was just going for root myslef
j4mm3r said:
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
In
http://howto.ccroms.net/android_project/build/mod/root
I would have though that the purpose of the changes, specifically;
LOCAL_FORCE_STATIC_EXECUTABLE := true
LOCAL_STATIC_LIBRARIES := libc
Were what should resolve the _mktemp not found?
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
Howard from MagicAndroidApps.com noted this on the original Honeycomb thread. I'll update the OP to make this clear. Thanks.
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Mikey1022 said:
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Click to expand...
Click to collapse
yes, at the stands, its just root access. granted i had my own reasons for this

[Temp-Root] ZergRush the Amaze 4G

I got the 1.9.0004 Hboot on the Amaze to the guys with Revolutionary and hopefully they can find some exploit wizardry to save us all from the dreaded HTC unlock.
In the meantime, I can confirm that their ZergRush exploit works on the Amaze 4G with software version 1.36.531.5 (untested on any others, but probably still fine). Link: http://forum.xda-developers.com/showthread.php?t=1296916
The exploit provides temporary root only and any root-level changes will not survive a reboot. This means you can use ZergRush, then push the su app and binary via adb and then use root apps and delete bloat, etc but on reboot it will all go back to the way it was before (the nand partition is not unlocked with this).
Cayniarb said:
I got the 1.9.0004 Hboot on the Amaze to the guys with Revolutionary and hopefully they can find some exploit wizardry to save us all from the dreaded HTC unlock.
In the meantime, I can confirm that their ZergRush exploit works on the Amaze 4G with software version 1.36.531.5 (untested on any others, but probably still fine). Link: http://forum.xda-developers.com/showthread.php?t=1296916
The exploit provides temporary root only and any root-level changes will not survive a reboot. This means you can use ZergRush, then push the su app and binary via adb and then use root apps and delete bloat, etc but on reboot it will all go back to the way it was before (the nand partition is not unlocked with this).
Click to expand...
Click to collapse
can we do anytime type of a recovery?
Nice Job bro
Sent from my HTC_Amaze_4G using xda premium
anybody know where i can find a tutorial on how to do this? the link provided has instructions but very vague... i really would like to get this thing rooted... even if just temporary
Enzopreme said:
anybody know where i can find a tutorial on how to do this? the link provided has instructions but very vague... i really would like to get this thing rooted... even if just temporary
Click to expand...
Click to collapse
It's all there, trust me. follow the instructions with adb in the first post then refer to http://forum.xda-developers.com/showthread.php?p=18373159 in the same thread to push su and superuser to the phone.
Sent from my HTC_Amaze_4G using Tapatalk
Confucius say - Longest journey begins with first step
Credit's for my man Revolution being in IRC# asking question's about ZR haha & nice , remember this only allow's you to run root only applications .
Does this zergrush allow you to remove the bloatware and it stays gone after a reboot? Or do they come back..
Adamp24 said:
Does this zergrush allow you to remove the bloatware and it stays gone after a reboot? Or do they come back..
Click to expand...
Click to collapse
It comes back on reboot.
That's so weird. If you remove the system .apks via uninstall.. how would they magically restore themselves?
There has to be a way to clear off this bloatware! =\
Adamp24 said:
That's so weird. If you remove the system .apks via uninstall.. how would they magically restore themselves?
There has to be a way to clear off this bloatware! =\
Click to expand...
Click to collapse
There is..... its called "permaroot"! Relax and be patient... good things always come to those who wait...
Adamp24 said:
That's so weird. If you remove the system .apks via uninstall.. how would they magically restore themselves?
There has to be a way to clear off this bloatware! =\
Click to expand...
Click to collapse
NAND is still locked, anything root level reverts to the way it way after a reboot and this is only a temp root.
when i try to adb shell chmod 755 /data/ local/ zergRush i get a error message "unable to chmod read-only file system"....any thoughts
bizal05 said:
when i try to adb shell chmod 755 /data/ local/ zergRush i get a error message "unable to chmod read-only file system"....any thoughts
Click to expand...
Click to collapse
Either change permissions of the file, or see if a file manager will let you change the folder to R/W. Since i do not have my Amaze yet (in the mail), I cannot go to the folder to see if you can do the latter without root.
Does not work on Wind's Amaze ROM.

Categories

Resources