Database Users

All Uses For ADB For NON-ROOTED Eris

I jumped the gun installed the original and the latest 2.1 leaks, so I am not rooted. I just recently learned how to use the ADB push feature in the tools of the Android SDK to install a custom boot animation and I'm stoked at how awesome it works.
I was wondering what all you can use the ADB push feature for on a NON-rooted Eris. Any help is greatly appreciated.
Thanks devs for all your hard work!

Adding custom boot images.

Thanks jcase! I was seriously hoping that there was there would be other things that I could use it for. Oh well, guess I'll just wait until the Official OTA 2.1 is released, then wait until you genius devs crack it open and get it rooted. Thanks again!

You can make a script to quickly install apps in mass.
#!/bin/sh
echo "Installing apps..."
./adb install apps/app1.apk
echo "app1 Installed."
./adb install apps/app2.apk
echo "app2 Installed."
./adb install apps/app3.apk
echo "app3 Installed."
./adb install apps/app4.apk
echo "app4 Installed."
./adb install apps/app5.apk
echo "app5 Installed."
echo "done"

how do i install ADB on my computer. I downloaded SDk and in the tools when i click or ADB or Emulator it opens and instantly disappears. im running windows 7.

interscion said:
how do i install ADB on my computer. I downloaded SDk and in the tools when i click or ADB or Emulator it opens and instantly disappears. im running windows 7.
Click to expand...
Click to collapse
....
EDIT: check your inbox interscion, I sent you a message in order to keep this thread uncluttered and on subject.

Android22 said:
....
EDIT: check your inbox interscion, I sent you a message in order to keep this thread uncluttered and on subject.
Click to expand...
Click to collapse
would you send me one too i have sdk setup and when i click adb a screen pops up and disapears ,,, help!! please please
trhanks

PM
Jimmie's 2.1 Eris said:
would you send me one too i have sdk setup and when i click adb a screen pops up and disapears ,,, help!! please please
trhanks
Click to expand...
Click to collapse
Sent, check your inbox...

I know this is an old thread, but I just got a replacement eris and i'm trying to avoid signing into the market before I root (for a completely clean install, probably doesn't matter, I'm just funny like that), in which case, I want to install 1-click root before I do anything. So, if someone could point me in the right direction to do an adb install on an un-rooted eris, that would be great.

demmo86rt said:
I know this is an old thread, but I just got a replacement eris and i'm trying to avoid signing into the market before I root (for a completely clean install, probably doesn't matter, I'm just funny like that), in which case, I want to install 1-click root before I do anything. So, if someone could point me in the right direction to do an adb install on an un-rooted eris, that would be great.
Click to expand...
Click to collapse
No need to bypass activation, skip account setup, Settings->Applications->Unknown sources, Settings->Applications->Development->USB Debugging.
Then this plus this:
Code:
adb install erisone010.apk
You are making unnecessary work for yourself - if you want a Nandroid backup of the factory ROM in a near virginal state, root the phone with OneClick (so that a custom recovery gets installed) - NOT including insallation of the engtools (or rootme, whatever it is called), and then perform a factory reset afterwards. (That will clear accounts & account data from the phone, and you can then boot to the recovery to make a backup of the virginal ROM).

bftb0 said:
No need to bypass activation, skip account setup, Settings->Applications->Unknown sources, Settings->Applications->Development->USB Debugging.
Then this plus this:
Code:
adb install erisone010.apk
You are making unnecessary work for yourself - if you want a Nandroid backup of the factory ROM in a near virginal state, root the phone with OneClick (so that a custom recovery gets installed) - NOT including insallation of the engtools (or rootme, whatever it is called), and then perform a factory reset afterwards. (That will clear accounts & account data from the phone, and you can then boot to the recovery to make a backup of the virginal ROM).
Click to expand...
Click to collapse
That's basically what I ended up doing (got impatient and didn't wait for a reply), except I did sign in to the market and picked up 1-click that way. Thanks for your reply though, to my question asked in an attempt to feed my OCD tendencies.
Sent from my FroyoEris using XDA App

Some Questions Before I Root

I've considered rooting and installing a custom ROM dozens of times ever since I got my Droid X back in August and I've finally decided I'm just going to do it, but i just want to double check a few things before I root my phone and install Fission:
1. I know that rooting voids your warranty, but if I have problems with my phone and I end up needing repairs, can I just unroot my phone back to stock and still have my phone be covered under the warranty?
2. Will my phone be secure rooted with a custom ROM? I don't want people having access to my personal info contact data, and my passwords.
3. If I Overclock to say 1.2 or 1.3 Ghz with ULV, will I have stability problems with demanding 3D games or other demanding apps?
4. After I root and install my Custom Rom, will I need to reactivate my phone or need to re-add my phone contacts/apps?
5. Will Z4Root work on system version 2.3.340?

I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk

I am having difficulty rooting my droid x. I am an android noob, but am a pretty savvy user. I used z4 (permanant) and it says it has been rooted when i launch the app. However i see no appreciable difference in access. My terminal still shows a $ prompt and i cannot uninstall verizons crapware. I used rage against the cage prior to z4 with similar results, but i was able to at least get temporary su access and install the bootstrap recovery and perform a system level backup. It reverted to user access after rebooting. Please help.

Superuser confirmation
alright, if you want super user privileges in terminal type "su", then once you hit enter, you get "#" instead of "$" To test if you have root access, first check app drawer for "Superuser" if its there, open an app that requires it, (wifi teather, root explorer, rom manager to name a few) you should get a pop up similar to this
http://www.google.com/imgres?imgurl...=1&ndsp=12&ved=1t:429,r:8,s:0&biw=888&bih=638
that would be a diffinitive confirmation that you have superuser permissions.
The way I remove verizons crap once rooted, is to use root explorer, go to system/app and find the .apk files you want to remove. There are lists around the forums what is safe to remove. I highly recommend simply renaming the files. For example, the 3g hotspot app is called mynet.apk, so I would just rename it to mynet.bak, or mynet.apk.bak, really anything that lets you know what it is, but removes the .apk extension.

Ok, I have confirmed su access, but am unable to rename any of the offending .apk's. I am simply told that the operation was unsuccessful. I have tried a couple of different file managers, as well as trying from a terminal, still no luck. I like 2.2.1 alright, but if i can't control what apps are running on my phone with root access, I may want another ROM. Any suggestions are appreciated, aswell as any links to a rom installer that is pc-less.

I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.

SharkBaitDave said:
I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.
Click to expand...
Click to collapse
If you are trying to rename apps in the /system/app portion of the OS, you will need to mount /system as RW first.
from terminal: mount -o rw,remount /dev/block/mtdblock4 /system
After it has been mounted read-write, you should be able to rename...
to remount as read-only: mount -o ro,remount /dev/block/mtdblock4 /system

zwade01 said:
I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.

Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.

galaga4991 said:
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.
Click to expand...
Click to collapse
I used rom manager to load apeX 1.3.1 and did not need to #228. I did not clear the user data or cache, but I do not know if that affected my results or not. Your mileage may vary.

stpvapor said:
Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.
Click to expand...
Click to collapse
I don't know that anyone has really done a side by side per say. Since you say you are apeX, then if you are looking for more ROM's that contain blur features, then I would recommend looking into ZapX Bazinga, or Fusion (from the same creator as Fission, but just with blur). I have not worked with any of the Blur ROM's so far...
If you are looking for ROM's that do not have blur, then the big ones are Liberty, Fission 2.5.7, GummyJar 2.5, and Rubix Focused 1.9.5. Liberty is the big one right now, because it just came out and combines the great talents of Kejar31 and Jrummy. Most others I believe are using Fission. All are great choices, as the dev's do some AMAZING work.
Each has their owns unique feel...so I woudl recommend just digging through each thread for their respective ROM's as they usually include what components are built into each ROM on the original post of each thread.
Hope this helps somewhat =)

another ROM to try is DarkSlide. It comes in both flavors, Blurred & Blurless. It's fast, stable & well supported. You only have to re-activate if you wind up bricking your phone & have to flash an SBF. My advice it to spend the $$ on DroidXBootstrapper (available in the market) to make a nandroid backup prior to flashing your new ROM. This way you have a base to go back to in the event you run into problems, or want to try multiple ROMS. One other suggestion is to rename each backup into something that will let you know what the backup actually is, like StockROMBU or the like.

Unable to Re-Root Droid 2 after Gingerbread OTA

Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker

Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?

Hope somebody comes up with an answer - same thing happened to me.

did you use the d3 root method? thats the only one that works 100% on gingerbread.

Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.

SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni

Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.

Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!

My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?

Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.

I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================

drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.

This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!

Awesome! Thanks!

Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!

Awesome!
Thanks! This worked for me as well! (after additional reboot)

Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.

Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew

awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer

It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.

[Gingerbread Root] Pete's Motorola Root Tools

This does not work with Droid X System Version .621.
(Information on this post was taken from Pete's website: http://www.psouza4.com/Bionic/)
NOTE: If you were rooted on the original OTA and took the update to .602 and lost root, read the 'Droid X' notes under the how-to.
-----------------------------------------------------------------------------
How to: One Click Root for Windows 7/Vista
1. Your phone must be connected via USB data cable to your computer and be recognized.
2. If your phone is connected, but not recognized, you may need to install one of these software drivers:
-Windows universal 32-bit Motorola drivers version 5.2.0
-Windows universal 64-bit Motorola drivers version 5.2.0
3. Download this one-click root package: PetesMotorolaRootTools_v1.08.zip
4. Extract the contents of the one-click root package to a new folder on your computer.
5. Make sure USB Debugging is enabled on your device. This should be under Settings -> Applications -> Development -> USB Debugging.
6. From the new folder on your computer, double-click on Pete's_Motrola_Root_Tools.exe to begin the root process.
7. Click 'Root My Phone'.
-----------------------------------------------------------------------------
Droid X Note:
Droid X Notes
Your phone may need to be in either charging mode or PC mode or you may need to toggle it a number of times for the device to recognized correctly.
If you are trying to root from the OTA Gingerbread update and you were previously rooted, you will probably experience problems with this root method because of the pre-existence of busybox and superuser.apk. For that reason, you may need to attempt both the script method (for Windows XP users) and program executable method (Windows Vista/7 users). If you are still having problems, please follow these instructions:
Open a Command Prompt in the folder where you extracted the one-click root package (see instructions for rooting). If you are using Windows 7, you can just use Shift+Right-Click on the folder you extracted the package and choose to "Open a command prompt here". For other operating systems or versions of Windows, you may require some DOS experience or need to Google how to change directories.
In the command prompt, type the following command:
adb shell
Click to expand...
Click to collapse
If you receive any kind of error, then you may not be in the folder where you extracted ADB.exe or you may need to reboot your computer, your phone, or check the connection. You should receive an ADB prompt ending with either a # or a $.
If the line ends with a $, then run the one-click exploit for Windows XP (even if you have Windows Vista or 7) and only complete step 1.
When you have adb shell ending with a #, type the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
Click to expand...
Click to collapse
Ignore any messages that warn you about the file not being found/missing. We're removing old copies of su/superuser which are causing this one-click root method to fail.
(credit: KevlarGibs)
Additionally, during the parts of the one-click root that reboot your phone, your phone will most likely reboot into recovery instead of into the standard Android lock screen. If this is the case, simply unplug the cable and reboot the phone manually. When you are finished rebooting, plug the phone back in again. Some people have had to reboot their PC too.
Finally, some users have mentioned that the root isn't taking affect right away for all apps. Eventually, after several reboots, the phone finally takes root. We're not sure why this is (I don't have a Droid X -- I'm just re-posting this information for brevity).
-----------------------------------------------------------------------------
Please try the Windows Vista/7 method first! It will work better for most Windows XP users.
Only use this method if the other has not worked yet.
http://www.mediafire.com/?pj5lk8u2s0zhqo8
----------------------------------------------------------------------------
Nothing you see here is my work. All credit goes to Pete and everyone he's credited. I simply created this thread on XDA using Pete's information.

Reserved for future information.

Awesome
Great tool, thanks so much!

Confirmed OTA
Works fine!!!

Awesome! Works perfectly!

Nice, I may give it a go (may sbf to 602 for a clean start)
D.

I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?

Hi I'm trying to unroot my x2 and it keeps saying Error: you are missing adb.exe, which was packaged with this program. The adb.exe is in the same folder as all of the other files i extracted to my restore folder. Any ideas?

I will try this at thanksgiving for my dad's X
It was rooted froyo and got the ota GB and wont root. Hopefully this works

choonami said:
I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?
Click to expand...
Click to collapse
Your preinstall is full. With Root Explorer go to preinstall/app/ and delete something (NFS). Reflash Clockwork mod. Then try again.
Sent from my PC36100 using XDA Premium App

I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?

Greatdane said:
I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?
Click to expand...
Click to collapse
Were you previously rooted on .602? If so, you may need to follow the Droid X notes.
Sent from my DROIDX using XDA App

This worked perfectly on my Droid X....thanks for making it so easy!!

Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks

skeeterpro said:
Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks
Click to expand...
Click to collapse
First of all, let me reassure you that anything you do to your phone can be reversed with a simple SBF. ^_^
Install ClockworkMod Recovery through Droid 2 Bootstrapper, then use ROM Manager to update it to the latest version.
There is plenty of things that you can remove that will cause issues =P It's pretty much trial and error, there are lists you can look up that will tell you what can and can't be removed, but regardless, always make a backup in CWM.
Sent from my DROIDX using XDA App

Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?

skeeterpro said:
Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?
Click to expand...
Click to collapse
You are correct.
Sent from my DROIDX using XDA App

I amaze myself sometimes. lol
Has anyone flashed working CWM via ROM Manager?
Can't say I have interest in flashing ROMs. Just want CWM for nandroid system backups actually.

STRANGE!
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?

noguru said:
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?
Click to expand...
Click to collapse
You should be able to find Superuser by using the search key. It's not really important to have, it just manages the superuser permissions. I think of it as a background app.
Sent from my DROIDX using XDA App

rooting A7+

I want to root my A7+ WITHOUT installing someone elses custom rom. I just want it rooted long enough that I can push GAPPS onto it. Is there any special trick with Elocity A7+ ??
Will I only be able to do this with earlier versions from Elocity?
The reason I want to do it this way is twofold.
1) I want EVERTHING to keep working.
2) I don't want Superuser snoops.
I can work with ./adb shell on this Linux or it would be even better for someone to show me how to COMPILE the newly released source from Elocity.
Thank you all !!
Dan

as shown in this thread http://forum.xda-developers.com/showthread.php?t=1431967 you could use Z4root.apk
It allows for temporary root
Cheers !

Yes Thanks . I did Z4Root PERMANENT. Did my thing and then turned off root .
I remembered just before coming back to post here. I never used ./adb shell push this time. Couldn't get RW with ./adb so I just copied from GAPPS folder to /system/app/ using Root Explorer.
First time I copied TOO MUCH AND IT WAS IN ENDLESS LOOP.
I repaired and then copied the important stuff...Installed Gmail and then rebooted.
All is well after reboot. But I had to go through Wizard again. Now running everything !!
Dan

another thing that i find funny about this new setup is that bluetooth and foursquare only run when while im rooted????
if i turn off root they dont work

So as I said in my last post, BLUETOOTH only works while rooted. (after having rooted once) So, I wanted to use BLUETOOTH with a new keyboard. I removed Z4root, but left Superuser running in the background. Well , once again, everything seemed to run great for a week, but then things went south. I was getting a reboot loop type thing, about 5 times before it would finally boot up.
I'm not sure, but is suspect this leaves you wide open to a virus or other malicious garbage. So now I'm back to factory with no Gmail or Youtube but I'm finding workarounds.
Dan