Database Info

Please Help - Updated JB bootloader - can't boot

I just bought a new Infinity today to replace my Prime. I never bothered unlocking/rooting/etc the Prime but given I'm starting from scratch thought I'd go that route out of the box on the Infinity.
I've been carefully reading all of the guides, etc and have used the unlock tool, then created the nvflash backup files (which involves a custom bootloader first).
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next? I'm not new to flashing but w/ my Galaxy Nexus things have always gone pretty smoothly.
Thanks in advance.
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
ALSO,
I had not accepted the software update from Asus yet so I was still on ICS. Does that have anything to do w/ my problem? What should I do?

Kidd_Funkadelic said:
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next?
Click to expand...
Click to collapse
Simply boot to recovery and install CROMI.

Kidd_Funkadelic said:
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
Click to expand...
Click to collapse
Are you on Windows? The "$" sign is not used under Windows -- have you tried typing "fastboot -I.... " ?

_that said:
Simply boot to recovery and install CROMI.
Click to expand...
Click to collapse
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Either way I'm stuck at the moment w/out adb and no SD card. I'm running out on my lunch break to pick one up, which should be all I need to get working again. To be safe I'm going to go back to the .30 ICS stock image first. Once I know that worked, I'll take another stab at CROMI.

Kidd_Funkadelic said:
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Click to expand...
Click to collapse
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.

_that said:
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.
Click to expand...
Click to collapse
Gotcha. I didn't realize TWRP supported adb. Anyway I was able to get back up and running w/ my nvflash backups, though I have to say finding info on actually using the backup files took a ton of digging and some trial and error... Now to try again at CROMI!

I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.

SilentOrchestra said:
Flashing cromi or reflashing the same bootloader yields an error message.
Click to expand...
Click to collapse
And now we are supposed to guess what error message you saw?
The next step is to set up an adb connection from a computer to your TWRP. This way you can get more detailed info what went wrong.

SilentOrchestra said:
I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.
Click to expand...
Click to collapse
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?

FordPrefect said:
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?
Click to expand...
Click to collapse
I agree, it seems you never updated to a JB rom. A JB boot loader needs a JB Rom, It seems the JB boot loader wont boot ICS. Just flash Cromi and you should be good.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.4 Odex
Kernal: Hundsbuah V2.0 OC 1.75 GHz
Theme: Timberwolf's Blues & Jazz Theme V1.9

[Q] Root, Custom Roms, Unlock on Asus TF700T

Hello,
i was wondering if someone could answer some questions that i have about android and the asus tf700t.
now i already searched on google and on xda but there are so many informations and i just cant tell which one is the "best" or the right one.
My Asus is unlocked. i got that far and didnt think it would be too hard to root but i see command lines and/or 3 different kinds of software or files that i have to download first or programs like unlockroot etc.
so i was wondering if you could answer me a few questions.
1. do i need to root to put on a custom rom or is it enough that the device is unlocked?
2. what is the easiest and safest way to root?
3. what are 3 good custom roms?
i have android 4.1.1 on my asus and heard that 4.2 is out so i would like to update it but i never had an android device until now so i just want to make sure i m not destroying it after 3 months of use.
Thank you very much
Ben

Custom ROMS are pre rooted, usually, so you best bet would:
1. Update to stock 4.2.1
2. Root using Motochopper
3. Download GooManager(give root rights') from Play Store and Install TWRP by installing open script recovery.
4. Perform a factory reset via TWRP, without wiping Internal storage, or MicroSD card.
5. Install CromiX or CyanogenMod
There are other ROMS out there, but it is advised to install CromiX first because it is stock based and can be flashed over the stock ROM.
Also, make sure you know how to get into the recovery manually, and make sure you check files before flashing to make sure things downloaded properly.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
ROM: CleanRom Xenogenesis 4.4 DeOdex
Kernel: Hundsbuah's V3.0.5 OC Kernel
Theme: Timberwolf's Blues and Jazz Theme

Thank you for the short guide....
but here is the first problem i have....
i dont know how to upgrade to 4.2.1. or if that update is available for my device yet. some pages said it is. some said its not available.
i have no idea where to get it since over the air update is not possible due to the unlock.

ben9000 said:
Thank you for the short guide....
but here is the first problem i have....
i dont know how to upgrade to 4.2.1. or if that update is available for my device yet. some pages said it is. some said its not available.
i have no idea where to get it since over the air update is not possible due to the unlock.
Click to expand...
Click to collapse
Asus pulled the JB 4.2.1 firmware off their website, probably because they realized it had too many bugs. They probably are working on a new release and I would wait for it.
In the meantime read the forums and familiarize yourself with the process of rooting, installing a custom recovery and flashing custom roms.
If you don't want to wait, search for the forums on the Motochopper tool. I believe you can also use it to gain root under 4.1, but I'm not 100% sure.
If you have root, download Goo Manager, tap the 3 dots in the upper right and choose: Install open recovery script.
This will install the TWRP 2.5.0 custom recovery.
Boot into TWRP and select 'Backup'. This will give you a nandroid backup of your current system. Copy it to a safe place.
Next, you still being on 4.1, you need to flash the JB 4.2 bootloader which is version 10.6.1.14.4. You'll find a link in post 1 of the Cromi Xenogenesis thread in the development section. The dev packaged it with TWRP 2.5. It doesn't hurt to re-install TWRP.
Also download the latest release of the Cromi-X (ODEX) ROM, currently 4.4.1, and place both zips into the root of your internal or external SD card (your choice).
Boot into recovery, choose 'Install', navigate to the 10.6.1.14.4 bootloader/TWRP zip you downloaded and swipe to flash it. After installation the tablet will reboot into your old rom - this is fine.
At this point, just to be safe, you may want to check if you have the correct bootloader installed: Boot up with Vol Down and Power button and read the tiny script. It gives you the bootloader version.
If you're 100% sure you have the correct bootloader and TWRP 2.5.0, proceed:
Boot into TWRP recovery again, select Install, select the CROMIX 4.4.1 zip and flash it.
The Aroma installer will start and give you options to choose from. Stick with most of the default options for the beginning. You can always re-flash the rom with a different set of options selected.
Enjoy!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

[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

Updating Android 4.1

Hey there, guys. I've been around XDA a while & have messed around with different ROMS. I had found one that I liked (decent battery life is the most important for me) & stuck with ParanoidAndroid 3.60 (4.2 based ROM) for Android 4.1 (I believe the firmware version is 10.4.2.20). TWRP is 2.5.0.0. This was around 1-2 years ago, and I finally decided it was time to upgrade it.
Can anyone point me the direction on where to start? I would like to update to the latest (or most stable) android version, if possible. I have a basic knowledge of fastboot & how it works.:fingers-crossed:

First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help

Duchman said:
First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help
Click to expand...
Click to collapse
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!

boxer3310 said:
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!
Click to expand...
Click to collapse
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.

Duchman said:
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.
Click to expand...
Click to collapse
I did everything as you posted:
1. Downloaded the most current firmware for the TF300T from the Asus site.
2. Pushed it to my device using fastboot
3. Installed custom recovery for my version of Android
4. Rebooted.
The Installation bar completed after I pushed the firmware & recovery. It just took long to reboot. I read that you have to let the ROM "stabilize," so I suspect it might have been the cause of the hang. Everything went pretty smooth after the reboot, though. I installed TWRP 2.7.1.0 (as you posted above) and installed a new ROM. Thank you very much for taking the time to reply. I love this update! :victory: