yashsingh1/xdaforums huggingface dataset:
[Xoom General] odyseus:
Fair do's - I don't blame you! You've done enough :) As you say why re-lock on WiFi?

What I would really like to do is flash all the images to my UK WiFi Xoom and then try to install Bignadad's BigDX Xoom|Zoom Theme..

Previously flashing this theme soft-bricked my UK xoom - got loads of Force Closures. Installing the extracted images from you, still caused the same problem. Maybe it only works on the US WiFi Xoom, but I might re-flash with 'stock' ROM to see if that makes any difference? (I do have CWM nandroid backups in case of another soft brick!)

Cheers

Ody
[Xoom General] qubz:
Is there a risk with using these cause of zip extra bytes warning?
[Xoom General] pricej636:
Gee thanks.

Someone want to give a real answer? I understand the commands. How/where do I use them...
[Xoom General] xoppaw:
If you have your xoom plugged in and you computer/adb sees it, then issue the command "adb reboot bootloader" (w/o quotes) from the platform_tools folder. this will reboot your device into the bootloader where you can then use the fastboot commands listed in the OP
[Xoom General] qubz:
You need to download the fastboot executable from here

http://developer.htc.com/adp.html

You need to downloaded and install the android sdk-

http://developer.android.com/sdk/index.html

Put the fastboot file and the files to relock and return to stock into the folder ../platform-tools in the android sdk.

Assuming your device is unlocked and rooted, open a cmd terminal and navigate to the platform-tools folder.

From the folder run in the cmd terminal:

adb reboot bootloader

and then the commands in the post above from the OP to re-lock and return to stock.
[Xoom General] subminimal:
Did you reattempt and get the Xoom to re lock?

Now if we can just get Honeycomb source... :)
[Xoom General] BlackDino:
That would be the day.

I am glad we finally got the stock image though,

I was holding off flashing the kernel until I had a backup plan and now its here :)
[Xoom General] xoppaw:
I downloaded the files and extracted them on my xoom using ES file explorer and then copied them off to my computer. the xoom didn't give me any errors, but when i tried to download and extract the files on my windows 7 computer with winrar the userdata.img doesn't show up and i got a bunch of errors.
[Xoom General] Scourge1024:
When you're changing between versions (US/Canada/UK/Europe), you have to wipe your user data clean by doing a "fastboot -w". I suspect the userdata that Motorola included is a blank one. I managed to soft brick my XOOM the 2nd time around but wiping the userdata fixed things.

I suspect the new theme was based upon the US version.
[Xoom General] odyseus:
Well I have sucessfully flashed my UK WiFi Only xoom. Rooted it and applied the Tiamat 1.4.0 Kernel.

I have also install the Red Bignadad's BigDX Xoom|Zoom Theme !!

All OK. Note I have found it is best to flash bigrushdog Clockwork Recovery and run it using adb reboot recovery.

I found that I couldn't install Tiamat's 1.4.0 kernel by booting into recovery from the CWM app on my Xoom???

Anyway, at least UK owners can now take the plunge if they need to??

Cheers

Ody
[Xoom General] pricej636:
Thank you all, once I got ADB working everything went without a hitch.
[Xoom General] bwcorvus:
i just relocked my wifi :)
[Xoom General] odyseus:
That was BRAVE!!! (I assume you have a US xoom anyway?)
[Xoom General] robbiev80:
Anybody with a Canadian WIFI Xoom relock yet?
[Xoom General] fabian29906:
Ok I'll be "that" guy. Now that this is out is there any chance a dev can make a kernel that does NOT overclock but provide USB hosting and give us ext SD access? Particularly for those of us who have held out on unlocking and rooting our devices until we had this to fall back on? Just sayin'......(or asking really)
[Xoom General] bwcorvus:
I know someone working on this, way before this release.
[Xoom General] bwcorvus:
Yes USA WIFI. Brave? Not really, i have yet to see one not be recovered from a softbrick :)
[Xoom General] tritran18518:
I just want to ask :With this stock image, are we 100% safe to root our wifi xoom?
[Xoom General] Scourge1024:
You're never 100% safe. You can still screw things up by trying to re-lock without official Motorola images. At that point, it's possible nothing will see your Xoom when plugged in. That happened to me and my first Xoom.

You can't flash something your computer can't see.

But I don't want to scare you. If you do things right, you'll be fine. And there's now official files to revert back to 100% stock assuming you're not uber-bricked.
[Xoom General] qubz:
Heads up, Moto upped the original zip again and its not corrupt ;)
[Xoom General] tritran18518:
Does this error happen when rooting the xoom or re-lock the xoom without stock.img ( i believe you got this error too)
[Xoom General] ydaraishy:
[delete, mispost]
[Xoom General] BeagleBoy:
Nice to know that I got it right. :D I mean, I certainly thought I had done it right, but reassurance is nice. And, yes, I'm pretty sure that one byte is from the mounting. Odd, though, since I didn't think read-only mounts affected it.

Cool. After bricking one xoom, I'm very happy to let others try locking theirs.;)
[Xoom General] JaymZ37:
hello guys,

so with these officials image from motorola, it's possible to restore to stock my Wifi Xoom, European model ? (France, MZ604 model, same FCC as US/UK Xoom Wifi)

Thanks a lot for that
[Xoom General] Al936:
These images are from US WiFi model. So if you flash them you will have stock US Xoom and not European model
[Xoom General] Scourge1024:
That is correct. You guys in Europe should follow the steps BeagleBoy did and which I copied to rip the Canadian images out. My Canadian images are supposedly pretty close to the European versions.

Essentially, someone has to flash Tiamat or some other kernel that gives you basic root (adb shell root privileges). Then rip it (boot and system) from /dev/block/blahblahblah/by-name/ using the "dd" command. I won't go into detail but I'm sure there are lots of guys over there familiar with Linux and can do that.
[Xoom General] yoshitweaky:
not sure there are many consequences to loading the us stock on a euro/uk version of wifi only. Maybe books and a few apps wont work but i'm sure that can be easily fixed?
[Xoom General] Ambrosios:
i wonder

can you use the canadian system/boot/recovery and then use the US userdata

then relock it?
[Xoom General] dean_fx:
What is the difference in this update? Is it worth doing? What has changed...
[Xoom General] Scourge1024:
I've found that using mismatched userdata keeps you stuck at the boot animation. You'd need to do a "fastboot -w" to wipe your userdata.
[Xoom General] bwcorvus:
All 4 have to be stock for lock to work...you can not mismatch.

Sent from my Xoom
[Xoom General] Ambrosios:
it would be a nice if we can do that......guess we just have to wait for the official one to come out (non-us version)

which probably wont happen anytime soon i think
[Xoom General] pmp.s:
canadian mz604

Guys am confused right now, I have the canadian xoom wifi. I need to relock it to return it .

Is there a way to relock it? And where can i download the files from?

Thanks
[Xoom General] bwcorvus:
Not as of today...
[Xoom General] robbiev80:
If you bought it at FS or Best Buy chances are they'll have no clue that the Xoom is unlocked. Don't sweat it.
[Xoom General] pmp.s:
I bought it from telus!
[Xoom General] pmp.s:
got it! thank you
[Xoom General] robbiev80:
even better! lol
[Xoom General] ydaraishy:
The byte difference isn't the mount count, in case anyone was curious:

$ /sbin/dumpe2fs system-orig.img > 1
dumpe2fs 1.41.12 (17-May-2010)
$ /sbin/dumpe2fs system.img > 2
dumpe2fs 1.41.12 (17-May-2010)
$ diff 1 2
6a7
> Filesystem flags: unsigned_directory_hash
[Xoom General] Land Master:
Flashable Stock Kernel

Does anyone know how to create a flashable ZIP file containing just the components needed for the stock Kernel?

Well... I guess I should ask..... is anyone willing to do this? Pretty sure it can be done.

Thanks in advance.....

PS.. I looked through the Dev section and did not see such a file. Did I miss it?
[Xoom General] davidsos:
No can do which is why we had to wait for Motorola to release the stock locked img files for the wifi version but from what I see they've only done so for the US version.
[Xoom General] stryker759a:
Will this also return me to the stock Kernal from Tiamat 1.4.1?

Thanks

Jason
[Xoom General] Hexbug:
Yes, it should. I just did it. Patiently awaiting the update now.....
[Xoom General] Lcsglvr:
I am trying to revert back to stock. I can't access my tablet. I am at the "Starting Fastboot protocol support". I tried to flash boot.ing etc but it stays at <waiting for device>. I rooted and etc so know I have the drivers. Just in case, I ran the MotoHelper again. I can't figure out why it will not recognize my Xoom.

Any help?

Thanks in advance.
[Xoom General] stryker759a:
Well does 3.1 enable micro sd card?
[Xoom General] arrtoodeetoo:
Can someone post a mirror of this so I don't have to sign up and all that crap? I need these files for my theme.
[Xoom General] flooppoolf:
3.1 [root-ed] can i go to 3.1 [un-root-ed]

Can i UNROOT and RELOCK ???? :p
[Xoom General] Kalberro:
Un-rooting my XOOM

Was wondering if I follow the steps described to put my XOOM from rooted back to un-rooted will I lose all my installed applications?
[Xoom General] ted911:
Bricked !

I have the Xoom Wifi USA. I was unlocked and rooted. I tried to restore to factory so I could get the 3.1 update. I followed the instructions in the OP (although I have since read in a few other threads I should not have entered the last line(oem lock)). Now when I try to boot it only gets to the big M and then says Failed to boot LNX 0x0004 and the under that it says Starting RSD mode 2. If I restart it and hold volume down it will say Failed to boot LNX 0x0004 and then under that it says Starting Fastboot protocol support. My computer will not recognize the Xoom, so I can not do anything through ADB. I believe I am now bricked. Is there anything I can do or am I right ?
[Xoom General] bwcorvus:
Do volume down and power, when you see starting fastboot, type this command "fastboot oem unlock".

Sent From My Evo
[Xoom General] ted911:
It just says <Waiting for device>
[Xoom General] guard3:
Thanks, successful port to US Stock from my Singapore Build.

and 3.1 update was waiting for me from the first check update click :)
[Xoom General] monadzback:
intereseting
[Xoom General] VaKo:
Do I have to not re-lock the bootloader if I do this on the UK wifi xoom?
[Xoom General] iammodo:
UK WIFI XOOMER not waiting for 3.1 just cus im in the UK

Okay just followed each step and it worked first time.

Just had to do fastboot oem unlock at the start

relocked at the end as well worked fine.

Booted up and is now downloading the 3.1 update this is great.

so why is it taking so long for uk xoomers to get this normally?

if its just a software thing?
[Xoom General] ted911:
I'm still bricked ! Has this happened to anyone else ? Did anyone resolve it ?
[Xoom General] Scourge1024:
Doing an OEM relock is the number one way to brick a Xoom. There's really no need to relock. I bricked my first one that way.Returned it and got an exchange. RSD Lite, fastboot and adb all failed to see it meaning can't flash.
[Xoom General] ted911:
Did you return it to Motorola or to a store ? If you returned it to Motorola, what did you tell them happened ? Did they give you a hard time ?
[Xoom General] Scourge1024:
I went to Best Buy where I bought it and got an exchange. All you need to do is play dumb. Those Geek Squad guys like to think they're smart so I let them try to show me what I did wrong. They feel good, I get free entertainment plus a replacement XOOM. Win-win situation for all.
[Xoom General] doobes:
Sigh!

Finally got mine un-semi-bricked. The magic was to use the Motorola drivers not the stock Android drivers. I had had the stock Android drivers installed from rooting my Nexus 4 and while they seemed like they worked they really didn't.

Thanks for all the good information here!

Chris
[XPERIA X8 General] wujekandrzej:
have anyone succesfully tried to changed pixel density on our device? if you did, please leave a comment - i'd like to know which app and rom you used. thanks in advance.

btw. is it possible to lower the resolution on android devices? (resolution, not density, some people seem not to realise that these are two different things)
[XPERIA X8 General] XperianPro:
You can change densyti in build.prop about 140 and 150 looks very good but apps does not show properly.

Anybody know how to change resolution?
[XPERIA X8 General] wujekandrzej:
bump... how about the resolution? anyone?
[XPERIA X8 General] josecabre:
i hear about the aplication that change density, but i have the same questions that you have guys, sorry about my english
[XPERIA X8 General] Cardotso:
wich is the best LCD Density for our X8 ?

i am gonna try to put 150 on mine, i think it would be better ;)
[Galaxy S II Q&A, Help & Troubleshooting] Pulverizer:
I've seen this blog.

http://blog.clove.co.uk/2011/04/12/samsung-galaxy-s-ii-umts-frequencies/

yeah, UK clove store said EU galaxy S2 doesn't support US 850/1900

network. (They said that may be US 850/1900 UMTS frequencies are locked.)

But, I find google news.

http://www.mydaily-gadget.com/news/5718-att-getting-samsung-galaxy-s2-gt-i9100-fcc-says-i-do

Follow this news, EU galaxy S2 using US GSM 850/1900 networks.

Who is say that TRUE? :D:D:D:D

i'm very confused.
[Galaxy S II Q&A, Help & Troubleshooting] apwhitelaw:
Quad band GSM 850/900/1800/1900

Source: http://www.samsung.com/global/microsite/galaxys2/html/specification.html

It should work.
[Galaxy S II Q&A, Help & Troubleshooting] Pulverizer:
So, only using ATT GSM network?

ATT UMTS network can't use?
[Galaxy S II Q&A, Help & Troubleshooting] kreoXDA:
That first link (that I provided earlier tonight I think) - read it to the end please, Clove has all the info on that page, just finish reading it. sorry for the tone , but I think you did not pay enough attention - there are comments to that blog post that say clove confirmed with the manufacturer and local distributor that all 4 bands are present.
[Galaxy S II Q&A, Help & Troubleshooting] Sebring5:
I'm confused here

I have SGSII ordered from Clove. I plan to use it with ATT sim card. Have I made a mistake? Will I be able to use it? Do I need to cancel?
[Galaxy S II Q&A, Help & Troubleshooting] kurtkbee:
I hope it works well with AT&T since I intend to get this phone.

My current (imported) GT-i9000 did not properly support AT&T and has very poor call quality and call drop issues.
[Galaxy S II Q&A, Help & Troubleshooting] mickliq:
Although Clove originally said they doubted it would support 850/1900 3G+, they did later confirm their stock would be quad-band 3G. So no need to worry about support for NAM 3G.
[Galaxy S II Q&A, Help & Troubleshooting] ignign0kt:
Once someone get's the GS2 in USA on ATT, can you confirm that it indeed works on Edge AND 3G?
[Galaxy S II Q&A, Help & Troubleshooting] cmd512:
That's because the i9000 is only tri-band UMTS and only supports AT&T's 1900 frequency. When it gets to an area where the 1900 H/3G signal is weak, it can't switch over to the 850 UMTS simply because its hardware doesn't support it. So, then the phone call drops. You'll notice if you switch the i9000 to 2G/Edge, you'll never get a dropped call... because it's quad band GSM.

Also, ever notice you never get dropped calls when stationary and on H/3G? That's because with a solid 1900 UMTS signal, the i9000 will never search for the unsupported 850 band.

(And yes, I have confirmed all of this as I also own an i9000.)

i9100 supports quad-band UMTS with 850/1900 H/3G, so you will not have the frequent dropped calls anymore.
[Galaxy S II Q&A, Help & Troubleshooting] pepemosca:
Here are the frequencies for AT&T: http://en.wikipedia.org/wiki/AT&T_Mobility#Radio_Frequency_Summary

Frequencies used on the AT&T Network

850 MHz	GSM/GPRS/EDGE	2G

1900 MHz	GSM/GPRS/EDGE	2G

850 MHz	UMTS/HSPA	3G

1900 MHz	UMTS/HSPA	3G

700 MHz	LTE	4G

So, the i9100 International will do almost all. Except LTE.
[Galaxy S II Q&A, Help & Troubleshooting] Pulverizer:
Thanks for your information. :):):)
[G2 and Desire Z Android Development] amazinglarry311:
Admin Edit: Links removed at OP request. I believe they will be available elsewhere. I have always ben very anti-setcpu, but profiles with this kernel really are a must if you want a smooth experience without constant freezing.

This is pershoots source code as of 04/25/2011 with added overclocking patches, all governors available, swap (requested) with a max scaling frequency of 1.708ghz (1708800) YOU SHOULD NOT HAVE THE USB MOUNT ISSUES present in flippy's kernel.

YMMV - Overclocking seems pretty unstable above 1.708 with the current state of the kernel (trust me i tried MANY different voltage variables, different schedulers etc..) that's why 1.8 and 1.9 are not supported, and will not be until they are stable for me again.

DO NOT SCALE ABOVE 1.516 without setting scaling governor to performance, or raising the min cpu frequency as you will experience lockups, setcpu profiles are useful in this situation. screen off profiles should have a MAX frequency of above 768 (this way when the screen goes back on it will ramp to the higher freqency THEN ramp back to the oc'd 1.708 without the jump from 245 causing a freeze) if you want to go with ondemand scaling and want the max at 1.708, you will have the most luck with min at 806 (even then it can and likely will freeze)

Edit: testing screen off profiles, it looks like you can pick whatever you want, currently mine us set to 245 min 368 max. No issues yet.

I have my device set for 368 min 1.708 max performance governor on boot and it hasnt frozen in the last two days. scaling through frequencies, or if the delta between min and max is too high, you may get a kernel panic and a battery pull will be required.

My particular setup (recommended):

on boot - 368 min, 1.708 max performance

screen off - 245 min 806 max ondemand (allows idle speed at 245)

battery < 50% 245 min 806 max ondemand

The same rules basically apply with this OC kernel that applied to flippy's. I'm not responsible for any damage that may result from your use of this kernel. yada yada yada.

you should retain wifi, gps, etc.. if not, flash it again, you did something wrong.

freezes? lockups? lower your clock speed, they shouldnt happen with any more frequency than with pershoots kernel if you stay at 1.516 and below. above that, if you experience a freeze, a last_kmsg wont help, the kernel failed to sync and panicked, there is nothing i can do about that. sorry.

wake-lag? i've gone over that, but here we go again:

generally with oc kernels:

oc+screen on/off animations+brightness > 50% = no wake lag

oc+screen on/off animations+brightness < 50% = wake lag

it isnt ideal, but get a program called screen filter from the market to apply a lesser brightness when above 50% so you dont experience the wake lag.

Enjoy. ;)

There is weirdness with benchmarks, if you've oc'd and you know it should be higher, reset the scaling options in cm settings and try again. It's very weird and i havent put together a full list of what causes the behavior, more as it develops i guess.
[G2 and Desire Z Android Development] evilive27:
Awesome thanks. Seems to be pretty stable for me at 1600 ondemand.
[G2 and Desire Z Android Development] bloodhawk:
The benchmark screenie is at 1.7 Ghz?

And thatnkyou for the kernel ..will be checking it out in a while :)
[G2 and Desire Z Android Development] adame09:
Works good using your recomended settings
[G2 and Desire Z Android Development] amazinglarry311:
It's a stable as I could get it. Been using for a couple days without issue to make sure before I posted it.
[G2 and Desire Z Android Development] dixxa:
Any chance of adding the smartass governor ?

I've read many things about that and nobody never included it in a kernel.

Only in roms.

Your kernel is really good so was wondering :)
[G2 and Desire Z Android Development] Carphedon:
This is awsome! Kernel is running fast and stable. Although i don't clock it all the way up to 1700 i love that i finally can use pershoot kernel with interactive governor.

Thanks very much!
[G2 and Desire Z Android Development] xboarder56:
will be adding to my rom on next version
[G2 and Desire Z Android Development] CarpeNoctem:
Same here if you don't mind
[G2 and Desire Z Android Development] amazinglarry311:
Don't mind at all, for the person who asked, there is source for the smartass governor, I just need to locate it and merge. I'll look into it today.
[G2 and Desire Z Android Development] theSpam:
Will flash tonight with the latest CM nightly. Thanks :)
[G2 and Desire Z Android Development] KCRic:
This show promise and potential. Love, love love. Did you ever find the source for the smartass governor?

Found the this on github. It's the smartass source from a kernel for the HTC Shift, should be the same mostly.

Also this governor look interesting, maybe give an alpha release with this one in it for testing?:D Scary just sounds like a bada$$ name for a governor. It's from Scaryghoul btw, just to give credit.
[G2 and Desire Z Android Development] mejorguille:
Thanks for this amazinglarry. I'm gonna test this out for a few days before I can give you some useful feedback.

In the meantime, can I refer you to a kernel in the MT4G section that seems to try to accomplish exactly what you are doing (all available kernels, high overclock, etc.). It has all the source readily available. The link is here. http://xdaforums.com/member.php?u=2491887
[G2 and Desire Z Android Development] amazinglarry311:
I'll take a look. Gracias.
[G2 and Desire Z Android Development] ihateusernames:
Please forgive my ignorance but what might this offer over pershoots kernal? His newest kernal fixed a huge headache I had with wifi and I don't want that headache back. Is it just the addition of higher oc and the added govenators or is there more added as well?
[G2 and Desire Z Android Development] amazinglarry311:
No, just, swap, governors, and overclocking a bit more.
[G2 and Desire Z Android Development] mejorguille:
I'm getting instability with the camera and gallery. It either locks up or saves pictures as a black square. Gallery FC's when I try to delete pictures. As far as I recall, this didn't happen with pershoots or stock CM. I'm running 7.0.2 with no profiles, clocked at 245-979 on demand with CM settings, no setcpu. When I can get in front of a computer with adb ill post some logs.
[G2 and Desire Z Android Development] amazinglarry311:
I'm not able to reproduce, camera and gallery are working st 806 and 1.708 on my device, clear pictures, no force closes.

Grab some logs, there should be very little difference in functionality (if any) between this version and the official version of pershoot's kernel, unless he does some magic that isn't in his git, which I highly suspect, seeing as how quadrant scores are a little lower at the same clock speeds with my version and his.

But as far as functions and drivers, you shouldn't have issues.
[G2 and Desire Z Android Development] mejorguille:
I'm thinking its something wrong with my setup. I reflashed pershoots kernel, cleared caches, and ran a fix_permission. I no longer have force closes but my camera isn't saving? Ill have to look into it.
[G2 and Desire Z Android Development] amazinglarry311:
Let me know if you can pinpoint the issue, and need some possible help.
[G2 and Desire Z Android Development] xboarder56:
thanks for the kernel amazinglarry311i compiled a boot.img and now its in my rom v1.9.5 :D
[G2 and Desire Z Android Development] amazinglarry311:
Just in case, you may want to include the wifi module as well.

It'll if course stay updated as pershoot updates as well, let me know, I could do a custom build with the rom name etc.. Pm me.

Cheers.
[G2 and Desire Z Android Development] sino8r:
Larry, nice work man! Any plans for a FroYo version or is it completely dead? I may just be living in the past but there a couple minor things holding me back... Either way, great stuff lately!