Database Info

[Q] Cannot flash custom rom

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

[Q] Installing new bootloader: brick-risk?!

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.

[Q] Trying to install 4.4

Brand new to this tablet. So I had the stock 4.2.1 software and I wanted to try out the CM11 4.4 rom. I flashed that but recieved a fail on TWRP. I was hoping that flashing CWM would fix it but no dice. I want to go back to stock but I have no access to fastboot and it bootloops into CWM. any help with this?

Ok I have managed to recover the tablet to boot using this tutorial http://forum.xda-developers.com/showthread.php?p=44244313#post44244313 :laugh: Now, how do I install 4.4? Whenever I tried to install it using TWRP 2.6, it always fails on me.

[Q] loading stock firmware without screwing custom recovery

Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!

mertonv said:
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
Click to expand...
Click to collapse
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.

cmendonc2 said:
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
Click to expand...
Click to collapse
Thanks, then guess i only need to flash the kitkat twrp...
Asked the same question about my bootloader at the omni thread to be sure, if they say that it works too, will go ahead and give it a try

[Q] Custom ROMs won't boot

Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?

muqy said:
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
Click to expand...
Click to collapse
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.

chairsz said:
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
Click to expand...
Click to collapse
Hey man, worked a charm thanks!
For users who may have the same problem:
After flashing 4.3 onto the device it did NOT boot.
- However I then went into the bootloader flashed custom recovery, I used cwm.
- Then I went into recovery, used adb to push the rom and gapps onto sdcard
- Full wipe and then installed rom. Then installed gapps
Working fine.
Cheers chairsz :good::good: