Greetings. Today I wanted to try a KitKat rom on my TF300T (currently on PacMan Rom 4.3), but as I've figured out, I needed a new version of recovery, since I was using TWRP 2.4.4.0.
So I flashed it (version for 4.2 Bootloader, of course), but even though I've tried nearly all versions higher than 2.4.4.0 (for ex. 2.5.0.0 or 2.6.1.0), I was still getting this weird screen (not my picture, but the same problem) and the only way, how to solve it, is to go back on my default TWRP version - 2.4.4.0.
Any help is much appreciated!
spenat said:
Greetings. Today I wanted to try a KitKat rom on my TF300T (currently on PacMan Rom 4.3), but as I've figured out, I needed a new version of recovery, since I was using TWRP 2.4.4.0.
So I flashed it (version for 4.2 Bootloader, of course), but even though I've tried nearly all versions higher than 2.4.4.0 (for ex. 2.5.0.0 or 2.6.1.0), I was still getting this weird screen (not my picture, but the same problem) and the only way, how to solve it, is to go back on my default TWRP version - 2.4.4.0.
Any help is much appreciated!
Click to expand...
Click to collapse
Which stock rom were you on, 10.x.x.x.x.x?
Hello and thanks for quick reply! My stock rom was 10.6.1.8.
Anyway, some really weird thing happened - I downloaded TWRP 2.6.1.0 (again, version 4.2BL), flashed it, went to recovery but whoa - It installed CWM 6.0.4.5...? How is that even possible? And yes, the blob was downloaded from the official TWRP site.
Anyway, with this new "TWRP" (aka. CWM ) I was able to install this KitKat rom, but still I would like to know the solution for the TWRP problem.
But still, truth is, that my stock rom is very old, going to update it then - Thanks!
EDIT: Ah, now I see it, my bad Just found this:
If current bootloader = 10.6.1.8 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.4.4.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device. Also flashing 2.5.0.0-tf300t-4.2 on the 10.6.1.8 bootloader results in a split-screen issue.
Click to expand...
Click to collapse
Yes, update to 10.6.1.27 to use the TWRP.
Sent from my TF300T using xda app-developers app
Related
Hello everyone,
My problem is this: I wanted to install a CM10 nightly on the device, so I root using the DebugfsRoot method, install rom manager, flash a recovery, try to install a ROM and it did not work. Rebooting into recovery got me the red triangle, but using the volume buttons allowed me to get in (only it did not have the option to install updates or anything. I think it was just he mounting and partition options)
Since I did not unlock the device before doing this, I chose to do so using ASUS's unlock utility. Once done, I tried booting into recovery, but the device would be stuck at "booting recovery kernel image" and won't budge. I tried flashing different version of CW but it did not seem to work.
Finally, for some reason, I chose the "wipe data" option from the bootloader and the device was stuck, again, at "booting recovery kernel image", only this time I can't boot into a ROM nor can I boot back into bootloader.
What happens when I boot using power and volume down is this:-
The device is Unlocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel image
and then everything's stuck.
Booting normally makes the device stop at "the device is unlocked" message because, I assume, there is no ROM flashed into the device.
Thanks for helping in advance.
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
ShiroiKage said:
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
Click to expand...
Click to collapse
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
buhohitr said:
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
Click to expand...
Click to collapse
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
ShiroiKage said:
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
Click to expand...
Click to collapse
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
okantomi said:
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
Click to expand...
Click to collapse
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
ShiroiKage said:
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
Click to expand...
Click to collapse
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
buhohitr said:
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
Click to expand...
Click to collapse
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
ShiroiKage said:
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
Click to expand...
Click to collapse
You can't install the ASUS firmware through custom recovery. It has to be stock. I believe there are signature checks that prevent it from installing otherwise.
Sent from my ASUS Transformer Pad TF700T
did you unzip the file? should be a zip within a zip. you flash the zip inside
lafester said:
did you unzip the file? should be a zip within a zip. you flash the zip inside
Click to expand...
Click to collapse
You know, I unzipped the file the first time I installed it to get Clean ROM to flash, I had the unzipped folder there yet I managed to forget to use the unzipped file. /InfiniteFacePalm
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
mikaole said:
just fastboot TWRP for ICS and then flash the 1st JB StockRom(dl from Asus and unzip once) in TWRP.
Then fastboot TWRP for JB, then flash the latest JB StockRom(dl from Asus and unzip once) .
Then fastboot TWRP for JB and then the Rom you like
Click to expand...
Click to collapse
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
bsaman said:
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Thanks! So you were going from another set of instructions but ended up just flashed twrp-jb and installed the unzipped zip of Asus JB release via TWRP (I left out the revert to ICS part since I'm already there)? And do you have nvflash installed? No issue running the JB version of TWRP prior to upgrading to JB (had thought bootloader or ... would have an issue with it)? Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
wha2do said:
Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
Click to expand...
Click to collapse
I think you're right... I was on BB6 w/ICS bootloader (NVflashed, though I don't think it matters) and had to roll back to ASUS ICS ROM first, then rooted, then upgraded to ASUS JB ROM, and then it goes blurry. Not sure if I upgraded TWRP or rooted stock JB at this point.
In any case, I followed the "update to JB" thread to a tee, and all went well except for the step regarding the actual JB update.
Sent from my Transformer Pad TF300T using Tapatalk HD
wha2do said:
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
Click to expand...
Click to collapse
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
tobdaryl said:
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
Click to expand...
Click to collapse
Thanks for the info. To add to your one comment (for others that may come across this looking for add'l info), flashing a full stock rom will overwrite any custom recovery previously in place. TWRP (using the appropriate version for your firmware) or CWM will need to be reflashed again...
Checking, it does appear v10.4.2.9 is the first version of JB on the TF300T.
I've come across at least one or more posts/guides that mention ICS v9.4.3.30 should be installed before updating to JB - one being: [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]. I'm wondering if it's because that method updates to JB using the dlpkgfile (not sure what format it is)?
My take is doing the additional flash to v9.4.3.30 first can't hurt anything, but quite possibly unnecessary here? Any other thoughts or words of warnings from anyone? Thanks!
Fellas, this is kind of weird.
I installed CromiXenogenesis over stock 4.2.1, then downgrade to stock 4.1.1 and installed CM 10.1. Then upgrading again to stock 4.2.1 (wich by the way didn´t boot) and installing again CromiX.
Obviously, during those changes, I chaned also the twrp according to 4.2.1 or 4.1.1 as necesary.
The problem is this. After going back to cromix, I installed the twrp for 4.2.1 but the screen it´s split in two halfs horizontally! Yes, showing the same up and down and making almost impossible to navigate (wich I achieved very carefully).
So, the question is: somebody could help to fix this problem with showing the screen split on twrp 2.6.0 for bootloader 4.2.1?
Thanks in advanced. Maybe one of this days take a pic so you can see
Use twrp 2.5.0.0 -4.2!
Sent from my sensational HTC Desire C
noahvt said:
Use twrp 2.5.0.0 -4.2!
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Hey man, the problem has been since I was on twrp 2.5.0.0 for 4.2.1
Now I´m on twrp 2.6.0.0 for 4.2.1 and I´m going to flash 2.5.0.0 and see what happens.
Thanks for the advice :good:
Hello xda-developers,
My TF300T was becoming very slow in the last few months so I decided to reset it to do a "fresh start". While doing so I would also like to upgrade my ROM. (Im currently running Android 4.1 with CleanRom 3.2).
I'm using the CWM Recovery 6.0.1.3 and would like to upgrade to CyanogenMod 10.2 (Stable - the *.zip file from the CM-website)
By reading several threads there seems to be some problems with current Android Versions and older bootloaders. My question is now:
Can I simply flash the new CM-zip with my recovery (After doing the factory reset) - or is there anything else I have to watch out for?
Thanks for your help in advance!
Nijin said:
Hello xda-developers,
My TF300T was becoming very slow in the last few months so I decided to reset it to do a "fresh start". While doing so I would also like to upgrade my ROM. (Im currently running Android 4.1 with CleanRom 3.2).
I'm using the CWM Recovery 6.0.1.3 and would like to upgrade to CyanogenMod 10.2 (Stable - the *.zip file from the CM-website)
By reading several threads there seems to be some problems with current Android Versions and older bootloaders. My question is now:
Can I simply flash the new CM-zip with my recovery (After doing the factory reset) - or is there anything else I have to watch out for?
Thanks for your help in advance!
Click to expand...
Click to collapse
If you are on a 4.1 ROM you probably need to upgrade your bootloader first.
The easiest way is to flash the latest ASUS stock ROM, then do a factory reset and after that flash recovery and your new ROM.
There are several ways to accomplish this, all covered in detail in several threads.
Sent from my TF300T using Tapatalk
Nijin said:
Hello xda-developers,
My TF300T was becoming very slow in the last few months so I decided to reset it to do a "fresh start". While doing so I would also like to upgrade my ROM. (Im currently running Android 4.1 with CleanRom 3.2).
I'm using the CWM Recovery 6.0.1.3 and would like to upgrade to CyanogenMod 10.2 (Stable - the *.zip file from the CM-website)
By reading several threads there seems to be some problems with current Android Versions and older bootloaders. My question is now:
Can I simply flash the new CM-zip with my recovery (After doing the factory reset) - or is there anything else I have to watch out for?
Thanks for your help in advance!
Click to expand...
Click to collapse
f69m said:
If you are on a 4.1 ROM you probably need to upgrade your bootloader first.
The easiest way is to flash the latest ASUS stock ROM, then do a factory reset and after that flash recovery and your new ROM.
There are several ways to accomplish this, all covered in detail in several threads.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
When you upgrade your bootloader, you will need to upgrade your recovery as well to a -42 TWRP if you are flashing CM10.2 or TWRP 2.6.3.1 for KitKat.
f69m said:
If you are on a 4.1 ROM you probably need to upgrade your bootloader first.
The easiest way is to flash the latest ASUS stock ROM, then do a factory reset and after that flash recovery and your new ROM.
There are several ways to accomplish this, all covered in detail in several threads.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
cmendonc2 said:
When you upgrade your bootloader, you will need to upgrade your recovery as well to a -42 TWRP if you are flashing CM10.2 or TWRP 2.6.3.1 for KitKat.
Click to expand...
Click to collapse
Alright, get Asus Stock from their website, install that, then reset and flash recovery (TWRP - what exactly does the "-42" mean?) After that I'm good to install CM.
Okay, I think I understood - thanks!
Nijin said:
Alright, get Asus Stock from their website, install that, then reset and flash recovery (TWRP - what exactly does the "-42" mean?) After that I'm good to install CM.
Click to expand...
Click to collapse
Oops, got the order wrong: first flash recovery, then do the factory reset using recovery. Don't use the wipe option on the bootloader screen.
There are several versions of TWRP, usually named -ics, -jb and -42.
Don't use the -ics or -jb versions with the new bootloader, but use a -42 version for flashing CM 10.
For flashing CM 11 you need yet another variant of TWRP that is not available from the official download site. Check the CM 11 thread for a download link.
Be careful, using the wrong recovery can result in an expensive brick.
Sent from my TF300T using Tapatalk
f69m said:
Oops, got the order wrong: first flash recovery, then do the factory reset using recovery. Don't use the wipe option on the bootloader screen.
There are several versions of TWRP, usually named -ics, -jb and -42.
Don't use the -ics or -jb versions with the new bootloader, but use a -42 version for flashing CM 10.
For flashing CM 11 you need yet another variant of TWRP that is not available from the official download site. Check the CM 11 thread for a download link.
Be careful, using the wrong recovery can result in an expensive brick.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Ah okay - but this leaves another question: Why exactly do I need the Asus ROM when I already have a 4.2 recovery? Shouldn't Cyanogenmod 10.2 take care of the bootloader then?
Thanks for your help!
Nijin said:
Ah okay - but this leaves another question: Why exactly do I need the Asus ROM when I already have a 4.2 recovery? Shouldn't Cyanogenmod 10.2 take care of the bootloader then?
Click to expand...
Click to collapse
No, CM does not include a bootloader. That is only included in the stock ROM.
That bootloader runs early before the CM Linux kernel is loaded.
The "4.2" recovery only means that it works with the updated bootloader ASUS introduced with the Android 4.2 update. Sorry, I know it is confusing. Thank ASUS for giving us all those incompatible bootloader versions.
Sent from my TF300T using Tapatalk
f69m said:
No, CM does not include a bootloader. That is only included in the stock ROM.
That bootloader runs early before the CM Linux kernel is loaded.
The "4.2" recovery only means that it works with the updated bootloader ASUS introduced with the Android 4.2 update. Sorry, I know it is confusing. Thank ASUS for giving us all those incompatible bootloader versions.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Okay, this makes sense (kind of). I think I know everything now - I'l try to update when I get a little free time. Thanks for your help!
Hi,
i'm using the official CM 11 on my XT925 and pretty much installed every new Nightly - never had any serious Problems, not even with Bluetooth (i get no Track in the Display, but at least it works ).
Since the 01.07.2014 Nightly i can't install the Nightlys anymore, because it wants a KK/ Kernel 3.4 compatible Bootloader. First, i flashed the new TWRP 2.7.1.0. Didn't work, very strange Problem (see below). So then i tried the new CWM 6.0.4.9. Also didn't work... same error message as with CWM 6.0.4.4 (which I used until now) - "no KitKat Compatible recovery detected". So I tried philz touch recovery. Also doesn't work.
Now i'm back with the 30.06.2014 Nightly.
Now the strange part: TWRP didn't recognize any touch inputs at all, I had to hard-reboot the phone. Also Philz touch recovery didn't recognize any touch inputs. CWM 6.0.4.4 hat the "Swipe-Touch" thingy, which I used, but it seems that CWM 6.0.4.9 also doesn't recognize any touch inputs! I can't swipe.
So the big questions are: What the hell have I done wrong, that no Recovery is not recognizing any touch inputs anymore?! Flashed it with fastboot, everything looked ok, only got an "ERROR: could not get pipe properties", but it flasehd it and it worked - apart from the touch.
It wouldn't even be such a big "bother" if the new CWM could install the new CM Nightly... Am I really stuck with 30.06.?
greetings,
David
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, to install new nightlies we have to flash the KK OTA first, right?
TYG
pbosio said:
So, to install new nightlies we have to flash the KK OTA first, right?
Click to expand...
Click to collapse
Take a look HERE.
If I were you I'd wait for the official kk bootloader....if you read the previous post the method being used is risky for our model.
Sent from my RAZR HD using XDA Free mobile app