Persistant root - Page 3

deathclutch · January 20th, 2010, 10:22 AM

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?

devrdander · January 20th, 2010, 10:40 AM

Quote:

Originally Posted by deathclutch

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?

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.

deathclutch · January 20th, 2010, 11:00 AM

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

devrdander · January 20th, 2010, 11:16 AM

Quote:

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

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.

deathclutch · January 21st, 2010, 09:16 AM

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

Mr S · January 21st, 2010, 09:45 PM

Quote:

Originally Posted by devrdander

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.

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.

Mr S · January 22nd, 2010, 09:15 PM

ended up using Odin back to stock, it seems as if it works better than before.(well, except for the battery)

behold_this · January 28th, 2010, 10:17 PM

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.

Eugene373 · February 16th, 2010, 02:13 PM

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

kam187 · February 16th, 2010, 03:26 PM

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.

Eugene373 · February 16th, 2010, 03:31 PM

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

Quote:

Originally Posted by kam187

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.

yatimameiji · February 16th, 2010, 03:33 PM

I'm curious, what exactly is try3?

kam187 · February 16th, 2010, 04:18 PM

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.

Nu11u5 · February 16th, 2010, 05:46 PM

'try3' is actually called 'asroot2' and is part of the flashrec app, used for flashing custom recovery images on other android phones.

http://zenthought.org/content/project/flashrec
flashrec - Project Hosting on Google Code

The website reports that it doesn't support Android 1.6+ as since then the root exploit it uses was patched out of the kernel. When the SB2 finally does get an official update the existing root method will no longer work.

Eugene373 · February 16th, 2010, 07:39 PM

Got SU ( 33.8k ) file working with the SU apk..

Proof are in the Pic's..

Su working with SU file

on Twitpic & SU working with SU APK on Twitpic

kam187 · February 16th, 2010, 08:35 PM

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!

Eugene373 · February 16th, 2010, 08:37 PM

Quote:

Originally Posted by kam187

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!

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 · February 17th, 2010, 10:25 AM

Its all explained in this thread so anyone can pick it up and have a go

http://androidforums.com/samsung-behold-2/45441-behold-2-flashing-kernel-security.html

Eugene373 · February 17th, 2010, 10:26 AM

Sorry man, I missed that Post ( Not sure How )... Thanks again for the speedy reply..

Quote:

Originally Posted by kam187

Its all explained in this thread so anyone can pick it up and have a go

http://androidforums.com/samsung-behold-2/45441-behold-2-flashing-kernel-security.html

BH_MAN · February 23rd, 2010, 11:45 PM

Quote:

Originally Posted by kam187

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!

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

texasmade · February 24th, 2010, 03:36 AM

has anyone had anyluck with set cpu i didnt anyhelp would be appreciated

chadmd23 · February 24th, 2010, 08:16 AM

Quote:

Originally Posted by texasmade

has anyone had anyluck with set cpu i didnt anyhelp would be appreciated

I don't think the chip speed is the bottleneck with this phone.

kam187 · February 24th, 2010, 03:44 PM

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.

jklong03 · March 8th, 2010, 01:29 PM

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!

Just thought you guys would like to know this!

teknick · April 1st, 2010, 02:55 PM

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?

megabiteg · April 1st, 2010, 03:02 PM

Quote:

Originally Posted by teknick

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?

Did you perform the whole instructions listed in the first page to the last dot? It seems to me, that your missing a whole lot of steps, please take a look at the first post in the first page and compare.

BH_MAN · April 1st, 2010, 03:03 PM

Quote:

Originally Posted by teknick

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?

Just Flash This Kernel with Odin if you are Using the 1.5 base

OLD Revision 2
Shell Enabled Root-Full ADB Access-Root Permission's for App's Set By User
Root For App's On stock Rom needs SU in /system/bin & chmod 04755
Here's the Odin Ready Kernel Download. This is the Kernel Only. Works with all Known Ports & Factory Rom!
Root_boot.tar

teknick · April 1st, 2010, 03:30 PM

I ha ve Samsung Galaxy

firmware version 1.5
kernel version 2.6.27

I have perform all instruction!

Do I put your kernel?

paul89 · April 1st, 2010, 03:39 PM

Quote:

Originally Posted by teknick

I ha ve Samsung Galaxy

firmware version 1.5
kernel version 2.6.27

I have perform all instruction!

Do I put your kernel?

ya I don't think it will work on your Galaxy??? you do realize this is a Behold2 thread?

teknick · April 1st, 2010, 03:41 PM

Oh!! Oky!!
Thx!

BH_MAN · April 1st, 2010, 03:41 PM

Oh, it's a Galaxy Phone... No it wont work... Sorry man.

kam187 · April 2nd, 2010, 03:45 PM

Not necesary for the galaxy

Google flashing a custom recovery and u can enable/disable root from there.

The same exploit should work on the galaxy, but you're probably running a newer kernel containing patches which closed the hole.

Calisto1224 · April 2nd, 2010, 07:15 PM

I'm really a newbie this is my first android and I like it but would love it if I could get root so I can delete some apps or whatever there name is that it has. I have been searching for weeks and tried all the posts but still can't get it to work. Is there a step by step post that I haven't found? Oh and I would like to root my phone but I like t/wiz and the camera. I can't even get the computer to recognize the phone I have the downloaded the behold 2 usb drivers and android sdk. Please, any help is very appreciated .

aequitas3 · April 12th, 2010, 09:00 AM

@calisto

what OS you running on your computer?

Calisto1224 · April 17th, 2010, 10:02 PM

OK so I have followed this video that I found in the unlckr.com I have done it 7 times already and when I write everything at the end when I have to write the 3 exit words I can only write two. On the second one the comand promt close. Can't figure out what I'm doing wrong....Please any suggestions

Calisto1224 · April 17th, 2010, 10:09 PM

i have vista and my computer is 32 bit

inaz4sun · April 21st, 2010, 06:14 PM

Can the Behold II with the most recent patch from Samsung/TMO still be rooted (without flashing the ROM)?

BH_MAN · April 21st, 2010, 07:50 PM

Quote:

Originally Posted by inaz4sun

Can the Behold II with the most recent patch from Samsung/TMO still be rooted (without flashing the ROM)?

No, as they close the exploit we was using to Gain root.

krasticx · September 5th, 2010, 11:53 AM

I will repost this on a new thread if I don't get a response, but I am having a problem of when I type

adb push try3.dat /data/local

it returns

568 KB/s (0 bytes in 75000)

568 KB/s varies each time the 0 is always there and 75K I am just rounding as to what that is. I am assuming some sort of time out. any help or suggestions...I am doing this on windows xp and I added the environment variable. and the proper driver is installed.