yashsingh1/xdaforums huggingface dataset:
[Droid X Android Development] blubyu87gt:
Personally I went with the sbf, one click root, then apply 2.2. Worked like a charm. Have gone pretty much into everything I could think of lookin for bugs and issues. Haven't found one yet. Didn't even have to do a system or data wipe! Thanks for posting!
[Droid X Android Development] MXMike:
Anybody else notice the new photo gallery is uber laggy?
[Droid X Android Development] Zilliano:
Nevermind.
[Droid X Android Development] jobless:
I followed the directions and didn't put my phone in bootloader mode but it is in PC mode. the phone details show up in RSD lite but the start button is grayed out. Any ideas?

EDIT: Needed to have the SBF file at root of my PC.
[Droid X Android Development] eighty1:
Can anyone give insight on what I can do to get around adb shell permission denied? I tried it in terminal and I have Mac so I dont know how or if there are command prompts on a Mac. Thanks
[Droid X Android Development] Kingtech677:
So I got back a bit ago and tore into it. Couple of things.

Through google I learned that a bug was stopping ADB, switching to "media sync mode", allowed me to get in to adb shell, but then even for "adb devices" I get permission denied. (Is this because there's no development mode in media sync?

Also, I cant seem, to install drivers for the device, I was going to attempt to reroot strait up but I cant get in with adb. So I grabbed RSD lite and was going to flash back to 2.1 and start over. But now im worried about doing it without green lights across the board in terms of drivers. Ideas?

Edit: tried to flash the sbf. I got "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected"
[Droid X Android Development] Rockeef:
Did you move the pst_iforgotthename.ini to the root directory on your pc? Look at the first post in this thread.
[Droid X Android Development] Kingtech677:
Seems to have done it. Thanks. Didn't seen a guide had been posted since this morning and I was trying to figure it out for my first time. Ill update, now to .604/root/2.2

Edit: Oh god, flashed finished, it rebooted. Now its looping between "DROID" and the red eye.

Edit1.1: guess its supposed to loop and then you do a battery pull, man i feel like a newb.

Edit2: after the sbf flash, did a factory reset from recovery which got me back into OS. I'll update this some more. maybe itll help someone.

Edit3: Ok. So I updated to .604, unplugged it after adn what fidding a bit on it. Then the battery was low. Turned it off/it died (not mid flash) but now it wont turn. Green light is on when its plugged in but power button does nothing. This is SO nerveracking.

Edit4: Back into 2.1 rooted. Trying to move su so i can update, but adb hangs on "adb shell" and trying to intall terminal emulator i get "Installation error, the package file was not signed correctely". What, is going on, with my phone...
[Droid X Android Development] MrDJ:
I had the same problem, I didn't see the superuser app on my phone was asking me to click allow. Also make sure your phone is in PC mode.
[Droid X Android Development] The_Moo:
I cannot get into adb shell at ALL. 2 different OS's and 2 different computers ...

I got it to 2.2 and then poof none work ...
[Droid X Android Development] bouchigo:
Updated to 2.2 earlier today, but now i can't connect to the market. It was working fine an hour ago, now it just says network error......my fiancees phone at 2.1 can get to the market just fine..........anyone else experiencing this?
[Droid X Android Development] c0uRtJe$t3r:
Ya. No market atm.
[Droid X Android Development] zubinsub:
Help with SBF

Ok so I have a rooted X, when I tried following the instructions for a rooted phone when I get to the step where I try to install the update i get an error something about motobluralarm.apk

So I figure I'd just run the SBF as thats supposed to restore phone to factory default...Installed RSD lite, copied the ini file into the program files dir, unzipped sbf to C drive on computer, fire up RSD (as admin) and select the SBF file connect the phone in bootloader mode, while the phone is detected in RSD all the values are N/A and if I click start it immediately says failed.

Any suggestions guys...I've tried reinstalling driver, RSD but no luck and its getting really frustrating.

My computer us running Win 7, RSD v4.7, drivers for x64.

Thanks in advance
[Droid X Android Development] MXMike:
I was just experiencing this as well...but after clicking retry about 50 times it is working but really really slow even on wifi. My wifes phone on the other hand also has 2.2 and she can't connect as of right now.

hopefully this doesn't turn out to be a time where I regret adopting early ><
[Droid X Android Development] Rockeef:
Might sound stupid, but try moving the sbf into my documents. If that doesn't work go back a few pages and try the other options I posted.
[Droid X Android Development] Rockeef:
What's the message say? Have you tried using media sync when connecting?
[Droid X Android Development] mgarcia2682:
when i go to the market my phone will click on a link by itself and when i click back it will click it again. it will finally stop if i put it into standby by but after a while it will do it again any ideas as to whats going on
[Droid X Android Development] Kingtech677:
Guys, just wanted to let you know I think I solved the losing root issue. I ran into this and with limited adb access due to froyo i couldnt reroot. ended up flashing the sbf and starting over.

Grab the "rooted update.zip" from here: http://www.mediafire.com/?b1zzgdn8yk6ul

^^^This worked for me/solved the issue^^^

And dont forget to "mv /system/bin/su /system/xbin/su", Aka move su from /system/bin to /system/xbin

Let know me if this helped.
[Droid X Android Development] deepducky:
Stuck at the M bootscreen

I just wanted to give anyone who may be having this problem a heads up. I've been struggling all day with this update (I was rooted with the bootloader installed, and thought it would be SMOOTHER to just use the sbf and start fresh.... I've hated myself for a good 8 hours for thinking that was the smart thing to try first)

I tried a fresh install after sbf.. 2.2 booted fine, all seemed great UNTILL I tried to reboot. Then the system just hung at the M. Pulled the battery, turn it on again, same thing. I was forced to run the SBF again.. this time I reloaded the bootstrapper apk, went into clockwork recovery and recovered to a backup I made this morning. I then uninstalled the bootstrapper and proceeded to follow the steps to update my system.. got 2.2 loaded AGAIN, but this time before installing anything, I decided to reboot... and wouldn't you know it, I was stuck at the damn M again, no matter how many times I rebooted.

Then a funny thing happened. I heard the DROID sound that plays when the system boots. I touched where the slide lock normally is and felt the haptik feedback. The whole time I thought my system was frozen, but it actually booted in with the M hiding everything. I could lock and unlock the screen and it would stay the black screen with the white M.

I tried booting into normal recovery and wiping data/cache, which would work until the next time I rebooted. I even tried doing the whole setup using clockwork and the rom manager, with the exact same results.

I decided to boot into normal recovery mode one last time, thinking I'd just go back to 2.1 and forget about this process until something new came out, but I figured I'd try one last thing... I cleared JUST the cache. Rebooted, and finally saw the Red eye, and then the lock screen. I tried not to get excited, and rebooted again, and again I saw everything I was supposed to see, and not just a ridiculous M.

Maybe I'm jinxing it, but I've restarted 5 times and everything seems to be loading exactly how it should be now. I thought I'd spread the word in hopes that it helps someone else who may be about ready to put their phone through the wall.

UPDATE: Yep, I jinxed it. On the 8th or so reboot I'm back to the M. I can hear sounds and receive calls, but can't see anything but the M... I really don't understand what could possibly cause this.
[Droid X Android Development] Zaphod-Beeblebrox:
I would not rule out that x64 is part of the problem. I struggled greatly last night trying to get RSD working on my desktop (Win7 x64) and couldn't get it to see the phone at all. I had come to the conclusion I was just doing it wrong (leaving it in bootloader mode as the directions indicated).

In desperation, I installed RSD on a Win7 x32 Laptop and it worked fine. Of course I also did not put the phone in bootloader mode, but just let it boot normally.

So, In the end, I don't know if my x64 desktop was part of the problem. You may want to try and find an x32 machine around.
[Droid X Android Development] Crondar:
Thats odd, RSD worked fine for me on a x64 bit Windows 7 machine, using the x64 drivers.
[Droid X Android Development] eighty1:
I tried to sbf but it said permission denied in terminal. Any suggestions? Im using a Mac and I followed the directions from alldroid and put the sbf file and the other file but to no avail. Also Im rooted if that means anything. Thanks
[Droid X Android Development] daverdfw:
i ran into the exact same issue, i finally just went back to 2.1, if you figure it out let me know, seems a few of us ran into this issue.
[Droid X Android Development] zubinsub:
I actually tried it on a non x64 computer and worked like a charm, now i can enjoy the froyo goodness.

Thanks Zaphod-Beeblebrox
[Droid X Android Development] deepducky:
This solved my problem as well. I noticed every time I tried to load the SBF using Windows 7 x64 it would fail during the last steps with the bootloader. The phone would restart and appear to have been restored, but every time I tried to load 2.2 it would boot fine once, and then every other reboot would only show the M logo, even though the phone was loading in the background.

I decided to do the SBF using a Windows 7 x32 virtual machine (using VMWare), and this time the recovery passed. I loaded the new stock 2.1, logged in to my account to download Root Explorer, rooted using the 1-click method (still using the x32 virtual machine), used Root Explorer to move su from /bin to /xbin, restarted the phone in recovery mode and ran the update.zip to 2.2

The first reboot hung at the M longer than I liked, so I decided to just pull the battery, reboot into recovery and wipe data/cache (something I had considered doing right after the update anyway).

I have now rebooted the phone over 10 times, signed in to all my accounts, downloaded all my apps, and have yet to see a single problem other than some of the Motorola Widgets looking a little bigger and fuzzier as others have mentioned (I noticed it the most with the date and time and quick contacts).

I hope this solves some problems, and I really hope this ends the nightmare of a time I had all of yesterday.
[Droid X Android Development] invisiblek:
cant seem to find a dump of 2.2, i dont have a droidx but i would really like to get my hands on a dump of the leaked 2.2

only been able to find a 2.1 rom and this update, but not a full rom
[Droid X Android Development] BACARDILIMON:
Ok maybe i missed something. I went from a 1 click root and followed all the adb steps and it was good till i tried to use the update zip. Keeps saying verifications signature is wrong and aborts the install. Any help here.
[Droid X Android Development] byproxy:
okay... just gave the dinc to the wife and picked me up an X. i rooted using one click root. superuser now appears on the phone. trying to upgrade to froyo.

problem: when i type in "mount -o rw,remount /dev/block/system /system" i get the following error -

mount: Operation not permitted

can anyone help?
[Droid X Android Development] navychief52:
Did you run su first. su is "Switch User" and when run with no arguments, switches you to the root user.
[Droid X Android Development] c0uRtJe$t3r:
Glad I didn't have these problems. I just downloaded from rom manager and flashed with bootstrap. No problems, and have been running since an hour after release.
[Droid X Android Development] byproxy:
that was it. sorry. it wasn't in the instructions and i didn't think to do that first. all good. thanks!
[Droid X Android Development] byproxy:
okay... sorry... new problem. i can't get into recovery. vol down, home, and power only bring up the exlamation point. same with quick boot... it brings up the triangle but no prompts.

what am i doing wrong here?
[Droid X Android Development] MrDJ:
Hit The magnifying glass
[Droid X Android Development] byproxy:
nm. still need help with recovery issue though.

LOL: sorry MrDJ. i thought you were flaming me for not searching. you literally meant to hit the magnifying glass on the phone!! hehehe. got it. sorry about that. thanks for the help!!
[Droid X Android Development] iGLOMP:
Anyone else getting a force close when trying to open up battery usage on 2.2? The problem seems to be popping up on other forums
[Droid X Android Development] BACARDILIMON:
By the lack of answers i guessing not that many are having this issue of signature verification failure. If anyone can help please let me know
[Droid X Android Development] dvation191:
I don't seem to be having any of the problems others have reported with 2.2 (with the exception of the market filtering but that's not really a bug). I do have one odd problem I'm wondering if anyone has experienced.

Although I did not have this problem before 2.2, suddenly all my download attempts using the browser results in a "download unsuccessful". If I download files using Dolphin or the market it works fine. I've tried clearing cache on the download manager as well as the browser. Anyone else notice this?
[Droid X Android Development] gunkle:
Same here. I installed Koush's rom manager app (free on the market) and one of the options is to fix file permissions or something like that. Once I ran that and then rebooted all works well. A few other little oddities were fixed by this too. Figure with all the messing I've done in the phone something got changed.
[Droid X Android Development] evilkal:
Getting a couple force close problems but most are remedied by fixing permissions. Quadrant doesn't wanna check for past benchmarks but that's okay with me lol.
[Droid X Android Development] ruddymart:
I am still debating whether to update to 2.2 or not.

If I decide to pull the trigger i have few questions to address.

I rooted the phone with the Easyroot app within the phone, never removed or renamed any bloatware (unnistalled only NFS) so my question is, do I need only these steps below?

1. Run "adb shell"

2. Run "mount -o rw,remount /dev/block/system /system"

3. Run "mv /system/bin/su /system/xbin/su"

4. Copy update.zip

5. Reboot into recovery (power down - hold volume down and home button and press the power button)

6. Run update.zip

7. Reboot

I read somewhere that there is a step missing here, can someone confirm this for me. (like run "su" between steps 1 and 2 above)

Another question I have is. Prior to updating to 2.2 do I need to remove any/all apps I downloaded from the market or I can leave them on the phone and they will still be there after the update?

And lastly, what feature/s does 2.2 brings worth the update? Aren't the bugs/problems so far greater than whatever new features the update brings?

Thanks
[Droid X Android Development] jmiller148:
Can someone give me the "Usb.apk" from 2.2. Please don't ask why... I don't want to talk about it. Duh!
[Droid X Android Development] davisbs999:
"1.Download THIS ARCHIVE and expand it to a folder you can find (eg. c:\DroidXRoot)"

Would someone please be kind enough to PM the archive mentioned in the above step? I couldn't get the link to work. Thank you very much in advance!

EDIT: I found the archive on another site
[Droid X Android Development] kymikes:
Success at last

Thought this might be useful to others. I started with an unrooted Droid X with a number of apps installed.

1. Followed post #2 to root (no troubles after realizing it assumes that the Android SDK is installed)

2. Followed the 'Install Froyo" section from post #1

3. All appeared to be successful until I realized that the USB connection (drivers??) were 'frogged' AND the phone no longer was charging from the USB connection to the PC

4. Had to take the USB link out of debug mode, then reboot the phone. Then change the USB connection to mass storage and re-install the moto usb drivers again (originally could not change the mode of the USB connection from the pull down until I reinstalled the drivers). This fixed the USB mode issue and fixed the charging issue. Went back to PC mode and back to USB debugging mode.

5. Discovered that root had been disabled in this process (Froyo still is running fine)

6. Tried several recovery steps (including 1 step root) w/o success.

7. Found a post from dmeg listed below that fixed the root issue

-------------------------

If you have /system/xbin/su and /system/app/Superuser.apk, but cannot use "Superuser" (no prompts from Superuser app, "permission denied" when you try to run "su"), just do the following:

1. Run "adb shell"

2. Run "/system/xbin/su"

3. Watch your screen for Superuser app to prompt for permission and click "allow"

4. Run "mount -o remount,rw /dev/block/system /system"

5. Run "cp /system/xbin/su /system/bin/su"

6. Run "chmod 4755 /system/bin/su"

7. [optional] Run "mount -o remount,ro /dev/block/system /system"

------------------------

Don't know why step 2 worked as I really thought I had changed directories to /system/xbin to run su but . . .

BTW, ADB devices would not find the phone until after I fixed the USB driver issue above. Now all is working fine. I am definitely a noob on DX (all prior phones were WinMo) and my Linux skills are very rusty (12+ years away) so there may be better ways to get here. Thought this might be useful.
[Droid X Android Development] bignadad:
I have been having a few issues with Froyo and wanted to see if anyone else is experiencing them...

I had just done a factory reset (sbf) and installed just a few apps prior to upgrading to froyo.. the apps i installed were widget locker, aquarium live wallpaper and adw...

here are the problems i am experiencing..

1 - when i wake device up (by pressing button on top) i briefly see the default lockscreen for a second or so then switches automatically to widget locker lock screen.. Not a big deal, but just wanted to mention

2 - First i wake device then slide to unlock. when i try to slide panels i get a 1 or 2 second delay.. as i continue to keep sliding panels it eventually gets faster with no delay. but i have to slide 2 or 3 times to get rid of delay, and it happens every time i wake device up...

3 - Gallery seems to mess up occasionally... i have about 500 pics on my SD card that its reading.. when i press the gallery link it brings it up to where it displays "camera roll" "my tags" etc..... BUT sometimes the camera roll will not load correctly. i say that because the pictures that looks spread out behind the front picture are not there. when i click on camera roll to look in that folder i get a blank screen. i have to go home or get device to respond. once i go home then back to gallery it will work no problem...

4 - Video playback will sometimes work faster that it did on 2.1 which is to be expected according to post 3... BUT sometimes when i go to watch a video i get a blank screen when trying to open video and device is unreponsive to matter what i press. it stays unrepsonsive for at least 20 to 30 seconds before finally getting back on track.. most times i can try to play move again then it works fine...

Anyone else experiencing these small problems? the delay on sliding home screens is killing me, but i dont want to uninstall adw to find out that wasn't it.. any feedback is appreciated

Also, should i updated post 1 with the clockwork way of updated froyo?
[Droid X Android Development] jaskru:
Stoked about froyo and doing my best to hold back until I see more stability. I sure hope you guys can figure it out soon. There are prob some that have had no issues but past experiences keep me on the other side of the fence. Almost thinking of just waiting for the ota. Prob not though.

............
[Droid X Android Development] kdkinc:
Bignadad:

I leave my phone on the charger all night so that Slacker Radio will cache my radio station.

Re:1&2, when I first wakeup the phone Slacker says it did its thing. But then I had a double lock for 1-2 seconds . I had the same issue ,minor with the pages sliding.

I want to attribute it to updating my Weather bug plus My Widget locker & LLP wx Widget. Lot going on for a few seconds...LOL.

Re; 3 & 4 I only have 50 pics on the high side I tend to clear them to my PC to work on some of them.

Video No time !!! I spend to much time messing with threads an updates:)
[Droid X Android Development] kdkinc:
I think you'll see it after Labor Day....where the Summer GO???:eek:
[Droid X Android Development] davisbs999:
Perhaps, I've been lucky, but the only problem I've encountered after the update- not being able to gain root access with several apps- was my fault. I forgot to move su to xbin. I haven't checked to see if i have the gallery issue described on the previous page though. I am grateful that the sbf was posted, as it tempers much of the risk associated with being an early adopter. Without rsd lite and that file, I may have waited to update as well.
[Droid X Android Development] kymikes:
Big, I am running LauncherPro so this is a little different data point. I am not seeing either of the effects in item 1 & 2. When I "wake up" the phone, I am looking at the Locker Widget and 'slide to unlock' is very smooth and responsive. Doesn't sound like what you seeing at all. On item 3, I only have about 180 pictures in the gallery but, again, I am not seeing the effects that you are. My pictures are a bit disorganized (I am pulling all my music & pictures onto a separate drive on my network and haven't made any effort to 'organize' what is on the phone as yet). Other than the disorganization, everything is very quick to open w/o any blank screens or pauses. But I have less than half the number of images at this point. Can't help with item 4 as I don't really have any video's so I just don't have a data point.

Hope this helps.
[Droid X Android Development] bignadad:
Yep, that helps... Thanks!

you still using your tp2?
[Droid X Android Development] kymikes:
Yes, moved over to my 2nd number but with the time I have spent on the Droid, it hasn't gotten nearly as much love.
[Droid X Android Development] Mikerrrrrrrr:
I'm running LauncherPro as well and I'm seeing the original lockscreen "fade" into WidgetLocker. But I also have the phone capped at 300 Mhz when the screen is off.
[Droid X Android Development] ruddymart:
Ok, I did it.

Went butter smooth. Here is what i did.

Phone was rooted with easyroot, all the bloatware was on the phone, so I went straight to this

Apply Froyo 2.2 Update

1. Run "adb shell"

here between 1 and 2 I ran "su" (have no idea why)

2. Run "mount -o rw,remount /dev/block/system /system"

3. Run "mv /system/bin/su /system/xbin/su"

4. Copy update.zip to sdcard (after this step I disconnected from the USB)

5. Reboot into recovery (power down - hold volume down and home button and press the power button)

6. Run update.zip

7. After Completed Reboot

root is still present.

So far everything runs great ( checked all reported problems). Many new features which I love. One thing I noticed and I am not sure if it's new or not (just do not remember) but on google maps street view I just need to rotate the phone and not scroll with finger. Can someone with 2.1 see if it is the same and I just did not notice it?
[Droid X Android Development] bignadad:
In response to problems I was having a few post back

I edited me build.prop, updated new new release of adw that dropped today and got rid of my aquarium live wallpaper.

WOW. Its smoking now. All problems are gone but the gallery when loaded still hangs occasionally. I can live with that. This device just got even better :)