• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Persistant root

So i ran into alittle problem with my rooting last night! i followed the directions exactly... got it rooted... reboot the phone... and now its nothing but lag and something is eating my memory! left the phone on the charger last night.. wake up late for work this morning cause my phone turned itself off...

I started the phone this morning and everything runs super laggy, after the phone is booted up completly i ran ATK to kill all the processes.. memory freed up to 120mb... less than an hour later i boot up ATK again and kill processes... this time i only have 62mb of free ram with only pandahome and ATK running... something is terrible wrong.. any ideas? guess my next question is.. how can i revert this back to stock if i cant figure out whats wrong?
 
deathclutch said:
So i ran into alittle problem with my rooting last night! i followed the directions exactly... got it rooted... reboot the phone... and now its nothing but lag and something is eating my memory! left the phone on the charger last night.. wake up late for work this morning cause my phone turned itself off...

I started the phone this morning and everything runs super laggy, after the phone is booted up completly i ran ATK to kill all the processes.. memory freed up to 120mb... less than an hour later i boot up ATK again and kill processes... this time i only have 62mb of free ram with only pandahome and android running... something is terrible wrong.. any ideas? guess my next question is.. how can i revert this back to stock if i cant figure out whats wrong?
Click to expand...

Make sure you copy the txt 1 line at a time. The echo on the adb shell can cause problems if trying to paste multiple lines.

from the shell, type cat /system/bin/playlogo

You should see:
Code: 
#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
cat /system/bin/sh > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real

If not, you can either odin back to stock and try again, or work with someone in IRC to see if they can help you figure out where your pasting went wrong.
 
yeah thanks for the tips this morning.. its a shame im at work, where can i get odin? i keep hearing about it.. but cant find it
 
-----------------
If you want to undo this you need to use odin to flash the original
files. You can find tuorials in alot of places. The Flash files
you'll need are here:
http://shrunk.me/uvij6.zip
------------------
Click to expand...

You put the phone into download mode by holding Vol Down + OK (Round center button) and power, hold it till it shows Download Mode on the screen, then run the odin app...

Just a note on my windows7 64bit box i run the Odin app as Administrator.
 
thanks for all the help last night dev... but i ran into the same problem.. 4 or 5 times after you went to bed... good thing odin is working lol
 
devrdander said:
Make sure you copy the txt 1 line at a time. The echo on the adb shell can cause problems if trying to paste multiple lines.

from the shell, type cat /system/bin/playlogo

You should see:
Code: 
#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
cat /system/bin/sh > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real

If not, you can either odin back to stock and try again, or work with someone in IRC to see if they can help you figure out where your pasting went wrong.
Click to expand...
I have the same problem with the phone being extremely laggy; typing cat /system/bin/playlogo does give me what you said it should. Odin back or try flashing the galaxy rom? >:\
I also have GDE if that matters.
 
ended up using Odin back to stock, it seems as if it works better than before.(well, except for the battery)
 
hey guys i could use some help. my phone shows up in the adb list of devices, but says offline. nothing seems to change it, so i know i'm doing something wrong. can someone point me in the right direction. i have uninstalled and reinstalled the drivers twice already.

**update
nevermind I got working.
 
For those that want Root in ADB Shell without typing SU / Dealing with $ then SU everytime. though, chmod 2000 may not be needed, but I chose to add that for the time being..... Enjoy & use at your own RISK!!

Change the Script to:

echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
cat /system/bin/sh > /system/bin/su
mv /system/bin/sh > /system/bin/sh1
mv /system/bin/su > /system/bin/sh
chmod 2000 /system/bin/sh
chmod 04755 /system/bin/sh
/system/bin/playlogo_real" > /system/bin/playlogo


Thanks goes to Kam187 for the Root :)
Thanks man :)
 
Thats wierd so it doesnt reset permisions on sh.

Anyway thats a bit of a long way to do it.

You're doing this:

copy sh to su
move sh to sh1
move su to sh

set permisions on sh

You just move the sh around and back again! Instead you can do the following:

echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
/system/bin/playlogo_real" > /system/bin/playlogo

But this will open ALL shells as root.
 
Thanks Kam187 for the Feedback, I was just playing with stuff... Stuff that needs Root :) but, found it useful & wanted to share.. I'm not sure if this gives you other idea's or not, but, like I said I found it useful was all.

Thanks for the Short hand version of that, wasn't to sure on it, but found it did work correctly..

kam187 said:
Thats wierd so it doesnt reset permisions on sh.

Anyway thats a bit of a long way to do it. Line by line what you're doing:

# open 'sh' shell as root
/data/local/try3 /system/bin/sh
# remount filesystem as writable
mount -o rw,remount /dev/st9 /system
# copy sh to su
cat /system/bin/sh > /system/bin/su
# move sh to sh1 (not needed)
mv /system/bin/sh > /system/bin/sh1
# move su to sh (not needed)
mv /system/bin/su > /system/bin/sh
# set permisions on sh (not needed)
chmod 2000 /system/bin/sh
# set different permisions on sh
chmod 04755 /system/bin/sh

Instead you can do the following:

echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
/system/bin/playlogo_real" > /system/bin/playlogo

But this will open ALL shells as root.
Click to expand...
 
try3 is a root exploit. it runs the command that follows it as root.

I forget the exact exploit now. Its not mine, someone else found it.
 
Thats it asroot. There is one other root exploit thats available for < 2.1. But once you get to 2.1 all known exploits are closed :(

Having said that, samsung dont prevent downgrading. Also we can flash the kernel without any root exploit, so we can root from init.rc anyway :)

Dont panic!
 
kam187 said:
Thats it asroot. There is one other root exploit thats available for < 2.1. But once you get to 2.1 all known exploits are closed :(

Having said that, samsung dont prevent downgrading. Also we can flash the kernel without any root exploit, so we can root from init.rc anyway :)

Dont panic!
Click to expand...

Hi Kam187,
I know you're a busy person.. But, what method are you using to flash the Kernel?

I'm more than willing & happy to help test any idea's you may have.
 
kam187 said:
Thats it asroot. There is one other root exploit thats available for < 2.1. But once you get to 2.1 all known exploits are closed :(

Having said that, samsung dont prevent downgrading. Also we can flash the kernel without any root exploit, so we can root from init.rc anyway :)

Dont panic!
Click to expand...

Idea just Popped in my Head.... Though they Might not let Downgrading be possible, But if we do get the newer Kernel we can Remove everything in the .tar keeping the Header, thus letting us flash to a newer Kernel...

Once that happens then porting via system.img with yauff should still be fine :) wll, Hoping that is w/ odin restore when needed.. :)
 
you need to have ROOT for setcpu. You can also test manuall by cat into a file in /proc (forget which now).

You will need to have a 'su' file or 'sh' as root for root programs to work properly. See the post a little bit up about the alternative method.
 
I posted this elsewhere, but if you get tired of having to reset the USB debugging in settings everytime you reboot your phone then:

Edit the default.prop file in the the root of your phone and set the 3 flags there that are currently set to "0" and change to "1" and you won't need to go through all the settings to enable adb!

I just reverified this method by editing the files (I use "root explorer" from the Market, but you could edit it on your PC if you like and push the edited version back to your phone instead) and as soon as I rebooted the phone, I plugged in USB cable and was able to "adb shell" with no problems!:D

Just thought you guys would like to know this!;)
 
C:\androidsdk\tools>adb push try3 /data/local
485 KB/s (74512 bytes in 0.150s)
C:\androidsdk\tools>adb shell chmod 0755 /data/local/try3
C:\androidsdk\tools>adb shell
$ ./data/local/try3 /system/bin/sh
./data/local/try3 /system/bin/sh
[1] Killed ./data/local/try3 /system/bin/sh
$ /data/local/try3 /system/bin/sh
/data/local/try3 /system/bin/sh
[1] Killed /data/local/try3 /system/bin/sh


Do you know what's the problem?
 
You must log in or register to reply here.
Back
Top Bottom