Hi guys I have researched this and did not find any answers. I installed CleanRom Inheritance 3.5- 10.4.4.25US DEODEX and now when I click to display keyboard it appers super zoomed in and when I click any key it activates a different key. Any help would be appreciated. Thanks in advance.
You flashed a really old rom (and no longer supported). What resolution did you flash it with?
Assuming you are on the 10.6.1.14.10 bootloader, I would recommend you flash a compatible recovery (TWRP 2.6.1+) and CROMi-X 5.4 if you want to stay on a JB 4.2 Asus firmware based rom (but do not expect any further updates on it) or you flash TWRP 2.8+ and flash a KK rom like CROMBi-KK or ZOMBi-X which are still supported. Well, kinda. The main dev for these roms has some more urgent stuff to care of right now, so there has not been an update lately...
I would recommend you clean flash CROMi-X 5.4 and take it from there...
Related
I haven't updated in a while (still on 4.0.3)
I have CWM 5.5.0.4(it is running a backup right now)
Should I update to stock 4.2 and then root or is there a way I can use CWM now to update.
Reasons: I hear there is a new boot loader for later versions? How does this affect me?
Sora3087 said:
I haven't updated in a while (still on 4.0.3)
I have CWM 5.5.0.4(it is running a backup right now)
Should I update to stock 4.2 and then root or is there a way I can use CWM now to update.
Reasons: I hear there is a new boot loader for later versions? How does this affect me?
Click to expand...
Click to collapse
First, you should consider making a NVFlash backup first, by reading http://forum.xda-developers.com/showthread.php?t=1894867
Nvflash can make your tablet virtually brickproof.
For custom recovery, I think TWRP works better for TF300T. However, as you've researched, for ASUS 4.2 firmwares, you will need TWRP versions with "-4.2" suffix (i.e., openrecovery-twrp-2.5.0.0-tf300t-4.2.blob), since ASUS updated the bootloader.
I would recommend reading/following this excellent guide here: http://forum.xda-developers.com/showthread.php?t=2187982 to upgrade your tablet to Android stock 4.2.1.
To gain root for stock Android 4.2.1 rom, use motochopper: http://forum.xda-developers.com/showthread.php?t=2228613
By the way, if you want to try Cyanogenmod (CM10.1, which is based on Android 4.2.2), DO NOT update to ASUS Android 4.2. Just update to ASUS Android 4.1. Currently, CM10.1 and most custom AOSP-based rom will only work with ASUS Android 4.1 bootloader. They won't work with the new bootloaders that came with ASUS firmware 10.6.1.8 and 10.6.1.15.3.
Sora3087 said:
I haven't updated in a while (still on 4.0.3)
I have CWM 5.5.0.4(it is running a backup right now)
Should I update to stock 4.2 and then root or is there a way I can use CWM now to update.
Reasons: I hear there is a new boot loader for later versions? How does this affect me?
Click to expand...
Click to collapse
ImmovableObject said:
First, you should consider making a NVFlash backup first, by reading http://forum.xda-developers.com/showthread.php?t=1894867
Nvflash can make your tablet virtually brickproof.
Click to expand...
Click to collapse
I second this suggestion. I'd also like to add that this suggestion isn't just a suggestion. It's a requirement if you would like to take advantage of NVFlash. NVFlash backups MUST be done before you upgrade to the Jellybean OTA. The NVFlash procedure only works with the ICS bootloader, and there is no way to go back to ICS once you upgrade to Jellybean.
Howdy folks, it appears that I've run into a bit of a hurdle playing with my transformer.
-----------------------------------------
Problem:
Stuck Boot (static "ASUS" logo, with nvidia logo in bottom right and "unlocked" in top left)
-(rebooting into bootloader and recovery is possible)
-----------------------------------------
Background Steps:
1. device got the 4.2.2 OTA from ASUS and is running the 10.6 bootloader
2.performed 4.2 unlock as per ASUS instructions
3.loaded TWRP 2.5 (4.2 version)
4.did a full wipe within TWRP (except SD)
5.installed stable release 10.0.0 =
6. wiped cache and dalvik
7. rebooted
------------------------------------------
I figured this was a problem with the kernel (similar symptoms before on previous devices) so i went into fastboot and loaded the boot.blob from the cm zip. - It had no effect!
I then wiped and tried again with 10.1 (nightly), again updating kernel - It had no effect!
Getting nervous, i flashed a rom based on stock 4.2 (kernel flash was required) -It's working but not what I want to end up with.
-Can you folks help me out?
Any help is appreciated
As far as I know the this [OFFICIAL][4.2.2][TF300T][NIGHTLIES] CyanogenMod 10.1 for TF300T does not work with the 4.2 bootloaders, even though it's 4.2.2 it needs a 4.1 bootloader like 10.4.2.20.
There is an experimental build for the 4.2 bootloaders here [ROM][4.2.2][CyanogenMod 10.1 Unofficial][TF300T(G) with BL 4.2][2013-05-09], if your using twrp 2.5.0.0-4.2 you should have JB 10.6.1.15.3 bootloader as twrp 2.5.0.0-4.2 on JB 10.6.1.8 has a split-screen issue.
As far as I know, the official CM10 and CM10.1 (including nightlies) are still not compatible with the ASUS new 4.2 Boot loader. You have to wait a little while for the official CM10.1 maintainer to catch up.
However, there is an unofficial CM10.1 that can work with your current 4.2 bootloader, look here: http://forum.xda-developers.com/showthread.php?t=2252990
would you recommend downgrading to 4.1 to use the stable release, or should is it safer to just stay with what i got til they decide to make an official cm release that'll work with it?
n00b1c1d3 said:
would you recommend downgrading to 4.1 to use the stable release, or should is it safer to just stay with what i got til they decide to make an official cm release that'll work with it?
Click to expand...
Click to collapse
It is safer to stay. Messing with recovery, fastboot and bootloaders is risky business. Although, it may work, there is also a chance you might brick your tablet when done incorrectly. Not that I doubt your abilities. It's just that we are seeing an alarming rate of bricked TF300T being reported in the forum. Better wait for a much safer version of TWRP recovery.
EDIT: However, if you have NVFlash backup of your tablet, downgrading and bricking won't be much of a problem.
Roger, i'll stay with 4.2, maybe i'll try that experimental 4.2 one.
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Holyman8388 said:
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Click to expand...
Click to collapse
You must be on Jelly Bean 4.2.1
with the Asus Stock bootloader 10.6.1.8 and TWRP Recovery patched 2.4.4.0
or
Bootloader 10.1.15.3 and TWRP patched 2.5.0.0
You will find all versions of Stock firmwares and Stock kernels here
And the TWRP recoveries here
philos64 said:
You must be on Jelly Bean 4.2.1
with the Asus Stock bootloader 10.6.1.8 and TWRP Recovery patched 2.4.4.0
or
Bootloader 10.1.15.3 and TWRP patched 2.5.0.0
You will find all versions of Stock firmwares and Stock kernels here
And the TWRP recoveries here
Click to expand...
Click to collapse
I am currently running the 10.1.15.3 bootloader and TWRP 2.5.0.0, yet it still does not finish flashing the ROM. I even tried to flash a more simple stock based ROM, ie. black beans 8. This did not work either. It went through the twrp flash and restarted but when it got to the ASUS boot up screen it simply stopped. I waited about 10 minutes for it to possibly load however it never did. So I am restored back to my stock and am awaiting any further help.
Holyman8388 said:
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Click to expand...
Click to collapse
In the OP for PACman rom it says you must be on android 4.1.1 to flash his rom. You need to pick a rom for your 4.2.1. I am also on 4.2.1 and run CROMI 4.6.6 with no issues. Have also succesfully tried the Energy rom. Read carefully the OP for the rom's you are considering and make sure they are for 4.2.1
Holyman8388 said:
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Click to expand...
Click to collapse
I am having the same problem! I am running 4.2.1 and im trying to install blackbean 8 using twrp 2.5.0.0. I factory reset in twrp and wipe cache and dalvic. I then install the the rom and reboot but it will not go past the first boot screen with the tegra logo in the bottom right. It always flashes for a second but then does nothing. I have even tried cm 10.1 and it does the exact same thing. I am still able to restore back to stock. This is my first time flashing a rom so any help would be appreciated!
For the latest [ROM][4.2.2][ OFFICIAL] PAC-man v23.0.0 [OC up to 1.7GHz][New Update 22/06/2013], if you read the installation process, you need to be 4.1.1 and not 4.2.1 and also you need installed custom recovery for JB 4.1 BL !
For the latest [ROM]ASU-JellyBean-Hydro 8 (6/29/13)Liquid Butter..- Tf300 -Official 10.6.1.15.3 Base, you need to be on 4.2.1 and 10.6.15.3 bootloader
and you will see to the changelog:
...not sure if any bootloader will work...
Click to expand...
Click to collapse
Hope it's helpful for you
My device:
- TF300
- Android 4.2.2. / CM10.1 (10.1-20130621-nightly-tf300t)
- WW_epad-10.4.2.9-20120809 (= 4.1 bootloader version)
- TWRP 2.6 recovery (for bootloader v4.1)
My aim is to update to CM10.2, therefore I need a bootloader version 4.2. I downloaded the latest firmware from the asus-website (TF300T-WW_epad-10_6_1_27_5-UpdateLauncher.zip) and put it on /sdcard.
But I'm in doubt:
- Is the asus firmwire described above the best way to upgrade my bootloader? And can I use TWRP to install this zip?
- If so, do I need to change the TWRP version to 2.6 ready for -4.2 (teamw.in/project/twrp2/97) not at all, before or after I installed the new bootloader?
I know bootloader/recovery issues can easily brick a TF300, so to be sure I ask. Thanks in advance!
Found this thread:
Quote:
Originally Posted by Nschneider7 View Post
Nope missed that and was just reading about it. Can I just flash the "TF300T-US_epad-10_6_1_27_1-UpdateLauncher" zip in TWRP? Then from there flash the new TWRP and then install CM? Or do I have to go back and let it upgrade to that point?
I flashed the blob via fastboot. Then flashed recovery via fast boot. Then cm10.2 from recovery. I was on old June build of 10.1 and 4.1 bootloader same as you. Be safe fastboot flash follow guide in q and a section
Sent from inside my mkv.
Same question, but not exactly answered: can you do this without a cable connection with your pc?
X10i/3011 said:
Found this thread:
Quote:
Originally Posted by Nschneider7 View Post
Nope missed that and was just reading about it. Can I just flash the "TF300T-US_epad-10_6_1_27_1-UpdateLauncher" zip in TWRP? Then from there flash the new TWRP and then install CM? Or do I have to go back and let it upgrade to that point?
I flashed the blob via fastboot. Then flashed recovery via fast boot. Then cm10.2 from recovery. I was on old June build of 10.1 and 4.1 bootloader same as you. Be safe fastboot flash follow guide in q and a section
Sent from inside my mkv.
Same question, but not exactly answered: can you do this without a cable connection with your pc?
Click to expand...
Click to collapse
Honestly, I'd rather be safe than sorry when upgrading bootloaders. So I would always suggest using the cable connection because it is less likely to fail. You probably could get away without using it to flash stock, but you wouldn't be able to flash TWRP without fastboot, and then couldn't flash a custom ROM. But everything feels safer once you have Nvflash backups.
X10i/3011 said:
My device:
- TF300
- Android 4.2.2. / CM10.1 (10.1-20130621-nightly-tf300t)
- WW_epad-10.4.2.9-20120809 (= 4.1 bootloader version)
- TWRP 2.6 recovery (for bootloader v4.1)
My aim is to update to CM10.2, therefore I need a bootloader version 4.2. I downloaded the latest firmware from the asus-website (TF300T-WW_epad-10_6_1_27_5-UpdateLauncher.zip) and put it on /sdcard.
But I'm in doubt:
- Is the asus firmwire described above the best way to upgrade my bootloader? And can I use TWRP to install this zip?
- If so, do I need to change the TWRP version to 2.6 ready for -4.2 (teamw.in/project/twrp2/97) not at all, before or after I installed the new bootloader?
I know bootloader/recovery issues can easily brick a TF300, so to be sure I ask. Thanks in advance!
Click to expand...
Click to collapse
I was in the same situation as you not so long ago. Was on 4.1.1 with TWRP 2.6.3.0 JB installed. Asked myself these questions repeatedly. I updated via fastboot to the staging partition using the blob within the latested ASUS firmware zip file. The blob file contains, bootloader, recovery, system and boot. This means your are essentially returning to stock everything upon flashing. This was a huge sigh of relief as I didn't want to brick my device because of the same concerns you have. So I flashed via fastboot to 10.6.2.10 then flashed to TWRP 2.5.0 4.2 as 2.6.3.0 didn't work for me for some reason. I heard a number of people say that 2.6.3.0 4.2 is buggy and suggested to stay with 2.5.0 in which I would recommend from experience. Then flash your custom firmware.
Pretty lost by now. I am still (sick of it) on an unlocked Asus stock 4.2.1 with TWRP 2.5. My intention is to change the ROM but was considering CM 11 which I understand does require TWRP 2.6.X at least. I was hoping for a fix for installing navflash on post JB but I believe does not possible so anything that means touching the bootloader makes me very concern.
I was wondering:
- Can I flash TWRP 2.6 (4.2 img file i beleive) directly from my already installes TWRP 2.5 bootloader and then install CM 11? or do I need fastboot process again?
- Is CM 11 worth on the TF300? I just need some stability and reasonable speed after having so many problems with the stock rom.
Thanks.
luison said:
Pretty lost by now. I am still (sick of it) on an unlocked Asus stock 4.2.1 with TWRP 2.5. My intention is to change the ROM but was considering CM 11 which I understand does require TWRP 2.6.X at least. I was hoping for a fix for installing navflash on post JB but I believe does not possible so anything that means touching the bootloader makes me very concern.
I was wondering:
- Can I flash TWRP 2.6 (4.2 img file i beleive) directly from my already installes TWRP 2.5 bootloader and then install CM 11? or do I need fastboot process again?
- Is CM 11 worth on the TF300? I just need some stability and reasonable speed after having so many problems with the stock rom.
Thanks.
Click to expand...
Click to collapse
Yes, CM11 requires TWRP 2.6.3.1.
You can install NvFlash on a JellyBean Bootloader, link and guide is in my signature.
If you bootloader is above 10.6.1.8, you can just flash the TWRP 2.6.3.1 and then reboot and then flash CM11 + gapps.
I think it is super smooth with the OC Kernel.
My TF300T still has the old stock firmware from October 2012 (4.1).
It is unlocked and has TWRP from february 2013.
Now I will be jumping to a current custom firmware (Crombi-kk 4.4).
If I understand correctly, I have to flash the latest STOCK firmware (V10.6.1.27.5 android 4.2) and install the new CWM/TWRP before I can flash a custom firmware.
My main worry is flashing the newest stock rom on my already TWRP/rooted/unlocked TF300T. Will that cause a problem or will the stock firmware wipe everything clean (except for the unlock)?
Also, the unlock utility on Asus's website is made for 4.2 only. When I unlocked my TF300T, it was 4.1. What will happen when I flash the stock 4.2? Will my 4.1 unlock cause problems or will it be wiped, or will it still be effective?
alkizmo said:
My TF300T still has the old stock firmware from October 2012 (4.1).
It is unlocked and has TWRP from february 2013.
Now I will be jumping to a current custom firmware (Crombi-kk 4.4).
If I understand correctly, I have to flash the latest STOCK firmware (V10.6.1.27.5 android 4.2) and install the new CWM/TWRP before I can flash a custom firmware.
My main worry is flashing the newest stock rom on my already TWRP/rooted/unlocked TF300T. Will that cause a problem or will the stock firmware wipe everything clean (except for the unlock)?
Also, the unlock utility on Asus's website is made for 4.2 only. When I unlocked my TF300T, it was 4.1. What will happen when I flash the stock 4.2? Will my 4.1 unlock cause problems or will it be wiped, or will it still be effective?
Click to expand...
Click to collapse
If you would like help with this shoot me an email here [email protected]
We can get you where you need to be and than we can post what we did back here so everyone can see what we did...
Thx Josh
Thanks for your offer. I actually got the green light on the CM 4.4.x Q&A thread.
I read that flashing the CWM for 4.1 would brick your tablet if you had 4.2 installed, so I was worried that flashing 4.2 on top of an existing 4.1 CWM would brick it as well. It turns out it simply removes the CWM entirely. Good times.
Basically what I ended up doing was:
1 - Transfer the latest official TF300T firmware (zip file) onto an SD card.
2 - Start my TF300T with my old (4.1) CWM recovery and select to flash my android with the zip file on the SD card.
3 - The TF300T bootloader stayed unlocked, but the old CWM was gone.
4 - Using ADB: Upload & flash the new CWM Philz Touch
5 - Install/flash the desired custom rom (from within CWM using SD card)
6 - Restore to factory default (from within CWM)
Now I even installed Grimlock's kernel to allow overclocking.
My TF300T has a new life. It is now very much acceptable in terms of speed.