Database Develop

Shell command to halt/restart the Java VM?

A few times recently I've found that my phone will lock up, or go VERY slow, and I can't do anything with it. But if I plug it in and run ddms and Halt VM after about 10s it restarts Android and 20s later back to normal.
This is not a full reboot, don't need that. It's just restarting the Android VM.
My idea is that maybe I can have Tasker intercept incoming SMS with a command to run this program. I know in general this idea will work, but I wonder how long it might take for it to actually execute, or if the SMS will even be received in this state.

Try "hot reboot", now on the market. It kills the system server process.
http://forum.xda-developers.com/showthread.php?t=787611
Some background info (hope this answers all the questions above): the app kills the system server and reboots android without rebooting the linux kernel. It uses busybox to execute the command because not all devices come with the same set of linux/unix commands. So yeah, you need to have busybox installed otherwise you see only the beautiful animation. Furthermore, there are buggy busyboxes around so you may wish to install the newest from the market.
Click to expand...
Click to collapse
Not free anymore, but I have a backup of old version.

britoso said:
Try "hot reboot", now on the market. It kills the system server process.
http://forum.xda-developers.com/showthread.php?t=787611
Not free anymore, but I have a backup of old version.
Click to expand...
Click to collapse
Cool, thanks for that reference. Sounds like it's clearly possible from the command line. Probably as simple as killall java-something Just haven't looked or experimented yet.

Code:
adb shell
su
killall system_server
that worked for me. Took a few seconds before it hot rebooted.

[Q] I9000M: Rooting Froyo (JL2)

How do you root a JL2 Froyo on an I9000M?

I am looking how to root it also.

http://forum.xda-developers.com/showthread.php?t=803682

same here, superoneclick doesn't work. Tried all possible methods.
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
adb server is out of date. killing...
OK
Pushing rageagainstthecage...
adb server is out of date. killing...
OK
chmod rageagainstthecage...
adb server is out of date. killing...
OK
Running rageagainstthecage...
adb server is out of date. killing...
FAILED

Superoneclick works fine for me: http://goo.gl/DxOP7

What worked for me Bell I9000M JK4 or JL2 was to:
Disconnect Phone
Enable USB Debugging Mode
Shut Down Phone
Open SuperOneClick
Press ROOT
Wait until you see "Waiting for Device"
Connect Phone, wait for battery charging graphic
Turn On Phone
Let it do its thing, it should work all the way until you get SuperUser pushed to your device
If you get an USB error, try again from the start using another port

That's exactly what I did and had no problems. To get busybox installed, I opened titanium backup, clicked the "problems" button and let that app overall it.

has anyone found any other options to root other than SuperOneClick? I'm not sure if it's just my phone, but I start to get a lot of lag after using this to root...

For me, i just flashed speedmod inside the cwr there is a setting to root & install busybox

omg how does it take rageagainstthecage to run its thing.... it feels like its stuck

galaxywolf said:
omg how does it take rageagainstthecage to run its thing.... it feels like its stuck
Click to expand...
Click to collapse
make sure the phone is Awake, if it's in sleep mode (black screen) it wont do anything

How do I get a root file for my Bell Samsung Galaxy S Vibrant GT-I9000m with android 2.2 Froyo.UGJL2. I tried rooting it but I can't find any root file. I think I accidentally reformatted my internal sdcard. Pls. help!

I am having trouble using SuperOneClick, but it seems to be different from problems that other people are getting. I read through and watched the video. Everything said it was ok, and it seemed like all worked. I even got the "superuser" application installed. The problem is that su doesn't seem to work. If I go to a terminal window and type "su", I get Permission Denied. When I go to Titanium it says there is a problem with root. I tried installing busybox, and upgrading superuser, however these fail.
I just got my phone back from Samsung and they replaced the motherboard, and obviously put the new sotfware on it, however it seems to be the same 2.2 OS that everybody is talking about "JL2"
Has anybody seen this? any idea what might be happening?

I was able to answer my own question. I was able to root my phone using SuperOneClick by choosing the radio button for rageagainstthecage, instead of psneuter.

I have heard of many ppl having issues with Superoneclick and antivirus software preventing it from working properly or straight out removing it from the pc. Disabling the av software when you unzip and use the superoneclick may help.

[Q] nTelos Milestone Root Failed. Can't find Mount Path or /etc/fstab

Hey all, just purchased my Milestone 1 from my local provider nTelos. They are CDMA carrier located in the Shenandoah Valley of Virginia. Now, everything has been working fine for almost a week and a half now, but yesterday upon trying to update my Busybox install (from 1.14.x to 1.17.x) it completely killed my root. What I mean by that is no Barnacle, no Titanium Backup, no SuperUser privileges!
Even from the Terminal Emulator, if I try to su into the system after "rerooting" with Universal Androot, it says that I need to be suid for it to work.
Upon typing anything else, suid, root, suid su, etc. it says permission denied.
ADB is a hit or miss because I can obtain shell root using SUPEROneClick for a short time in order to push and pull things from the device. Thinking this would be a cure all, I tried rooting with SOC and found out that it cannot do this because it cannot find the mount path. Digging around further, I find out that my Android can't access /etc/fstab because it doesn't exist on Android devices do to no media drives.
So, is there anyone out there that can help me in any way possible? I've been digging online for over 24 hours for this and have yet to find anything helpful/useful for my situation. I'm thinking if I can reset the "su" permissions or remove Busybox and reinstall, it could fix things? Idk, any help is appreciated!

I reinstalled the GOT 2.2.1 ROM and also could not get BusyBox to work. Even though the phone is rooted, apparently, BusyBox cannot remount.
Anyway, I'm no longer using Titanium. So long as you have real root access, there are plenty of other back up apps that you can use (Root Explorer, Super Manager, etc.).
Try z4root by RyanZA for rooting your phone. I'm sick of BusyBox and its fussiness.

Found out that after flashing with the sbf file for my build A854, I was unable to join the nTelos network. Had to get a new phone, for free of.course
Sent from the Milestone

[Perma-Temp Root] Better Temp Root [From The Rezound]

This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.

con247 said:
This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
Click to expand...
Click to collapse
Just don't execute the program again after you have done it once, or it will boot loop the vivid to high hell. And you'll have to do a factory reset.
Sent from my HTC PH39100 using xda premium

Did that just happen to you? There is a 20 second timeout for a reason...

Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium

drewdatrip said:
Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
If you know how to use adb on Mac or Linux you can just run the equivalent command one by one
Sent from my ADR6425LVW using XDA App

Code:
timeout /T 20
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
adb push zergRush /data/local/
adb shell chmod 755 /data/local/zergRush
adb shell /data/local/zergRush
adb wait-for-device
adb shell sleep 1
adb remount
adb shell mkdir /system/xbin
adb shell mount -t tmpfs none /system/xbin
adb push busybox /system/xbin
adb shell chmod 4755 /system/xbin/busybox
adb push su /system/xbin/su
adb shell chmod 4755 /system/xbin/su
adb shell cd /system/xbin
adb shell /system/xbin/busybox --install -s /system/xbin
adb install Superuser.apk
Does nothing different from the original scripts that were posted here a month ago.

Read my OP bud. I have downloaded all of the ones posted in your Vivid section and made sure. This one stores the root to a ramdisk that lasts until a reboot instead of /system rw mount going away after a short time.

I had a problem pushing this to the phone at first. Then I made sure the screen didnt time out and everything worked fine for me....just a little FYI incase someone runs into this problem as well.
Thanks

Didn't work for me.
I followed the instructions to the letter, and when I ran the batch file, there was no 20-second wait; it started immediately. It found the phone, went through the "sending speedbots" or whatever, and then rebooted the phone. It then re-ran ADB with "wait-for-phone" and the phone got stuck in a bootloop. I kept it connected to the PC and did a battery pull, and as the Beats Audio logo came up during boot, the command window on my PC flashed some more text and then closed. I let the phone completely boot and tried to run Titanium Backup and I get an error indicating it doesn't have root access. Any thoughts?
BTW - running Windows XP on a Dell Optiplex 755 with 4GB of RAM.
UPDATE - I tried performing the whole process again, and it ran for about 10 seocnds then just closed. So, I tried again, and it went through the process, up to rebooting my phone and indicating "wait-for-device," but the phone never completely shut down; it hung at that shutdown point where the entire screen is black but you can see a bit of lighting. So I did another battery pull and turned the phone on again, and after about 15 seconds, the command window scrolled a bunch more stuff and then closed and the phone continued to boot. It did manage to boot this time without a battery pull and no loops, and SU is there, but when I run Titanium Backup, I still get a "phone not rooted" error.
Looks like I'm waiting for perm root. Thanks for your work though. I'm glad it worked for others. Viva la Android!!!!

FYI: I did disable bloatware using a script, within the same command prompt window right after achieving temporary root.
The bloatware APPS and widgets remain disabled even after full reboots, including a battery pull.
I'm very grateful to temporary root, since it allows to disable most of the pre-installed bloatware.

Went from bad to worse.
I ran this on my phone last night, and even though it didn't temp root my phone, it still ran fine for the rest of the night and all day today. I decided to reboot the phone before I went to bed and now I am stuck in some kind of loop. The phone actually boots to the lock screen, and I can unlock it, but some of the icons on my homescreen don't load and the phone becomes unresponsive after about 10 seconds and then reboots. It's done this about 10 times and a battery pull does not resolve the issue. Help?

Have you tried a factory reset ? After that it may allow you to run the temp root. At least that is what happened once when I tried it.

Well through trial and error, I have found out several things...
1. The temp root that comes with the Rezound Clean Tool is the only temp root tool I can get to work.
2. Even if you have BT turned on before using the Rezound Clean Tool, turning it off permanently disables it until a reboot is done.
3. It is common for the Rezound to suddenly start boot looping, even if you haven't done any rooting or anything. This is caused by the connection type in Phone Properties randomly changing to a type that is incompatible with the Verizon SIM. (Google search "rezound boot loop" and you'll find the fix quite easily.) Also, removing the battery cover may disable the antenna but only a SIM-less boot will stop the boot looping so that the communication type can be set back to what it should be.
4. I still love this phone. It is the best phone on the market today; it has the fastest processor available from any carrier and has the most internal memory of phones that allows for removeable storage.
Thanks to all the devs for their hard work - I can't wait for perm root and custom ROMs!!!!

[ROOT]Help with 7.3.1 KFHD 7"

So I have run into several problems using several different methods, none of which have worked properly and I really need some help. Now, I am by no means stupid when it comes to computer stuff but I am not a programmer nor any sort of software engineer. I understand much of the command line stuff and some simple code but I don't understand why nothing I have tried is working. So let me list the problems I've run into in my attempts to root my KFHD 7":
Root Many Android:
I am using v28 (which I believe is the latest and is reported to work on my device hardware and software).
I am unable to run the batch file as an administrator which I believe is the problem that results in the "permission denied" errors when trying to push the packages like superuser and busybox.
I am certain I have followed the tutorial to the letter so I don't know where I am going wrong. I can open the command window as an admin and cd to the C:\Root and run the batch but that doesn't fix the permissions errors.
Qemu:
I am using the latest version.
I select option 1 to root and it runs through the processes but nothing works and it just goes through several reboots so I am assuming it is running into the same issues as RMA, above.
KFFirstAide:
I am using the 64 bit as per my system. I run through option 21 to root my device using method 2 (Preferred).
It shows some success in that I can see the apps BusyBox Installer and Root Checker, however it does not push the rest of the packages necessary and this is evident by when it says I should receive a SuperSU or SuperUser popup, nothing happens and so the rest fails, though it says the root check passes in the final step.
So now I ask, is there a better way or something I am doing wrong with my Kindle Fire HD 7" 7.3.1?
Thanks in advance.