Database Info

[RECOVERY][APP] 4-28 One-Click NvFlasher ClockWorkMod Touch 5.8.1.3/5.0.2.0/4.0.1.5

Objective:
Thought I would create an app to try to make it easier to flash the ClockworkMod to your phone so you can get to recovery without having to use ROM Manager. This app will also let you revert back to Stock Recovery.
Flashing the custom recovery using NvFlash is the only way to ensure that in the case your phone will not boot up, you will be able to get into recovery to fix the issue / flash a ROM / restore from nandroid backup. That is what this app will do for you.
If you flashed the ClockworkMod recovery from ROM Manager it does not flash the recovery to your phone, it fake flashed it. The only way you can gain access to ClockworkMod recovery is through ROM Manager at that point. Using this method is the only way to flash recovery so it is persistent and accessible booting to recovery.
If you have already flashed through ROM Manager you can still proceed with this method. Flash Away!
(You can use both ROM Manager CWM and have the nvflashed version working together. You just access either or one at a time, having the nvflashed one means you can boot to CWM. Welcome to Tegra2)
Click to expand...
Click to collapse
Credits:
Thanks goes to player911, djmcnz, ctso(Chris Soyars) and mapin0518 for their contributions!
Thanks goes to omarsalmin for posting the guide and pulling it together for us!
Thanks goes to David Cogen at Unlockr for creating a video tutorial for this app!
Thanks goes to Krylon360 for his original modding work.
Thanks goes to RussUnderHill for his touch port.
And of course thanks (as always) goes to Koushik Dutta for developing ClockworkMod Recovery!!
-----------------------------------------------------------------------------------------------------------------------------
Krylon360's Updates to CWM 4.0.1.5
Ext4 Support
Internal SD ROM Flashing Support
Internal Nandroid Backup Support
Koush's updates to CWM 5.0.2.0
New option for flashing from the internal memory! When you choose "install zip from sd card" there is now an option "choose zip from internal SD card".
External Only Nandroid Backup Support.
EXT4 Support
Fixes a bug where root is sometimes lost during a ROM restore.
CWM Touch Port from P990 updates to CWM 5.8.1.3
Touch Interface
Experimental
Click to expand...
Click to collapse
Procedure:
If you came here first, go here and read the getting started before flashing this recovery: GETTING STARTED GUIDEhttp://forum.xda-developers.com/showthread.php?t=1060715
This process consists of 2 steps.
1. Install the windows driver.
2. Flash the Recovery using the OneClick App.
*** You will need to have .Net Framework 2.0 or above installed. ***
_________________________________________________________________________________________________
VIDEO:
You can watch a Video provided for us by the UnLockr for a walk-through of how to use the One-Click ClockworkMod Recovery Flasher. (Thanks Dave!)
Click on The UnLockr Image to watch the video:(Video is no longer relevant pertaining to entering recovery from boot. And the buttons you can click.)
_____________________________________________________________________________________________________________________________________________
Click to expand...
Click to collapse
One-Click ClockworkMod Recovery NvFlasher​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
One-Click-G2x-recovery-flasher-04-28-12.rar
Click to expand...
Click to collapse
****Warning I am not responsible if you brick your phone!****
Instructions:
Extract the package:
Extract the One-Click-G2x-recovery-flasher-04-28-12.rar to some location of your choosing.
Click to expand...
Click to collapse
Nvidia NvFlash APX Driver
Unlike a lot of Android phones out there the Nvidia Tegra2 chipset require additional drivers in Windows to support low level flashing.
Install APX Windows driver from APX folder.
(Windows x86 and x64 O/S Drivers):
****If you are running VmWare kill it.****
Remove the battery.
Plug in your USB cable to your PC.
Hold Volume Up and Volume Down at the same time keeping them held down.
Plug in the USB cable to your phone. (Keep the buttons held until Windows detects a new APX device.)
Open Device Manager in Windows and you should see "APX Device" listed with an error icon.
Right click on the APX device.
Select 'Update driver software'.
Select 'Browse my computer...'.
Select 'Let me pick...'.
Select 'Have disk'.
Browse to directory you extracted the *driver* software to: One-Click-G2x-recovery-flasher-04-28-12\APX.
Accept any warnings, including the big red alert (you may need to disable UAC).
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'.
If not, uninstall the driver, reboot, rinse and repeat.
Click to expand...
Click to collapse
Flash ClockworkMod Recovery
Remove the battery.
Goto NvFlash directory and Double Click "OneClickRecoveryFlasher.exe".
Make sure the USB cable is unplugged from your phone.
Hold Volume Up and Volume Down at the same time keeping them held down. (Keep them held until you see the "S/W Upgrade" screen on your phone after you complete step7!).
Plug in the USB cable to your phone.
Click the "Flash CWM" button of your choosing. If you own a External SD card I suggest to choose version 5.0.2.0. This gives you Internal and External SD Support for ROM flashing but has External SD Nandroid Backup Support Only! If you do not own a External SD Card choose version 4.0.1.5 what has full Internal SD support for flashing ROMS and Nandroid backup.
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". Once the files are sent and the program is finished running in the command window, you can just pull the USB cord while it still says "S/W Upgrade - Please wait while upgrading...".
Put the battery back in and you can now boot into Recovery. (see below..)
Click to expand...
Click to collapse
Booting into ClockworkMod Recovery
Power off your phone.
Hold Vol Down + Power.
Keep holding them, as soon as you see a "Blue LG Graphic" logo let go of the buttons.
Click to expand...
Click to collapse
Restore LG G2x Stock Recovery
Flash Stock recovery only when you want to send your phone in to T-Mobile. Otherwise do not flash Stock recovery. Stay on ClockworkMod Recovery.
Remove the battery.
Goto NvFlash directory and Double Click "OneClickRecoveryFlasher.exe".
Make sure the USB cable is unplugged from your phone.
Hold Volume Up and Volume Down at the same time keeping them held down. (Keep them held until you see the "S/W Upgrade" screen on your phone after you complete step7!).
Plug in the USB cable to your phone.
Click the "Flash Stock" button.
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". Once the files are sent and the program is finished running in the command window, you can just pull the USB cord while it still says "S/W Upgrade - Please wait while upgrading...".
Put the battery back and you are done.
Click to expand...
Click to collapse
Take it easy guys! I was a pleasure working with all of you.
I am moving on to another device Galaxy S IV.
PM me if you have any support questions.
Click to expand...
Click to collapse

Nice!! Thank you, sir!
Sent from my LG-P999 using Tapatalk

Niiiice

in the extracted folder,someone could place recovery-clockwork-3.0.2.7-p999.img in there and edit the FlashCWMRecovery.cmd to
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 cwm-recovery-recovery-clockwork-3.0.2.7-p999.img and it should work,correct?

crazythunder said:
in the extracted folder,someone could place recovery-clockwork-3.0.2.7-p999.img in there and edit the FlashCWMRecovery.cmd to
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 cwm-recovery-recovery-clockwork-3.0.2.7-p999.img and it should work,correct?
Click to expand...
Click to collapse
I will wrap it up and add it to my app.
EDIT: OK Done Deal

couldn't you have just done the same with a batch file or am I missing something?

could you set it to a variable that allows you to enter a file path to a recovery image and it just flashes that? rather than just the two hard-coded options
j2eubank said:
couldn't you have just done the same with a batch file or am I missing something?
Click to expand...
Click to collapse
Yes, but isn't this more pretty?

j2eubank said:
couldn't you have just done the same with a batch file or am I missing something?
Click to expand...
Click to collapse
Yes I could have and did. But for the new guys, they seem to like just clicking buttons. This should be newbie proof and easier in my opinion.

version 3.0.2.7 has been added.

could you set it to a variable that allows you to enter a file path to a recovery image and it just flashes that? rather than just the two hard-coded options
Click to expand...
Click to collapse
I will keep it updated with the latest versions. Soon there will be just one.

Awww thanks sweetie. I guess I have no reason to not upgrade to the lastest CWM.
I'll add this to my comprehensive "first-steps" thread.

I finally found a pc to recognize my phone and was about to try it the hard way, wow that was so fast and easy it almost scared me lol. Thanks so much for this.
Sent from my G2x

Thanks so much for your very kind and sensational work. I used and still use your one click root for the Vibrant. Your a gentleman and a scholar.

What is the difference in this 3.0.2.7 and the one flashed in rom manager?

TGA_Gunnman said:
Yes I could have and did. But for the new guys, they seem to like just clicking buttons. This should be newbie proof and easier in my opinion.
Click to expand...
Click to collapse
You should make it go get the files and extract them too...
Sent from my Xoom using XDA Premium App

Sweet, just upgraded from 2.4-2.7. Thanks!!

Painless! Thanks!

THANKS!
Awesome!!!! Thanks x10 man! ;D

oddities and/or errors ?
"reboot system now"
the First option in V. 3.0.2.7
powers off the device NOT reboot it
unless "reboot system now" is code for
Turn it off!
when you "reboot system now" (IE: Turn it off) with the USB plugged in
you get the the green charging screen with an oddity and/or error (o/e)
the o/e is that the Touch capacitive LED lights stay on
the only resolution is to unplug the USB till they go off OR turn on the phone
SECOND: (oops i think this is Thrid)
Holding down the Down volume key and power button to get into Recovery FAILS
if the USB is plugged into the phone
it will just keep refreshing the green battery charging icon
Boots into recovery fine if USB is not plugged in
OR plugging in the USB once IN recovery
BUT I'M NOT SURE THIS IS safe!
the last o/e is subjective BUT
seems to take a good 10-20 seconds longer to boot and recognize I'm on T-Mobiles network
it took SO Long the phone said "Emergency calls only" for about 5 seconds
this phone NEVER did that before!!!!
these o/e 's (oddities and/or errors) can't be normal and safe for my phone
can they ?
Rom Manager never caused these problems
that i get these o/e 's in a recovery program is kinda worrisome
PS:
OOPS ONE MORE O/E
because of the slow boot and not recognizing network for so long
i decided to run
"Quadrant"
i got 2686 Before flashing this recovery
NOW i get 2559
THIS is a big difference
and i have rebooted the system twice before running that benchmark
to make sure the recovery program just was not having a bad first boot, hence possibly lowering Quadrant scores
.

a1yet said:
"reboot system now"
the First option in V. 3.0.2.7
powers off the device NOT reboot it
unless "reboot system now" is code for
Turn it off!
when you "reboot system now" (IE: Turn it off) with the USB plugged in
you get the the green charging screen with an oddity and/or error (o/e)
the o/e is that the Touch capacitive LED lights stay on
the only resolution is to unplug the USB till they go off OR turn on the phone
SECOND: (oops i think this is Thrid)
Holding down the Down volume key and power button to get into Recovery FAILS
if the USB is plugged into the phone
it will just keep refreshing the green battery charging icon
Boots into recovery fine if USB is not plugged in
OR plugging in the USB once IN recovery
BUT I'M NOT SURE THIS IS safe!
the last o/e is subjective BUT
seems to take a good 10-20 seconds longer to boot and recognize I'm on T-Mobiles network
it took SO Long the phone said "Emergency calls only" for about 5 seconds
this phone NEVER did that before!!!!
these o/e 's (oddities and/or errors) can't be normal and safe for my phone
can they ?
Rom Manager never caused these problems
that i get these o/e 's in a recovery program is kinda worrisome
PS:
OOPS ONE MORE O/E
because of the slow boot and not recognizing network for so long
i decided to run
"Quadrant"
i got 2686 Before flashing this recovery
NOW i get 2559
THIS is a big difference
and i have rebooted the system twice before running that benchmark
to make sure the recovery program just was not having a bad first boot, hence possibly lowering Quadrant scores
.
Click to expand...
Click to collapse
confirmed working with windows 7 x64 home prem.. however it does power dwn with the reboot device now option.. did not do that with rom manager CWR 3.0.2.7... power off also powers dwn no reboot lol just though id check..

Xoom root and bootloader unlock

I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).

wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?

Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.

RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.

Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?

llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted

TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)

llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?

TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me

I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?

madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.

Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!

Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?

do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.

factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!

madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5

sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).

madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge

Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!

madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

tf101 flashed touch cwm and could not intall driver correctly

1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. windows notice found an unknow device but fail to intall the driver
4 i tried many times to manaual install the apx drivers that posted in the bbs, in device manager it always showed as""unknow device"" instead of ""apx device"" , driver installation fail by auto search the apxusb folder liked everybody said
i was able to force install the apx driver by manaul selected the usb.inf fil. however in device manager it said device is not running correctly error.
i try to rebooy laptop ans the error remain
my tf101 is now softbrick with touch cwm. i could not operate with removeable sdcard but internal sdcar.
the worse thing is i dony have any roms storage in internal sdcard
please anyone can give me a hand？

justinmise said:
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. windows notice found an unknow device but fail to intall the driver
4 i tried many times to manaual install the apx drivers that posted in the bbs, in device manager it always showed as""unknow device"" instead of ""apx device"" , driver installation fail by auto search the apxusb folder liked everybody said
i was able to force install the apx driver by manaul selected the usb.inf fil. however in device manager it said device is not running correctly error.
i try to rebooy laptop ans the error remain
my tf101 is now softbrick with touch cwm. i could not operate with removeable sdcard but internal sdcar.
the worse thing is i dony have any roms storage in internal sdcard
please anyone can give me a hand？
Click to expand...
Click to collapse
Further more
When i pressed V+& Power tf101 screen turn off and window found a unregonized device.
But, window only show" unknown device" instead of "APX" Device which yellow A! remark.
Did any one know how to slove this issue, i tried every drivers file i can file in this bbs but none of them work.
thx
justin

Did you install the APX driver?
You can find it with the nvflash package

baseballfanz said:
Did you install the APX driver?
You can find it with the nvflash package
Click to expand...
Click to collapse
hi
thx for ur reply
i tried to install the APX driver but fail
window pop up and said it found a new device and can not recongized.
device manager recongized it as a "UKNOW Device" With out Yellow ! remark.
as i read in other posts it should read as " APX" with yellow remark.
i also try to froce install the driver but fail again.

It means both WINXP and WIN 7 64bit not able to recongized my TF correctly,
device manage keep show " unknow device" but not able to indentity it as a APX device.
what steps am i missing ?

Exact same problem
I am at the same place as this person.
I Booted into CWM Recovery 5.5.0.4 and I can't get back out. I tried wiping. I had an update.zip on my internal SD card. I've tried everything I've seen on the forums. and NOTHING. On windows I get an Unknown Device in both APX and ADB and ADB won't recognize the device. ADB works fine on all of my other android devices. I feel like i've got a 200 door stop. PLEASE HELP!
My device is a B50 TF-101 SBK1
I'll give anyone that can help me solve this $40 through paypal.
Thanks!

Download universal naked driver from easy flash thread.. unzip the drivers into a folder.. Go to device manager in your laptop and look for that unknown device and there double click on unknown device and select update/install driver.. point the installation to the unzipped folders and click update driver and this should install apx drivers and you should be good to go as that's what I did. Its very easy so take your time and do it...
Sent from my Transformer TF101 using xda app-developers app

udupa82 said:
Download universal naked driver from easy flash thread.. unzip the drivers into a folder.. Go to device manager in your laptop and look for that unknown device and there double click on unknown device and select update/install driver.. point the installation to the unzipped folders and click update driver and this should install apx drivers and you should be good to go as that's what I did. Its very easy so take your time and do it...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Same problem ! dosn't work even with naked driver any solution yet ?

mickz said:
Same problem ! dosn't work even with naked driver any solution yet ?
Click to expand...
Click to collapse
Try plugging your tf101 into another usb port and installing the naked drivers.

I am at the same place as this person.
I Booted into CWM Recovery 5.5.0.4 and I can't get back out. I tried wiping. I had an update.zip on my internal SD card. I've tried everything I've seen on the forums. and NOTHING. On windows I get an Unknown Device in both APX and ADB and ADB won't recognize the device. ADB works fine on all of my other android devices. I feel like i've got a 200 door stop. PLEASE HELP!
My device is a B50 TF-101 SBK1
Click to expand...
Click to collapse
Remove the apx drivers you already have and try installing them again by following these steps:
1- Boot up your transformer into apx mode.
2- Goto device manager and right click on the unrecognized device and goto update drivers.
3- Manually point them to the Folder you extracted have the universal naked drivers and install them. Scan for hardware changes
4- Hopefully your transformer will be recognized in the apx mode.
5- Download the EasyFlasher tool from http://forum.xda-developers.com/showthread.php?t=1688012
6- open EasyFlasher and Choose your device SBK1 or SBK2
7- Flash a new recovery on the transformer with the tool and reboot it.
8- You will have the access to your external sd card where u have ur ROM stored.
These step did the trick on my transformer. Hopefully your problem will be solved.
Hit thanks if i have helped in any way!!

konark500 said:
Remove the apx drivers you already have and try installing them again by following these steps:
1- Boot up your transformer into apx mode.
2- Goto device manager and right click on the unrecognized device and goto update drivers.
3- Manually point them to the Folder you extracted have the universal naked drivers and install them. Scan for hardware changes
4- Hopefully your transformer will be recognized in the apx mode.
5- Download the EasyFlasher tool from http://forum.xda-developers.com/showthread.php?t=1688012
6- open EasyFlasher and Choose your device SBK1 or SBK2
7- Flash a new recovery on the transformer with the tool and reboot it.
8- You will have the access to your external sd card where u have ur ROM stored.
These step did the trick on my transformer. Hopefully your problem will be solved.
Hit thanks if i have helped in any way!!
Click to expand...
Click to collapse
I can't thank konark500 enough. I had previously installed ClockworkMod Touch Recovery using the img file using the instructions on the Cyanogenmod Wiki. It worked, but every time I rebooted it would reboot back into flash and I would have to vol- at reboot to get it to boot to Android. Using EasyFlasher I was able to install TWRP and I am so glad I did. Everything is running better and I boot straight to Android when I need to. TWRP also has a way to wipe system. I was having strange issues with bluetooth and wifi others were not having until I wiped system and started over.
Thanks again konark500

Hi,
Sorry to resurrect a dead thread, but I am facing a similar issue. I installed a bad CWM recovery and since then I am not able to use my TF101. I tried to install the Naked drivers, but it does not work. I tried changing ports, but still the same issue. Please help. I am using Windows 8.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

My guess - your TF101 cable is bad. I had a bad one but it still works with the wall wart to charge. One of the Data + or - cables is disconnected. Try a new cable is my best suggestion.

[Q] Able to access TWRP but cannot install Rom

I apologize if this has been answered elsewhere but after hours of trying to figure this out on my own (with search), I'm posting for help. I'm going to provide as much info as I can. Thanks in advance
I had CleanRom 2.3 installed and totally flubbed upgrading to something else. I current have TWRP v2.5.0 installed but no OS.
In the upper left corner on the bootloader screen it says the following
Key driver not found.. Booting 05
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
I see 3 icons "RCK, Android, Wipe Data"
In the mount menu the only things checked are "cache, data, micro SDcard" (not system). I can manually check system.
I am trying to flash the stock rom found here: http://forum.xda-developers.com/showthread.php?t=2223918 (I don't care if I need to go to a different rom, I just want my tablet to work)
When installing it says successful, however the readout above says "Checking for MD5 file... // Skipping MD5 check: no MD5 file found."
When I reboot it prompts me to install SuperSU, device does not appear to be rooted. If I swipe to install the screen immediately goes black and begins reboot. It gets to Asus boot screen with the blue bars, loads the bars and then reboots again. It will hang on Asus screen if I don't go into bootloader.
I have tried going into TWRP and using the advanced wipe to format everything prior to installing and it did not help.
I have tried installing the SDK on my computer to run fastboot, but when plugging in to my PC, it does not recognize the android device.
I'm sorry but I seem to have bit off a bit more than I can chew with this stuff and may need quite a bit of help here. Thanks for anybody willing to help me

skaplan86 said:
I apologize if this has been answered elsewhere but after hours of trying to figure this out on my own (with search), I'm posting for help. I'm going to provide as much info as I can. Thanks in advance
I had CleanRom 2.3 installed and totally flubbed upgrading to something else. I current have TWRP v2.5.0 installed but no OS.
In the upper left corner on the bootloader screen it says the following
Key driver not found.. Booting 05
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
I see 3 icons "RCK, Android, Wipe Data"
In the mount menu the only things checked are "cache, data, micro SDcard" (not system). I can manually check system.
I am trying to flash the stock rom found here: http://forum.xda-developers.com/showthread.php?t=2223918 (I don't care if I need to go to a different rom, I just want my tablet to work)
When installing it says successful, however the readout above says "Checking for MD5 file... // Skipping MD5 check: no MD5 file found."
When I reboot it prompts me to install SuperSU, device does not appear to be rooted. If I swipe to install the screen immediately goes black and begins reboot. It gets to Asus boot screen with the blue bars, loads the bars and then reboots again. It will hang on Asus screen if I don't go into bootloader.
I have tried going into TWRP and using the advanced wipe to format everything prior to installing and it did not help.
I have tried installing the SDK on my computer to run fastboot, but when plugging in to my PC, it does not recognize the android device.
I'm sorry but I seem to have bit off a bit more than I can chew with this stuff and may need quite a bit of help here. Thanks for anybody willing to help me
Click to expand...
Click to collapse
It is a bug in the twrp.. Go to mount and check the box for /system. Shutdown your device completely without install anything when asks for a few seconds and boot back into your twrp. Go back to mount and check to see if your system is mounted. If it is mounted, then you can install the ROM that you like, good luck...:fingers-crossed:

LetMeKnow said:
It is a bug in the twrp.. Go to mount and check the box for /system. Shutdown your device completely without install anything when asks for a few seconds and boot back into your twrp. Go back to mount and check to see if your system is mounted. If it is mounted, then you can install the ROM that you like, good luck...:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the tip! It didn't work I loaded into TWRP. went into Mount and checked the system partition. Then went to Reboot and selected Power Off. No OS Installed, swiped to power off. When prompted to install SuperSU I selected Do Not Install.Left off for about 5 minutes
After booting into TWRP again, system is not showing as mounted.

skaplan86 said:
Thanks for the tip! It didn't work I loaded into TWRP. went into Mount and checked the system partition. Then went to Reboot and selected Power Off. No OS Installed, swiped to power off. When prompted to install SuperSU I selected Do Not Install.Left off for about 5 minutes
After booting into TWRP again, system is not showing as mounted.
Click to expand...
Click to collapse
It happens to me a few time in the past and that was how I fixed the problem. You may want to try that a few time... You could also try to mount the /system and install the new ROM at the same time to see if it works.. Another the solution is to update your twrp to a newer version v2.6.3.1. I don't see that bug any more with that version and let us know if any of those tips is working out for you, good luck...:fingers-crossed:

What is the best way to install the newest version of TWRP? I'm looking here http://teamw.in/project/twrp2/105
I cant do the app install, and fastboot isn't working (pc doesn't recognize device) and I'm not sure how to get it from an external SD card to the internal SD in order to do the ADB/Terminal Method.
Thanks

skaplan86 said:
What is the best way to install the newest version of TWRP? I'm looking here http://teamw.in/project/twrp2/105
I cant do the app install, and fastboot isn't working (pc doesn't recognize device) and I'm not sure how to get it from an external SD card to the internal SD in order to do the ADB/Terminal Method.
Thanks
Click to expand...
Click to collapse
Here is the link for the twrp. Select the version that you like:
http://techerrata.com/browse/twrp2/tf700t
Whatever custom ROM that you choose, you may want to get the bootloader that is going to work for that ROM.
Also, if you have a nandroid backup, you can always restore it to see if it works..
Edit: Oops I did not read carefully. Here is the guide that you could follow, sorry...
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html

LetMeKnow said:
Here is the link for the twrp. Select the version that you like:
http://techerrata.com/browse/twrp2/tf700t
Whatever custom ROM that you choose, you may want to get the bootloader that is going to work for that ROM.
Also, if you have a nandroid backup, you can always restore it to see if it works..
Edit: Oops I did not read carefully. Here is the guide that you could follow, sorry...
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
I really appreciate your help with this, I'm still having trouble even getting that utility working. The linked guide takes me to http://forum.xda-developers.com/showthread.php?t=2588979 which is not installing properly. when it tries to install ADB & fastboot it says " 'setx' is not recognized as an internal or external command, operable program or batch file.
I'm also having driver issues that my pc is not recognizing the device. It sees the unknown device in device manager but when I try to manually add the driver as in that guide it doesn't work the way the guide says it should.
It looks like I'm going to need to spend some time troubleshooting why I can't get fastboot and ADB installed properly. I'll probably try a different PC.
Thanks!

skaplan86 said:
I really appreciate your help with this, I'm still having trouble even getting that utility working. The linked guide takes me to http://forum.xda-developers.com/showthread.php?t=2588979 which is not installing properly. when it tries to install ADB & fastboot it says " 'setx' is not recognized as an internal or external command, operable program or batch file.
I'm also having driver issues that my pc is not recognizing the device. It sees the unknown device in device manager but when I try to manually add the driver as in that guide it doesn't work the way the guide says it should.
It looks like I'm going to need to spend some time troubleshooting why I can't get fastboot and ADB installed properly. I'll probably try a different PC.
Thanks!
Click to expand...
Click to collapse
Since you have SDK tool available, you can try to install the USB driver from this guide and instead using USB driver, you can use the naked driver from this download:
http://developer.android.com/sdk/win-usb.html
http://forum.xda-developers.com/showthread.php?t=2513339
You may want to manually install your driver from your device manager on your pc.
When you are browse to the naked driver, you need to select "android_winusb.inf" file for your fastboot and adb. Reboot your pc when you are done with the installation, good luck...:fingers-crossed:
Edit: Are you using win 8? The naked driver is working fine with win 7 but may not work with win 8....
Update: If you know linux, you can follow this post because linux does not require a driver to run fastboot...
http://forum.xda-developers.com/showthread.php?t=2679916&page=2

LetMeKnow said:
Since you have SDK tool available, you can try to install the USB driver from this guide and instead using USB driver, you can use the naked driver from this download:
http://developer.android.com/sdk/win-usb.html
http://forum.xda-developers.com/showthread.php?t=2513339
You may want to manually install your driver from your device manager on your pc.
When you are browse to the naked driver, you need to select "android_winusb.inf" file for your fastboot and adb. Reboot your pc when you are done with the installation, good luck...:fingers-crossed:
Edit: Are you using win 8? The naked driver is working fine with win 7 but may not work with win 8....
Update: If you know linux, you can follow this post because linux does not require a driver to run fastboot...
http://forum.xda-developers.com/showthread.php?t=2679916&page=2
Click to expand...
Click to collapse
Thanks so much for all your help. There is a lot here for me to try now. I think I am done for the night but will check back when I have had a chance to go through all this stuff. I'll be sure to update you
Many thanks

skaplan86 said:
Thanks so much for all your help. There is a lot here for me to try now. I think I am done for the night but will check back when I have had a chance to go through all this stuff. I'll be sure to update you
Many thanks
Click to expand...
Click to collapse
Don't know, but this thread (post 23) may be helpful to you to get the drivers installed.
http://forum.xda-developers.com/showthread.php?t=2670645&page=3
CROMi 2.3 - wasn't that still ICS based? You may have messed up your file system on /data if you had stock JB and need to reformat it before installing a new rom.
In your current TWRP select Wipe > Advanced > Format Data (you will loose all data on the internal SD)
Go to the CROM--X thread: http://forum.xda-developers.com/showthread.php?t=2425383
Download the bootloader/TWRP 2.6.1 package for your SKU and the CROMi-X zip
Flash the bootloader/TWRP zip in your current recovery
Reboot! Even if your boot hangs or loops, the BL/TWRP will get flashed before Android boots (you should see a blue progress bar)
Reboot into TWRP which now should be 2.6.1
Install CROMi-X
Good luck

[Q] TF101 - upgrade or buy a new tablet ?

Hi All, new to this forum... what brought me here is trying to figure out if I can upgrade the TF101 to android higher than 4.0.3 that seems to be the "normal" latest version you can get.
Issues I have are: lockup, freeze, twitter post (crash twitter), screen weird colors (need reboot) etc... Maybe I have some hardware issue... planing to open the case and verify all connectors are ok and well seated.
I just spent 4 hours looking around this forum and saw the KatKiss 4.4.4 thing... I say thing because I have no clue (and did not find how) to install this thing.
So! Is it worth it that I spent hours more on understanding how to upgrade, debug and all... or I just go buy a new tablet?
I saw some post around the twitter issue that did not work either after KatKiss upgrade, so not sure if it's worth it ?
I was looking at the Samsung Pro tablets with 8 cores... seems amazing! But pricy!
Anyhow, recommendations?
If you say... sure try to upgrade to 4.4.4 with KatKiss... ok, I can try that, but from the last 4 hours of reading/looking around, I did not find instructions steps I could understand.
Most of those steps I have not clue what they are!
These builds are designed to be installed from your favorite recovery. MAKE SURE TO INSTALL A COMPATIBLE ANDROID 4.2/4.3 RECOVERY!
TWRP >= 2.3.2.3 is recommended, new TWRP available here
Backup everything !
Go to recovery
Make a full wipe / factory reset (you can skip this step if you're already on KatKiss-4.4, if ever you encounter a problem do the full wipe and try again before reporting )
Format /system (only if Version<026)
Flash the rom
Flash KatKiss gapps
Wipe cache/dalvik
Reboot
Click to expand...
Click to collapse
Thanks for any feedback
Cheers!
Simon

I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk

r2go said:
I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon

SimonFiliatrault said:
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon
Click to expand...
Click to collapse
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk

r2go said:
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon

SimonFiliatrault said:
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon
Click to expand...
Click to collapse
Easiest way, use Easyflasher (If your TF101 has a serial number B6O or eariler (Some B7O), it is an SBK1, most B7O and all higher are SBK2) choosing the wrong one in Easyflasher will not do any harm, it just won't work
http://forum.xda-developers.com/showthread.php?t=1688012
1: Flash TWRP recovery with Easyflasher
2. Download KatKiss ROM #33 & Latest Gapps and copy to your MicroSD, stick MicroSD Card into TF101
3: Boot to TWRP Recovery by powering off the TF, then pressing and holding Power & Volume Down until the white text appears at the top of the screen, then quickly hit Volume Up once
4: Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
5: Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
6: When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
7: Once GAPPS have completed installing (Ignore any messages about failing to mount partitions etc) WIPE Cache and Dalvik Cache (Might ask you immediately after flashing Gapps, if not, do it from the WIPE menu
8: Choose REBOOT > SYSTEM or POWER OFF > REBOOT
9: All being well, you are now running the KatKiss ROM
---
TIPS:
When using Easyflasher, you're gonna need to install the "Universal Naked Drivers" from the Easyflasher thread - use a 32bit Windows 7 for least chance of any problems, 64bit windows requires driver signing, and so do all versions of Windows 8.x, you can use 8.x but you'll need to disable driver signing mode before installing them
---
Any problems, reply here and I`ll check every now and then

ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?

CRAP!!! The main reason I updated this tablet was in the hopes to fix the twitter issue... that is, when trying to post a new tweet, the app crash and restart...
SAME issue!
Any tips on this one would be wonderful.

It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!

SimonFiliatrault said:
ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?
Click to expand...
Click to collapse
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.

706
Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
Unsure what you are referring to?
1) Rooting the TF101
2) Fixing Twitter issue
As you see in the thread, I have successfully installed 4.4.4 KatKiss.

barkeater said:
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.
Click to expand...
Click to collapse
Did you make sure the zip on the flash drive are ok? Did you try to open them on a PC?

Found a solution for twitter! Simply installed which is better! TWEEDLE

Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
KatKiss is already rooted!
SimonFiliatrault said:
Found a solution for twitter! Simply installed which is better! TWEEDLE
Click to expand...
Click to collapse
Great pleased you managed to get it working in the end, you can now update TWRP to either the latest official 2.3.2.3 or the unofficial which has been taken over by another member, that's possibly why you ended up with the DATA failing to wipe
Twitter works ok for me, but there are 2 different types of KatKiss, there is the normal one which has a speed increase, and the NonLinaro version which has much better compatibility with apps
Its possible twitter is not liking the Linaro version (Normal one)
Anyway, you are set to flash whichever ROMs you like now you have TWRP, but Id advise updating to 2.3.2.3 to avoid issues, that's the version Ive been running since it was released
Oh and SBK1 and 2 mean, Secure Boot Key, SBK1 was leaked and therefore very easy to flash recovery and other stuff to that required the key, SBK2 did not leak, so devs had to find workarounds in order to flash recovery

Wow Simon.
Already so much.
By the way you sound like a pro already
Now just follow what *detection* says.
That Rom is fast and smooth.
Verstuurd vanaf mijn SM-G900F met Tapatalk

I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon

SimonFiliatrault said:
I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon
Click to expand...
Click to collapse
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)

*Detection* said:
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)
Click to expand...
Click to collapse
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?

SimonFiliatrault said:
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?
Click to expand...
Click to collapse
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery

*Detection* said:
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery
Click to expand...
Click to collapse
After first attempt, yes I entered KK then did reboot in recovery and did not work.
I have tried many time to do power with vol down and vol up... I see "cold-booting linux"... then KK, not recovery mode
I started another thread for this, not sure where the best place to discuss this is?