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

Root The Moment has been rooted!!(?)

Zefie. Don't sweat it much. It doesn't seem like root is actually helping with anything yet, or were you able to delete the pre programed apps we dont use?

I think I would be with you though. Not want to play till we have a way to restore. There are some apps I want to delete, but I'm not sure if they are used with other things. like moxie mailer, it opens, but I dont use it. It transfers data also. Not as much as I mail though. Who knows.
So much crap. So much to do.

thats a lot of typing. I could do it with the instructions, but some of it is a bit vague, like the stuff about the SD card, makes no sense to me. he talks about makign some folders.
Then all of a sudden talks bout some files from here or there and i have no idea how they got there.
 
Hey Zefie or anyone else. Have we figured out how to mount the fs as rw yet. I'm kinda wanting to remove some crap (bejeweled) but haven't figured out how to remount as rewritable yet. Thanks
 
Hey Zefie or anyone else. Have we figured out how to mount the fs as rw yet. I'm kinda wanting to remove some crap (bejeweled) but haven't figured out how to remount as rewritable yet. Thanks

Yes, the instructions for rooting the phone contain a step where the fs is remounted r/w. If you don't want to read the instructions, use the mount command without any arguments to get the device and options, then do a mount remount command with the same options to get it in rw mode.

I removed bejeweled, nascar and nfl apps by removing them from the /system/app directory. (I just moved them up to the parent directory so that I'll still have them if I ever need them for something.)
 
Just curious how much more anyone who has rooted it has been able to do? Of course removing the default system apps but anything else yet? Has anyone tried the 2.0 SDK yet and writing it to the moment?
 
I guess that'd depend on if the app that allows other apps to be installed to the SD card needs persistent root access, or just when the app is being installed. As I understand it with the current root method, a lot of things don't function properly while root is accessible. Luckily it looks easy enough to reboot and get everything back to normal, but then root access is lost.
 
Been reading up on rooting phones in the past and I understand most access that's gained by doing this. I'm just wondering if its necessary to do something simple as install your own apps from your PC?? Or there another way to install .apk files from your PC without rooting ? Thanks.
 
Been reading up on rooting phones in the past and I understand most access that's gained by doing this. I'm just wondering if its necessary to do something simple as install your own apps from your PC?? Or there another way to install .apk files from your PC without rooting ? Thanks.

I'm not sure exactly what you're asking, but it's possible, without rooting, to transfer APK files from your computer to the phone's SD card (using the USB cable) and then using an app like AppManager (free in the Android Market) to install the APK's off the SD card (though they are installed into the internal memory).
 
@Wags4:
Also, you'll have to allow Non-Market Apps to be installed following this step:
Menu > Settings > Applications > Unknown sources (check-enable)

Hope you realize installing non-Market apps is risky.
 
I'm not sure exactly what you're asking, but it's possible, without rooting, to transfer APK files from your computer to the phone's SD card (using the USB cable) and then using an app like AppManager (free in the Android Market) to install the APK's off the SD card (though they are installed into the internal memory).

Thanks for the help, didn't mean to hijack this thread at all but this seemed like it should be simple. When i looked before I was just search market for wrong application. I'll test now thanks!
 
Has anyone attempted a temp root (non persistant) and ran into a boot loop brick?!? I have hit it 3 times now and been forced to reflash with ODIN... i am guessing when we insert btld_testmode it is always hiding in the background..

I am mainly interested if anyone has successfully temp rooted their phone, then booted the phone with the usb cable plugged in and pdanet open on their computer...
PDAnet uses adb (same as the terminal we are using to access root function) and my guess is it causes a boot glitch when this scenerio happens.. it has happened 3 times with me (i am to afraid of having to redo all my settings yet again to test this with a fresh flash, root and pdanet but i think i am going to have to eventually) unless someone else has done this and not hit a boot loop brick... PDAnet should say "device connected" on the computer when the phone is booting and my guess is this is when the brick happens.. then after that it breaks the boot script until you reflash it...
 
Moved thread here because the topic are very similar, you will also likely find an answer with those monitoring this thread.
 
Has anyone attempted a temp root (non persistant) and ran into a boot loop brick?!? I have hit it 3 times now and been forced to reflash with ODIN... i am guessing when we insert btld_testmode it is always hiding in the background..

I am mainly interested if anyone has successfully temp rooted their phone, then booted the phone with the usb cable plugged in and pdanet open on their computer...
PDAnet uses adb (same as the terminal we are using to access root function) and my guess is it causes a boot glitch when this scenerio happens.. it has happened 3 times with me (i am to afraid of having to redo all my settings yet again to test this with a fresh flash, root and pdanet but i think i am going to have to eventually) unless someone else has done this and not hit a boot loop brick... PDAnet should say "device connected" on the computer when the phone is booting and my guess is this is when the brick happens.. then after that it breaks the boot script until you reflash it...

I successfully temp rooted and then used PDAnet afterwards, I think that you just need to make sure the adb.exe process is stopped on your task manager before starting PDAnet. Never had a boot loop happen to me though luckily.
 
I successfully temp rooted and then used PDAnet afterwards, I think that you just need to make sure the adb.exe process is stopped on your task manager before starting PDAnet. Never had a boot loop happen to me though luckily.
That is actually a really good point that i didn't think about.. ADB doesn't close down when you kill the command prompt (once the daemon is running you have to manually shut it down)... Wonder if that could be the cause of the boot loop.. PDAnet also uses an ADB connection, that is why i assumed it was the cause..
 
Well... now I have the boot loop problem, but I haven't even thought about rooting, much less done it (I intended to remove some stuff, but was going to wait until after the holiday mess so I had some time to concentrate on what I'm doing). I think it was Startup Auditor... funny thing is it was fine while it was installed, but I uninstalled it (after reading about it causing this exact problem) and the first time I restarted the phone after that... bam... boot loop. Very annoyed. I'm not even going to try to re-image it... I'm just going to take it to Best Buy and get an exchange as I was having some issues which seemed specific to my phone anyway.
 
Well... now I have the boot loop problem, but I haven't even thought about rooting, much less done it (I intended to remove some stuff, but was going to wait until after the holiday mess so I had some time to concentrate on what I'm doing). I think it was Startup Auditor... funny thing is it was fine while it was installed, but I uninstalled it (after reading about it causing this exact problem) and the first time I restarted the phone after that... bam... boot loop. Very annoyed. I'm not even going to try to re-image it... I'm just going to take it to Best Buy and get an exchange as I was having some issues which seemed specific to my phone anyway.
THERE IS A VERY BIG ISSUE WITH STARTUP AUDITOR!!!

This has been discussed on another board and has been determined this will Brick (boot loop) your phone because of the very nature of it forceclosing programs during the boot sequence before they even have a chance to startup without root access (the phone keeps trying to start up the program and startup auditor keeps closing it and the OS wont complete until it starts it up, but startup auditor wont let this happen and thus you get a very nice loop...)
As for the boot loop due to root.. i have a feeling it is due to the daemon still running without any commands.. going to test this further and see what i come up with..
 
Where's the other thread? I'd like to know if it usually causes this problem AFTER uninstallation... IMO that's even worse than causing it while it's installed.
 
i use PDAnet everyday at work (work network blocks stuff so I grabbed a second computer and 4th monitor to get around that) i've used both persistant and temp. right now just using temp root. my PC at work doesn't have adb on it right now. but at home i connect my phone to my laptop at night to charge and it has adb on it. i've never used pdanet on my home laptop. i've never used PDAnet and adb on the same computer(which is easy for me, i have 9 computers at home(don't ask))
 
i use PDAnet everyday at work (work network blocks stuff so I grabbed a second computer and 4th monitor to get around that) i've used both persistant and temp. right now just using temp root. my PC at work doesn't have adb on it right now. but at home i connect my phone to my laptop at night to charge and it has adb on it. i've never used pdanet on my home laptop. i've never used PDAnet and adb on the same computer(which is easy for me, i have 9 computers at home(don't ask))

Thanks for this clearification.. I am really trying to nail this boot loop problem down, but it is like nailing jello to the wall...

I root and use pdanet on the same machine.. this might be a problem (having the adb daemon in pure form and having the adb daemon through pdanet).. I know what you mean abotu 9 computers.. currently working with 4 right now (dell e1505 laptop fully speced, samsung n130 netbook, dual prestonia xeon server with dual monitors, and an old old dell latitutde laptop that i use as a ubuntu terminal)..
I know the pains of work blocking everything (i work for the state of florida).. I recently found out how to sign onto aim on my work computer (have to go through gmail and use their aim client extension.. but atleast it works)
 
yeah like bejeweled demo. i mean, why would they even put that on there?

I don't mind that it's there but I do mind that I can't take it off without doing risky hacks on the phone. Why make it so complicated to get the dam thing off? Anything that's a demo should have a "remove this demo" feature in the settings.
 
Back
Top Bottom