Database Info

[Q] Stock OTA 3.2 to Tiamat Katana, is this possible?

My Xoom is completely stock and I just received and installed the 3.2 update. I am pretty disappointed in the SD card support and lack of other features. I held off on rooting and installing Tiamat before as I wanted to see what Google would give us, and well I think I have waited long enough to see that it pales in comparison to what you devs can do.
So now I would like to give the Tiamat kernel a try. So I read through several of the threads and on the Tiamat 2.0.0 Kernel thread it assumes you are on 3.1, where I am already on 3.2. As it took me several months to convince the wifey that I needed my Xoom I do not want to risk bricking it, so I am looking for some help.
-First, is it currently possible to go straight from complete stock 3.2 to Katana?
-Second, and much more difficult, can someone provide me step by step instructions? I've seen several of the threads out there, some of them are very helpfull, some get me part way, but none of them cover this exact upgrade scenario. This just makes me very concerned with doing something wrong or if something changed in 3.2.
I know this is a lot to ask, but I think there are a lot of people who would benefit from this information.
Thanks

HuckFinn said:
My Xoom is completely stock and I just received and installed the 3.2 update. I am pretty disappointed in the SD card support and lack of other features. I held off on rooting and installing Tiamat before as I wanted to see what Google would give us, and well I think I have waited long enough to see that it pales in comparison to what you devs can do.
So now I would like to give the Tiamat kernel a try. So I read through several of the threads and on the Tiamat 2.0.0 Kernel thread it assumes you are on 3.1, where I am already on 3.2. As it took me several months to convince the wifey that I needed my Xoom I do not want to risk bricking it, so I am looking for some help.
-First, is it currently possible to go straight from complete stock 3.2 to Katana?
-Second, and much more difficult, can someone provide me step by step instructions? I've seen several of the threads out there, some of them are very helpfull, some get me part way, but none of them cover this exact upgrade scenario. This just makes me very concerned with doing something wrong or if something changed in 3.2.
I know this is a lot to ask, but I think there are a lot of people who would benefit from this information.
Thanks
Click to expand...
Click to collapse
The quick answer to your question is Yes, you can go from stock 2.3 to Tiamat Katana 2.0 kernel, but you must be rooted.
Are you rooted? If so, and if you have already installed Clockwork Mod Recovery 3.2.0.0 (from solarnz' thread in Development) you can just flash the Katana kernel and you should be fine.
If you are not unlocked and rooted--you can follow the directions here:
http://forum.xda-developers.com/showthread.php?t=1170760
There are actually some more user-friendly (for noobs) instructions http://forum.xda-developers.com/showthread.php?t=1130996 in this thread, but for STEP 5 (ROOTING) you have to substitute the method from jase's post (above) for the instructions for Step 5 in the "idiot's guide" I can't find any 3.2 root files yet. It's the same procedure but a bit more hands on. No matter what you do, you will have to use adb to unlock your bootloader and root, so gather all the necessary files, drivers and print out your instructions.
One thing to know is never try to install a .zip file through adb...that will cause massive headaches. However, it seems pretty hard to actually brick one of these Xooms through updating and flashing. (Don't drop it into water, though!)

Thank you for the information. All the posts asking for help because something did not go right still have me pretty apprehensive. I am not at all interested in over clocking, so it is really the what I assume is proper SD card support and USB tethering that interest me the most.

HuckFinn said:
Thank you for the information. All the posts asking for help because something did not go right still have me pretty apprehensive. I am not at all interested in over clocking, so it is really the what I assume is proper SD card support and USB tethering that interest me the most.
Click to expand...
Click to collapse
It's only by rooting that you are able to get the full functionality of the Xoom. It's great as it is...HC 3.2 is very good and improved, but this device is made to driven like a sports car, not just sat in like a minivan.

okantomi,
Well I have gone back and forth on wether to root or not and you have been very helpful with pointing me to good information. I am hoping you do not mind answering a couple more questions.
-In the "Idiot's guide to flashing" you pointed me to it installed CWM before rooting. Is this the proper order or would you root first? I know I should just follow the guide and give it a shot, but that just seems odd.
-Can you explain to be the difference between the Tiamat kernels and the ROMs? My assumption is that the ROM would include the kernel, but I have a strong feeling that is incorrect. I have read posts of installing the ROM first and then the kernel and I am just more confused.
Thanks, one day I will get there.

HuckFinn said:
okantomi,
Well I have gone back and forth on wether to root or not and you have been very helpful with pointing me to good information. I am hoping you do not mind answering a couple more questions.
-In the "Idiot's guide to flashing" you pointed me to it installed CWM before rooting. Is this the proper order or would you root first? I know I should just follow the guide and give it a shot, but that just seems odd.
-Can you explain to be the difference between the Tiamat kernels and the ROMs? My assumption is that the ROM would include the kernel, but I have a strong feeling that is incorrect. I have read posts of installing the ROM first and then the kernel and I am just more confused.
Thanks, one day I will get there.
Click to expand...
Click to collapse
I've got to be quick...I have to do some work today, lol, but here goes:
Actually, follow the Idiots Guide regarding the adb, moto drivers setup.
Then follow this http://forum.xda-developers.com/showthread.php?t=1170760
It's got all the right files and steps, and though it's pretty much to the point, it's user friendly enough. It will get you rooted, I'm sure.
While the difference between ROMs and kernels is somewhat over my head, the ROM does contain the kernel (it's sort of an all inclusive package to tell the device how to behave, whereas the kernel manages particular functions, but not others. It's more limited.) Because the Honeycomb source code hasn't been released, the developers are somewhat limited in the ROM-development department, but they have been able to work wonders with kernels. However, the Tiamat 1.1 Rom for HC3.1 was great and the new ROM in development for HC3.2 will be great too, if the Katana kernal for HC3.2 is any indicator.

Sorry to be a pest but just want to make sure I understand.
A) Follow the idiot's guide steps 1-2, which covers Xoom driver installation and ADB installation.
B) Then follow the other link (How to root your Xoom from stock 3.2) for unlocking and rooting.
C) Then go back to the idiot's guide, skip step 3 (unlocking-already done above) and do step 4 (CWM Installation), skip step 5 (rooting-already done above), then follow step 6 (installing the new kernel).
Again I really appreciate all the advice.
-HuckFinn

HuckFinn said:
Sorry to be a pest but just want to make sure I understand.
A) Follow the idiot's guide steps 1-2, which covers Xoom driver installation and ADB installation.
B) Then follow the other link (How to root your Xoom from stock 3.2) for unlocking and rooting.
C) Then go back to the idiot's guide, skip step 3 (unlocking-already done above) and do step 4 (CWM Installation), skip step 5 (rooting-already done above), then follow step 6 (installing the new kernel).
Again I really appreciate all the advice.
-HuckFinn
Click to expand...
Click to collapse
I guess that my original idea of using the idiot's guide for everything but step 5 still might work, as long as you substitute any older HC 3.1 specific files with the new ones from jase33's post.Meaning new boot image for old boot image, etc...At some point, someone willcreate a "rootboot"zip for HC3.2 but til then, jase33's way is it.
The Tiamat recovery listed in the Idiot's Guide is still valid and jase33 didn't include a custom recovery in his guide (at least I didn't see it). So I think you can install it earlier or later. I'm not sure it makes a difference, as long as you have it installed so you can flash the new kernel!

I just upgraded from a rooted Viewsonic G tablet to the Xoom WiFi. I have not had a chance to work with it yet. A list of reasons to root would be helpful. Thanks in advance.
.

okantomi said:
I've got to be quick...I have to do some work today, lol, but here goes:
Actually, follow the Idiots Guide regarding the adb, moto drivers setup.
Then follow this http://forum.xda-developers.com/showthread.php?t=1170760
It's got all the right files and steps, and though it's pretty much to the point, it's user friendly enough. It will get you rooted, I'm sure.
While the difference between ROMs and kernels is somewhat over my head, the ROM does contain the kernel (it's sort of an all inclusive package to tell the device how to behave, whereas the kernel manages particular functions, but not others. It's more limited.) Because the Honeycomb source code hasn't been released, the developers are somewhat limited in the ROM-development department, but they have been able to work wonders with kernels. However, the Tiamat 1.1 Rom for HC3.1 was great and the new ROM in development for HC3.2 will be great too, if the Katana kernal for HC3.2 is any indicator.
Click to expand...
Click to collapse
I believe the kernel is the Linux derivative operating system that the Java based android layer runs on top of. Technically ROM means Read Only Memory which is not being used correctly. A ROM really is a factory produced Masked ROM (burned in, fixed) or an EPROM (Erasable Programmable Read Only Memory) as in a chip or integrated circuit.

davidsos said:
I believe the kernel is the Linux derivative operating system that the Java based android layer runs on top of. Technically ROM means Read Only Memory which is not being used correctly. A ROM really is a factory produced Masked ROM (burned in, fixed) or an EPROM (Erasable Programmable Read Only Memory) as in a chip or integrated circuit.
Click to expand...
Click to collapse
Your answer is more technically correct. Thanks.

Random reboots, coming from 3.2 stock OTA
Does anybody else get random reboots in Tiamat Katana coming from 3.2 stock OTA? So far it's been exclusively a sleep-related problem; I haven't seen it reboot during active use. I'm not (over|under)(clocking|volting).
I've tried clearing cache and Dalvik cache. If it matters, I've been using the Overclocked GPU version. I'll try the Standard GPU version of Katana, but that's not a likely fix, since all the problems seem to be sleep-related.
(PS: I've read all the FAQs I could find, but I couldn't find the answer to this one: I'm coming from a Viewsonic G, and I'm used to the ability to nvflash completely back to a working state no matter what. Is there an equivalent method of restoring a Xoom to absolute stock? Thanks!)

Nevermind...I did one more "clear user data" and now it's stable. Tiamat devs, you are gods among men and heroes to all the little children. Thanks!

redhairedscot said:
Nevermind...I did one more "clear user data" and now it's stable. Tiamat devs, you are gods among men and heroes to all the little children. Thanks!
Click to expand...
Click to collapse
And if you set WiFi sleep to NEVER (hardly uses any additional battery) you will not have any more random sleep-related reboots.

CWM after rooting?
I followed the instructions in Post #2 of this thread to root my Xoom (HC 3.2). All seemed to go well. However, I have noticed that when following pingvinen's instructions (linked from Post #2), in http://forum.xda-developers.com/showthread.php?t=1130996, to install Tiamat 2.0.0, the steps include installing CWM before rooting. I can't see that it matters that I install CWM after rooting and before Tiamat installation, but I thought that I had better check. Could somebody please confirm that it doesn't matter whether CWM is installed before or after rooting?
Thank you
Gordon

cwm before root, because you need to flash a new recovery to root and flash a new ROM. I'm a noob, too, and just figuring this out myself, but think I am explaining this right.
one of the many guides I reviewed was by steady Hawkins (now part of team tiamat) over on xoomforums... partly pasted below... I actually rooted using the older files and images he references, then upgraded cwm to 3.2 then flashed tiamat 2.0... probably more steps than necessary, but these were the clearest directions and by going through several rounds of flashing I learned a good bit about the process.
Prerequisites:
1) Copy whatever you want to retain, your device will wipe when it unlocks 2) You must have SDK/ADB set up, for instructions please see- Setting up ADB on Windows 7 64 bit (and other Windows platforms) 3) Open SDK and copy all of the files inside of tools folder and paste them inside of platform-tools folder. Vice versa will work as well. If it asks you if you want to replace files select no. The folder you paste these files into will be the folder you will run ADB commands from. 4) Download the files from the link below. Place recovery.img in the file you will run commands from in ADB. ***Wifi-Only Users***- manually put the System and bootloader zips files onto a sdcard card and insert card into xoom. ***3G/4G Users***- manually put the System, bootloader, and 3G fix zips onto a sdcard and insert card into xoom.
Downloads:
Recovery- http://db.tt/GXNxZkF System- 3.1 System - Downloads - Android Forum Bootloader- Bootloader Patch - Downloads - Android Forum 3G Fix- 3G Fix for 3.1 - Downloads - Android Forum
Notes:
In the following two sections you will see red text. This text represents the command that needs to be entered in ADB/Command Prompt. After each command press enter and wait for your computer to push the info to your Xoom. When you see the next command line come up you are ok to enter the next command. You can copy and paste the commands if you would like.
1) To start the process place your Xoom into USB debugging mode. This is done by going to settings, applications, development, and checking the box next to USB Debugging. 2) Plug your Xoom into your computer, open your command prompt (with the path set to the correct folder) and type adb devices 3) If you get a string of numbers your good to proceed, if not refer back to Setting up ADB on Windows 7 64 bit (and other Windows platforms) to see where you went wrong.
Unlocking:
adb reboot bootloader Xoom will reboot into a screen with text on the upper left corner. While you are on this screen enter the following fastboot oem unlock A bunch of text will appear and you will need to use the down volume rocker to select yes, followed by volume up to confirm Xoom will then wipe, reboot, and your back up and running. At this point you will need to go back and re-enable USB debugging
Flash Recovery Img:
Make sure Xoom is connected to computer. Test connection by running adb devices if you get the string of numbers proceed.
Rename the Recovery img you downloaded ~~~> recovery.img
adb reboot bootloader Xoom will reboot into a screen with text on the upper left corner. While you are on this screen enter the following fastboot flash recovery recovery.img Wait for it to finish, then read the below note before you enter the next command!!!!!!!!! fastboot reboot ***As soon as you enter the "fastboot reboot" command in the previous step, your device will reboot. You have to boot into recovery right away or your Xoom will reflash the stock recovery over the custom recovery you just flashed. Follow these next steps very carefully-
a. When you see the Motorola logo appear, wait approximately 3 seconds. b. Tap the Volume Down button. You should see the words "Android Recovery" appear at the top of the screen. Now tap the Volume Up button to boot into recovery. c. If when attempting to boot into recovery it says 'Starting Fastboot protocol support' then you hit Volume Down too soon. Hold Vol UP + Power to reboot and try again.
Root Time:
***For the following use the volume rocker to move the selector up and down, use the power button to select***
1)Select wipe data/factory reset and confirm 2)Select install zip from SD and confirm 3)Select the system file and confirm After it loads select install zip from SD again and confirm 4)Select the bootloader file and confirm
***3G USERS ONLY- Select 3G fix and confirm***
5)Select Reboot and confirm
At this point Xoom will reboot. Please note the first boot will take a while. After it boots up you will be rooted and you should have SDsupport!
Root info:
To ensure that you are rooted download Terminal Emulator from the market (its free). Open it and type su followed by pressing enter. On the next line you should see #. If you do your dialed in.
To view your SDcard use a file manager program such as Root Explorer. Your sdcard will be located in /sdcard/external.
Big thanks to Bigrushdog for the imgs!!!!!

kosenn said:
I just upgraded from a rooted Viewsonic G tablet to the Xoom WiFi. I have not had a chance to work with it yet. A list of reasons to root would be helpful. Thanks in advance.
.
Click to expand...
Click to collapse
Had my 3g zoom for 4+ months before deciding to root. The advantages I've seen in a few short days rooted:
better performance, faster booting, smoother webpages
full SD card use (write access to go along with read in stock 3.2)
ability to fully and truly back up the device
a very resposive developer community
a very knowledgeable and helpful user community (though they'll help you even stock)
a growing understanding of how this great device works
what I'm not sure of is how much effort and attention it will take to keep up with updates from the dev community, and whether tinkering with this thing will become addictive and end up consuming as much time as my original reasons/uses for buying it in the first place

Thank you for the reply. I thought the thread had died
You say:
cwm before root, because you need to flash a new recovery to root and flash a new ROM. I'm a noob, too, and just figuring this out myself, but think I am explaining this right.
I tried to install CWM (flash with fastboot) on a rooted stock US 3.2 WiFi Xoom. I am not clear why starting with a rooted device would make any difference for flashing a new recovery, before flashing a new ROM. Can you explain further? Nevertheless, I haven't managed to flash a fully functioning CWM. It works but with error messages, as indicated in my post at http://forum.xda-developers.com/showthread.php?t=1130996&page=4.
Maybe I need to go back and unroot.
Thank you
Gordon

1st, a disclaimer that I'm not much more experienced than you (if at all). Take what I offer knowing that.
I actually experienced an identical problem. Like you, I was working from several "guides" at once and I think the issue resultedbfrom mixing instructions for one cwm version with an earlier (or later) version. I THINK the version you have is the same as the one referenced in the guide I pasted. If you'll note his directions, he suggested renaming the recovery document to "recovery.img" before flashing it. When I went back and did that, it worked for me... then I was able to flash the updated cwm 3.2.0.0 with no errors.... then tiamat 2.0
I have no idea, though, whether there are ramifications to being rooted without a error-free recovery.

Thanks again for this ... at least someone has been through the same problems as me!
The version of CWM that I am trying to flash is "recovery-Tiamat-R4c-100611-1150-cwm.img", which is what is shown in the fastboot line in http://forum.xda-developers.com/showthread.php?t=1130996. However, I am not seeing any reference to renaming to recovery.img. Are we looking at different threads?
If necessary, I will go back to stock 3.0.1 and un-root, but I would like to avoid the stress, if possible
Thank you
Gordon

[Q] Multiple Questions - Backup Issues, Installing a New ROM, etc.

Hello everyone. This is my first post, so please be gentle. I've been reading around and I can't seem to find specific answers to my questions so I figured it would be best to make a post. This is my first Android phone and also the first phone I have rooted so I'm trying to be extra careful. I've already received tons of help from other threads in these forums, but as I said I've still got a few questions.
I rooted my SGS4G using SuperOneClick v2.1.1, then proceeded to install CWM ROM Manager as per the instructions I found in many articles online. Once I got that installed I was unable to make backups as it would boot me into the stock recovery menu, which led me here searching for answers. That is when I came across this thread: [RECOVERY]CWM FINAL for the SGS4G After following the instructions I wasn't exactly sure what to do, so I attempted to boot into the "new" recovery menu which ended at an infinite boot logo, which I assumed was a soft brick after reading around a bit.
After thoroughly freaking out about my phone being bricked I looked around a bit more and came across this thread: [GUIDE] Noobs guide to Odin to flash your SGS4G (Windows) Following that thread I was able to install the T959VUVKB5 Stock + Root ROM which restored my soft brick. Once that was installed I installed CWM ROM Manager again thinking the Recovery Menu would be fixed and I could finally make a backup before moving on, but it wasn't. Then I came across this thread: [Odin][Kernel] drhonk's Bali 3.3 for Froyo, Installs CWM!
After installing drhonk's Bali 3.3 for Froyo kernel I was finally able to make a single nandroid backup (and backup my apps using Titanium Backup)! I messed around on the phone for a few days with no issues (other than the Android flickering in the boot logo). Now I am ready to move on to trying out a few ROMS. So, first thing first I said: I need to make another backup. So I entered the Recovery Menu via the CWM ROM Manager and attempted to make another backup, and this is what I get:
E: failed to open /etc..... (I couldn't write fast enough to copy the entire message)
E: unknown volume for path [/sdcard] (10s)
The second of which repeated over and over until it reached 0s and then my phone was rebooted.
TL;DR
- Rooted using SuperOneClick
- Installed ROM Manager and couldn't make a nandroid backup correctly
- Attempted to install CWM FINAL for the SGS4G, which resulted in a soft brick
- Restored using ODIN and installed T959VUVKB5 Stock + Root ROM and drhonk's Bali 3.3 for Froyo kernel
- Cannot make nandroid backups (other than the initial one apparently), Recovery Menu does not seem to be working correctly
- I am not comfortable trying new ROMs until I am able to make backups correctly
Anyway, so here are my questions:
1. What do I need to install to allow me to make nandroid backups correctly? Or is there another app besides CWM ROM Manager that will allow me to do this?
2. I would like to try a few other ROMs, but I when I reach the so-called "Do the mounting stuff" step I am unable to continue as my Recovery Menu isn't working correctly. What do I need to install in order to be able to do complete this step? I have a feeling the answer to #1 will solve #2 as well.
3. I would like to try a few of the GB ROMs (such as Valhalla v1.3.2 or Stock Gingerbread 2.3.3 Deodexed + Root), but I am not sure exactly where to go from here. Is the GB Ext4 Starter Pack the way I need to go, or would this way be better? Can I do either of these without a working Recovery Menu?
Thanks in advance for all the help!

Your first mistake was rom manager. It does not work for this phone correctly. Odin one of Dr honks kernels to get cwm recovery. They are in the dev section.
Sent from my SGH-T959V using xda premium

im not sure how many times this has been posted (i think i say this once a day....) but rom manager DOES NOT WORK ON THIS PHONE.
it is fine. if you can wait a day or two, i will make a nice noob guide on getting from stock to a custom rom. i will be sure to link every pertinent thread and be sure to have a little FAQ section. hopefully it will help you.

Exodian said:
Your first mistake was rom manager. It does not work for this phone correctly. Odin one of Dr honks kernels to get cwm recovery. They are in the dev section.
Click to expand...
Click to collapse
As I said in the post, I've already installed drhonk's Bali 3.3 for froyo kernel.
jager555 said:
im not sure how many times this has been posted (i think i say this once a day....) but rom manager DOES NOT WORK ON THIS PHONE.
it is fine. if you can wait a day or two, i will make a nice noob guide on getting from stock to a custom rom. i will be sure to link every pertinent thread and be sure to have a little FAQ section. hopefully it will help you.
Click to expand...
Click to collapse
Thanks, but I figured that out shortly after installing it. What alternative are we supposed to use? Hopefully your noob guide will help.

are you sure you understand? seeing as you mentioned BOTH bali and krylon's cwm, yet you still do not know how to get the custom recovery on the phone. once again, i will write a nice guide for you, so for now, just odin back to stock and give me a day or two. once im out of work, i will take a nap and write this for you.

jager555 said:
are you sure you understand? seeing as you mentioned BOTH bali and krylon's cwm, yet you still do not know how to get the custom recovery on the phone. once again, i will write a nice guide for you, so for now, just odin back to stock and give me a day or two. once im out of work, i will take a nap and write this for you.
Click to expand...
Click to collapse
Apparently I do not understand. I guess I will just wait for your guide. Hopefully it will pick up where the other guides failed (for me anyway).
Edit: After reading around a bit I think I understand where I went wrong. As a noob I was confusing CWM with ROM Manager (after all, they're both made by the same people right? I believe that's what was confusing me ). I have since uninstalled ROM Manager and have booted to the Recovery Menu and successfully made a backup.

I myself have been a member for coming up on one year. And when I originally joined I was modding my Mytouch 3G. Much easier phone to mod and especially with ROM manager. This phone on the other hand requires more attention to detail. It is very important to do your due diligence to research this site for answers before posting. The reason is, all the wonderful and talented folks making all this possible are providing us all these great hacks, cracks, and roms for free. The information is here if you just look for it. Now if you are having trouble understanding the info that is also understandable. I find questions are better received if you show everyone what you have researched and then say what your are confused about.
Enough of the lecture, the end result is that everyone here is really nice and helpful. Here are the 3 links you should save. The Bible lists everything about our phone. Now at this stage in the game unless you really want to get more background on how the phone has evolved from Froyo to GB you won't need to read the Bible. The first thing you will need to do is follow the instructions for Bali 3.3 + CWM. This will provide you with the Red CWM recovery making it possible for you to flash Froyo Roms. Once you have completed this step you can move on to the GB Starter Pack. This guide will prepare your phone with the correct bootloaders it requires to run GB Roms. Once this process has been completed you can flash GB Roms. And if you need a quick list of the roms available just look in the Bible. Hope this helps, just be patient and make sure you understand what you are reading and attempting before doing anything. And if you don't understand a step or a process then come and ask and you'll get better answers and better understanding of what you're actually doing to your phone.
SGS4G Bible
http://forum.xda-developers.com/showthread.php?t=1117554
Bali 3.3 + CWM
http://forum.xda-developers.com/showthread.php?t=1195860
GB Starter Pack
http://forum.xda-developers.com/showthread.php?t=1223765

Thanks for the help. I tried to do as much research as I could before posting (as you can see, I've posted two of the three links you suggested in my OP, and I basically keep the Bible open at all times ). It's just the little things that I find confusing, which is why I posted this thread. It's nice to know that from this point I can proceed to the GB Starter Pack and play around with the GB ROMs, but I think I'd like to try a few Froyo ROMs before I take that step Thanks for confirming that!

Sorry for the double post but I have another question.....
I've been reading over FB's GB Ext4 Starter Pack thread and I just wanted to make sure that once you get to the part where you flash your "favorite GB rom" that Valhalla v1.3.2 would be an acceptable ROM to flash there. If not, which ROM should I flash first, then flash Valhalla? Thanks in advance.

Yes, Valhalla would be fine to flash at that point (any version). just as long as you went through each step of the directions first. you'll be fine.

Updating ROM with CWM just reverts to menu?

Hey,
I'm trying to install the [ROM] Team Tiamat Xoom Rom 2.2.2 - Moray [9/10/11].
I've got CWM installed (version recovery-Tiamat-R4c-100611-1150-cwm.img but also tried latest version from ROM Manager).
Each time i try to install the .zip it get's to opening package and then just exits to the CWM menu?
It's probably a common thing, but couldn't find anything from a search? Anyone got any ideas?

This has been covered many times so take the time to do a search.

Muffycheeks said:
This has been covered many times so take the time to do a search.
Click to expand...
Click to collapse
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.

kar200 said:
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.
Click to expand...
Click to collapse
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.

okantomi said:
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.
Click to expand...
Click to collapse
I just ralised tnat my sd card was screwed (very old 1gb i found lying around). The files on the pc were fine.
I used a different card and now typing from a custom rom! All good.
K.
Sent from my Xoom using xda premium

[Q] Complete flashing noob help

Hello all,
I've been lurking the XDA forums for a couple months now. I had a couple posts in the past referring to my phone and my girlfriends phone and was looking for help mainly with hers at the time... Hers is fixed... Perfectly even, despite her phone being a total piece of garbage (an LG Optimus.... *barf*).
I have a SGH-T959V.
I have read the 10 commandments.
I KNOW my phone is NOT a Vibrant OR an i900.
I have read the noob guides.
I have become completely confused.
Here's my details:
I have running the stock GB that I installed with Kies Mini some time ago.
Phone Data:
Firmware Version: 2.3.6
Baseband Version: T959VUVKJ6
Kernel Version: 2.6.35.7-T959VUVKJ6-CL694130
Build Number: GINGERBREAD.VUVKJ6
I rooted my phone with one of the one-click apps after the stock GB update so that I was at least able to overclock it and get rid of the T-Mobile bloatware, etc.
I notice that my phone reboots entirely on it's own completely randomly, has random application hangs, all the bad icky stuff that sucks... (right????)
Anyways, I've looked at some of the Custom ROMs available and I'd like to check out some of them, but I'll be quite honest, I've read the instructions for how to do it, but I'm getting extremely confused as the current instructions seem rather daunting.... It's like information overload...
Now, don't get me wrong, I'm not some kid that really doesn't know what he's doing... I'm 33 and work in IT for The Nielsen Group... so I kinda know what the heck I'm doing MOST of the time. This is something I'm unfamiliar with and am being EXTREMELY cautious about because i don't want to brick my phone....
Question time!:
1. Is there a COMPLETELY SIMPLE step-by-step process/Video Demonstration for the CORRECT method of how to put a custom rom on the SGH-T959V?
2. Does it matter that I ALREADY rooted my phone in respect to me loading a custom rom? (ie. is my already rooted phone going to have issues loading a different rom?)
3. I would like to stay with a GB based rom unless there is absolute NEED to use a Froyo based Rom - Or is this a non-point when using custom roms?
4. If i want to load a custom rom to my phone, do I need to use a specific loader? (Like, does Odin work for everything??? Loading roms and unbricking your phone? Or do I have to have different loaders for the specific roms that I want to load and try out????)
5. Please don't jump down my throat with the "read the guide" responses... I HAVE been... really. As many as I've found... and every time I read a new one, rather than feeling like I'm coming out of the darkness of knowledge and into the light of understanding the correct process for how to do this, I feel like I'm being cast deeper down the confusion pit.
Would someone KINDLY please help me. Really... I don't want to screw up this thing... I'm not worried about the warranty. From what I've read, these things are mostly fixable unless it's an actual hardware issue or if it's totally fried. I just want to do it once, do it right, move on to my next project.... Dig?

First and foremost, we keep the most updated information in the wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G
We've been updating it a lot lately so you're better off checking there. I'm sure you'll wanna bookmark it since you know what you're doing already.
1) Specifically you'll want to look at this section:http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#Installing_a_ROM
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running.
3) For our phone you're either going to use Odin/Heimdall (learn Heimdall, it's much more useful) and CWM Recovery. Most roms available right now are for CWM.
Here's the list of custom GB roms:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G_ROMs
4) Honestly the forums are too cluttered and as I stated above, knowledgeable senior members are the ones who update the wiki, so that'll be your most useful resource.
If you already have some experience with computers I'll gladly help you, you're already asking the right questions.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

FBis251 said:
First and foremost,
...
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running...
Click to expand...
Click to collapse
When I last played with my phone, I had used Odin on Windows... I have replaced Windows with Linux... I have installed Heimdall and did an initial test. So it is working.
My question is: Is Heimdall a valid replacement for Odin? In other words, I am wanting to use your guide, but it only refers to Odin. Can I go through those steps replacing Odin with Hamdall?

Yes it should work fine. The csc files for kc1 should be extracted over the pda files though
Sent from my SGH-T959V using XDA App

FBis251,
Thank you so much for the quick reply! I had seen it immediately after you responded, but was driving home from work and went right to bed. I'm back at the office now for the evening and perhaps may have some time to look into these tonight... I don't know as of right now.
If you are serious about the offer of some assistance, I would be more than open to it if I honestly felt it was needed. I am MORE than experiences with computers, i'm a full on uber-geek (just not with smartphones...... yet....), so VNC, etc would not be an issue.
I will most certainly get back to you about this in the next few days (perhaps even tonight). Let me see how my work load looks this evening and I will update the thread later.
Thank you again so much!

I'm usually in #teamnerd on freenode if you do IRC.

It doesn't take much to confuse me these days...
Moved my issue into a new question in the Q&A forum...

Hey, just an FYI (even tho I'm sure that ultimately you don't really care - just being realistic, not a douche... ), I haven't had a single moment to look into this beyond briefly skimming the Wiki's you linked up for me. (thanks for that one). I've had a butt-load of server issues at work that have taken a lot of my time. I'm HOPING to be able to look into some of this stuff a little deeper tonight (god willing)....
I will drop a note if I have issues....
Thanks again!

n00b to rooting and CWM for P3113

First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.

Please be sure and thank the person who decides to do your homework for you.
:laugh:

FlynnErik said:
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Click to expand...
Click to collapse
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.

ryphil said:
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
Click to expand...
Click to collapse
Fully agreed! That's why I came to the experts. I have done my homework but the thing is my homework leads me to several different files from before the ICS update. There has only been 1 thread on 1 forum that has been post ICS update, and no real feedback on it. I think I even found one that uses ADB (I understand that concept, but would prefer not to use it since I don't know Linux well enough).
I would love to know what files to use, which ones to stay away from. As I said I have the concepts, I have the understanding, its the actual files that I want to verify, I can rattle off tons of files from tons of sites, but they may or may not be correct (and may have the same name as a correct one but still be incorrect, ie "update.zip" appears a few times on different threads from different time frames).
There is only post in the teamhacksung CM10 wiki that was last edited 8/12/2012, but that could have been anything that was updated, not the files/links to be used.
So I thank you in advance for your help, and you will certainly get a thank you in the forum for help you are providing, I always give credit where credit is due.
Well here goes nothing, going to reboot (to ensure the Kies drivers are installed and loaded into the system 100%), and try the instructions from this link http://forum.xda-developers.com/showthread.php?t=1788625
It seems to work for most, the only concern I have is that I have a different end to the build than most others do (and I am not sure why?)

Did I screw myself?
I rooted, and have CWM installed.
Is it to late to create a ROM backup of my device for when i go to install CM10 (I need a drink for now, so I might install it tomorrow night lol).
That link I posted in the last post is good to go if anyone else needs a safe bet set of directions.
Seriously though, I didn't do a backup, am I screwed now?
EDIT: I just did a back up and it said no sdcard/.android secure found, skipping of backup of apps
and
no sd-ext found skipping backup of that.
is that normal? Did it backup to my microSD?
Still hope I didn't screw myself by backing it up after rooting.