Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shravan #3

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Shravan #3

wants to merge 2 commits into from

Conversation

nextgensh
Copy link

On some devices when the adb deamon is killed after changing the
ro.secure key value pair, the adb link freezes on the terminal and
the server manually by running a adb kill-server. After connecting
to the adb shell again the user gets only upto 20 seconds of root,
before the device restarts itself and reboots in normal more with
ro.secure set.
In this modified version we do not depend on the device to restart the
adb process, but do it manually. Does this is much more reliable method
as some devices are programmed to restart or freeze when the adb server
is killed manually.

LGP970 was one such device. Running the modified version of this code
fixed the problem.

nextgensh added 2 commits July 8, 2012 22:47
After restart the user is dropped back into the normal shell.
This code modifies the original psneuter code written scotty2.
Immediately after the adb deamon is killed the code forks, and creates another
adb deamon process. Hence when the user reconnects to via adb again there is
already a deamon running and the phone does not restart. The user is dropped
into the root shell.
Tested on -
LGP970 : Froyo 2.2 with LG version v10d
 	modified:   README
	modified:   psneuter
	modified:   psneuter.c
ro.secure key value pair, the adb link freezes on the terminal and
the server manually by running a adb kill-server. After connecting
to the adb shell again the user gets only upto 20 seconds of root,
before the device restarts itself and reboots in normal more with
ro.secure set.
In this modified version we do not depend on the device to restart the
adb process, but do it manually. Does this is much more reliable method
as some devices are programmed to restart or freeze when the adb server
is killed manually.

LGP970 was one such device. Running the modified version of this code
fixed the problem.
I will test this on more devices and keep the README file updated
accordingly.
	modified:   README
	modified:   psneuter
	modified:   psneuter.c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant