Database Info

[Q] Why can't I install a kernel?

I can't install *any* kernel. I've rooted from 8.4.4.11 with the Pure.Root batch file, which works perfectly. I've tried using CWM to install several Clemsyn kernels, STOCK kernel (?!), and even pulled a blob out of one of Clemsyn's packs and turned it into a '.img', which I then nvflashed. NOTHING works.
I get the blue bar across the screen, the quick reboot, then the "Eee Pad" screen forever. It won't power off from the power button (immediately powers back up to "Eee Pad" screen); I have to go into CWM and power down from there. The only recovery options are 1) re-do the 'boot.img' from Pure.Root or 2) start over with the full recover to 8.4.4.5 from Tabletroms, both of which work without incident. I've even done a data wipe (volume down), and tried doing a cold boot (volume down, then volume up at the prompt)
Maybe I'm asking too much, but I'd *really* like a rooted tab with OC kernel, running on stock ROM. Is this simply not possible? (*shrug* works on my Nook Color...)
-B60* unit, perfect working order
-8.4.4.11, "manual" install (never picked up the OTA)
-this -> Pure.Root works perfectly, except CWM (noted below)
-cwm-solarnz-8.4.4.11.img (had to replace 'recovery.img' in Pure.Root; no other method would allow entry into recovery mode)
-wiped cache/cleared Dalvik EVERY TIME

did you try kernel manager from the market?
Sent from my Transformer TF101 using Tapatalk

didn't think it was working with the xformer yet...
--edit--
Ah, gomen, it was Rom Manager I was thinking of... Regardless, it (Kernel Manager) didn't work either.

Stupid question, but in CWM you did the following ?
-Install zip from SDcard
-Select zip
-pick the kernel zip
-go back
-reboot (CWM option)

bud77 said:
Stupid question, but in CWM you did the following ?
-Install zip from SDcard
-Select zip
-pick the kernel zip
-go back
-reboot (CWM option)
Click to expand...
Click to collapse
Yes

Then I would suggest a reinstall via NVFlash, and retry kernel installation
You might have screwed at some point, which makes you stuck now

bud77 said:
Then I would suggest a reinstall via NVFlash, and retry kernel installation
You might have screwed at some point, which makes you stuck now
Click to expand...
Click to collapse
I think you might've misunderstood; I'm not currently "stuck", - I can recover any time I want, I'm just limited to the rooted kernel from Pure.Root. No other kernel will boot (well, except for stock, of course)

Ah, my bad, I kinda misunderstood
I trhink there might be some limitation with pure.(stock.)root
Have you tried a "real" ROM then change kernel ?

bud77 said:
Ah, my bad, I kinda misunderstood
I trhink there might be some limitation with pure.(stock.)root
Click to expand...
Click to collapse
That's my working theory as well...
bud77 said:
Have you tried a "real" ROM then change kernel ?
Click to expand...
Click to collapse
I've been hesitant to, particularly with 3.2 coming soon out now
There's also the question of which one... There's a lot to choose from.
Depending on what 3.2 offers, I may upgrade and wait for a new rootkit before I do anything else.
Thanks for the replies!

Well, I'm a Prime user, so I can only guide you to it (Roach does a great job & support on it)
Closest to the stock ROM, with nice optimization
But the best rom for one person, might not be for another
Best is to try, and find which suits you best ^^

[Q] ClockworkMod Recovery, ROM Manager, and Nandroid confusion

So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!

bobblack said:
So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!
Click to expand...
Click to collapse
Forget about Rom Manager. You have the correct recovery installed and you have made a "nandroid" backup when you used the backup option in CWM recovery 3.2.0.0 R4c. The Rom you want to flash needs to be on your MicroSD card and that needs to be in your Xoom when you boot into recovery. It is from the CWM recovery menu that you will choose to flash the zip file that will install the Rom. You will need to be able to boot into recovery and you can do it by pressing volume up and power to get to dual core screen, then after 3 seconds, press volume down then volume up and you should be in recovery. Or you could download Quick Boot from the market and use its boot into recovery option (that's what I do).
About the version you need to be on to flash Hammerhead...what does it say? I think you may need to be on 3.1 but just read the OP on the Hammerhead thread...it will tell you the requirements.
Good luck!

Thanks a lot for explaining that okantomi, that's very helpful and reassuring!
The only thing I'm left with now is to figure out the version part... the rom OP doesn't say anything about a required version. Here's the thread btw: http://forum.xda-developers.com/showthread.php?t=1203635
I made my way through the first 18 or so pages of the 434 total pages in that thread, but still couldn't find any info on that. I'll keep looking - not giving up

Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?

bobblack said:
Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?
Click to expand...
Click to collapse
Me too! ;^ )
Enjoy your shiny new Rom!

[HOW-TO] Return to stock rooted ICS US 9.2.1.21 from custom rom (One Stop Shop)

I decided to return to stock today so i could check out the newest ota which was not implemented in my fav rom yet. I soon realized its a pain in the ass to get there. Flash rom, update, update, etc, etc. And even worse is tracking down all the threads required for it.
Though I've narrowed it down to three or four, I thought i'd make a thread to put it all in one spot.
First off thanks to the members/devs that make these updates and roms for us. I dev on the HTC eVO 4g and know how time consuming and tedious it can be.
I am renaming and reuploading all the files required to ensure links stay current and are easy to follow. I will however be linking to all original threads where i got the files as well as giving props to the members who provided them.
I have a US version TF101 and will only be testing on that device. I dont know what works on tf101G, WW, TW models etc
I will update this thread as new rooted ota's come out.
ALL YOU NEED TO INSTALL IS A ALREADY ROOTED ASUS TRANSFORMER WITH A CUSTOM RECOVERY
THIS WILL NOT ROOT YOUR DEVICE, UN-ROOT YOUR DEVICE OR CHANGE YOUR CURRENT RECOVERY.
DONT FORGET TO BACK UP ALL YOURS APPS/DATA
FOR US VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
- STEP 3 - FLASH ROOTED OTA 9.2.1.17 AND REBOOT (DOWNLOAD) originally provided HERE by daoist
-STEP 4 - FLASH ROOTED OTA 9.2.1.21 AND REBOOT (DOWNLOAD) originally provided HERE by gee one

FOR WW VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
CANT FIND ROOTED VERSIONS OF THE NEXT FEW UPDATES THAT DONT REQUIRE ROOT KEEPER, SO IM STOPPING HERE. THIS WILL GET YOU STARTED THOUGH. i JUST DONT WANT TO BE RESPONSIBLE FOR NEWBS THAT CANT READ LOSING ROOT.
FAQ
-Will this root my transformer = no
-Will I lose root if i flash this = NO
-Can i flash this on top of a custom rom = NO
-Will this replace the custom recovery with the stock recovery? = NO, this will not touch your current recovery
-OMG, I lost root after this = NO you didnt or you did something wrong.

Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?

locutus7o9 said:
Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?
Click to expand...
Click to collapse
its my understanding that you have to have the last prior ota installed to be able to install the next. The last update may not include everything from the others.

Will this replace the custom recovery with the stock recovery?

xbs said:
Will this replace the custom recovery with the stock recovery?
Click to expand...
Click to collapse
I knew i'd forget one of the typicals in the FAQ..
Answer is no, this will not change/touch your current recovery

I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english

jouix said:
I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english
Click to expand...
Click to collapse
What ROM did you flash? If you flashed the official ROM from Asus you unrooted the TF.
Looks like you have stock recovery now.

Yes I have
My biggest problem is to get out on this sh*t Now

jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
Try this.
Hold Vol down plus power button
When you get the option of COld boot Linux or wipe data,
choose wipe data.

jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
What model do you have? B50, B60, B70?
If you have a B50 or B60, try this
Once you get back to stock honeycomb, you'll have to root it again.

@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!

I use NVflash way and from modded(rooted/CWM/Overclock) 9.2.1.17 directly flash back to stock clean 9.2.1.17 and it's very quick... and root it agan via Vipermod and flash 9.2.1.21 update zip.. Takes about lest than 30mins..

Thats one way to do it. I just dont wanna re-root etc.
Flash, reboot, flash, reboot, flash, reboot..done Definitly 30 mins or less.

jouix said:
@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!
Click to expand...
Click to collapse
If you can return to honeycomb, then just reroot and then flash any rom you want. Whats the issue?

Simple, clear, straightforward directions - very nice. The file naming is clever also, no "now which file do I flash next?..."

Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)

Try This
JohnMcLane said:
Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1558170
i just used the search bar above, im sure theres more than this one.
You will also need a NVflashable tf101 with this....

I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?

Sumsar94 said:
I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?
Click to expand...
Click to collapse
Same here, its an assert issue, I remember dealing with it when flashing my epic touch and I believe that had to do with the version of CWM that it was being flashed from
can anyone confirm?
EDIT: B40 using roach v5.5.0.4 r2 CWM

[Q] Overwriting CWM with TWRP and replacing 4.1 with 4.2

Hello everyone!
I'm hoping to get a little bit of guidance from the members here regarding my TF300T. Last week I started down the road to unlocking my TF300 and honestly, I am finding it painfully slow to use. I also have a Samsung Note 2 and find it just blazing fast compared to my TF300. I read a little bit online and having tried a "Factory Rest" etc. I found it still lagged at key entry, browsing etc.
I successfully unlocked my TF300 and then installed CWM. I think however, that the guide I was following was a little outdated (?) because when I went looking for a new ROM to install, most posts STRONGLY recommended TWRP. So my first question is:
If I follow the instructions here:
h t t p : / / teamw.in/project/twrp2/97
using, openrecovery-twrp-2.5.0.0-tf300t-JB.blob specifically, will TWRP automatically install over CWM (on the bootloader partition I believe)? My research and gut is telling me "yes", but I'm hesitant to do this without some additional confirmation.
As a side note, my TF300 currently has Android version 4.1.1 installed. Build: WW_epad-10.4.2.20-20121228.
On another note, I tried to update to Android 4.2 by downloading : TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip from the ASUS Website. I extracted the file : WW_epad-user-10.6.1.15.3.zip onto the root of my SDCard, put the card into my TF300. From what I read online, the TF300 was supposed to recognize the file (which it did and I clicked "Install update"). The TF300 rebooted it booted directly into CWM and I received the following error at the bottom of the screen:
E:Invalid command argument
I'm not sure why that error came up, the only thing I can think of is because I have CWM installed?? Can I use CWM to "install zip from sdcard" and would it install Android 4.2? Or if I can successfully install TWRP, can I then use it, to install the 4.2 update? If I do, then would I have to then immediately install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob as I've upgraded to Android 4.2?
Thanks everyone for your help!!!

ACaton said:
Hello everyone!
I'm hoping to get a little bit of guidance from the members here regarding my TF300T. Last week I started down the road to unlocking my TF300 and honestly, I am finding it painfully slow to use. I also have a Samsung Note 2 and find it just blazing fast compared to my TF300. I read a little bit online and having tried a "Factory Rest" etc. I found it still lagged at key entry, browsing etc.
I successfully unlocked my TF300 and then installed CWM. I think however, that the guide I was following was a little outdated (?) because when I went looking for a new ROM to install, most posts STRONGLY recommended TWRP. So my first question is:
If I follow the instructions here:
h t t p : / / teamw.in/project/twrp2/97
using, openrecovery-twrp-2.5.0.0-tf300t-JB.blob specifically, will TWRP automatically install over CWM (on the bootloader partition I believe)? My research and gut is telling me "yes", but I'm hesitant to do this without some additional confirmation.
As a side note, my TF300 currently has Android version 4.1.1 installed. Build: WW_epad-10.4.2.20-20121228.
On another note, I tried to update to Android 4.2 by downloading : TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip from the ASUS Website. I extracted the file : WW_epad-user-10.6.1.15.3.zip onto the root of my SDCard, put the card into my TF300. From what I read online, the TF300 was supposed to recognize the file (which it did and I clicked "Install update"). The TF300 rebooted it booted directly into CWM and I received the following error at the bottom of the screen:
E:Invalid command argument
I'm not sure why that error came up, the only thing I can think of is because I have CWM installed?? Can I use CWM to "install zip from sdcard" and would it install Android 4.2? Or if I can successfully install TWRP, can I then use it, to install the 4.2 update? If I do, then would I have to then immediately install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob as I've upgraded to Android 4.2?
Thanks everyone for your help!!!
Click to expand...
Click to collapse
Flashing official rom will automatically overwrite your recovery. In other words, your custom recovery will be gone. Do it with fastboot commands instead of SD Card. If you upgrade to 4.2 (10.6.xxx), you'd need to flash the 4.2 custom recovery again.
If you have CWM, the device doesn't detect the official rom automatically when you select RCK. Flash 4.1 official without custom recovery if you want that to happen.
Once on 4.2 bootloader, you'd have to use either TWRP or the CMW version in the flatline (NV Flash) img. No other CWM works. CMW Flatline installs custom roms ok, but does not back up well, if at all. Which leaves you with TWRP as the only viable alternative. I'd suggest you create the NVflash files first, then install TWRP 4.2.
After that, you can flash any 4.2 or 4.3 custom roms.

graphdarnell said:
Flashing official rom will automatically overwrite your recovery. In other words, your custom recovery will be gone. Do it with fastboot commands instead of SD Card. If you upgrade to 4.2 (10.6.xxx), you'd need to flash the 4.2 custom recovery again.
If you have CWM, the device doesn't detect the official rom automatically when you select RCK. Flash 4.1 official without custom recovery if you want that to happen.
Once on 4.2 bootloader, you'd have to use either TWRP or the CMW version in the flatline (NV Flash) img. No other CWM works. CMW Flatline installs custom roms ok, but does not back up well, if at all. Which leaves you with TWRP as the only viable alternative. I'd suggest you create the NVflash files first, then install TWRP 4.2.
After that, you can flash any 4.2 or 4.3 custom roms.
Click to expand...
Click to collapse
Ok, so to clarify, if I want to flash the official rom from Asus to upgrade from Android 4.1 to 4.2 then I should use fastboot instead of trying via the SD Card. In the process however, it will overwrite CWM (the custom recovery) correct?
Where would I find the instructions on how to use fastboot to install the official rom? I know it would be from the command line, but what exactly would the command be?
Once I've installed the official Asus 4.2 rom, then I can install TWRP correct?
Thanks

There is a useful script. Actual command is
Code:
fastboot -i 0x0b05 flash staging blob
It will overwrite CWM with stock recovery so You may like to install custom one. But be sure that it suitable for 4.2 bootloader.

Graiden05 said:
There is a useful script. Actual command is
Code:
fastboot -i 0x0b05 flash staging blob
It will overwrite CWM with stock recovery so You may like to install custom one. But be sure that it suitable for 4.2 bootloader.
Click to expand...
Click to collapse
Thanks!!
For my own edification, the command from what I can interpret is:
fastboot - the program
-i 0x0b05 - the USB identification
flash - command to flash (as opposed to say reboot)
staging - this I'm not sure of ... staging because it's a new rom that's going to be installed. Curious why it wouldn't be system, as aren't I installing a new system rom?
blog - the blob file I want flashed.
Correct?

Yes. As I understand this, staging - partition used to store something that going to be flashed. Blob from stock firmware contain data for bootloader, recovery, boot, system partitions. Here full description of fastboot command.

I want to update my android too.
I have twrp installed but I want install official rom.
I'll use fastboot (After read some threads, including this) but I have some doubts:
the blob to use is from WW_epad-user-10.6.2.6.zip with 782MB ?

nbranquinho said:
I want to update my android too.
I have twrp installed but I want install official rom.
I'll use fastboot (After read some threads, including this) but I have some doubts:
the blob to use is from WW_epad-user-10.6.2.6.zip with 782MB ?
Click to expand...
Click to collapse
Hey there. Here is my experience with doing what was mentioned in this thread.
I had CWM installed. I downloaded the official Asus stock ROM and followed the fastboot instructions above. The official ROM over wrote everything. Took about ... maybe 5 minutes total. The new official ROM worked like a charm.
I then reinstalled TWRP. No issues. I used TWRP to install Cromi-X, which is awesome. Also, no problems.
The only thing I found weird, is that I had cleared all cache etc. and I thought I had deleted all my data by doing so, but everything on my "Internal SD Card" was there even after I installed a fresh copy of Cromi-X.
As for what blob you should use (and I'm STILL A NEWB) I'm pretty sure you need to match the blob to the type of tablet you have. If you go into : Settings --> About Tablet --> Kernel version, (pretty sure that's the right spot) you should see something like "WW_epad" or "US_epad".
Over all, this was one of the most simple "tech" processes I've ever experienced.

ACaton said:
Hey there. Here is my experience with doing what was mentioned in this thread.
I had CWM installed. I downloaded the official Asus stock ROM and followed the fastboot instructions above. The official ROM over wrote everything. Took about ... maybe 5 minutes total. The new official ROM worked like a charm.
I then reinstalled TWRP. No issues. I used TWRP to install Cromi-X, which is awesome. Also, no problems.
The only thing I found weird, is that I had cleared all cache etc. and I thought I had deleted all my data by doing so, but everything on my "Internal SD Card" was there even after I installed a fresh copy of Cromi-X.
As for what blob you should use (and I'm STILL A NEWB) I'm pretty sure you need to match the blob to the type of tablet you have. If you go into : Settings --> About Tablet --> Kernel version, (pretty sure that's the right spot) you should see something like "WW_epad" or "US_epad".
Over all, this was one of the most simple "tech" processes I've ever experienced.
Click to expand...
Click to collapse
Thx for the alert, I already have the correct blob for my tablet.
The process work fine and now I have the JB installed on my Tablet!
Thx.

took out the tf101 after about a year or so

hey guys, ill get straight to the point:
i decided to take out my old tf101(non-3g) after after a year or more, dont remember. it works relatively well, but im sure theres a lot that can be updated rom-wise. right now it has this:
Kernel version
2.6.39.4-JELLYBEAN-g18e8917-dirty [email protected] #89 SMP PREEMPT Wed Aug 22 17:40:05 CEST 2012
Build number
full_tf101-userdebug 4.1.1 MASTER eng. RaymanFX.20120821.232608 test-keys
I include this because I'm not exactly sure what version i have.. i think its the 6.0.0 from raymanfx
Anyway, from what I could from a quick glance of these forums, there's a ton of new features for this tablet! or at least one i really like, multi-window.
So can I get some suggestions from you guys on whats the best way to get my tablet up to date? I'm looking for a stable rom also. Is the best way to get to this point to return my tablet to stock and start over from there?
Any useful suggestions are welcomed. Thanks

First thing you should do is make sure you have TWRP recovery installed
Make sure if you have CWM recovery installed that you change over to TWRP before flashing the ROM or you have a good chance of a boot loop
Easiest method, install Goo Manager from here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Open app > Hit the top right 3 dots menu button > choose "Install Open RecoveryScript"
Follow instructions to get TWRP running, boot into TWRP to check it has worked by holding Power & Volume Down from a powered off state until you see the white text at the top of the screen
Then release all buttons and tap volume up to enter recovery
If that works fine, then download a new ROM and Gapps and copy to a Micro SD Card
This is the latest and most stable version that has Multi Window support
http://forum.xda-developers.com/showthread.php?t=2392087
Copy the ROM & Gapps to Micro SD and stick it in the TF
Boot into TWRP
Press the WIPE option and wipe everything apart from External which is where your new ROM is
Go back to the main screen by hitting the home button at the top right
Press the install button
Choose External memory to find your new ROM and Gapps
Install ROM
Install Gapps
Wipe Cache & Dalvik Cache
Press reboot to Reboot into your new 4.3.1 Jellybean ROM with Multi Window
----
If you have problems getting TWRP using Goo Manager, use EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012

roadrunnerx7 said:
Anyway, from what I could from a quick glance of these forums, there's a ton of new features for this tablet! or at least one i really like, multi-window.
Click to expand...
Click to collapse
Because you want Multi-Window, go with the previously mentioned KatKiss 4.3.1 or, if you can wait a few days, go for 4.4.2 v023. Tim's changelog indicates the next version is going to fix it.
4.4.2 really flies, BTW!

*Detection* said:
.
Click to expand...
Click to collapse
Thank you very much for the thorough explanation. When I get a chance I'll get started on updating things. Thanks!!
DoughMucker said:
Because you want Multi-Window, go with the previously mentioned KatKiss 4.3.1 or, if you can wait a few days, go for 4.4.2 v023. Tim's changelog indicates the next version is going to fix it.
4.4.2 really flies, BTW!
Click to expand...
Click to collapse
Thanks for the suggestion. Why is 4.4.2 v023 better though?

roadrunnerx7 said:
Thanks for the suggestion. Why is 4.4.2 v023 better though?
Click to expand...
Click to collapse
Android 4.4 (Kit Kat) runs much better on lower powered/memory devices than previous versions. The possible downside of KatKiss 4.4.2 compared with KatKiss 4.3.1 is that it is relatively new and may have some issues with some apps (i haven't seen any though).

So I followed all the steps and updated my tablet. Installed the 4.4.2 version. It's awesome!!! I never imagined this tablet would still have so much value in it.
Thanks again guy for helping me out!

Great!
Yea the latest 4.4.2 #23 is a superb ROM, best one so far imo & multiwindow is in this one too

I just bought my wife a used TF300T running stock 4.2.1 and, after rooting and using lagfix, it doesn't seem any faster than my TF101 running KatKiss 4.4.2. Maybe I should have bought another TF101 and saved a few bucks.

DoughMucker said:
I just bought my wife a used TF300T running stock 4.2.1 and, after rooting and using lagfix, it doesn't seem any faster than my TF101 running KatKiss 4.4.2. Maybe I should have bought another TF101 and saved a few bucks.
Click to expand...
Click to collapse
Run a few benchmarks like 3DMark and Antutu on each of them

*Detection* said:
Run a few benchmarks like 3DMark and Antutu on each of them
Click to expand...
Click to collapse
I ran Antutu on each...
TF101 (@1400MHz) got 10113. TF300T got 13444. But they feel pretty much the same for the basic stuff my wife and I do with the tablets.

I'm having problems with Netflix.. A lot of times it hang.. Not loading, but the picture. The video will seemingly stop playing and get stuck, but the sound continues and the playback timer continues also. Only the video gets stuck. The only thing that will temp fix it is to close the app and open again, but even then there's a 50/50 chance it will screw up again. And if I move to a specific spot in the video, so that it has to sort of reload it, it will likely get stuck again.
You guys have any problems like this with Netflix? Solutions?
I'm still on v23.. I see there's a v23c now but not sure if that's a newer version?

Instructions for issues are in post 2 of the main ROM thread
http://forum.xda-developers.com/showpost.php?p=49007034&postcount=2
--
Netflix
To get the latest Netflix versions to work you can use this XPosed module:
http://forum.xda-developers.com/showthread.php?t=2101525
You can also use an older version of Netflix ( 2.0..)

roadrunnerx7 said:
I'm still on v23.. I see there's a v23c now but not sure if that's a newer version?
Click to expand...
Click to collapse
23c just adds support for some international keyboards - they're otherwise the same.

*Detection* said:
Instructions for issues are in post 2 of the main ROM thread
http://forum.xda-developers.com/showpost.php?p=49007034&postcount=2
--
Netflix
To get the latest Netflix versions to work you can use this XPosed module:
http://forum.xda-developers.com/showthread.php?t=2101525
You can also use an older version of Netflix ( 2.0..)
Click to expand...
Click to collapse
I did the netflix fix before already. Thats why im not sure what to do to fix it. Havent tried getting an older version. Do you know where i can get an older version of netflix? Also if i do use the older, can i uninstall the Xposed module?
Thanks

*Detection* said:
First thing you should do is make sure you have TWRP recovery installed
Make sure if you have CWM recovery installed that you change over to TWRP before flashing the ROM or you have a good chance of a boot loop
Easiest method, install Goo Manager from here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Open app > Hit the top right 3 dots menu button > choose "Install Open RecoveryScript"
Follow instructions to get TWRP running, boot into TWRP to check it has worked by holding Power & Volume Down from a powered off state until you see the white text at the top of the screen
Then release all buttons and tap volume up to enter recovery
If that works fine, then download a new ROM and Gapps and copy to a Micro SD Card
This is the latest and most stable version that has Multi Window support
http://forum.xda-developers.com/showthread.php?t=2392087
Copy the ROM & Gapps to Micro SD and stick it in the TF
Boot into TWRP
Press the WIPE option and wipe everything apart from External which is where your new ROM is
Go back to the main screen by hitting the home button at the top right
Press the install button
Choose External memory to find your new ROM and Gapps
Install ROM
Install Gapps
Wipe Cache & Dalvik Cache
Press reboot to Reboot into your new 4.3.1 Jellybean ROM with Multi Window
----
If you have problems getting TWRP using Goo Manager, use EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Hi
Sorry to revive an old thread
I am in the same boat. I have a B40 tablet.
I followed the steps up till install ROM.
When I install, it is stuck at "updating partition detail".
I have tried to flash newest twrp without success ( cannot even get into recovery)
I have tried easyflasher to unbrick, flash twrp 2.2.1, flash twrp 2.3.2.3 using GOOmanager, but still stuck at "updating partition detail" when flash katkiss 4.4.2v23c.
I have tried different micro-sd cards and different downloads.
What may have gone wrong?
Thanks

strikeraj said:
Hi
Sorry to revive an old thread
I am in the same boat. I have a B40 tablet.
I followed the steps up till install ROM.
When I install, it is stuck at "updating partition detail".
I have tried to flash newest twrp without success ( cannot even get into recovery)
I have tried easyflasher to unbrick, flash twrp 2.2.1, flash twrp 2.3.2.3 using GOOmanager, but still stuck at "updating partition detail" when flash katkiss 4.4.2v23c.
I have tried different micro-sd cards and different downloads.
What may have gone wrong?
Thanks
Click to expand...
Click to collapse
Does it not flash the ROM first, then stop at "Updating Partition Details" ?
Are you sure it hasn't successfully flashed the ROM?
iirc Updating Partition Details is the last thing it says after flashing

*Detection* said:
Does it not flash the ROM first, then stop at "Updating Partition Details" ?
Are you sure it hasn't successfully flashed the ROM?
iirc Updating Partition Details is the last thing it says after flashing
Click to expand...
Click to collapse
Sadly not.
When I swipe to flash, that is the first and only line that pops up immediately.
If I let it sit at that line for the night, in the morning I see TWRP going back to home screen. But the log still only has that one line.

strikeraj said:
Sadly not.
When I swipe to flash, that is the first and only line that pops up immediately.
If I let it sit at that line for the night, in the morning I see TWRP going back to home screen. But the log still only has that one line.
Click to expand...
Click to collapse
Ok, try NVFLASH'ing the Stock ROM
NVFLASH will delete and re-create all the partitions on the device and then flash you back to 100% factory stock
Once you are up and running with stock, use Easyflasher to flash TWRP recovery again, then try flashing KatKiss ROM again from TWRP
Download > Extract > Plug TF into PC USB > Power off TF and Put TF into APX Mode (Vol Up & Power) > Run download.bat as Administrator
Download
https://mega.co.nz/#!tINBhLob!InI_F2Y6D8rSVZ5sDeCQx2T41c9gp_7Z_7kCqFNDVIs

*Detection* said:
Ok, try NVFLASH'ing the Stock ROM
NVFLASH will delete and re-create all the partitions on the device and then flash you back to 100% factory stock
Once you are up and running with stock, use Easyflasher to flash TWRP recovery again, then try flashing KatKiss ROM again from TWRP
Download > Extract > Plug TF into PC USB > Power off TF and Put TF into APX Mode (Vol Up & Power) > Run download.bat as Administrator
Download
https://mega.co.nz/#!tINBhLob!InI_F2Y6D8rSVZ5sDeCQx2T41c9gp_7Z_7kCqFNDVIs
Click to expand...
Click to collapse
Thanks for your reply.
Just a couple questions
1. I have used easyflasher to flash stock before flashing twrp and katkiss. Is that the same as using NVFLASH? Or should I not wipe everything before flashing katkiss so that the partition is not touched? If so, what should I wipe before flashing?
2. I thought katkiss requires twrp >=2.3.2.3 . Easyflasher flashes a version lower than that. Am I correct to use goomanager under stock rom to update twrp to 2.3.2.3 before flashing katkiss?
3. If I want to try flashing katkiss from internal memory, where should I put the zip file and what should I not wipe before flashing?
Thanks

strikeraj said:
Thanks for your reply.
Just a couple questions
1. I have used easyflasher to flash stock before flashing twrp and katkiss. Is that the same as using NVFLASH? Or should I not wipe everything before flashing katkiss so that the partition is not touched? If so, what should I wipe before flashing?
2. I thought katkiss requires twrp >=2.3.2.3 . Easyflasher flashes a version lower than that. Am I correct to use goomanager under stock rom to update twrp to 2.3.2.3 before flashing katkiss?
3. If I want to try flashing katkiss from internal memory, where should I put the zip file and what should I not wipe before flashing?
Thanks
Click to expand...
Click to collapse
1.) Use NVFLASH to flash stock - Wipe everything in TWRP once you're ready for KatKiss
2.) TWRP that comes with Easyflasher will work, you can upgrade later
3.)Flash KatKiss from MicroSD so you can wipe everything on Internal