Database Info

[Q] Semi-bricked tf300t

I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)

same thing just happened to me. Im going to download another version of CM and try that. It might just be that.

DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...

http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.

OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2

Glad you got it!

nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.

DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?

1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.

nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.

This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.

I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.

[Q] REQ Complete Guide to installing CM10.1 Nightlies on TF300T

Hi All,
I am looking for a complete guide (or links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information that's dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!

snoopspecial said:
Hi All,
I am looking for a complete guide (on links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information thats dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!
Click to expand...
Click to collapse
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.

snoopspecial said:
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.
Click to expand...
Click to collapse
To be honest, the lag is still there accross all the 4.2 roms I tried, even debloated. Its not as bad but its still there. My alternate device has a beastly exynos in it so im used to a perfect smooth experience. I notice even a little bit of jitter and it drives me crazy ( hence why I downgraded to 4.1 ) .
As far as what bootloader to use for which CM rom, each will tell you which to use specifically. I saw there is a cm10.1 for 4.2 and for 4.1. Just make sure to match things.
I used to be a CWM user all the way, but twrp does trump it in features and usability, especially for the transformer series. I beleive there is only one single twrp that works properly on the new bootloader for stock based roms ( no cwm will work on it at all). It ends in .42 so make sure you flash the correct one. If not, your partitions wont be writable.
One MAJOR warning.........
Do NOT use the wipe / factory reset on ANY bootloader. You will brick your tablet!!! Permanently!!!!
You can ONLY use the wipes inside of twrp / CWM.
Sent from my SGH-T889 using xda app-developers app

dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.

pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
okay - lots of options in TWRP - going the simple safe route and just following the norm:
http://teamw.in/whattowipe

snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
Im assuming you are flashing CM10 then? The only important thing is fully read the OP and match your bootloader to whatever one they tell you. Its generally not a suggestion, but an actual requirement.
Mines a 32gb so I keep all of my backups and rom flashes right on the internal storage. I feel its safer in case of SD corruption or an accidental wipe. It doesnt hurt to have it in 2 places though ( backup your original rom to SD card but keep everything on the internal as well ). I always flash from internal ( roms and nandroids alike ). Ive never had an issue.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.

snoopspecial said:
so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.
Click to expand...
Click to collapse
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.

snoopspecial said:
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.
Click to expand...
Click to collapse
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.

snoopspecial said:
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.
Click to expand...
Click to collapse
yeah so that worked fine. the CM10.1 version must require some different combination.

taking your suggestions now and downgrading to the 4.1 bootloader. will also install the CleanInheritance rom.
by the way, thanks again for your help and suggestions!

So just for other people out there... if you want to run the TF300T downloads from get.cm (the nightlies as of now).
I've confirmed the following requirements:
1. 10.4.2.20 - TWRP 2.5.0.0 - JB
2. CM 10.1 5/25/2013 Nighty (This is a 4.2.2 ROM - requiring the JB, not 4.2 bootloader - i imagine at some point this will be updated)
3. GAPPS 20130301-signed
ah so nice!

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

[Q] Upgrading from 4.1?

My TF700 is bogged down pretty hard and randomly freezing/rebooting so time to upgrade from Cleanrom 3.4.1 (JB 4.1) to whatever is out there now. It has been a few years since messing with roming and don't want to screw anything up. I also did some searching but didn't find anything on this specifically.
I see twrp is the way to go now for recovery but I am running cwm 6.4.x I think? I forgot since rebooting and looking. Anyways, I can just use adb per the instructions and re-flash twrp over the cwm then flash a KK rom right? I just want to make sure because my GS3 has to be reverted then something changed then re-updated...something crazy to not brick it and I obviously don't want to happen.

First of all you need to determine what your botloader version is. It's probably outdated if you've been on a CleanROM. You need to have the 10.6.1.14.10 bootloader if you want to flash a KK rom.
The easiest way to uograde your BL is to grab the BL/TWRP package from the OP of the CROMi-X thread in Development and flash it in your current recovery.
Reboot to let it install, then boot to recovery and check the version number. I forgot what TWRP version sbdags packaged in that file. If it is TWRP 2.6.0.1 go to the Teamwin website, downlaod TWRP 2.8.0.1 and flash it in fastboot.
Then you need to do a full factory wipe in TWRP (default under the Wipe command) and then you can flash the KK rom.
For general instructions read this:
http://forum.xda-developers.com/showthread.php?t=2688891

A little confused. It sounds from your message that I can flash the new recovery? The thread you sent me to said to flash in fastboot. I only ask because I don't have a windows box handy and am lazy.
Thanks for the help!
edit* - refamiliarizing myself with the terminology and starting to get it again.

Fastboot was kind of a pain to get working but once it had connection and I learned how to use it, worked like a charm. Thanks a ton!
Have CM11 working on my tab now. It has been in pretty desperate need for some time now.

lowriderdog37 said:
Fastboot was kind of a pain to get working but once it had connection and I learned how to use it, worked like a charm. Thanks a ton!
Have CM11 working on my tab now. It has been in pretty desperate need for some time now.
Click to expand...
Click to collapse
If you're in the mood for it, nandroid CM11 and try ZOMBi-X. I love it!

[Q] stuck in bootloop while installing elementalx.help!!!

i was installing elementalx on my nexus 5 via cwm. after going through the installer it asked if i wanted to fix root as i would lose it otherwise. i clicked yes. after that it started rebooting but got stuck on google. then went black. then again it showed google and is still looping. please help!!!

Try clearing cache by going to recovery.... Else my man you might need to flash stock again .....
To shutdown the phone press volume down and power till the time you get 3 vibrations

Dirty flash the ROM your on. What ROM did you flash EX on top of?

1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).

BirchBarlow said:
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.

theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
It was the other way round for me.... Twrp gave me issues .... I always use cwm touch .... Works good for me

i was on stock
BirchBarlow said:
1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
i am on stock so will i have to install the 5.0.1 factory image. also once in a while green screen comes asking whether to reboot or go into dload mode. also do i flash twrp before the factory image. can you tell me how this is done via pc as i was using flashify.

thanks guys
thanks guys it worked. i flashed stock and its working perfectly. thanks.

theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.

1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)

BirchBarlow said:
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.
Click to expand...
Click to collapse
Lethargy said:
1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)
Click to expand...
Click to collapse
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.

theesotericone said:
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.
Click to expand...
Click to collapse
Hey, what works for you, works (until it breaks, of course).
But for newer users, TWRP is now recommended as it's more friendly, as well as being up-to-date. CWM has had it's time.