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

Root [Release] Android 2.2 Froyo for the Droid X

I had root in 2.1 and did the copy thing of the su file and updated before the news got out you had to do the 'mv' thing... NOT the cp thing
 
I'm on 2.2 now. Everything from 2.1 seems to be intact other than no root. The UniversalAndroot still thinks I have root however... even 1.6.2. The OS has a different view.

Rebooting now to see who will prevail.... :)
 
hdokes said:
I'm on 2.2 now. Everything from 2.1 seems to be intact other than no root. The UniversalAndroot still thinks I have root however... even 1.6.2. The OS has a different view.

Rebooting now to see who will prevail.... :)
Click to expand...

lolololol:):):):)
I was under the impression that you were on 2.1 and rooting to get ready to go to 2.2.

You can't root 2.2:D

Now if you want me to walk you through everything to get root on 2.2, then I can do that
 
ummmmmm... how you say.... uh oh.

Rebooted and am now stuck at the Moto Logo again like last night when I updated.

My apologize droider13... thought I had already indicated I was on 2.2. Is that to suggest that universalandroot doesn't work for the 2.2 then?

And yes... I would really like to root it if you have instructions.... just as soon as I loose the moto logo and get back to a screen.

Another side note... it's like my droid is in a coma. I know it's alive and still thinking inside... it just can't express itself visually. I ultimately get notification beeps and the audible "Verizon Wireless" but no screen... just the moto logo... did this last night when I rebooted after updating to 2.2. Instead of spending the time going back to 2.1 I called it a night... came back to it this morning... pulled battery and cable... put battery back in... and damn if it didn't awake from it's coma and begin to visually communicate with me again... you shoulda been here... brought tears to my eyes.... it was a kodak moment!

Well it's doing it again it appears!
 
hdokes said:
ummmmmm... how you say.... uh oh.

Rebooted and am now stuck at the Moto Logo again like last night when I updated.

My apologize droider13... thought I had already indicated I was on 2.2. Is that to suggest that universalandroot doesn't work for the 2.2 then?

And yes... I would really like to root it if you have instructions.... just as soon as I loose the moto logo and get back to a screen.
Click to expand...

well actually the next step is wiping data and cache in recovery, does rsd lite work for you
 
what is rsd lite? Is this a terminal type program? If so... I have one on the unit which gets me to a prompt... but no su command.

If it is a host app in windows.... I lost communications with the droid through the usb pc mode once I upgraded to 2.2.
 
Cool... I've downloaded it. I do have usb 'mass storage' connectivity to the droid so I can get the file to the sdcard... however... till moto starts playing nice with me again and gives me a screen I'm kinda stuck here I think.
 
hdokes said:
Cool... I've downloaded it. I do have usb 'mass storage' connectivity to the droid so I can get the file to the sdcard... however... till moto starts playing nice with me again and gives me a screen I'm kinda stuck here I think.
Click to expand...

no its all through the computer:D
 
ok... loaded and running. Droid is tethered to the usb port. I assume that since there is only one exe in the RSD directory... that would be the file I run?
 
hdokes said:
ok... loaded and running. Droid is tethered to the usb port. I assume that since there is only one exe in the RSD directory... that would be the file I run?
Click to expand...

did you put the patch file in its program files. And it should of made a shortcut but yeah run it that way
 
I did put the patch in... it probably made a short cut but I try not to look at the desktop to much... it hurts my eyes....... :) It's like having to look at your own bedroom.... socks all over and everything...

The tool is up and open... am curious to see how this is going to work
 
hdokes said:
I did put the patch in... it probably made a short cut but I try not to look at the desktop to much... it hurts my eyes....... :) It's like having to look at your own bedroom.... socks all over and everything...
Click to expand...

does it recognize your phone and how familiar with adb are you

1000th post:D:D:D
 
congrats on the 1000th post... figure if I talk to you long enough here I will hit it too!!! then we can go out and celebrate!

RSD does not appear to be re-cog-a-nizing the droid. As I indicated I lost contact with the droid from Win7 once I upgraded to 2.2. The drivers on win7 fail to load now. Is there a fix for that?

I have used adb on a superficial level... light stuff... however... I am a programmer from way back.... does the term 360/370 assembler mean anything to ya? Also an electronics ing-g-neer so I have a pretty fair understanding of what's going on .... lay it on me.
 
hdokes said:
congrats on the 1000th post... figure if I talk to you long enough here I will hit it too!!! then we can go out and celebrate!

RSD does not appear to be re-cog-a-nizing the droid. As I indicated I lost contact with the droid from Win7 once I upgraded to 2.2. The drivers on win7 fail to load now. Is there a fix for that?

I have used adb on a superficial level... light stuff... however... I am programmer from way back.... does the term 360/370 assembler mean anything to ya? Also and electronics ing-g-neer so I have a pretty fair understanding of what's going on .... lay it on me.
Click to expand...

well...I got to catch some sleep but I will get back to ya in the am
the goal is to
wipe data and cache in recovery
flash the sbf
re-root
do these commands in adb
"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
"mv /system/bin/su /system/xbin"
then reapply the update
:D:D:D:D
sorry
but have fun:D
 
SHANE!!!! COME BACK!!!!

hehehe... Always wanted to use that line. n/p droider13..... I was gettin ready to do the same... have to make the donuts in the early mornin.

Pretty much what your sayin is I gotta start all over huh. Oooooh... allllll right!.

Maybe my droid will be out of it's coma in the mornin too.

I heard tale that one could unload the moto drivers in windows 7 and reload them and it would talk to the droid again... just did that.... they ain't talkin.


..... later that evening.....

HA! They's talkin again. For anyone that has this issue... get a hold of MotoConnect 1.1.31 which has version 4.7.1 drivers for the usb. That took care of it. Holler at me if you can't find it.

Oh! And droid is out of it's coma again.... Waited an hour or so.... pulled battery and plugged it back in and presto! I'm so happy I could just curl up and watch fried green tomat....... woo.... what happen there... did I black out?... yeah... that's it... I blacked out... I thought I was my wife there for a moment...
 
hdokes said:
oooooh..... nope.... probably not good.... loaded universalandroot.... first it said I was already rooted.... which I already knew for sure I was not... asked if I wanted to re-root.... well hell yes I replied.... so it said 'well hell yes I will' and proceeded.... darn thing is... it failed. Had this msg...

Failed! No ~~~ Fu goo ~~~

Had I known I needed some Fu goo before hand I'd have bought a mess of it to be prepared. Anyone know where I can get this?
Click to expand...

I can't believe you didn't have the Fu goo installed EVERYONE KNOWS you got to have FU GOO to get SU GOO :D Noobs! PHFFFRTTTTTTTTTTTT :rolleyes:
 
Well... another day... and all is well.

I have overcome the root access issue WITHOUT having to hose the entire installation of 2.2.

Essentially it boils down to if you use the cp command to copy su from /system/bin to /system/xbin and then you did your upgrade... you will have to get in to effectively 'remove' the original su from /system/bin as it is still there.

You can do this by:

1. loading up a terminal pgm on your system if you don't have one already
2. connecting to the 'localhost' through the terminal program
3. cd /system/xbin
4. type './su' and hit enter and you should get a '#' prompt indicating you now have root access
5. Now type "mount -o remount,rw /dev/block/system /system" and hit enter
6. type 'cd /system/bin' and hit enter
7. type 'rm su' and hit enter
8. type 'reboot' and hit enter

Your droid will politely reboot and when you come back up you will have root access. You can then load Koush's recovery program and you can now backup and restore with 2.2.

Now... with that all said... one consistent issue I am having is when I do reboot... My screen does not come up on the first go around. I am stuck with a moto logo however I know the unit is coming up as there is audible activity indicating so.... AND... I can ping the droid through wifi so it is connecting as well. Just no screen. I have always had to wait about 20 to 30 minutes to do a full battery pull restart and then it finally goes to the droid eye and comes up the rest of the way.

This only happens on a reboot mind you. Any thoughts? Anyone? You! how bout you?
 
hdokes said:
Well... another day... and all is well.

I have overcome the root access issue WITHOUT having to hose the entire installation of 2.2.

Essentially it boils down to if you use the cp command to copy su from /system/bin to /system/xbin and then you did your upgrade... you will have to get in to effectively 'remove' the original su from /system/bin as it is still there.

You can do this by:

1. loading up a terminal pgm on your system if you don't have one already
2. connecting to the 'localhost' through the terminal program
3. cd /system/xbin
4. type './su' and hit enter and you should get a '#' prompt indicating you now have root access
5. Now type "mount -o remount,rw /dev/block/system /system" and hit enter
6. type 'cd /system/bin' and hit enter
7. type 'rm su' and hit enter
8. type 'reboot' and hit enter

Your droid will politely reboot and when you come back up you will have root access. You can then load Koush's recovery program and you can now backup and restore with 2.2.

Now... with that all said... one consistent issue I am having is when I do reboot... My screen does not come up on the first go around. I am stuck with a moto logo however I know the unit is coming up as there is audible activity indicating so.... AND... I can ping the droid through wifi so it is connecting as well. Just no screen. I have always had to wait about 20 to 30 minutes to do a full battery pull restart and then it finally goes to the droid eye and comes up the rest of the way.

This only happens on a reboot mind you. Any thoughts? Anyone? You! how bout you?
Click to expand...

I have heard this problem before, the only thing you could do is a fresh install
 
hdokes said:
Well... another day... and all is well.

I have overcome the root access issue WITHOUT having to hose the entire installation of 2.2.

Essentially it boils down to if you use the cp command to copy su from /system/bin to /system/xbin and then you did your upgrade... you will have to get in to effectively 'remove' the original su from /system/bin as it is still there.

You can do this by:

1. loading up a terminal pgm on your system if you don't have one already
2. connecting to the 'localhost' through the terminal program
3. cd /system/xbin
4. type './su' and hit enter and you should get a '#' prompt indicating you now have root access
5. Now type "mount -o remount,rw /dev/block/system /system" and hit enter
6. type 'cd /system/bin' and hit enter
7. type 'rm su' and hit enter
8. type 'reboot' and hit enter

Your droid will politely reboot and when you come back up you will have root access. You can then load Koush's recovery program and you can now backup and restore with 2.2.

Now... with that all said... one consistent issue I am having is when I do reboot... My screen does not come up on the first go around. I am stuck with a moto logo however I know the unit is coming up as there is audible activity indicating so.... AND... I can ping the droid through wifi so it is connecting as well. Just no screen. I have always had to wait about 20 to 30 minutes to do a full battery pull restart and then it finally goes to the droid eye and comes up the rest of the way.

This only happens on a reboot mind you. Any thoughts? Anyone? You! how bout you?
Click to expand...

I was having the same issue so I decided to flash it again, going through the routine of getting stuck in the boot loop, pulling the battery, doing the factory reset, and then rebooting into 2.1. Rather than install 2.2 now I flashed it a second time, which was completed (100% - Done) and it booted directly into 2.1. I then installed 2.2 and I have yet to have any bugs pop up, this could be a coincidence but who knows.
 
I have a fair understanding of linux given I have several dozen full time servers running it... seems to me that this isn't stuck in a loup as program activity is allowed to continue and finish. It just has to do with the screen or perhaps... a call to a particular vector that isn't getting nudged hard enough... be it a result of the change... or lack of hand shaking... I certainly wish I could get an x windows service running on it... that would be to cool to remote into it and run it... at the very least tho I ought to be able to get an external telnet client to access it... after all... it does connect via a terminal client locally. I may be able to infuse some kind of boot monitoring routine that could give me an idea of where it may be holdin up at for the screen.

I just hate to have to revert back to 2.1 given I have been able to overcome the other issues without having to do so so far.
 
Can I get any help?
I rooted using universalandroot but I cannot move the su from bin to xbin using root explorer. I keeps saying "cannot move file read only"

Any help is very appreciated

Thanks
 
You must log in or register to reply here.
Back
Top Bottom