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

Root Persistant root

The 'playlogo' hijack happens _after_ init.rc. That means all the services and system proceses are already setup and running. And of course all the filesystems are already mounted.

You need to kill each process (that you're custom rom won't use), extract the new files over to system, and delete any u want to delete, and then run the new versions of those processes.

You also need to make sure none of the 'old' processes screw up anything on /data

Its all possible, but it needs work and a physical device to work on, which i dont have!
 
Thanks for the video. I am getting closer to understanding but something is still not write. I installed the sdk and the adb drivers. I can now key in androidsdk in the commands. i type "cd androidsdk/tools then adb devices and my phone shows up as "sgh-t939". I dont know what to do next.
 
bigch0ps said:
Thanks for the video. I am getting closer to understanding but something is still not write. I installed the sdk and the adb drivers. I can now key in androidsdk in the commands. i type "cd androidsdk/tools then adb devices and my phone shows up as "sgh-t939". I dont know what to do next.
Click to expand...

ok, to make things easier, add the android sdk tools directory to the path variable. First make sure its somewhere easy to get to no spaces, like c:\androidsdk\tools then on vista or 7

Right click computer > Properties
Advanced System Settings
Environment Variables
Under system variables select PATH click edit
at the end add ";c:\androidsdk\tools" without the quotes

open a cmd prompt, and type adb devices if you see your device, you are all set and good to go,

After that download the try3 file in the first post, put it in c:\ and do cd c:\ then just follow the commands in the first post
 
bigch0ps said:
Thanks for the video. I am getting closer to understanding but something is still not write. I installed the sdk and the adb drivers. I can now key in androidsdk in the commands. i type "cd androidsdk/tools then adb devices and my phone shows up as "sgh-t939". I dont know what to do next.
Click to expand...

Well since you are able to see your phone using adb devices all you have to do is put the try3 file in whatever folder you are in.

For example your command promt reads: "C:/androidsdk/tools" then put the try3 file in C:/androidsdk/tools and then start issuing the commands listed in OP.
 
I got all the way to reboot and then nothing happened. Is my phone supposed to reboot ? It seems like nothing happened. After typing reboot I tried getting back to adb shell and couldn't.
 
echo#!/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: not found

hmmm

ls /system/bin/p*
/system/bin/ping
/system/bin/playlogo
/system/bin/playlogo_real
/system/bin/playmp3
/system/bin/pm
/system/bin/port-bridge
/system/bin/printenv
/system/bin/ps
 
You need to type this exactly line by line:

echo "#!/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" > /system/bin/playlogo

Then you can do:

cat /system/bin/playlogo

to check its correct. It should return:

#!/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


[You forgot the " in the command]
 
Awesome


# cat /system/bin/playlogo
cat /system/bin/playlogo
#!/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
#
 
even after setting it in the path I'm getting " not a recogonized command"

when I run it straight from the path I get the error " no device found" USB debuging is on and the fone is set on PC studio. I'm getting the same thing on all three of my box's Vista XP and ubuntu.
it took some major tweeks to get that far on ubuntu. So if I can get this running on my vista machine I would be happy. also the only SDK I see to DL is the r3 version is that the one I need it's the one I have installed. If not how about a pointer to 1.5

PS: 1st post I've been lurking and reading since the 18th when I got the fone. and registered on the 23rd. but it seems NOW I need some help.

later
Rich
 
armalite_ar50 said:
even after setting it in the path I'm getting " not a recogonized command"

when I run it straight from the path I get the error " no device found" USB debuging is on and the fone is set on PC studio. I'm getting the same thing on all three of my box's Vista XP and ubuntu.
it took some major tweeks to get that far on ubuntu. So if I can get this running on my vista machine I would be happy. also the only SDK I see to DL is the r3 version is that the one I need it's the one I have installed. If not how about a pointer to 1.5

PS: 1st post I've been lurking and reading since the 18th when I got the fone. and registered on the 23rd. but it seems NOW I need some help.

later
Rich
Click to expand...

Do you have the proper drivers installed?

http://androidforums.com/samsung-behold-2/22626-usb-drivers.html
 
THANK YOU CHAOSCENTRAL!!!!!!!
that was it. missing the drivers. I wonder why the android SDK site doesn't have these? So now I'll be off to root the fone and hopefully I'll get this working in juanty soon along with the wintell boxes.

once again thanks
Later
Rich
 
Once again THANK YOU!!!!
It worked perfectly the 1st time through. su gives me the # instead of the $
upon reboot of the fone.
There are some intersting directories on this thing.
once again thanks.
later
Rich
 
I have finally figured everything out. The only problem I am having now is... Once i type reboot it shuts my phone off but my phone doesnt restart. I have tried this a few times and the same thing happens. What am I doing wrong???
 
When I did mine I did a hard boot (pulled the battery) I didn't want to chance a soft boot. (power down/restart) try it with a battery pull. you should be able to hard boot it. also I didn't disconnect the USB cable upon reboot. but that didn't seem to matter as it's been unplugged a few time since and I still have root when I type su.
SO this is persistant and it does work. my barrier was the USB drivers.

I know a lot about linux slackware and ubuntu but this is my 1st android fone. not my 1st fone hack but my 1st android hack. OH WELL gotta start somewhere.
Once again thanks to the pple who wasted countless hours like me getting this working.
later
Rich
 
well I guess I rooted the phone.. but i had to do a factory reset because it was extremely laggy and my homescreen shortcuts kept dissappearing. I guess its just not going to happen. This sux
 
bigch0ps said:
well I guess I rooted the phone.. but i had to do a factory reset because it was extremely laggy and my homescreen shortcuts kept dissappearing. I guess its just not going to happen. This sux
Click to expand...
rooting should never make that happen
all its doing is allowing elevated permissions to the device for more access and potentially improved functionality
 
i somehow bricked my phone doing this last night. I had to exchangr it. Every program firce closed and the phone wouldnt do anything.
 
You must log in or register to reply here.
Back
Top Bottom