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

Worlds Most Complicated Issue - HELP!

My TF is in a complicated mess because im stupid!
I need your help XDA Community!
My TF was rooted with KRAKD rom. I decided I wanted to unroot my TF and followed what seemed like a popular guide from theunlockr.com
And it worked except it rolled me back to the stone age - 8.2.3.13
Naturally I connected to my WIFI network to update to the latest version but it kept saying that there's no update available so I thought I would give a manual update a try which I have done before so I know I followed the correct procedures.
In asus recovery mode the loading bar pops up for a while then the triangle with the exclamation mark appears. When I booted it a window popped up which read something like "update failed (12)".
Then I tried something I saw in a forum which apparently is another way to do a manual recovery. Renaming the zip file to EP101_SDUPDATE.zip and leaving it on the root of external SD or internal (tried both) and booting in recovery. It didn't work.
So I stupidly thought that I might aswell try rooting it again with nachoroot and flash recovery then flash the latest stock rom. Well what happened was that it rooted but I could not flash CWM following any methods. The one click recovery installer apk didnt work just said file parsing error. Tried doing it through ADB but always eventually leads to permission denied.
So I have a half rooted transformer with 8.2.3.13 on which razor claw and one click recovery cant be installed and I cant update it to the latest firmware.
Device Details:
Model Number: EPAD
Android Version: 3.0.1
GPS Version: V1.2.4
WIFI Version: V5.248.35
Bluetooth Version: V6.12
Kernel Version: 2.6.36.3-00004-g069b8b5 [email protected] #1
Build Number: HRI66.WW_epad-8.2.3.13-20110511
Dont have a mobile dock.
COME ON XDA SEE IF YOU CAN SOLVE THIS ONE!!!

Try to use nflash of any ROM, Revolver for example

Cant believe NVFLASH slipped my mind
I will give it a go
thank you for the suggestion

samsung said:
Try to use nflash of any ROM, Revolver for example
Click to expand...
Click to collapse
NVFLASH doesn't seem to detect my device
When I put the TF in APX my computer recognises but when I run NVFLASH it doesn't detect it plus I can hear the Windows 7 disconnect sound only when I run NVFLASH.
The drivers seem to be fine.

did you even install superuser from market after you rerooted?

Get the 8.6.5.23 ROM, put it on your SD card and make 2 copies, name one WW_epad-user-8.6.5.23.zip and name the other EP101_SDUPDATE.zip, I find the first one is good enough, but having multiple copies can't hurt.
Now try to let stock recovery flash your SD card file
That worked for me..(the 8.6.6.23 is for the tf101G, but it works as well on mine which is standard tf101, if you happen to find that one, just name the zip file appropriately)
Let me know if this works, your problem is not complicated BTW haha

Dual boot Ubuntu (or other Linux) on TF300T?

Hello all,
I have an interesting problem I would love some information about. I recently bought an Asus Transformer Pad (TF300T). I have already unlocked the bootloader via the Asus utility, flashed TWRP recovery, and rooted it. Now I'm interested in the possibility of dual-booting.
I know that Ubuntu has support for ARM, but I have no experience installing something like that on a device like this. Ideally, I would install Ubuntu (or another Linux distro that supports ARM) to the external SD card and be able to choose at boot time to boot into Ubuntu or into Android. I have seen that some people did something like this on the TF101, but I don't know if that would still work.
If anyone has any ideas about this, I would appreciate hearing them.
Thanks,
Vincent

issues
hi to help to answer your question, if im correct because we do not have much support for building custom kernels to support dual booting into linux, that is a reason why currently there is zero support towards this feature, but there are alternatives, here is a link
https://play.google.com/store/apps/...MsImNvbS56cHdlYnNpdGVzLmxpbnV4b25hbmRyb2lkIl0.
this link has an application to install linux on your asus tf300t tablet, it is confirmed to work with stock, but has not been tested on a custom rom, this is using the CHRoot method, aka running next to android requiring a vnc viewer to be used to view it and interact with it. this is not a dual boot, until developers on here can get a JB custom kernel that supports dual booting, there will simply be no possibility, plus we do not even have finished NVFlash files yet to help doing this/ unbrick our tablets. i hope this helped, if it did please hit the thx button below

Dual booting for TF300T
I am currently trying to Dual Boot the TF300T with Ubuntu as well with little success.
I've been going from the TF101 Method...
http://forum.xda-developers.com/wiki/ASUS_Eee_Pad_Transformer/How_to_install_Ubuntu/Ubuntu_Install
I have been unable to get Frank'sTools to Run through Windows, or Successfully use OliFE through Linux on my PC.
With OLiFE, Once I enter that I wish to Dualboot in the 2. Flash option, Nothing happens. Though it says it should ask me which system should be default etc. I have gone through the sh files and have tried to tweak them a bit to get the scripts to work, but nothing has worked.
There is a guide here for the TF201 which I am thinking of trying but you have to flash the boot.img whenever you want to switch between the OS by the look of it.
Not sure if it is worth trying though. The main reason why I want Linux is so that I can run DSUME since the current DS Emulator for Android isn't fantastic yet. (Good job so far though guys)
If Anyone has any ideas for how to Dual boot the TF300T, please let me know!!! I don't want to run linux through Android as this would be terrible for emulation
P.S. I am still a complete noob at all of this

[Q] Newbie Confusion About Rooting, Unlocking, Installing Custom Rom

Hello great people of XDA,
I am a newbie to Android and XDA ecosystem. I am trying to summarize my situation below. Sorry if it is too long.
Goal for using tablet: My main purpose for using tablet is having a mobile device I can use both form my studies and my work. I will take notes via smthng like supernote, open word and excel documents and track my mails. All files will be kept in microsd, I just load apps and movies and music to internal storage.
I won’t use my tablet as a gaming machine. Of course I can play some games like chess or small games but not big ones.All I want is performance and smooth usage. A laggy device while surfing or taking notes makes me crazy.
My tablet is a 15 days old tablet but I want to root it, unlock it and install a custom rom. The device is running Android 4.1.1 (JB) with WW…….10.4.4.18_20121012 firmware. Here is my plan.
Phase 0 : Downgrade it
1. Download Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for WW SKU (Android 4.0.3)
2. Unzip it
3. Rename it to EP201_768_SDUPDATE.zip
4. Copy it to microsd card
5. Insert microsd
6. Power off
7. Press power on + volume down
8. See some small lines at left top
9. Press (only) volume up in 5 seconds
10. Hope the machine sees the file in the SD card and downgrade your device
Result : you have a machine with android 4.0.3
Phase 1 : Root it
1. Mark USB Debugging and Unknown sources
2. Load the drivers to computer
3. Connect the device
4. Run the rootdebugfs
5. Follow the instructions
6. Hope to be root
Result : you have a rooted machine with android 4.0.3
Phase 2 : Unlock it
1. Install GooManagerBeta via GooglePlay
2. Run GooManagerBeta
3. Install open recovery script
4. Machine reboots itself
5. Power off
6. Press power on + volume down
7. See some small lines at left top
8. Press (only) volume up in 5 seconds
9. TWRP (I dont know which version is installed via GooManagerBeta) should be opened
10. Backup your data to your external sd card if necessary
11. Wipe all data/cache
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty
Phase 3 : Install custom rom
1. Copy custom rom and gapps file to microSD
2. While TWRP is infron of us, choose install
3. Find your custom rom files
4. Flash to install
5. Find your gapps files
6. Flash to install
7. Hope to boot again
8. Hope to get enough performance
Result : you have a rooted/unlocked machine with custom rom with no warranty
Here are my questions
1. Is my flow correct?
2. Where is the real risk for hard or soft bricking? (I have no idea what is the difference)
3. I have not decided yet what to choose clearrom 2.3 or CM10? All I want is performance and smoothness
4. Does it worth to make all these things? Will I get a real performance and smoothness boost?
Thanks for your help…

Almost correct. Your phase 2 is missing the actual action of unlocking the tablet. What you're doing in the second phase, is actually installing a custom recovery. Before you can do that, you need to be unlocked.
You need to download the unlocking utility from Asus' website to unlock it. You can do this just before you start phase 2. Besides that, it's almost exactly what I did.

In my point of view you could forget about Phase 0
The things that you want to do are possible on JB

jokapo said:
In my point of view you could forget about Phase 0
The things that you want to do are possible on JB
Click to expand...
Click to collapse
I'm worried about this too. I'm about to unlock, but my tab is currently on 4.1. Are you saying that the unlock tool from ASUS will still work with android 4.1?

People have reported it working, yes.

rikkoko said:
I'm worried about this too. I'm about to unlock, but my tab is currently on 4.1. Are you saying that the unlock tool from ASUS will still work with android 4.1?
Click to expand...
Click to collapse
Firebrazer said:
People have reported it working, yes.
Click to expand...
Click to collapse
It works without any problem.
I also unlocked when on JB

ingenihero said:
3.I have not decided yet what to choose clearrom 2.3 or CM10? All I want is performance and smoothness
Click to expand...
Click to collapse
I would highly recommend CleanROM 2.3 - it's the fastest, smoothest ROM that I have ever used on the TF700 (and I've tried them all!). Plus, the developer is simply amazing in terms of support, etc. Being that it is a stock-based ROM, you will get to keep some very useful stuff, such as the keyboard dock battery level on the status bar and some useful apps that are only available in stock-based ROM's.
Then again,once you are unlocked, it's very easy to install different ROMs and try them for yourself - that's half of the fun of unlocking - getting to try different ROMs!
Good luck and have fun!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
I would highly recommend CleanROM 2.3 - it's the fastest, smoothest ROM that I have ever used on the TF700 (and I've tried them all!). Plus, the developer is simply amazing in terms of support, etc. Being that it is a stock-based ROM, you will get to keep some very useful stuff, such as the keyboard dock battery level on the status bar and some useful apps that are only available in stock-based ROM's.
Then again,once you are unlocked, it's very easy to install different ROMs and try them for yourself - that's half of the fun of unlocking - getting to try different ROMs!
Good luck and have fun!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
How can I be sure that GooManager is using TWRP not CWM? As I heard CMW is problematic with managers.

Once you open GooManager and press the "Install OpenRecoveryScript" button, it will tell you which recovery it will install, before it starts downloading and installing it. It is always TWRP.

jtrosky said:
I would highly recommend CleanROM 2.3 - it's the fastest, smoothest ROM that I have ever used on the TF700 (and I've tried them all!). Plus, the developer is simply amazing in terms of support, etc. Being that it is a stock-based ROM, you will get to keep some very useful stuff, such as the keyboard dock battery level on the status bar and some useful apps that are only available in stock-based ROM's.
Then again,once you are unlocked, it's very easy to install different ROMs and try them for yourself - that's half of the fun of unlocking - getting to try different ROMs!
Good luck and have fun!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
AMEN to that
ingenihero said:
How can I be sure that GooManager is using TWRP not CWM? As I heard CMW is problematic with managers.
Click to expand...
Click to collapse
I have used both TWRP and CWM and never had any problems with both.
I just like the simplicity of CWM though.
Maybe because thats the one that i encountered using first when i stepped into the wonderful world called ANDROID

Looking for better understanding
I too could use a better understanding of this. I am about 70% happy with my TF700. About 70% of the time it is fast enough and smooth enough. The other 30 it kind of crawls. This is especially noticeable when trying to navigate Netflix.
What exactly is CleanROM replacing? Do you get to keep all the built in apps? What about upgrading as new versions of Android are released or minor updates come out?
Is there a CleanROM info page or guide that explains it all?
Thanks for the information.
Scott

The CleanROM thread can be found in the Development part of the TF700T forum. It explains a lot of it.
You have the option of installing all the stock Asus apps, none of them, or whichever ones you want.
You can always go back to stock, should you wish it, but once you're unlocked you won't receive OTA updates anymore, you'll have to install them manually. The developer will most likely update the ROM as new versions of the stock becomes available, assuming it's a stock-based ROM (CleanROM is stock-based).

Firebrazer said:
The CleanROM thread can be found in the Development part of the TF700T forum. It explains a lot of it.
You have the option of installing all the stock Asus apps, none of them, or whichever ones you want.
You can always go back to stock, should you wish it, but once you're unlocked you won't receive OTA updates anymore, you'll have to install them manually. The developer will most likely update the ROM as new versions of the stock becomes available, assuming it's a stock-based ROM (CleanROM is stock-based).
Click to expand...
Click to collapse
Hi again,
I downgraded to 4.0.3 ICS but rooting tool is working for 20 minutes is that normal? SHould I interrupt the process?

It shouldn't take that long. Have you followed the on-screen instructions? Maybe you forgot to press a key after the tablet rebooted?

Firebrazer said:
It shouldn't take that long. Have you followed the on-screen instructions? Maybe you forgot to press a key after the tablet rebooted?
Click to expand...
Click to collapse
I have succeed to install CleanRom 2.3 at the end. First impression, there is a performance and stability increase but not a dramatic one. I will continue with trying Clemsyn Kernel. If this does not bring expected perfromance, I will try Data2sd Mod.
Here is my actualized flow.
Phase 0 : Downgrade it
1. Download Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for WW SKU (Android 4.0.3)
2. Unzip it
3. Format micro SD to FAT32 format (not a quick format) if it is not FAT32 already
4. Copy needed downgrade firmware to microSD without renaming
5. Insert micro SD to tablet
6. Tablet recognizes the downgrade update and ask for continue
7. Continue with the process
8. Tablet reboots
9. Tablet downgrades its OS to 4.0.3
Result : you have a machine with android 4.0.3
Phase 1 : Root it
1. Mark USB Debugging and Unknown sources
2. Load the drivers to computer
3. Connect the device
4. Run the rootdebugfs
5. Follow the instructions
6. It takes too much time to complete the action, but after 20 minutes or a little more I kill the process via CTRL+C and process interestingly continued and rooted my device.
Result : you have a rooted machine with android 4.0.3
Phase 2 : Unlock it
1. Install Asus Offical Unlocker
2. Follow the instructions
3. You have easily unlocked your device.
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty
Phase 3 : Install Custom Recovery
1. Install GooManager via GooglePlay
2. Run GooManager
3. Give root permisson
4. Install open recovery script
5. Machine reboots itself
6. Power off
7. Press power on + volume down
8. See some small lines at left top
9. Press (only) volume up in 5 seconds
10. TWRP (I dont know which version is installed via GooManagerBeta) should be opened
11. Backup your data to your external sd card if necessary
12. Wipe all data/cache (In TWRP Factory Reset Under Wipe Menu)
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty and custom recovery installed
Phase 4 : Install custom rom
1. Copy custom rom and gapps file to microSD
2. While TWRP is infron of us, choose install
3. Find your custom rom files
4. Flash to install
5. Find your gapps files
6. Flash to install
7. Hope to boot again
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty and custom recovery / custom rom installed
That worked for me.

I think actualized is a very groovy word!
May I use it from here forward?

Thats OK said:
I think actualized is a very groovy word!
May I use it from here forward?
Click to expand...
Click to collapse
Sure you can
P.s. : I am not very good at english.

ingenihero said:
Sure you can
P.s. : I am not very good at english.
Click to expand...
Click to collapse
I think you are very good at english!

Make sure to cold boot a couple of times after installing CleanROM. That usually helps a bit. Also, try Browser2Ram.

I thank the OP for this thread as I was also having some questions, even though I don't consider myself an actual newbie. I think this thread will help a lot of people out with an outline process of what to do with the TF700 regarding the root to flashing custom ROM process. I am still left with a few questions that I'm hoping can be answered. [btw, my TF700 is totally stock, no root, locked, on the latest OTA JB release, US version]
1) for the OP, what made you decide to proceed with your Phase 0, rather than going straight to Phase 1?
2) If a person only wanted to root their device, could the simply follow the Phase 1 listed here only? Is there a need to unlock the bootloader if you want to just be Rooted?
3) Does anyone think that there will be a way to go from Rooting to Installing a Custom Recovery, without unlocking the boot loader (similar to the TF101 process)?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

My TF700T is finally failing.

Running on android 4.0 ICS, my software fails on a cold reboot, and performs badly in normal mode.
It has reached the point where I need to replace all software with a modern ROM - any competent rom.
Tried I can use ADB but cannot connect my win7 to my transformer.
Is there a rom I can use (via my win7) to completely replace my corrupted rom?
If so are there simple instructions without having to resort to different loaders?
I have nothing of residual value on the transformer.

What ADB/Fastboot tool are you using to access you TF700 in fastboot mode and do you have "Universal Naked Driver v0.72" installed on your computer/laptop? - NP

Thank you for your reply.
Not running ADB, it does not seem to work.
Perhaps I cannot get fastboot to run.
Do not have "Universal Naked Driver v0.72"
Looking for a simple replacement to existing rom

Step 1:
You will need to unlock the bootloader 1st using the file found here and running it from the file manager on the tablet;
https://androidfilehost.com/?fid=817550096634776735
Once unlocked, when you boot the tablet you should see this in the upper left of the screen. - NP

Tacty said:
Running on android 4.0 ICS, my software fails on a cold reboot, and performs badly in normal mode.
It has reached the point where I need to replace all software with a modern ROM - any competent rom.
Tried I can use ADB but cannot connect my win7 to my transformer.
Is there a rom I can use (via my win7) to completely replace my corrupted rom?
If so are there simple instructions without having to resort to different loaders?
I have nothing of residual value on the transformer.
Click to expand...
Click to collapse
First you should update your rom to the latest firmware and bootloader. All the tools and roms still out there require you to be on the 10.6.1.14.10 firmware. Download the firmware from here:
https://www.asus.com/us/supportonly/ASUS Transformer Pad Infinity TF700T/HelpDesk_BIOS/
The instructions to manually update are here: http://www.transformerforums.com/fo...e-firmware-tf101-tf201-tf300-tf700-tf701.html
Once that is done, follow instructions in this thread to flash KatKiss Nougatella to your tablet.
https://forum.xda-developers.com/showthread.php?t=2688891
The rom is here: https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
It is a project for sure, but can be fun if you give yourself time and like learning new stuff. There is not shortcut, if this is too much for you it is time to buy a new tablet

@Tacty also there are 4 version of the firmware JB (Japan), UA (United States), TW (Taiwan) and WW (World Wide) for the rest of the world. Judging by you post Method B in the link provided by berndblb looks to be the best route, it will update the ROM and the bootloader. I just got a stock TF700t off eBay, it came with the latest ROM/Firmware already loaded so it made unlocking and flashing KatKiss a breeze, one you get your TF700t updated to the last stock ROM for our tablets you can go from there. -NP