Database Info

[Q] Completing Root Process

I'm trying to root my Rogers One X running 4.1.1 using these instructions, howtorootandroid.org/2013/05/28/how-to-root-htc-one-x-step-by-step-tutorial/ (as a new user I'm restricted from posting actual links).
I've got everything completed to the point where it says to disconnect the USB cable and select Recovery from the HBoot menu. When I select that, the phone reboots to the home lock screen. The next step says to go to Backup and backup the system partition. Problem is, I don't know where they mean when they say go to Backup. The only Backup function I know of is in Settings and that just backs up the Google user account data. How does one backup the system partition? Is the phone supposed to reboot to the lock screen from the Recovery prompt? Or is something going awry in that step?
After that it says go to install and install the SuperSU.zip file. Using a file manager I can locate the apk for the Superuser app and it installs but when I open it I get a message saying "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" That last part seems obvious.
Thoughts appreciated on how to resolve.
Thanks.

Stop what you're doing, you're using a root process for the wrong device. That's for the quad core One X, if your phone is a Rogers phone then it is the dual core version. To be sure, go into your bootloader and tell us what it says there, only the top four or five lines. To get into the bootloader, simply power the phone on by holding the power button and the volume down button at the same time, keep holding until it boots into a white screen, that's your bootloader.
Sent from my Evita

Thanks. Don't need to go into bootloader, just checked the device hardware information and you're right, it's a dual core. Using the volume + power buttons won't go into bootloader. I can get there with the Hanson2000 utility. The items in the Fastboot USB menu are Bootloader, Reboot, Reboot Bootloader and Power Down.
Through the process I used last night, the bootloader is unlocked and I haven't bricked the phone.
What's the process to root a dual core version, then?
Another question. Since the bootloader is now unlocked, do I need to continue to finish rooting the phone? With the bootloader unlocked, I can install custom ROMs, right? That's, ultimately, the goal. I'm trying to be able to update to 4.2 or 4.3 which, I've been led to believe, will also enable full USB host functionality on the phone.
Thanks.

Essentially you've done the hard part now. All that is left to do is install a custom recovery, and then you'll be able to flash custom ROMs from within that recovery. The AIO kit only has the ability to install TWRP 2.5 I believe, and that version is riddled with faults. So below I'll outline how to install a stable version.
Download TWRP 2.6 from here. You'll need to flash it manually using fastboot. So once you've downloaded it, put it in the same directory that adb and fastboot reside in on your pc and connect your phone. Now you need to open a command prompt from within that directory (shift + right click opens the menu, then select open command prompt here). Enter the following command:
fastboot devices
This will make sure you're connected properly, hopefully it will return your device serial number. Now you want to enter the following commands:
fastboot flash recovery "filename.img"
(the exact recovery filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you'll have a custom recovery which you can enter by pressing the recovery option on your screen. Now it's time to select the ROM you want to try and download to your pc. Once you've done that, select mount from the recovery menu, then select mount usb storage. Your phone memory will now show up as a removable drive on your pc and your can copy a ROM across.
Before you flash a ROM, make a backup of your current setup, you can do this by entering the backup option from the main recovery menu. It's essential to backup the system partition in case something goes wrong in the future, you can easily restore it.
In terms of ROMs, only EVER download ROMs you find in our forum. Never download from a different device forum or from another site, that's a surefire way to brick your phone. Your two options are Android Development, where you'll find Sense based ROMs, and Original Android Development, which is where you'll find aosp ROMs.
Once you've copied a ROM to your phone, simply perform a full wipe in recovery (cache/dalvik cache/factory reset/system), do this by going to the wipe option, then advanced wipe. Just don't wipe sd card. Then you can select the install menu, and find the ROM on your sd card, and install it.
Your phone is s-on, so you'll need to perform one extra step. When you download the ROM, within the root folder of the zip file there is a file called "boot.img", you need to extract this and copy/paste into your adb/fastboot directory. After the install process has finished in recovery, go back to the main menu and select reboot, then select bootloader. When the phone reaches bootloader, make sure it's connected again and issue the following command:
fastboot flash boot boot.img
Now you can reboot your phone and enjoy the ROM. Please note, you will need to flash the boot.img from each ROM you want to install. Unless you decide to get s-off, which removes that need.
Sent from my Evita

Actually, AIO allows you to use the TWRP, ClockWorldMod or your own file. I downloaded the file you linked and WinZip says it's an invalid archive. Can I use CWM instead?

It is suggested that you use TWRP, other recoveries are known to have bugs. Don't worry about what WinZip says, just check the md5 and as long as it matches the md5 listed on the download page it's fine.
I'd also suggest doing it the manual way as you actually learn something during the process. The time will come when one day you need to do something manually, and it's better to have a little experience than have to learn at zero hour.
Sent from my Evita
---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------
Don't get me wrong, AIO kits are convenient, but they're also a big part of the reason why people have absolutely no idea about what they're doing to their phones, or how to recover if something goes wrong.
Sent from my Evita

Problem is that WinZip shows no file when it opens the archive. Can't do anything with it.
I understand your point about doing it manually. I'm a photographer and an end user, not a programmer and don't do code well. I can likely manage getting the recovery installed but took a look at a couple of the custom ROM threads and have no idea what the people posting the threads are talking about insofar as some of the instructions. I just want to get the phone able to operate as a USB host.

It's not a zip file, that's why. You're not meant to be able to do anything with it on your pc. Check the md5 like I said and you'll know the file integrity is good. Then you just need to flash it as per previous instructions.
Sent from my Evita
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
What do you mean by usb host? In what kind of application?
Sent from my Evita

Sounds like he wants a rom with OTG support

Yeah that's what I was thinking.
Sent from my Evita

Yes, I do want a ROM with full OTG support. It's getting there that's the thing. Stock, it has USB storage capability and some devices (mouse/keyboard) but not broader for things like cameras.
I'm sorry for the problems. Remember I'm not a coder or a deep 'inside baseball' guy. When a file shows up on my computer as a zip file, I think I need to unzip it. I don't have the first flying flipping clue what md5 is, other than some sort of hash function, and have no idea how to check it.
It seems there are utilities to check it. Based on what the WinMD5 utility I downloaded tells me, it seems that the file is fine. I'll try to load it and see what happens.
EDIT: OK, I think I need to just do a factory reset and forget about it.
I downloaded ADB and fastboot, put it on my desktop. There are two nested folders inside the main folder. I put the recovery file into the Android folder which has the fastboot application. Opened a cmd window from within that folder and typed 'fastboot devices'. Nothing happened. It just came back to the same command prompt. The serial # wasn't returned. Nada.
EDIT II: I booted into bootloader manually and tried 'fastboot devices' again from the command prompt. It worked this time, returning the serial #. Next I tried to flash the recovery file and got the following message - "error: cannot load 'openrecovery-twrp-2.6.0.0-evita' : Unknown error. I decided to try the AIO kit and see what happened. Selected Your Own Recovery and started the process. The window opened to select the .img file and no file was showing that had that file extension. I think the problem is that the downloaded file is being seen by my computer as a zip file. Can I simply change the file extension to .img?

RFPhotog said:
Yes, I do want a ROM with full OTG support. It's getting there that's the thing. Stock, it has USB storage capability and some devices (mouse/keyboard) but not broader for things like cameras.
I'm sorry for the problems. Remember I'm not a coder or a deep 'inside baseball' guy. When a file shows up on my computer as a zip file, I think I need to unzip it. I don't have the first flying flipping clue what md5 is, other than some sort of hash function, and have no idea how to check it.
It seems there are utilities to check it. Based on what the WinMD5 utility I downloaded tells me, it seems that the file is fine. I'll try to load it and see what happens.
EDIT: OK, I think I need to just do a factory reset and forget about it.
I downloaded ADB and fastboot, put it on my desktop. There are two nested folders inside the main folder. I put the recovery file into the Android folder which has the fastboot application. Opened a cmd window from within that folder and typed 'fastboot devices'. Nothing happened. It just came back to the same command prompt. The serial # wasn't returned. Nada.
EDIT II: I booted into bootloader manually and tried 'fastboot devices' again from the command prompt. It worked this time, returning the serial #. Next I tried to flash the recovery file and got the following message - "error: cannot load 'openrecovery-twrp-2.6.0.0-evita' : Unknown error. I decided to try the AIO kit and see what happened. Selected Your Own Recovery and started the process. The window opened to select the .img file and no file was showing that had that file extension. I think the problem is that the downloaded file is being seen by my computer as a zip file. Can I simply change the file extension to .img?
Click to expand...
Click to collapse
That's a bit odd, it shouldn't download as a zip, it should be a file with the ".img" extension. Did you download it from the link I posted? Are you able to check the extension type in file properties?
Also I noticed you had a command return saying 'openrecovery-twrp-2.6.0.0-evita', did you make sure you put the ".img" extension on the end of your fastboot command?
Sent from my Evita

I did include the .img extension. Tried it again now and it worked. I must have made a type when I tried the first time.
So, I have a custom recovery process installed. Now, what ROM would you suggest?
By the way, I do appreciate the help.

I can't really suggest a ROM, as best/favorite ROM threads and questions aren't allowed on XDA. In this case I can probably point you in the right direction though.
The OTG side of things lies within the kernel though, not the ROM itself. The only kernel I can think of that has this support is the Rohan b6 Kernel, which you'll find here.
This means you'll only be able to use 4.1 based ROMs from this section though. The reason for this is because aosp kernels can only be used with aosp ROMs. If you try to use this kernel in conjunction with a sense based ROM, or an aosp ROM from a different android version (4.0, 4.2, 4.3) it won't work.
Keeping all that in mind, there are some great 4.1 aosp ROMs in that section. Development has moved into 4.2 and above but you'll still find the 4.1 ROMs there. Just make sure to look at the android version in the title and features of the ROM.
Flashing a custom kernel is an extra step in the install process too. Do the wipe in recovery like I described earlier, then install the ROM, then install the kernel. Instead of extracting the boot.img from the ROM zip, extract it from the kernel zip and use the same method I outlined before to flash it in fastboot.
Sent from my Evita
---------- Post added at 02:22 AM ---------- Previous post was at 02:22 AM ----------
Oh, and it's no problem at all, always willing to lend a hand.
Sent from my Evita

Well, we're getting there, I think.
I've got the file loaded onto the phone. The filename is rom.zip. I've done the wipe and then from the Install menu I selected the rom.zip file and swiped to start. Got an error message saying 'unable to open zip file'.
Tried a different ROM and it worked.

Which ROM did you end up going for?
Sent from my Evita

Started with Evervolv. That's the one that didn't work. Then went to Cyanogen. It's still booting for the first time so still hoping it all worked.

Did you flash the boot.img via fastboot afterwards?
Sent from my Evita

Yep. The one from the new kernel.
Did a wipe, advanced wipe, installed the ROM, installed GAAPS, installed the kernel, flashed the boot.img from the kernel zip file.
It's at the Cyanogen spinning wheel. My understanding is that it can take a while on the first boot?
If it sits here for much longer, I'll do it again, wipe and reinstall.

It can take a while, not normally longer than five minutes though.
Sent from my Evita

[Stingray] Did you BigPart and lose data? I may have the solution...

For my fellow Stingray users (and possibly Everest users as well, if they're having similar issues), I was one of the group of people who couldn't get data on any 4.4 roms after going through the BigPart process. After a bunch of trial and error (and some excellent suggestions from fellow community members, I was able to get data working again and I'm happily enjoying KitKat on my three-year-old Xoom. If you've got a bit of patience and an hour or so, I believe I've got the solution to help you restore your data as well.
IMPORTANT: This entire process should be completely harmless to your Xoom, and the goal here is to help the group of Stingray users who lost all data functionality to repair that issue so that they can enjoy the full benefits of Android 4.4 (and potential future updates). That said, you do this at your own risk, and in doing so, you agree not to hold me accountable if you brick your Xoom, or if it dies, loses data (you’re going to lose everything but what’s on your SD Card, so think about that before you start the process), or any other unforeseen circumstances.
STAGE 1: Reverting to Stock Partitions
1.) DISCLAIMER: Any and all data on anything but your external SD Card will be completely wiped. If there are any back-ups you value, move them to your SD Card, your computer, or a cloud storage account. There’s no getting them back once you start this process.
2.) First off, you need to make sure you have everything you need downloaded and ready. You will need the following on your SD Card:
-TWRP 2.6.3.0 touch recovery from @runandhide05
-TWRP 2.6.3.0 BigPart touch recovery from @runandhide05
-a standard partition Stingray rom (I used CM 10.1 from @Steady Hawkin, 10/28 build, which you can find here)
-(optional) GApps package for standard partition rom (I used the 02.20.2013 Unified GApps found here, but you seriously don’t need them for anything.
-your BigPart rom of choice (I went with CM 11, which you can find in this thread, but there’s also OmniRom, which you can find in this thread, both of which were kindly ported by @Schischu. If you opt for Omni, you’ll also need a flashable zip file of the Superuser app of your choice.)
-your 4.4 GApps of choice (I use the PA Modular Full GApps, but any 4.4 GApps will be fine once you’ve repartitioned)
-Universal Xoom root .zip file, created by @solarnz (which you can find here)
As well as the following on your computer:
-The Android SDK, specifically ADB and Fastboot (if you don’t have this set up yet, start at the very beginning: http://developer.android.com/sdk/index.html)
-a stock android rom for the Stingray (I used HRI66, which you can find here)
-TWRP 2.6.3.0 touch recovery from @runandhide05
And one last thing:
-A good wifi connection (either through a wireless router or using your phone or other device with a data plan)
3.) Reboot your tablet into recovery and flash the non-BigPart TWRP 2.6.3.0 touch recovery. DO NOT REBOOT YET!
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
5.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
6.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
7.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time. (I’ve done this process multiple times and each time, the amount of time that it needed on various reboots was different, so be patient if you don’t want to brick your Xoom.)
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’re back to the standard partitions.
9.) Tap the Install tab. Your external sdcard should be showing by default. Flash your standard partition rom (in my case, CM 10.1) and your GApps, if you so choose (though again, they serve no purpose).
10.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen standard partition rom. Ensure that everything loads (again: this may take some time) and go through the setup process.
11.) Go into Settings and enable developer options (Settings --->About Tablet--->tap Build Number several times until Developer options are enabled.
12.) Go into Developer options and make sure that Android debugging is checked. Now you’re ready for Stage 2.
STAGE 2: Returning to stock Honeycomb
1.) Find your stock Honeycomb rom (as mentioned earlier, I used HRI66) and unzip it into a folder of its own.
2.) Inside the folder you unzipped, you may find another folder designated MZ600_HRI66. Inside that folder, there will be four files, boot.img, recovery.img, system.img, and userdata.img
3.) Copy those files into the folder that has adb.exe and fastboot.exe (if you simply installed the Android SDK as instructed, it’ll be inside the platform-tools folder, which is itself inside the sdk folder).
4.) Connect your Xoom to your computer using a USB data cable (preferably a Motorola one if you have one available) and ensure that there is a notification that says “Android debugging enabled” (if you don’t see this notification, go back into Settings --> Developer options, and make sure that “USB debugging notify” has a check in the box next to it).
5.) Open a command prompt in the directory that contains adb.exe and fastboot.exe (Windows 7 and up, click the File tab and choose “Open Command Prompt”; if you’re on Vista or older, I can’t help you, but I’m sure Google can).
6.) Enter the following command:
Code:
adb reboot bootloader
7.) Your tablet will reboot to the red “M” logo and it should say “Fastboot protocol initiated” at the top in white letters. If so, proceed to step 8; if not, and assuming your tablet has rebooted normally, try step 6 again.
8.) Enter the following commands into your command prompt, one at a time, and let each one compete. You’ll get a series of status updates in both your command window and on your tablet as each process completes. Wait for it to say “Done!” before entering the next command.
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
9.) Once all those steps have completed, enter one last Fastboot command:
Code:
fastboot reboot
10.) Your tablet should now reboot into factory Honeycomb and you can disconnect from the USB cable. As mentioned before, this is one of those reboots that could take a few seconds up to several minutes, so just be patient!
NOTE: These next several steps are much easier to complete if you have a high-speed wifi connection. At this point, if you don’t have a data connection, don’t panic, at least not yet. I tried multiple times to activate my device on the Verizon network, and while it said it was successful each time, I never managed to get a 3G connection back. Your best bet is to connect to Wifi and continue the process.
11.) On your tablet, go to Settings --> About tablet --> System Updates. More than likely, your tablet has already started downloading the next update, so you can just sit back and wait for it to download. You’ll get a notification when the download is complete. While you’re waiting, on your computer, move boot.img, system.img, recovery.img, and userdata.img from your ADB folder back into a folder where you’ll have them on-hand if you need them again.
12.) Once you get the notification that the update is downloaded, you’ll have the option to reboot and install or install later. Choose to reboot and install. Your tablet will reboot into the stock Android recovery and install the update, then go to the “M” logo screen and more white text will appear. Wait for this to complete and your tablet to reboot again.
13.) Repeats steps 11 and 12 until you receive and install the IMM76L build (I believe that’s the one) – it’ll be Ice Cream Sandwich and your data should be working. If it’s not, then I’m not sure what to suggest. Your tablet will attempt to download the stock 4.1.2 build (JZO45M) and if it completes, it’s not a big deal, but MAKE SURE YOU DON’T INSTALL IT!
14.) Go to Settings --> Developer options and turn on USB debugging again. (If everything is grayed out, tap the On/Off slider in the upper righthand corner to make the checkbox clickable). At this point, you’re ready for Stage 3.
STAGE 3: Re-rooting
1.) On your computer, find the copy of TWRP 2.6.3.0 touch recovery from @runandhide05 (the standard one, not the BigPart one, yet), and unzip it into its own folder. Copy the recovery.img file from the unzipped folder into the same directory that contains adb.exe and fastboot.exe. IT IS CRUCIAL THAT YOU REMOVED THE RECOVERY.IMG FILE THAT YOU USED TO GET BACK TO STOCK EARLIER!
2.) Connect your Xoom to your computer via USB data cable and ensure that the USB debugging notification appears and that your computer recognizes your Xoom.
3.) Open a command prompt in the directory with adb.exe and fastboot.exe and enter the following command:
Code:
adb reboot bootloader
4.) Your tablet will reboot to the “M” logo screen and it will again say “Fastboot protocol initiated”. When it’s ready, enter the following command into your command prompt:
Code:
fastboot flash recovery recovery.img
5.) Once you get the “Done” notification in the command prompt and on your tablet, enter the following command:
Code:
fastboot reboot
6.) Your tablet will reboot, and when you see the “M” logo screen, wait three seconds and press the Volume Down key. “Android recovery” will appear, press the Volume Up key.
7.) Your tablet will now boot into TWRP 2.6.3.0 and it may “hang” at the TWRP splash screen for some time – that’s normal, wait it out, and when TWRP loads, tap the Install tab. Navigate to the root of your external sdcard (if it’s not showing by default), choose the Xoom Universal root.zip file, and install it.
8.) Tap the Home icon, tap the Reboot tab, and tap System from the reboot menu. Your tablet should boot back into ICS, but you should now have a superuser app installed (ChainsDD’s, I believe). If that’s the case, and you’ve still got data functionality, then it’s time to move to Stage 4.
STAGE 4: BigPart and KitKat
1.) Reboot your tablet into recovery (you have two options – either shut down your tablet, power it back on, wait three seconds at the “M” logo screen and then press Volume Down, followed by Volume Up when it says “Android Recovery”, or reconnect your tablet to your computer with a USB data cable, open a command prompt in your adb directory, and enter the following command: adb reboot bootloader)
2.) Reboot your tablet into recovery and flash the TWRP 2.6.3.0 BigPart touch recovery. DO NOT REBOOT YET!
3.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
4.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
5.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
6.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time.
7.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’ve successfully repartitioned your tablet back to BigPart.
8.) Tap the Install tab. Your external sdcard should be showing by default. Flash your BigPart rom (and, if you’re installing Omni, your superuser zip file, or, if you’re not flashing one of Schischu’s KitKat roms, the corresponding BigPart boot img or the ElementalX kernel). NOTE: BECAUSE THIS WASN'T SUCCESSFUL FOR EVERYONE, FOR THIS STEP, PLEASE FLASH SCHISCHU'S JANUARY 4TH VERSION OF CM 11 FOR THE STINGRAY, WHICH YOU CAN FIND HERE.
NOTE: You probably can flash your GApps at this point as well; however, I’m detailing the process as I had success with it.
9.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen BigPart rom. Go through the setup process, ensure you have data, and if you do (and you didn’t do so already), reboot and install your GApps.
NOTE: You may get com.android.phone force close errors when going through setup – if this happens, it’s a good thing – pull your SIM card and reboot, complete setup, re-insert SIM card and reboot again.
If this post helped you, then give thanks to the following people (because they did all the hard work):
@bigrushdog (for the hard work on BigPart) @realjumy (for the hard work on BigPart)
@Schischu (for the excellent KitKat roms)
@xyrcncp (for clarifications that led to a minor breakthrough) @rapson2000 (for thinking outside the box and leading to my breakthrough)
There are probably a bunch of other people who contributed that I missed, but I wanted to get this up there in case other people were still having issues.

Reserved to answer any questions that may arise.

LTE data still not working
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.

variatbg said:
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
Click to expand...
Click to collapse
I've repartitioned multiple times now - once from stock, rooted Jelly Bean, and got no data, then back to standard partition and CM 10.1 with only 3G, back to BigPart with no data, then I followed the steps that I wrote up here and now I'm BigParted on CM 11 with data. So it's not the repartitioning process. I'm a testament to that. What were you on when you did the BigPart process for the first time?
Edit: if you're willing to do the whole process again, would you try installing the very first CM 11 that Schischu released? I should've specified that that's the rom I installed first after repartitioning this time. One I had working data, I updated to the latest version.
Sent from my HTC6435LVW using xda app-developers app

Help with MZ605 (Everest) stock (step 10 of stage 2)
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!

LTE data still not working
webeougher said:
What were you on when you did the BigPart process for the first time?
Click to expand...
Click to collapse
I was first using OmniROM of January 12, though I can't quite recall. Then I also tried CM 11 and no dice there. Following your process, when I first reverted to CM 10.1 on original partitions, data was immediately present again.
It was there through all the reversions to stock 3.2.2, and through every OTA update Motorola sent to the device. In fact, some of the updates wouldn't even show up except over Mobile Data.
One thing that might make a difference is that this Xoom is on a business account through Verizon. It's not part of a shared data plan, but there might be a different categorization perhaps?
Anyways, I'm not going through all that partitioning and flashing again just now. I will though, eventually do a Nandroid backup and try again, once I see here or elsewhere that something might have changed for me. I have spent just too much time on this, and data is more important in this case than KitKat.

Thiago Delatorre said:
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
Click to expand...
Click to collapse
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app

webeougher said:
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Not stupid at all, it could make all the difference!
I flashed the MZ605 Brazilian, MZ601 International and the one you linked. The formers booted and asked for the SIM card and the last just didn't boot. I put two different SIM cards and it didn't work, I was wondering it there were a way to circumvent the first check. I also read somewhere that the MZ601/MZ605 US Retail version didn't check for a SIM card on the first boot, but I didn't find an official stock rom for such a device (I don't even know if these devices exist).
The next trial would be with the MZ600 Verizon 3G, but I'm not that confident that it is gonna work...
Another problem is that I stopped using the 3G data on Xoom for more than one year, so I can't even tell if the SIM card would be recognized nowadays...
Beside that, what choices do we have? Is it possible to avoid the first boot SIM card verification? Is it possible to extract the baseband files from another MZ605 and put them in mine?
Do you know what kind of file/library is the baseband?
Another thing, how the modem stays working if we completely clean the internal storage of Xoom going from the official to the CM11 (on your procedure)? What I'm missing...?
Thank you very much for your guide, I didn't know how to revert the bigPart
Regards,
Thiago

So @webeougher ...I FINALLY had some time to sit down with my Xoom and try this. In the interest of verifying that this process works, I went through your guide step by step without deviation and... SUCCESS! I'm back to BigPart CM11 w/ full 4G LTE!!! Thanks for taking the time to write out such a detailed guide! It was just about perfect.
I have just two things to mention... First, the link to the stock image HRI66 didn't work. I had to look elsewhere (http://rootzwiki.com/topic/1586-stock-images/). Also, in step one of stage 4, the adb command should be "adb reboot recovery", not "adb reboot bootloader"... correct?
One last thing, at this point should we start recommending people not attempt BigPart / CM11 if they start from stock Jelly Bean?
Again, I can't tell you how stoked I am to be back up and running. This... all of it... BigPart, CM11 for Xoom, and the fix for the no data situation... it's all awesome.

Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!

rmkenney12 said:
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
Click to expand...
Click to collapse
It's not necessary to relock to get OTAs, so long as you're running a pure stock rom.
Sent from my Galaxy Nexus using xda app-developers app

webeougher said:
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
...
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked;
Click to expand...
Click to collapse
There was aleady a problem with Step 4... unable to mont /cache - therefore Failed to wipe /data and /cache.
Step 8 also showed NO /data-partition.
I downloaded the original Xoom stock boot,system,recovery (MZ601) MZ601_H.6.1-38-5_TMO_Germany...
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
Click to expand...
Click to collapse
boot status - done!
system status - done!
recovery status - done!
userdata status | | | | | | | | | | | | | | | | | | | | | | - done! (there have been such weird lines)
formatting cache: CAC status: -done!
Rebooting - after 60 min of M-logo I quit.
Is there a way to TOTALLY MANUALLY repartition the xoom and recover everything from scratch?
EDIT: New development: not even in fastboot mode I'm able to flash anything anymore... CWM recovery (recovery-clockwork-touch-6.0.3.2-everest.img and recovery-Tiamat-R4c-100611-1150-cwm.img) for example: status done! Still TWRP

Thank you and Question
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?

semp3rfi said:
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
Click to expand...
Click to collapse
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app

Thank you
webeougher said:
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Awesome thanks for the reply!

What does this whole sequence actually accomplish? Is the problem that we have the wrong radios installed, and this is a way to get the right ones installed? If so is there a way to extract the new radios so that they can be installed directly?
I am just trying to understand the process, and see if it can be simplified.
Thanks much for coming up with a solution. I will try it soon.

I'm no developer, but my best theory is that these BigPart roms and kernels use proprietary files from ICS. By taking the OTA to JB, something changed. I tried flashing other radio files and nothing worked, so when it was suggested that only people who had taken the OTA were losing data, I went through this process just on a whim to see if it worked. When it did, I didn't really think much else about it.
Sent from my HTC6435LVW using xda app-developers app

thx
The for this topic really informative

Wow
Talk about a long process but it worked for me! Thank you so very much!
I did have an issue with the google keyboard fc on me after going through the whole process but I ended up downloading the go keyboard (not selecting it) and for some reason that took care of the Google keyboard fcing.
I also used the omnirom instead of cm.
Again, thanks for your hard work!

Wanted to thank you. I pulled out the ole Xoom and flashed Omni and the data wasn't working... But you're instructions got me back on track. Thanks again bro! :good:

[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

Asus Padfone 2 - softbrick after SKU change + Fix

Hi Guys,
Just thought I'd provide a warning and a fix to a half day ordeal recovering from a soft-brick after wanting to make the switch from TW to WWE.
What made this all go wrong?
I have a Padfone 2 which had the latest TW_A68-10.4.17.15
I have a accidentally turned off adb USB debugging mode
The process:
I unlocked my bootloader using the ASUS official unlocker.
I had then install 2.7.0.1 twrp which didn’t work
Install 2.5.0.0 twrp which did.
Forgot to do a backup which I usually did, but guess I thought that I have done this so many times, nothing would go wrong.
DON’T GET COCKY BACKUP FIRST.
Opted for the easy way out and write to system VIA twrp using zip, which was reported to work.
This installed and didn’t report any error.
After reboot, app.phone and another OS programs crashed constantly and rebooted.
I removed my sim and this stopped the crashed apps, but not the reboots.
I realised I was in a whole world of trouble and it was only at this moment did I realise that I didn’t have USB Debugging turned on. Frantically tried to enable it in between reboots, but failed and was now presented with only a ASUS spinning circle of death, or even better later, only the which ASUS logo before it reached it.
All I had available was fastboot and twrp.
You’d think this was an easy fix, but I didn’t have a usable/original rom on the /data/media a.k.a /sdcard partition.
Note: have a handful of roms including your original rom saved on the phone before trying anything, as this phone has no access to external storage when all goes pear shaped.
I wiped caches, didn’t work.
I then wiped data, which then deleted the only rom I had access to. So I couldn’t even now retry installing from zip.
ADB didn’t work from any recovery including CWM 6.0.4.4
I was at a loss and didn’t know what to do.
The recovery:
Installed twrp 2.6.3.0 was persistent with ADB sideload, even though I didn’t have USB Debugging enabled.
Note: ADB sideload will still work even if you don’t have USB Debugging enabled. It’ll either take a min or two to register on your computer, but if not reboot and reboot again to get it to register.
Sideloaded the wrong firmware file again.
Note: If you are trying to sideload the original firmware, extract the zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip” and sideload the zip hiding within “ASUS” -> “Update” -> “TW_A68-10.4.17.15-0-ota-user.zip”
After another long time trying to get the ADB device to register, finally got a second chance and got back to the original firmware.
Did this deter me from the switch from TW to WWE. HELL NO!!
Enable ADB USB Debugging
Make sure you push the rom WWE to your /sdcard partition
How to do it right.
Load the original recovery attached recovery.stock.img
Reboot into recovery and select "apply update from external storage" and choose the zip file to flash.
This will fail! It's what it's meant to do
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
Upon rebooting to ADB stopped working under the stock recovery. It registered with my computer but the command to repush the WWE rom to /data/media kept failing.
Rebooted into fastboot and install twrp 2.6.3.0. At this stage as I knew that the partition table had been updated, I sideloaded the WWE rom, which works more reliably when it's originally enabled
Did a Wiped cache for safe measure
Reboot and welcome to another 2GBs of space and WWE firmware.
NOTE: Always flash the inner zip “TW_A68-10.4.17.15-0-ota-user.zip” not the outer zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip”

freak4916 said:
Load the original recovery attached recovery.stock.img
Click to expand...
Click to collapse
Where can I find this?

[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?