yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] xlGmanlx:
Other than super user and root only apps what are the benefits of rooting?
[Xoom Android Development] bwcorvus:
Right now only to delete **** you don't want and overclock.
[Xoom Android Development] thefredelement:
Try to download the file again? Curiously can you flash the stock image?
[Xoom Android Development] Darthus:
I don't think you continually posting this is going to get someone to do it any faster. And why do you need a video? The steps are pretty straightforward (even though they don't work for me)
[Xoom Android Development] Darthus:
I haven't tried flashing the stock image, though I could try as a test. I downloaded the image a few different times and from different posts. I think I might just try a different computer and see if that helps.
[Xoom Android Development] mojonation1487:
Yeah except it doesn't work for me either! so obviously we are doing something wrong. Hence my request and others requests for a video to make sure we're doing things correctly. And posting multiple times wasn't to get it done faster. Was just done to make sure people actually noticed and replied about it. Worked didn't it?
[Xoom Android Development] Darthus:
Yeah, except I don't think it's an error in the steps of what's been prescribed. Those steps are pretty straightforward. Unlock the device, reboot into fastboot mode, then run the command. I don't need a video for that. I'm 99% sure the issue is what my hardware, the motorola drivers or how I've installed the android SDK.
[Xoom Android Development] xlGmanlx:
11 hours and 80% left,honwycomb is a beast. What's battery life like when overclocked
[Xoom Android Development] JaxDomino:
Device Not found

I found the solution and created a post here: http://xdaforums.com/showthread.php?t=979760 to help.
[Xoom Android Development] JaxDomino:
Drivers

You need these driver from Moto. I would install them first! I found them after I ran into the device not found error in ADB.

http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
[Xoom Android Development] funnycreature:
Do I need to root to tether my iPhone to the Xoom? I think some programs that make tethering easy require root access.
[Xoom Android Development] xlGmanlx:
It requires root
[Xoom Android Development] tormsbee:
Nice work, thanks
[Xoom Android Development] droidrev71:
video?

any video of how to unlock, root, and overclock xoom yet?
[Xoom Android Development] Phylar:
Bump, the XOOM Root.zip link is broken. anyone post a mirror?

EDIT: This link has it.
[Xoom Android Development] DebianDog:
Not the overclocking part but yes. http://www.youtube.com/watch?v=4YkIw0y_Os4
[Xoom Android Development] Mudvayne622:
Found 2 different methods. Both are the same except for 1 step. Check out the link below and look at his step 17. Now compare that to step 10 of this guide. I know they are different commands but whats really the difference?

http://www.xoomfaq.com/hacks/
[Xoom Android Development] almostinsane:
No idea what the diff is but I used that guide and it worked perfectly. I then went to step two and overclocked it.
[Xoom Android Development] xlGmanlx:
Does updsting lose root and if so does this get it back?
[Xoom Android Development] p-slim:
the OP is off. these directions should be transferred to the OP, as they worked flawlessly for me
[Xoom Android Development] shyamk:
Will I be able to switch carriers once it is unlocked/rooted ?

Thanks

Shyam
[Xoom Android Development] el_bori1:
I'm having problem with step 10. I get an error (In: not found) any one can help me with this. Thanks
[Xoom Android Development] bwcorvus:
No

Sent from my Xoom
[Xoom Android Development] bwcorvus:
Try LN not in

Sent from my Xoom
[Xoom Android Development] el_bori1:
Thank you very much sir!! Worked flawlessly
[Xoom Android Development] pablo1010:
Im having problem with 7 I get error cant load rootboot.img
[Xoom Android Development] omeneo:
plz can someone tell me does/or how to do/ xoom works on another network then verizone.

Does "root"/unlock helps?
[Xoom Android Development] omeneo:
to be more accurate with m,y question: will xoom works in EU if I buy ut in US?

if answer is no is there a way how to use xoom in EU?
[Xoom Android Development] p-slim:
It is only possible overseas using wifi service. 3G/4G can't be activated on any carrier except Verizon.
[Xoom Android Development] Santoro:
I got this error on my 64 Bit Windows 7 Machine. Doing the procedure on my 32-Bit laptop worked fine. I suspect the fastboot driver in the Mot package isn't 64-bit compatible.
[Xoom Android Development] misdirection:
There's more than this simple instruction: download adb driver and sdk from android.. then you have to merge platform-tools to tools - which is confusing because I am not sure if I have to replace it, copy it but don't replace it, or keep files but renamed. I am so confused.. stupid English jargon which is UTTERLY confusing, and it's not making any sense.
[Xoom Android Development] Instien:
Wow. :eek:
[Xoom Android Development] p-slim:
This guide does require knowledge of adb to be considered simple
[Xoom Android Development] lokko21:
I'm having the same problem please somebody help please....!!!!

and I can't adb remount xoom.

"remount failed: operation not permitted"

Windows 7
[Xoom Android Development] lokko21:
Would you be so kind to link me to this bootloader please I can find it nowhere on motorola site, I want to get this going but I get stock in the same place.

Thanks.

Evo Better Than The Best...
[Xoom Android Development] ericdabbs:
Anyone able to root their wifi only xooms using the provided files on page 1?
[Xoom Android Development] sleeplessninja:
Here is a video on Unlock and Root. This is performed on a Leopard OS X Mac, I show both the screens of the Xoom and the Mac simultaneously as well as large text overlays on what I am typing in the console. Hope this helps.

http://www.youtube.com/watch?v=26EhGGOGUus
[Xoom Android Development] conmeo8ya:
adb shell push su /system/bin

"push: not found"

help me with this problem :D
[Xoom Android Development] bwcorvus:
Adb shell, then do the rest...not all in one command

Sent From My Evo
[Xoom Android Development] xguntherc:
Does this root method wipe out all the userdata?
[Xoom Android Development] xlGmanlx:
I think the only thing that does that is unlocking
[Xoom Android Development] jawonder:
Hey guys , i've restored my Xoom from soft brick and i didn't lock it at the final step i just select volume down for no and reboot my Xoom . Where should i start in the process in the OP to root it again if i didn't lock it or do i have to do everything over again ? , not sure . Never mind guys i got root .
[Xoom Android Development] MitchRapp:
actually if you follow the steps marked "do not follow the next 3 steps if you've unlocked" then yes

unlocking bootloader = wipe data
[Xoom Android Development] flakito81:
??

i have a LG g slate from tmobile usa i want to know if i cant root the glate with this method or if is different please let me know how to root it please and thanks
[Xoom Android Development] Metallaro:
Does this guide work on WiFi only version?
[Xoom Android Development] guod2002:
OP Should be corrected to reflect following...

1.# Download the XOOM root zip.

2.# Unzip the package.

3.# Put your junk in the box.

4.adb reboot bootloader (skip the next 3 steps if you have already unlocked via fastboot)

5.fastboot oem unlock

6.# wait for reboot

7.adb reboot bootloader

8.fastboot flash boot rootboot.img

9.fastboot reboot

10.# wait for reboot

11.adb remount

12.adb push su /system/bin/

13.adb shell ln –s /system/bin/su /system/xbin/su

14.adb shell chmod 4755 /system/bin/su

15.adb push Superuser.apk /system/app/

this was copied and pasted from Koush's website, all credit goes to him, the OP has some lines using shell where they shouldnt be and didnt work for me
[Xoom Android Development] Waza_Be:
I fear that doesn't work...

Followed the whole guide and stuck at: 7. fastboot reboot (wait for reboot)

My tablet is stuck at Motorola dual core logo...

No way to fastboot or adb command, none of them are working!

I have to admit I am a little bit afraid...
[Xoom Android Development] xxspark89xx:
I'm having this same problem as well... :/
[Xoom Android Development] sweetlilmre:
Hi,

I had the same problem, flashing the boot.img from here got the xoom booting again.
[Xoom Android Development] abn.geek:
Cool, thanks...

But uh, how did you get it back to a point where you could flash that? Can't figure out how to get back to the damn bootloader.

Edit: Nevermind lol. It's in the post you linked.

Hold VolUp and power to restart Xoom

Hold VolDown will booting unit for fastboot mode

Edit 2: Ok, If you're on WIFI ONLY and you're a 'tard like me and you tried this after upgrading to 3.1, use the guide here:http://xdaforums.com/showthread.php?t=1078019

If you're stuck in a boot loop on 3.1, flash the boot.img from this thread (not the one sweetlilmre linked to, it won't work).
[Xoom Android Development] despich:
If you get a error doing the "adb shell push su /system/bin" you should change it to "adb push su /system/bin" and try it again. Seems to me the the instructions should be rewritten. For some people (like me) the "adb shell push su /system/bin" will not work but the "adb push su /system/bin" will.

Dan
[Xoom Android Development] :
adb command window = command prompt right?

Can I do this on Windows 7, Vista, XP, Ubuntu? Which one is better?
[Xoom Android Development] sqx:
does this work with the euro 3g xoom?
[Xoom Android Development] MitchTank:
could someone repost the file, appears to be broked or outdated
[Xoom Android Development] MitchTank:
would be greatly appreciated, will it matter if on 3.0 or 3.1 or which kernal?
[Xoom Android Development] Barsky:
Will this work on 3.2 (wifi only)?

Thanks

(searched the thread for 3.2...found nothing)
[Xoom Android Development] arnaldop@cfl.rr.com:
Xoom Family Edition

As most of you are aware, the Xoom Family edition has some key differences with its counterparts: front camera positioning, screen specs, internal memory.

It is a WiFi-only version, but I am afraid to use the root methods out there, especially given that in most forums people aren't even aware that there are differences with the XFE.

Has anyone rooted the Family Edition? If not, is there a way to revert the current root process if it fails? I love Titanium Backup and Clockworkmod Recovery, but I need root for all those, and if the current method fails, I want to get it back to its regular state.

What can you guys recommend to me?

Thanks for your time!
[Xoom Android Development] rgloria12:
does anyone know where I can find a video showing the step by step processes on how to root the xoom? I know the steps outlined by the OP are pretty simple to the vast majority, but the whole process is quite intimidating for me. I don't want to mess up my xoom. Thanks for any help.
[Xoom Android Development] jaekidd1012:
+1

I, too, have a Xoom FE and want to know if the current root method(s) will work for our models (which would mean I've been doing something wrong somewhere) or does it entail a completely different root process?
[Xoom Android Development] kmmxracer:
From what I've tried so far on my Xoom FE is that it doesn't seem to have, or atleast allow access to bootloader. It does however go into APX mode by certain key combos. I'm just starting to read about APX mode and other devices using NVram to do certain thing to the devices inthis mode. My Xoom FE fails to respond to any of the NVram commands, so either there are no proper drivers for the FE and NVram or Motorola has locked this device down so hard that even low level boot processes like APX is signed or has permission restrictions.
[Xoom Android Development] marciosister:
Just rooting 3.1 stock

Hi

Terrific job what you guys do here! I´ve been following xda for a long time and I love it!

But now, I need help...I have a motorola xoom MZ605 with 3.1 honeycomb, bandbase N_01.83.36P, kernel version 2.6.36.3, version n. H.6.3-28.6. This is the official brazilian stock 3.1 honeycomb.

I already rooted it some time ago with Tiamat 2.2 and everything went fine but the only problem was that from then on, it showed up as Model Number: Verizon. This way my xoom was not being recognized by our brazilian android market. So, I flashed it back to 3.0.1 and did the official upgrade that it has now.

My question: is there a way to root the beast without messing up with the rom? just openning what it has to be open so I could really use the android OS? I miss the micro usb connection and all the rooted nice things one can do with a rooted device! I have been trying all kind of boot.img, and flashing all kind of zip roms but what I just would like is to root it...

Many thanks to any help you could provide.

Marcio
[Xoom Android Development] nazix:
Thank you
[Xoom Android Development] sweetboy02125:
how to root when already update to ICS 4.0.3?
[Xoom Android Development] mng777777:
I just stumbled upon my xoom in a drawer and was surprised to see that it's still kicking. I may wipe it and install CM on it...I'll see if I can find a good use for it.
[Xoom Android Development] p1gnone:
similarly, but mine is still locked, running 3.2 . The first post while could still be the procedure has a broken link. any help?
[Xoom Android Development] mng777777:
Are you trying to unlock, then flash? It has been a long time but I remember that unlocking was as simple as changing a setting as the Xoom didn't have the typical restrictions that the new devices do. I think I just went into recovery or boot menu then changed an option from the list.
[Xoom Android Development] boytoreckonwith:
Every time I flash TWRP via fastboot it gets wiped upon reboot. I think the stock firmware is erasing it? any idea how to get around it? it's hard to find answers in such an old device forum...
[Epic 4G General] Krazy_P@:
I got so sick of the 50% time without a signal bug and flipping the airplane mode on and off when i booted I went back and tried flashing the modem again though Odin and the results were kinda shocking. I'm sure that as you know Odin can be selective on when it wants 2 work and whatnot but now I'm starting 2 wonder if it isn't more related 2 the usb port you use....

OK I have a laptop so unlike a desk top all of my USB ports go directly into my motherboard... unlike a desk top where you have 2 use the back ports (99% sure about this and I don't want to take my laptop apart). the 2 ports I used are side by side and well call them "A" n "B" just to keep it simple. Port "a" has been hit and miss for odin success some times it fails some times it works sometimes. Port B on the other hand has never had an issue (ok well (95% success) but seems to work way better. Also Note that when I had the TWS bug my gps didn't work nearly as good as it did when I didn't have the bug. Here is the result of my 9 Flashes

Flash 1 Port A= 50% tws, Slow GPS

Flash 2 Port B= Perfect or as close as sumsung can get lol

Flash 3 Port A= 50% TWS slow gps

Flash 4 Port B= Perfect

Flash 5 Port B= Perfect

Flash 6 Port A= Perfect

Flash 7 Port B= Perfect

Flash 8 Port A= 50% tws, slower gps

Flash 9 Port B= Perfect and I want it to stay that way lol

SO as you can see only 1 in the 4 times I flashed though Port 'A' did it not give me the TWS Bug, There were also a few times it failed all together through port A but that didn't happen 2day so idk what the deal is with port A but from now on I won't be using port A anymore because it just seems 2 never get the desired results even when it is finished and says success... This is causing me to wonder how many of these bugs are results of "bad" flashes... Now I don't want to cause a huge flame fest or anything but just letting ppl know that even when Odin (or the samsung updater) has success it seems like it maybe wasn't all that successful. Just throwing this info out there so ppl realize that The USB port being used Might be the problem and hopefully 2 help a few ppl out

Also for the record I used the same modem file for all the flashes and didn't use a pit file for any of them... cuz as I understand the pit is only needed when flashing just a kernel. everytime modem.bin file was in PHONE section and only auto restart was checked. Honestly If You don't know how 2 use odin just search a little as there is a ton of places that tell you how 2 use it...

I understand that this was not a controlled test or anything I just wanted 2 let everyone know what I found... also I'm still on DK28 as the base just used the Modem File for EB13 and I have never b4 had the tws bug, not on DI18, Not On DK28, Not ever till the first time I flashed the EB13 Modem. And YES you can use the EB13 Modem on DK28.
[Epic 4G General] DeeODoubleD:
I've been meaning to find out... how do you check your TWS?
[Epic 4G General] muyoso:
You flashed your phone 9 times? You know that isn't good for your phone right? And the TWS issue is fixed by updating the PRL and profile. No need to flash a dozen times to fix it.

Menu>settings>About Phone>Battery Use>Cell Standby

Listed as Time Without Signal.
[Epic 4G General] Krazy_P@:
If you go 2 settings - about phone - battery usage... from there if you look under the radio you'll see your tws
[Epic 4G General] drakkahn:
I update my PRL and profile all the time and still have TWS issues...
[Epic 4G General] DeeODoubleD:
Thanks guys... I went there but didn't actually click on cell standby. Mine's at 0% and I could see it hitting 50% even though you had signal being an issue.
[Epic 4G General] edonnelly:
How much time are you letting go by between flashes? I can't imagine it's more than 30 minutes. I've been battling the TWS bug on my phone since day 1, but I don't even look at the % until the phone has had at least a couple of hours.
[Epic 4G General] edonnelly:
That trick (like every other one I've found for dealing with this) only lasts until you reboot the phone.
[Epic 4G General] Krazy_P@:
OK I bet you I could sit here and Flash My phone as many times as I could in A week and I wouldn't ever really Hurt my phone, Honestly I'm willing to bet some of the Devs Have flashed their phones 1,000+ Times, I Have NO CLUE where you get the idea that flashing my phone a few times hurts it, I know for a FACT I have ZERO bad blocks on my NAND, I flash it often and I run EXT4, Have been for quite sum time and Last time I checked my Nand was a week to 2 weeks ago ZERO BAD BLOCKS, where are you getting the IDEA that flashing my Phone through Odin would hurt it, and if you could please direct me to the information?

Yeah Updated My PRL and Profile = Didn't change Squat....

The point of my post was more that even when odin and sammy's updater are saying they were successful that infact they might not have been dead on and that there is EVERY possiblity that what USB port used could affect the outcome and that trying a diff USB port before you say its broken is a good idea. BTW FLASHING YOUR PHONE (correctly) WILL NOT HURT IT....
[Epic 4G General] Krazy_P@:
Yeah I wasn't letting a bunch of time go by, but I am in a good coverage area and there was no reason that I should have had more then 5% tws in the 5 min I tested 2 see the results of each flash, and I found it really interesting that my GPS worked way better (used gps test off the market) when I didn't have the 50% TWS... did you try flashing just the modem a few times? This is the only way I know of to 100% make sure you are overwriting the file in your phone...
[Epic 4G General] muyoso:
No. It lasts reboot after reboot. I have confirmed this on my Epic twice now.
[Xoom General] nzaw4:
Not really sure if this was correct, but the sales rep sucked me into the 9$ monthly insurance.

Was told it would cover Damage, loss and theft....

Can Anyone confirm? The rep didnt seem too knowledgeable...
[Xoom General] ocdtrekkie:
It's like the $5 insurance you can get on the phones. I did it, since the Xoom was such a large investment compared to the phone. You can always drop the insurance later.
[Xoom General] parrotheadmjb:
I was considering getting it, but does anyone know how to setup your account online, it wants to send me a temporary password via text message...but obviously the xoom doesnt get texts..
[Xoom General] nzaw4:
So if I lost it today, I could pay a 100 deductable to get another tab?
[Xoom General] ocdtrekkie:
That's the idea. They'd disable the original's ESN, and maybe even remote brick it.
[Xoom General] nzaw4:
hrmm... intresting ;)
[Xoom General] ocdtrekkie:
Please don't try to game the system. People intentionally breaking their Droid 1s hoping to get Droid 2s as a replacement kinda screwed people with legitimate issues.
[Xoom General] nzaw4:
I just reported mine lost, and i plan on doing it 2 more times...

jk. good to know my investment insured .

Got a sprint tab, no insurance. So im very happy with this
[Xoom General] bogatyr:
Is there a way to create folders on the home screen like 2.X?
[Xoom General] peto.dragoumanos:
I have the same question. For the life of me I can't figure out how to make a folder. As a work around I downloaded "Group My Apps" from the Market as a work around until somebody tells me how to make a folder.
[Xoom General] dino325:
I am using folder organizer. Icons are still somewhat small for the screen but its a good alternative
[Xoom General] squashpile:
Am I missing something? Droid newb here..

Long press - Folders - New Folder
[Xoom General] bogatyr:
In honeycomb there is no folders option after long press. Least not that I see.
[General Questions and Answers] NoWayHosei:
I love the ROM, when it works. At first I had a few apps that force closed, figured it might be a compatibility issue. Now I am getting a com.android.phone closing unexpectedly error, I press force close, it pops up again in about 2 seconds. I have rebooted, and it's still there. I can't do anything with the phone on because the error message won't go away. Very frustrated...
[Nexus One Q&A, Help & Troubleshooting] Drew11:
disregard, please.
[Captivate General] Firefly1428:
I've read up on the forums on this issue and because of my newbness , I'm confused a little. I have Cog4 flashed to my phone and I have no issue , But if I try Firefly or Axurma(?) I get little bars or no reception. I guess it has something to do with the i9000 ROMs and ATT. Are there any ROMs that use the same build as Cog , but with more bells and whistles like Firefly? How do I know which build a ROM is supporting that is captivate compatible ?
[Captivate General] kingmurry:
i have firefly on mine and flashed the ugjl2 modem and it helped with my signal
[Captivate General] Shammyh:
Search for more info and explanation but the dime store version is:

i9000 based ROMs (like anything JPX/JPY/JS3/JS5/JS7) require an i9000 radio and kernel.

AT&T based ROMs (anything based on KB1, and previous leaks) prefer an AT&T radio.

Single most important thing is to match an i9000 radio, with an i9000 based kernel. And an AT&T based kernel, with an AT&T radio.

Any i9000 ROM can be run on the Captivate if you use a specially designed kernel. If not, the ROM will boot, but certain functions (especially the orientation sensor) will not work properly.

If you don't do that, bad things *may* happen. There's plenty of "mix and match" but only to a certain degree.
[Captivate General] axis01:
Bottom line is, different roms use different modems. There are a few threads on modems that give dowload links. If you're on a I9000 rom, you have to use a I9000 modem. If you're on a KP1 rom, you need to use one that's compatible. It's as easy as copying the modem onto the root of your internal SD card then flash it with CWM. Different modems can give better reception, better DL/UL speed, battery life, and GPS accuracy. There's not one that is the "best" for everyone though. You need to try them to see what works best for you.
[Captivate General] REDMASTA:
This is the exact reason I went with the Cog 4.1 rom as it was based on the latest AT&T 2.2 update with the KB1 baseband so no reception issues.