yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] maxvsmith:
Hello,

I am not new to android I've had two asus transformer pads currently have the one I am using with Tapatalk. My dad's friend had the same tablet I do and his screen stopped working so my dad's friend who's friend works for motorola gave him a motorola xoom to give to his friend with the tablet that wasn't working. Shortly after my bluetooth stopped on mine and he told me the other day that she has another xoom that is looking for a home asked if I'm interested.

So long story short I got a free Motorola Xoom. It's a MZ640. It's a 32 GB wi-fi only model but it's on 3.1 and can't upgrade. I checked online and the model I have should be able to upgrade to jellybean through system update. However the back of it says something like confidential motorola only and not for re-sell. Also the boot animation has a cool android wallpaper with the honeycomb boot. But when I do the Volume Up or Volume Down start up there is no recovery manager to go into it just freezes. So maybe this is a dev version of some kind of special (in a not good way) version and I am stuck unless I root. I took some pictures to try and explain it better. If anyone has seen this model before or not please let me know. If this works out and I can get jellybean on it (PC is dead..need recovery disk so can't use that) I might replace the tf300t with the xoom. The HD Sound dock looks killer. My dad's friend got it.

Also, strangely enough it came with a micro hdmi cable, car charger, and cable. There was no box..would have been interesting to see the box. If anyone needs any other number or info I have it. Just trying to figure out why I can't do jellybean update.

I have considered doing a factory reset but a little nervous if that might mess something up. Any advice is appreciated thanks guys and I hope to enjoy this Xoom.
[Xoom Q&A, Help & Troubleshooting] oldblue910:
Dude, I would have responded to this earlier had I seen it. Sorry about that.

First off, that's really cool. What you have is an MZ604 WiFi-only US Xoom that was used inside Motorola for engineering and testing. It's running an engineering build of Honeycomb 3.1, which is why you're not receiving the OTA updates. What we'll have to do is get stock production firmware onto the device. At that stage, you'll get your updates. Here's what you'll want to do:

1. Install fastboot and adb drivers on your PC. You can find instructions for that here: http://androidteen.com/setup-adb-and-fastboot-driver-with-android-sdk/

2. Reboot your Xoom into bootloader mode. To do that, turn your Xoom off. Then, power it back on. Once you see the Motorola logo, count to three at a reasonable speed and press volume down. At the upper left of the screen, you'll see some text. Press volume down until you see "fastboot mode" and press volume up.

3. Connect the Xoom to your PC via USB.

4. At a command prompt, type "fastboot devices". You should see your device listed. If you don't, then the drivers aren't installed correctly.

5. Type "fastboot oem unlock" and follow the on-screen instructions on your Xoom to unlock your bootloader. If the bootloader is already unlocked (since it's an engineering device), you will get a message in your command prompt window telling you as much. Unlocking your bootloader will wipe all data from the tablet so make sure you back up any photos, documents, music, etc. that you want before you do this!!

6. If the bootloader did need to be unlocked, it will reboot after the unlock is done. Once it reboots, perform step 2 again to get the bootloader back into fastboot mode.

7. Go to http://www.randomphantasmagoria.com/firmware/xoom/tervigon and click the link for "images" in the first row of the table (for Android 3.0.1, build HWI69). Download that file, then unzip them somewhere on your PC.

8. Go back to your command prompt and go into whatever directory you unzipped the files into.

9. Type the following commands, in order:

fastboot flash recovery recovery.img

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash userdata userdata.img

fastboot erase cache

10. Optionally, if you want to re-lock the bootloader (unless you're going to run a custom ROM at some point, I recommend this for security purposes), type "fastboot oem lock". Follow the on-screen instructions to re-lock the bootloader. At the end of the lock process, the Xoom will reboot. Let it boot up.

11. If you choose to leave your bootloader unlocked, just type "fastboot reboot" and you'll boot up.

12. The Xoom will now boot into stock Android 3.0.1. At that point, you'll get eight separate over-the-air updates that will eventually get you all the way up to Android 4.1.2/Jelly Bean, build JZO54K.

13. Once you get the Xoom updated all the way to JZO54K, I'd do a factory reset again just to make sure everything is clear and you're starting anew.

At that point, you should be good to go. Let me know if you have any trouble.
[Xoom Q&A, Help & Troubleshooting] maxvsmith:
Thank you for replying. Oh so that's why I could never update. It said verizon on it too that must explain the locked bootloader. I just recently learned about how verizon locks their bootloaders. I already did unlock the boot loader and installed recovery and tried a bunch of roms and I'm running CM 10.1 I was nervous of trying it at first but after realizing even if it's an engineering and testing tablet it's still the MZ604 and it should be similar to the others in terms of rooting and unlocking the bootloader. And fortunately I was right.

It actually came with really cool apps that I've never seen before too. I wish I backed those up before I factory reset. I tried factory resetting it initially but I lost a few of the apps and special things and it went to a Honeycomb 3.0 I believe. The one before the SD card support.

But I'm loving this xoom now that it's on CM 10.1 and using Jellybean 4.2. Even though it's tegra 2 and not as fast as my TF300T and other tablets out there the unique design, the placement for the ports and the accessories like the HD Dock make this a very unique tablet. It was never one I intended to buy so it was really cool getting it for free. My friend has one just like mine and he's not into hacking, rooting, and customization so I might be able to get the special apps and stuff that was on it from him. But even though I've never unlocked a boot loader once I figured out how to use command prompt it was really easy to do. Thank god for youtube.
[Xoom Q&A, Help & Troubleshooting] KidJoe:
The Verizon XOOM's (MZ600/MZ602) boot loader was not locked any differently than any other Xoom (example Wifi MZ604). It is/was unlockable out of the box, and Moto had the directions on their web site.

Funny, if it says Verizon on the front, I would not expect it to be a MZ604 model, unless the previous owner flashed the Wifi only Xoom (MZ604) firmware/software onto it. Does that bar code label on its back have a model or MEID on it?
[Galaxy S III Mini Q&A, Help & Troubleshooting] Acc_Fiesta:
Hello.

yesterday i tried the new Dmod rom and my phone worked 100% corectly. after 2 hours i flashed the Golden kernel V2 next to it. and my phone wont boot anymore.

i managed my way out of the problem by re- partitioning my phone with a pit file i found here and an old faria kernel i already had tried and knew it was working.

but offcourse i'm a real hardhead so when my phone worked again on the Faria rom i tried the Dmod V6 again and offcourse my phone is bricked again :eek:

the only problem is that i cant do the previous fix anymore because it doesnt work anymore.

when i try to boot it i get the samsung galaxy logo and then black screen.

i cant boot into recovery(it's a know bug in the golden kernel V2) by using the 3 button combo. and i cant reboot my phone in recovery with ADB or something because i cant boot phone. so a reboot to recovery is not possible.

anybody has any idea's what i can try next? anybody has an idea of a pretty standard kernel i can try to flash using ODIN (the only way i can get to the phone is going into download modus with the 3 finger combo and using adb/odin, yes download modus still works)

ow and i'm going to the welcome pages in a minute. its my first post over here!
[Galaxy S III Mini Q&A, Help & Troubleshooting] kicker63:
Try one these stock kernels here.

http://xdaforums.com/showthread.php?t=2187295 if you have a standard i8190 try the last kernel but new AME1 at bottom of the list.
[Galaxy S III Mini Q&A, Help & Troubleshooting] dolar4ik:
Have you tried to boot to download (odin) mod?
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
A I remember the three button to recovery should work on golden kernel v2. It's the "reboot recovery" command that doesn't work. Makes a normal boot instead.
[Galaxy S III Mini Q&A, Help & Troubleshooting] Acc_Fiesta:
tried a stock kernel and one kicker63 said. no progress.

still just the samsung galaxy logo and nothing else.

i can get to download modus. that aint a problem ( i'm happy this still works )

@ Tyson: in the thread of the golden kernel V2 it states the recovery mode aint working... could be its the adb commando or the 3 buttons combo... dont know. all i know is that the 3 button combo is not working anymore on my device!

anybody knows a way to flash a recovery with odin?(just cant find it.... would be nice to try to get to recovery so maybe i can wipe and flash from there! )

thx 4 reply's
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
You'll find all recoveries in my signature :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] Acc_Fiesta:
found an old rom(HOME_I8190XXAMA1_I8190OXAAMA1_790526_REV00_user_low_ship.tar.md5) flashed with odin.

phone reboots. goes to recovery(so that works again :victory:) asked to install an UNTRUSTED.zip did this.... phone reboots... works....

i realy like have NO idea what the solution is for my problem. the good thing is its working.

so steps are: flash another kernel(preferable standard one ) + repartition with the .pit file using odin(you wil find the .pit file here on the forum) then try some odin flashable roms....

not a realy clear solution but i hope somebody can use it in the future.

thx everybody for the reply's. realy nice to see some new input!
[Desire HD Q&A, Help & Troubleshooting] Creadskel:
Dear someone who reads this

Today I was checking my phone and it just froze so I removed the battery, booted it up and then it wouldn't boot.

I made a back-up and cleared the cache and dalvik cache and that didn't help.

I wiped my phone and restored everything BUT my data partition.

But that's the only partition I really want to restore.....

Can someone help me please with getting my data back?

I'm running Jellytime R11 on my Desire HD A9191, ask for more details if you need them

Greetings,

Don
[Android Q&A, Help & Troubleshooting] Droid Premium:
I am still trying to get Jelly Bean on a device right now. I went from trying to port a JB ROM from a clone to just plain out compiling an AOSP ROM. I already got everything set up. I am even compiling a ROM right now. (full-eng). I figured that this was the option for all devices but being an idiot i started reading and the 10 options or so didnt include my device. It was nexus and samsung phones. Is there a way to compile AOSP or even Cm10.1 or AOKP for an Unsupported device? I am dying to find out and get this released!

Any help will be greatly appreciated!
[Android Q&A, Help & Troubleshooting] zelendel:
The main thing is you will need a kernel to support the device. So you will have to track sown the kernel source code.

Wayne Tech Nexus
[Android Q&A, Help & Troubleshooting] Droid Premium:
I have a kernel source code for it. This is it right here: https://github.com/leopesto/kernel_mtk6577

Can i build AOSP Jelly bean from that? And if so. how?
[Android Q&A, Help & Troubleshooting] zelendel:
Well you need to know it that is a JB kernel to begin with. Then I would look at the tut for building a kernel. Just a heads up. Most of the MTK so called kernel source is never the full and proper source code.

Wayne Tech Nexus
[Android Q&A, Help & Troubleshooting] Droid Premium:
Well i have that one and a source code from a clone (TCL-S600). I am almost positive that that kernel will work. My goal is to either compile some sort of Jelly Bean ROM for this device or De-grade it to Gingerbread. The users on this device don't like ICS for multiple reasons so I am just trying to do what they asked. Any suggestions?
[MDA III, XDA III, PDA2k, 9090 General] DaftMule:
Got my XDA IIs a couple of weeks ago and I presume it has the latest ROM.

(BTW, what is the "ROM"...been trying to find a definiton on here but no luck! Is it the install of Windows or is it the equivalent of the BIOS on a normal PC? Sorry if I've missed the link but if there isn't one, it may be handy to have a sticky with terminology in it for us noobs to the site and the BA)

Anyway, as to my XDA...it locks up all the time. e.g this evening, I realised that I had a call coming in but no sound, just the flashing screen image. When I pressed the green answer button....nothing. Locked solid. Had to do a soft reset. Other time it seems to happen is when I take it out of the dock and then there's just general lockups when I use progs. I don't use it heavily but often have to reset 3 or 4 times a day.

Shame really as I like the functionality...when it works :? The only other apps I have put on are PocketNav (well handy for closing down apps properly) and a couple of games.

Any pointers? Can you reinstall Windows on it or is that what this whole ROM thing is about?
[MDA III, XDA III, PDA2k, 9090 General] cruisin-thru:
The ROM is Read Only Memory which is used in many different appliances, in your phone the ROM contains the equivalent of the windows operating system, on your desktop the operating system is loaded from the hard disc by way of a short piece of code called a bootstrap, in your phone the ROM contains the basic operating system and programs, this memory is flashable and therefore can be upgraded. The BIOS I think is the basic input output system that controls the motherboard, irq, dma etc.
[MDA III, XDA III, PDA2k, 9090 General] DaftMule:
Thanks for that. I thought it was something along those lines. I understand pc's but this is the first PDA type device I've owned so I've gotta get used to it setup.
[Xperia Z Themes and Apps] Zephyr!:
Google Edition Camera dumped from Galaxy S4.

Working Photosphere, just flash in recovery.

For HD bootanimation and more 4.3 goodie see my signature :)

Happy flashing:D

Here

Or here

http://xdaforums.com/showthread.php?t=

Press thanks if you like my work/advice.
[Xperia Z Themes and Apps] JPWOA:
Will this remove Z stock camera app?
[Xperia Z Themes and Apps] Zephyr!:
No buddy.

But just for being in a safer side, back up your camera apk. What say? :)

Press thanks if you like my work/advice
[Xperia Z Themes and Apps] JPWOA:
No way to make it work? To have both apps working?

I would like to test but I like Sony camera app very much... :(
[Xperia Z Themes and Apps] Zephyr!:
It will not remove stock camera

Press thanks if you like my work/advice
[Xperia Z Themes and Apps] JPWOA:
Oh sorry my bad, have not read it right :p

Will try it later ;)
[Xperia Z Themes and Apps] juanmaasecas:
Zip is corrupted here. Anyone else have this issue?

Edit: my bad. I was trying to download without entering to mediafire and writing the captcha :(
[Xperia Z Themes and Apps] Zephyr!:
Lol :p

Press thanks if you like my work/advice
[Xperia Z Themes and Apps] juanmaasecas:
Now working Ok. Actually I installed the normal apk and it worked fine too, except the scenes. It's strange we can only choose 2 scene modes (night and action I think) and the icons and names doesn't fit. So I decided to install this one to check if the issue was solved here, but it doesn't. I'll continue with stock app since actually I don't need photosphere.

Enviado desde mi C6603 usando Tapatalk 4 Beta
[Xperia Z Themes and Apps] Zephyr!:
Yeah there are sone sort of error wirh scene modes I read at fonearena

Press thanks if you like my work/advice
[Xperia Z Themes and Apps] YudiA1:
Just flash that mod on my XZ. that working but some message is appear, like Google play service stopping, geotaging stopping and some other else. Idk how to fix that (noob here) so i choose restore all my system use twrp.

btw my device run FW 423 TW.

and should i clear dalvi/canche after flash this mod.

Thank for your great job. i hope can run on this device without other program stopped.

thank you and hope u can fix that :thumbup:
[Xperia Z Themes and Apps] Zephyr!:
No idea about camera apps :p

Press thanks if you like my work/advice
[Xperia Z Themes and Apps] Zephyr!:
Can someobe test this for me?

AOSP messaging app, move to system/app

http://db.tt/e7QYomQB

Press thanks if you like my work/advice
[Xperia Z Themes and Apps] imna357:
It worked on my Z, photosphere used to force close, now its perfect. Thanks a lot mate...BTW it merges on my old camera app, no other camera is present. I'm on a PA 3.6 ROM
[Xperia Z Themes and Apps] GatoL0c0:
I flashed the zip in recovery and it did replace my CM10.1 camera. Haven't tried manually dragging files files over to see if it would make a difference. I currently have the older Photosphere running side by side with the CM10.1 camera. I installed this version by manually dragging files and setting read write permissions.

-*-*-

Sprint - Galaxy S3

CM Nightlies / fre3
[Xperia Z Themes and Apps] mlamlam:
Same as you, now installed GAPPS from recovery could fix this...

but each time now reboot got a message "Android is upgrading" and now I am going to reflash the ROM....
[Xperia Z Themes and Apps] Zephyr!:
Please someone test this
[Xperia Z Themes and Apps] Vaith:
Why you can't test it? I don't have time to test and if this won't work I don't want to restore whole system.
[Xperia Z Themes and Apps] Zephyr!:
This messaging application, I customize AOSP apps. Lol do you think I should buy each device?

Just move this to system/app

Make.Believe
[Xperia Z Themes and Apps] fards:
You don't need anything in that zip except the gallery apk on 4.2.2.

The libs already exist and work fine as does gmscore

There's been several releases of this already. I don't really think you can claim this to be your own work...
[myTouch 4G Android Development] coderzs:
Downloads

changelogs - 28.10.13

​
[myTouch 4G Android Development] coderzs:
github - http://github.com/carbon-glacier
[myTouch 4G Android Development] coderzs:
2321
[myTouch 4G Android Development] ＿ⅠSmile™^_^:
wow，you are awsome guys!Would you consider built the MOKEE for galcier？https://github.com/MoKee http://www.mfunz.com/
[myTouch 4G Android Development] coderzs:
4.1 ?
[myTouch 4G Android Development] ＿ⅠSmile™^_^:
4.22:good:
[myTouch 4G Android Development] coderzs:
okay will build it tomorrow .. or today ... :)
[myTouch 4G Android Development] N_otori0us_:
I love you man lol!

EDIT: but you can't even lie, this is a pretty good rom :) I had some good battery life with it too
[myTouch 4G Android Development] coderzs:
ahahhah :laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh:

:highfive:
[myTouch 4G Android Development] coderzs:
I sat an hour on the forum just to see your reaction
[myTouch 4G Android Development] N_otori0us_:
lol, are planning to build the Avatar ROM too? I'm gonna try and port that, but you could build it lol. And does the camera work fine? My port from the 2shot had some FC issues; but I heard they are common on ports to the doubleshot. This is my new daily driver :)

---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------

lol I'm actually happy since I suck at porting :P and it encourages you to build more for our phone :)
[myTouch 4G Android Development] coderzs:
no ... i dont want to build avatar rom .. and yes camera works fine . im currently building Root-Box rom :victory:
[myTouch 4G Android Development] N_otori0us_:
If you look at it, your actually the only reason our phone is surviving lol. Look at the resource bible lol. And if I do port that Avatar ROM, its still gonna be pretty buggy lol.
[myTouch 4G Android Development] ＿ⅠSmile™^_^:
Thank you, I am willing to become a test, if you want.
[myTouch 4G Android Development] rowdykumar786:
headphone Overheat Battery?
[myTouch 4G Android Development] KuShToKeR:
Sorry missed this somewhere...but whats trds gapps?? been flashing some time never seen or atleast noticed this. THANKS coderzs for keeping phone alive... :)
[myTouch 4G Android Development] coderzs:
Its gapps with support black ui ( if its enabled in settings ).
[myTouch 4G Android Development] Metalingus903:
Usual jb issues?
[myTouch 4G Android Development] ughoji:
How was that done?.those icons at the corner that's why I flashed this ROM.now ain't seeing it
[Galaxy S III Q&A, Help & Troubleshooting] omgbuffguy:
Hello,

I will have to give background info on this before anyone can help so bear with me please ::).

I live in Pakistan and I bought a i9300 directly from samsung. In the beginning of the six months i owned the phone, I never rooted or put custom ROMs on it. Then unfortunately I got SDS. I gave my phone to a local repair shop (non samsung, but highly reliable, I bought the phone from there) who switched the motherboard on the phone. After I got it, I rooted it and started installing custom ROMs on it. First it was cyanogenMod, then Paranoid Android and Supernexus +AOKP and others. Everything worked fine. Then I installed Omega ROM (Samsung based ROM which changes the modem). Everything went fine, but I was unable to connect to my network (No texts, calls, data connectivity). It detected my network(Ufone) but was unable to register on it when I manually tried to. I mega-wiped my phone, cleared cache and factory reset and did everything. Alternatively, the following steps I also tried.

1)Checked if my IMEI is intact. It was. (I have EFS backups too)

2)Checked if my serial # is different. It is still the same (No need for Ariza Patch)

3)Checked if my SIM works. It does on different phones.

4)Checked my APN settings. They were fine. I even manually changed them to match the carriers

5)Changed my CSC settings (using the playstore app). Still doesnt work.

6)Checked different modems from the appropiate thread (I have tried Europe Unbranded, Middle East, Egypt and many others)

7)Restored nandroid backup of original stock 4.1.2 Sammy ROM, still not connectivity.

8)Flashed using ODIN, the stock 4.1.2 ROM for my country (Using SAM mobile). Still no connectivity.

9) Matched my RIL with my baseband (using the GetRIL app), still didnt work.

Stock Samsung 4.1.2 ROM details before OMEGA flash in which everything worked:

AP: I9300XXEMA2

CP: I9300XXELLA

CSC: I9300OJVEMA1

This has happened to me the 5th time now (Phone is currently at the repair shop) and I have sequentially tried every one of the steps I have mentioned. I called up the repair shop and they said that I can come tomorrow and pick it up, all they have left to do is "SIM UNLOCK "the phone. That confused me a lot. I will go tomorrow and ask them details as to what they meant by that. So my question is basically this:

1) Is it possible that the motherboard they put into my phone is from a software-unlocked phone not a hardware unlocked? (Is the 'unlock' on the motherboard of the phone)

2) Is there a way to find out if my phone is software or factory unlocked?

P.S.

Every single time I hand in my phone, I obviously unroot it and install stock on it (regardless of the fact that it doesnt connect to the network). But every single time I get my phone back, its ALWAYS ROOTED.. I even asked the technical team guy and he had no idea what I was talking about (repairmen here dont have that much of knowledge, they tend to follow guides online, thats it). So could it be that my connectivity issue is just because its software unlocked and not hardware?

Thank you!
[Galaxy S III Q&A, Help & Troubleshooting] omgbuffguy:
bump