yashsingh1/xdaforums huggingface dataset:
[Xoom General] rmax67:
If you are having such an issue, it, may be that the image update didn't take completely. You can try to reflash the image. I've been running 3.2 for about 5 days now and it has been flawless for me. Everything web based is much faster. No issues what so ever. Good luck.
[Xoom General] ahmed007:
http://xdaforums.com/showthread.php?p=15687135
[Xoom General] Manicor:
Mine goes gray also! Back & forth blue then gray!
[Xoom General] crisisinthecity:
Mine has been grey since the update. Still connected though.
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
Can anybody confirm, that wifi (wlan) roaming, between different access points on the same SSID network and different channels, is working?

I have at home 2 access point (one is on channel 1 and another is on channel 6) and my SGS2 wouldn't switch from one AP to another when I walk in the house. My son has SGS1 and wifi roaming works for him. Before I had Nokia N95 and I had no problems with wifi roaming. The same thing, when I'm at work. We have 3 AP's (all three Cisco) in the house and switching between them doesn't work. In order to switch between AP's I toggle WiFi off then back on again.

I went from KE2 to KE7, now I'm on Litening ROM 1.5, but it's all the same.

I tried everything, I can think off (set AP/router to b/g/n, only b, only g, only n, set different channels, set different security,...tried also flashing different modems on the phone...) but for me wifi roaming is not working... :confused:

Any ideas?
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
Anybody? :confused:
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
Nobody? Realy? :confused:
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
That's realy strange...

Nobody? :confused:
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
I really can't believe.... almost 90 views and no answer... :(

I'm I the only one with this problem? :rolleyes:
[Galaxy S II Q&A, Help & Troubleshooting] sleeco:
While you are moving round your house do you lose connection, i think that your phone will be connected to the strongest signal.

mine loses signal when i leave home and auto picks up an usecured signal down the road.
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
I don't quite understand, what you mean... :o

When I walk in my house from basement to the top floor, my SGS2 is always connected to the router in the basement. When I come to the 2nd floor, where I have another Access point, it should switch to that AP, but it wouldn't. Instead, it's still connected to the router in the basement, which (in the Wifi Analyzer) shows -90 db (and the AP on the 2nd floor shows -30). When I switch off Wifi on my SGS2 and then back on, then it will connect to the AP in the 2nd floor. But then, when I walk back, down to the basement, it stays connected to the AP on the 2nd floor, even when I stand next to the router in the basement and Wifi Analyzer shows -28 db on the router. :rolleyes:
[Galaxy S II Q&A, Help & Troubleshooting] zenofx:
I can confirm that wifi roaming is not working (at least for me). The phone stays connected to the same old AP all the time even with really poor signal quality.

Unless it loses the connection it doesn't connect to the best AP available.

Tried it on several ROMs (multiple stock roms and now I am on Cognition 1.20), same behaviour every time.
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
Exactly the same with my SGS2. :confused:

I also tried several ROM's, from original KE7 to latest KG3, now I'm on Lite'ning 3.2, and it doesn't work... :mad:

That's really strange...
[Galaxy S II Q&A, Help & Troubleshooting] Equinox102:
Exact same issue here. Tried three different stock ROMs and a couple of modified ROMs and no change.

I'm even running Cyanogenmod now and the problem persists! How does that work? Does Cyanogen use the Samsung source-code for the Wifi driver?

It's really pissing me off. I basically cant use Wifi on the end of the house I use it most in without cycling the Wifi on/off switch as I pass a different AP on my way into the house to get there!
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
The most strangest thing is, that nothing can be found on the web about this issue (only one on code.google.com)... :confused:

And also here, on XDA, millions of posts, but nothing about wifi roaming... :(

Are people not using more then one AP/router?
[Galaxy S II Q&A, Help & Troubleshooting] atinm:
Yes, I am sure most people use one AP/router - that is why you are not seeing too many responses. The source code is from the samsung source drop, the drivers were written by broadcom. We at teamhacksung have not modified them for CM7, so the behavior would be the same across all ROMs that are using the drivers unmodified.
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
So, that means, we are stuck with this, until Samsung fix it?:(

I still can't believe, that the best phone on the world (at the moment... :D) has such a flaw...

What about trying driver for Wifi from SGS1? On SGS1 wifi roaming works beautiful (my son has one and he is laughing at me all the time :D).

Is there much difference between SGS1 and SGS2 in the wifi handling?
[Galaxy S II Q&A, Help & Troubleshooting] MorRoquen:
Wow - this is an annoying issue to have. Yup, i have 2 routers too, and it really sux to be in an 'overlapping' zone and see the SGS2 connect to the router that is further away.

Is there nothing that can be done about this?
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
I'm very pis..... angry, when I'm in my room/office, and see, that my phone is connected to the AP, which is in my son's room, two floors above me... and I'm sitting 1m away from router... :D
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
Yesterday I tried in my office with 3 AP's with my friend's SGS2 with original stock ROM KE2 (he didn't change nothing on the phone).

Result:....... the same as with my SGS2.... wifi roaming not working.... :(
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
Any news about wifi roaming? :(
[Galaxy S II Q&A, Help & Troubleshooting] jimalmac:
How annoying!

I'm having similar problems at work.

At home connectivity's fine with just 1 AP. Here at work there are about 10 Cisco APs. Every now and then I have to turn WiFi off and on again and I use the original stock rom.
[Galaxy S II Q&A, Help & Troubleshooting] Morghus85:
I have exactly the same problem, it always connects to the same AP, not the one with the better signal... very annoying! How difficult is it to fix that?
[Galaxy S II Q&A, Help & Troubleshooting] zxcslo:
Which channel does this AP have?
[Xoom Android Development] Sodikop:
Excellent write-up, I'll try this when I get a chance.

Been trying to downgrade and then get to the rooted, stock 3.2 using a couple routes shown here. They seem to create an issue with CWM not sticking...
[Xoom Android Development] wayne710:
Works great!

I just flashed back to 3.01, re-locked the WiFi Xoom (USA), OTA'd to 3.1 and followed that with the OTA to 3.2. I then unlocked and went thru your rooting procedure and it worked great. All tests indicate a successful root. Thanks for the practical guide!
[Xoom Android Development] _delice_doluca_:
thanks for the easiest way (i dont have an sd card) ..

one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
[Xoom Android Development] jase33:
It is only a boot partition with rooted stock 3.2 kernel.

Sent from my HD2
[Xoom Android Development] Hussain Isa:
when I type adb remount after completely boot, I've got error device not found !!! any idea??
[Xoom Android Development] jase33:
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
[Xoom Android Development] eurominican:
Wow that was easy... Why cant all android devices be this open and straightforward? Im sooo pissed at HTC with the EVO 3D. Cant wait for the Galaxy S2 to come out

Mad respect to Motorola for getting this one right

And last but not least, Thanks so much to the OP for the great writeup!
[Xoom Android Development] Hussain Isa:
I tried both, enabled USB debugging.

After the xoom load or in fastboot I get the same error! !!!
[Xoom Android Development] jase33:
Are you certain you have unlocked the bootloader?

Sent from my HD2
[Xoom Android Development] Hussain Isa:
Its already unlocked, so I skipped the unlocking steps.

I will take another try from the beginning
[Xoom Android Development] jase33:
If you get an error please post exactly what it says.

Sent from my Xoom
[Xoom Android Development] droidx1978z4:
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
[Xoom Android Development] jase33:
Glad to here it! And thanks for pointing that out....I will clarify that in the op for others.

Sent from my HD2
[Xoom Android Development] Hussain Isa:
thanks jase33 my problem was with the driver, I re-install it & now rooted ;)
[Xoom Android Development] fwempa:
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.

SOLUTION: Ran fastboot command as root.

su

fastboot oem unlock
[Xoom Android Development] Just_Jim:
WOW! Thanks jase33 that was painless.

Everything worked great, just as you said it would.
[Xoom Android Development] jase33:
Sounds like you worked it out.

Sent from my HD2
[Xoom Android Development] apratomo:
Where did you get fastboot for Linux. I just get my self a xoom today, I'm planning to root it but my laptop is running ubuntu
[Xoom Android Development] Hussain Isa:
Reinstall the driver, that will solve your problem ;)
[Xoom Android Development] jase33:
links in OP are working.
[Xoom Android Development] K6dime:
ok i dled the rootboot.img and it doesnt open in winzip... so i placed it in the files with all the other files required to root.. i type fastboot flash boot rootboot.img and i get error: cannot load 'rootboot.img'

thanks for the help in advance!
[Xoom Android Development] jase33:
That is usually caused by the command window not being opened or started from the same directory as adb is going to look for the files. Make sure you have all files in the correct place (i.e. tools or platform-tools folder?)
[Xoom Android Development] R1150GSA:
Thanks for the guide, jase33.

Dumb question: Once the device is rooted will it receive OTA updates when new Android versions come out, or is there some other procedure we should follow?
[Xoom Android Development] wesamothman:
You wont be able to receive ota updares once rooted. However, if you flash a custom rom, such as team eos ics rom, they release updates every now and then that you can flash manually thru recovery.
[Xoom Android Development] Legato Bluesummers:
I want to do this in the next few days, let me just clear up a question...do i have to flash the rooted boot img file (kernel) or can i just flash say tiamat 2.0.0 the same way instead? Or can i flash ClockwordMod recovery after unlocking, and flash tiamat through that, and then use your command line commands to push over the Root and SU binaries?

Or will that bork me and i need to use the modified root image kernel....if i have to use the stock/modified one, can i just reflash tiamat later?

Sorry for all the dumb questions. Everytime i root a device or mod it i almost always brick it first, would prefer to not do that this time. LOL
[Xoom Android Development] jase33:
It would be best if you followed the instructions then flashed CWM then flash Tiamat kernel. That way you have no confusion.

Sent from my Xoom
[Xoom Android Development] Legato Bluesummers:
Cool. Grazie. Very Appreciated. :D Just hoping this will be the first time i root without a brick being involved. LOL Will hopefully get time to try this today after the gym or when i wake up before work tonight. :D Doesn't sound like it takes long. And it seems easy enough.
[Xoom Android Development] Legato Bluesummers:
That was super easy to do. :D Thank you very much for the write up. My only issue was ADB wasnt working right. I thought i had installed the Xoom drivers, since it was reading the Xoom and SD card fine (though i guess that could be from borrowing my droid x drivers possibly), but i guess i didn't. As soon as i installed the proper drivers ADB worked like a charm. Easy commands. No fuss. Very simple. Thank you. :D
[Xoom Android Development] Abracastabya:
Hmm I'm having the exact same problem...I installed the drivers from the OP but adb still wont work...can you maybe explain a bit more how you fixed it? :)
[Xoom Android Development] Legato Bluesummers:
i needed to go to Motorola's support webpage and download and install the drivers for the Xoom. Before i did that, if i went into Windows>System>device manager it would see the Xoom, labeled as some model # but the driver was bad, had an exclamation point on it. Once i got the proper installed i plugged in the Xoom and with USB debugging enabled i can see my Android device as an ADB device. :D
[Xoom Android Development] Abracastabya:
OK cool :-) I'll download the xoom drivers again and see if that does the trick.

No luck...I have the path setup as explained but I still get adb is not recognized an int/ext command.

Edit: crap! I think I know what I did...when editing the path I deleted the entire line instead of adding the code to the end of the existing path :( now I don't know what the default path was..looks like I boned it eh?
[Xoom Android Development] rickyx:
Getting an error message

It keeps saying : error:cannot load 'rootboot.img'

I cannot move forward...

I really wanna have my Xoom rooted, please help me at this point...!

RickyX
[Xoom Android Development] Abracastabya:
Does this directory need to be changed to C:\android-sdk-windows as well?
[Xoom Android Development] Janniktn:
Do you think this will wipe my device if I unlocked my xoom in the past? I have some saves and stuff I can't loose right now :)
[Xoom Android Development] jase33:
If you have already unlocked you can skip this step. It will not wipe your device.
[Xoom Android Development] jase33:
make sure you have opened the command window from the same place the rootboot.img file is. You can place the files on your desktop, right click on an area of the desktop and select open command window.
[Xoom Android Development] jase33:
It shouldnt make a difference where it is, mine is installed to E:\
[Xoom Android Development] Janniktn:
awesome, just as I thought, testing this when I get a hold of a laptop :)
[Xoom Android Development] Abracastabya:
Ok cool and thanks! Starting fresh again and reading everything quadruple X. Victory is imminent.
[Xoom Android Development] rickyx:
I'm ok now. It's wonderful. The issue was so dummm! i had to navigate into my sdk folder to run the command despite the fact that i configured it in My Computer - environment variable to run anywhere in command prompt.

So now i'm a happy rooted xoom user!!!

Thanks a lot!!!
[Xoom Android Development] JRd1st:
Maybe you needed to reboot your PC before the system saw the change to PATH?
[Xoom Android Development] Abracastabya:
Sweet! I did it! Fastboot wasn't in the right place...learned a lot about a adb:-)
[Xoom Android Development] TreyDaPrince:
Need quick help. Trying to root and it says that fastboot is not a known command. To my knowledge, I downloaded everything needed/what was said in this thread.

Edit: Thanks for the help Jase. I too had fastboot in the wrong place like a tard. FYI, when you open your command prompt, whatever that 1st line says i.e. C:\User\Name, thats where you want fastboot and the other files to be.

Thanks again Jase.
[Xoom Android Development] joshw0000:
Jcase,

How many Android devices do you own and/or have super simple rooting instructions for? I have your thread bookmarked for the Thunderbolt (I use it often) and I know I've seen your name in other device threads. Dude, you're awesome! I'll be giving this a spin sometime soon.
[Xoom Android Development] TreyDaPrince:
Unless I'm mistaken JCase and Jase are two different people.

Sent From My Xoom or Thunderbolt, pick one
[Xoom Android Development] 1el:
I am stuck at •Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)

i get the following error: "ln" is not recognized as an actual .....
[Xoom Android Development] jase33:
Keep trying, you will get it. Try copy and paste the command. Its easy to mess up the spaces if you're not carefull

Sent from my Xoom
[Xoom Android Development] 1el:
thank you Jase,

finally got it, but i am stuck at: chmod 4755 /system/bin/su . Once in the adb shell i get the msg: no such file or directory.

help please!!!!!!!!!!
[Xoom Android Development] TreyDaPrince:
Be sure to place the su and su binary in the same place you run fastboot.

Sent from my Xoom or Thunderbolt, pick one
[Xoom Android Development] Legato Bluesummers:
it sounds like he never pushed the SU and Super user APK files across if it can't find them in the device.
[Xoom Android Development] durrence:
stuck

I am stuck at "fastboot flash boot rootboot.img"

Computer shows "error: cannot load 'rootboot.img'" and xoom is stuck at the

Motorola flash screen which shows logo, and at top, "Starting fastboot

protocol support"

I can power down and reboot the xoom and it starts normally. I can run adb

shell and see all files in the xoom. I have started this procedure 3 times,

made sure I had the latest files and all files in the right places and it

stops in the same place every time.

Any suggestions?
[Xoom Android Development] jase33:
The file you are trying to push is not in the same place you opened the command window. That is why it can't find the file. Open command window where you saved the the files by right clicking in that folder and selecting open command window. If they are on your desktop, right click there and open a command window. The files you want to push must be in the same directory you have opened the command window.

Sent from my Xoom
[Xoom Android Development] 1el:
I had the same problem. I just updated the drivers. Put all files on the desktop (make sure to unRAr the file Zip file as well), and press shift and right-click, open command from there.
[Xoom Android Development] 1el:
Got it ThanKS
[Xoom Android Development] Scourge1024:
Thanks! The other solution using CWM recovery won't work for me because there's not enough space on my SD card for it. Hey, it's from way back. It's tiny. :D
[Xoom Android Development] Kdawg1700_1:
Thanks

Thanks for this procedure. It worked great after reading the whole thread
[Xoom Android Development] jayhammy:
None of the fastboot commands works. When I type adb reboot bootloader, the Xoom show "starting Fastboot Protocol support" in upper left corner. But typing the "fastboot" commands in the command prompt give me the error "not recognized as an internal or external command." What am I doing wrong?
[Xoom Android Development] JRd1st:
Try going to the folder where fastboot resides, usually C:\Program Files (x86)\Android\android-sdk\tools with your file manager. Then, in that window, click Shift+right click and select "Open command window here" and run your fastboot commands from there.
[Xoom Android Development] jayhammy:
Thanks. But am I typing the words "fastboot....." into the command prompt window or someplace else? What do I do with the fastboot app?

EDIT: nevermind! I hadn't changed the directory to where the tools are. All set for now. Thanks!

EDIT #2: SUCCESS!
[Xoom Android Development] Kagalaska:
ok so all seems good up to and including adb shell command. the next line that shows in the command prompt window is a # symbol, i paste the next code line in and get the following- the pasted command is repeated and "link failed File exists". any ideas?
[Xoom Android Development] 1el:
I had the same thing. I just restarted my xoom and started at the remount command!
[Xoom Android Development] Kagalaska:
thanks, will give it a try

edit restarted xoom, started at adb remount still same result. 3 attempts
[Xoom Android Development] JRd1st:
Sounds like the link is already created and it's not letting you do it again?

I'd try going to the next step. Worse that could happen is you wouldn't have su linked...
[Xoom Android Development] durrence:
I am having the exact same problem. The xoom stops responding to the computer because it does not completely re-boot after the second "adb reboot bootloader" and it hangs on the Motorola splash screen and shows "Starting fastboot protocol support". If it is re-booted it starts responding again.

There seems to be a problem with the bootloader in version 3.2.

I have followed these instructions precisely, for 5 tries and the results are always the same. Anybody else have any suggestions?
[Xoom Android Development] JRd1st:
Did you try restarting your PC? I've found that sometimes it looks like the xoom is connected properly but unexpected things happen. It seems that disconnecting the xoom in debugging mode when you can't do a "safe" disconnect makes windows flaky if you reconnect.

Disconnect the xoom, restart your PC, then reconnect the xoom and try again.
[Xoom Android Development] corenojoe:
I have the exact same problem. Did you ever figure it out.
[Xoom Android Development] durrence:
Why does everyone want to blame the computer when the problem is obviously with the xoom? As I said I tried 5 times with several re-boots and the results are always the same. I have verified that all files are the latest and in the proper location.
[Xoom Android Development] corenojoe:
*update

Nvm I got it

*update2

I got stuck for a second at the step right after remounting. It was because I never unzipped the su and superuser file. Luckily I figured that mistake out pretty quickly, but Noone be as stupid as me lol.
[Xoom Android Development] JRd1st:
I wasn't blaming anything. I was simply relating an idea since you asked if anyone had any ideas.

Also, reading your post it aounded like you were rebooting your xoom not your PC.
[Xoom Android Development] durrence:
I re-booted my computer several times. I assume the command "adb reboot bootloader" should re-boot the xoom but it doesn't.

Has anybody gotten this procedure to work? If so what kernel is running on your xoom. Mine is 2.6.36.3-gb899528.
[Xoom Android Development] jase33:
Yes, this works.

Connect your xoom to the pc and type "adb devices". You should get a response that looks like this.

C:\Users\JASE\Desktop>adb devices
List of devices attached
161c10b2431fb4d6 device

C:\Users\JASE\Desktop>

The number you see listed will not be the same as mine it will be the serial number of your xoom. If you do not get a serial number listed then you have to either make sure that usb debugging is enabled and/or verify your installation of the moto drivers and android sdk. There is a link in the OP to read about using adb if needed.