OK, I've done this many times to many devices, never had this happen before. Unlocked, rooted, TWRP installed, have tried two different ROMS, Slim and CM11, tried both direct download and from my PC then transferred, can't get a custom ROM to install, keeps erroring out while trying to install ROM from TWRP, even though I wipe System, Dalvik, and Cache. 'Error updating binary executor in zip'
thoughts?
EDIT: on twrp 2.5.0.0 - maybe need a newer version?
Tried 2.6.3.0 - it won't wipe dalvik, cache, or system? Actually, it cant see or mount any drives...
And CM Recovery has the same issue...?
This worked:
http://forum.xda-developers.com/devdb/project/dl/?id=3727
friedsonjm said:
OK, I've done this many times to many devices, never had this happen before. Unlocked, rooted, TWRP installed, have tried two different ROMS, Slim and CM11, tried both direct download and from my PC then transferred, can't get a custom ROM to install, keeps erroring out while trying to install ROM from TWRP, even though I wipe System, Dalvik, and Cache. 'Error updating binary executor in zip'
thoughts?
EDIT: on twrp 2.5.0.0 - maybe need a newer version?
Tried 2.6.3.0 - it won't wipe dalvik, cache, or system? Actually, it cant see or mount any drives...
And CM Recovery has the same issue...?
This worked:
http://forum.xda-developers.com/devdb/project/dl/?id=3727
Click to expand...
Click to collapse
If you are trying to install CM11, which is based on KitKat, looks like everyone says to use the Omni version of TWRP. Here's a link to that zip in my Dropbox. https://www.dropbox.com/s/cctivhx2kcpwnfz/TWRP-TF300T-2_7_0_1.zip. Install is different for it though. Put the zip file on a micro SD card or in the internal storage and then boot into whatever custom recovery you have working (I usually go back to stock and flash TWRP 2.4.0.0 or 2.4.4.0 whenever I run into problems. I found a great TWRP recovery installer someone made for Windows, here's that zip. https://www.dropbox.com/s/jut7sytp8n7c94u/recoverytf300t4.2.zip). Once in recovery, go to Install and flash the Omni version 2.7.0.1. After that finishes, reboot to system so that the Omni version can complete installation (you'll see the blue install bar, like what shows when you Fastboot install a recovery). Your tablet will reboot after that so I usually hold Volume Down when the display goes dark so that I can go into the new recovery. I've also recently found 2 "new" recoveries that work fairly with CM11, probably due to the fact that they are based on CM Recovery. I'll include the links for you. They both get installed via Fastboot. Hope this helps!
Philz Touch Recovery - https://www.dropbox.com/s/eea29g652s34p76/philz_touch_6.19.3-tf300t.img
Flatline Recovery (from the process of Wheelie/NVFlash for Jelly Bean, which I recommend you do if you haven't yet. It's been a life saver.) -https://www.dropbox.com/s/xvn7tg3tt0pxo8s/flatline_tf300.img
Related
Restored the Tablet TF101 back to stock rooted and everything worked. Installed CWM Did factory reset system wipes etc. Tried to install 3 different CM 10 all failed bad installation. Tried to installed the newest TWRP same thing I can't seem to install any rom from the external or internal just keeps saying bad?
What errors did TWRP tell you?
For TWRP why not download the GOO app from the playstore and find the option in the menu to allow it to install the open recovery script for you?
Had similar issues with my S4 with a particular rom but youve tried a few so i doubt its down to the download sites.
You may have to format the emmc and see how that goes as a last resort. (just make sure you have a rom placed on a micro sd as it will completely wipe the TF again but still keep your recovery)
Hi, i have Team EOS rom on my tf101 and it has been working without any problem. But today it stuck on EOS logo when boots. I enter on cwm (version 5.0.2.8) and do a wipe (factory settings / cache / dalvik and format /system) and try to install the EOS rom again but it stucks on "Installing update..." I have tried several times with the same result. I tried KatKiss 4.2.2_225 from sdcard with the same result.
Any help thanks.
anibol said:
Hi, i have Team EOS rom on my tf101 and it has been working without any problem. But today it stuck on EOS logo when boots. I enter on cwm (version 5.0.2.8) and do a wipe (factory settings / cache / dalvik and format /system) and try to install the EOS rom again but it stucks on "Installing update..." I have tried several times with the same result. I tried KatKiss 4.2.2_225 from sdcard with the same result.
Any help thanks.
Click to expand...
Click to collapse
I would HIGHLY recommend updating to TWRP.
If you can flash from the microSD, grab a flashable zip file like 2.6.1.0 from this thread: http://forum.xda-developers.com/showthread.php?t=2434422
If not, you can push the TWRP zip file to the /sdcard/ using adb and flash that.
A last option is to use EasyFlasher to install it using APX mode. I have repacked easyflasher with newer recoveries here: http://forum.xda-developers.com/showpost.php?p=43986513&postcount=250
In my experience, many users have had big issues (myself included) trying to use CWM and anything beyond Android 4.1.X ROMs on the TF101. TWRP has far fewer issues and it can flash from both internal and external storage.
frederuco said:
I would HIGHLY recommend updating to TWRP.
If you can flash from the microSD, grab a flashable zip file like 2.6.1.0 from this thread: http://forum.xda-developers.com/showthread.php?t=2434422
If not, you can push the TWRP zip file to the /sdcard/ using adb and flash that.
A last option is to use EasyFlasher to install it using APX mode. I have repacked easyflasher with newer recoveries here: http://forum.xda-developers.com/showpost.php?p=43986513&postcount=250
In my experience, many users have had big issues (myself included) trying to use CWM and anything beyond Android 4.1.X ROMs on the TF101. TWRP has far fewer issues and it can flash from both internal and external storage.
Click to expand...
Click to collapse
So the best way to do it is using EasyFlasher right?
What option should i use: Flash or Unbrik, and what recovery system do i select, TWRP? Thanks.
anibol said:
So the best way to do it is using EasyFlasher right?
What option should i use: Flash or Unbrik, and what recovery system do i select, TWRP? Thanks.
Click to expand...
Click to collapse
I would use the TWRP 2.6.0.0 repacked EasyFlasher and then just install recovery (select the TWRP 2.2.0 from the dropdown and it WILL install 2.6.0.0).
I have a detailed guide here: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
Hi Fred, thanks for you guides. I have following it and i have TWRP installed, i have booted in recovery mode and when i install EOS rom the progress bar remains stuck, move for 1 second , stuck again and move a bit again and i don't know if this is normal, how much time i have to wait....Any hint?
Thanks in advance
I forget it. When i did the wipe i get an "Unable to mount /system" Is this normal? May be i have not enough space for the update?
anibol said:
I forget it. When i did the wipe i get an "Unable to mount /system" Is this normal? May be i have not enough space for the update?
Click to expand...
Click to collapse
Hmmm....thats not good.
It could be that your internal storage has a personal issue. I would try using EasyFlasher to flash back to stock. Just download the update from Asus, put it in the "asusupdate" folder of EasyFlasher. Do not unzip the file at all.
Instead of installing TWRP, flash stock. See if that boots.
If it does, then flash TWRP again and see if you get the same system error.
I've searched and found a few different solutions for each of my problems. However, nothing has resolved the issue.
I tried to flash CM 11.0 to my Galaxy Tab 2 (GT-P3110) and now I can't get anywhere but my CWM Recovery screen.
When I try to install the ROM, I get a "Status 7" error. I've attempted the steps found here but they have not worked.
So, I decided to just recovery what I had before - easy enough. But then when I attempt to recover, I get an error of "MD5 Mismatch".
I've looked up ways to resolve this issue, but I can't complete the steps for 2 reasons. Firstly, I can't get to my File Explorer because my tablet won't completely boot. Secondly, my laptop has stopped recognizing my tablet for some reason. So, I'm unable to edit the file from there.
Lastly, when I just try to reboot system, I get an error explaining that I "may" have lost root access. If I select to "fix" this, it does nothing - just reboots back to recovery. If I choose no, same thing.
I've cleared dalvik, cleared cache partition, cleared data/factory reset, and formatted system - nothing makes a difference.
Any help is greatly appreciated. Thanks everyone.
IS there kitkat update for tab 2. Please inform about That}.
chandru andriod said:
IS there kitkat update for tab 2. Please inform about That}.
Click to expand...
Click to collapse
I believe so, yes.
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Android-Andi said:
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Click to expand...
Click to collapse
Okay - easy enough.
If I'm unable to get to ROM Manager, is there a way to update my Recovery within Recovery Mode?
I've zipped the .img file for the update.
Should I just install the zip from Recovery Mode?
THANKS!
download a flashable zip for your device from my thread and flash it in recovery. after that reboot the recovery to see the new recovery.
Can anyone tell me how I flash a recovery to the device from a zip file? Going into CWM and flashing the TWRP recovery initially seems to work, but if I then interrupt the reboot and go straight into recovery, I still see CWM, not TWRP. I'm stuck on the CWM recovery and need TWRP to try to install the Kitkat upgrade.
Should I unzip the components first and then flash the image using fastboot, or is there another way? I'm wary of fastboot as I've already (temporarily) "bricked" the Xoom by flashing a zip instead of an image that way. None of the instructions I've read has much advice on getting round installation problems.
I'm guessing the persistent CWM was caused by my selecting (at an earlier stage) the CWM option to fix the problem of the stock recovery being reinstated at each reboot. Can this be undone? Although I've installed Xoom-Universal-Root, apps that require root access - including GooManager - also fail with an access error. It's hard to tell whether the device is now rooted or not, so if there's any method of getting further without root access, that would be great.
====================
Edit: it looks as if the instructions I saw online, which mentioned two separate TWRP recoveries, were incorrect. To get Android Kitkat 4.4 onto my Xoom I didn't need the initial TWRP recovery, only the BigPart version. Once I skipped to the BigPart recovery, the problem described above did not recur.
Ive been trying to install katkiss lollipop 5.0 on my tf101 but every time it comes up with errors that leaves my tablet bricked i think i need to update my recovery ive got teamwin 2.6 how do i fix this or update my recovery pls give a detailed guide
Timmieh14 said:
update my recovery
Click to expand...
Click to collapse
download TWRP 2.8.1.1 zip for TF101.
Boot into recovery and choose 'Install'
search for your downloaded signed_twrp-2.8.1.1_tf101.zip and flash it.
I assume you have no working ROM installed, so this part is a bit different from normal
Now choose 'Reboot'(a warning pops up that no ROM is installed), and don't install root (we do that later).
While rebooting, you will notice a progressbar. When the progressbar is finished, you have to force a reboot to the recovery (since you are without a working ROM, nothing else will work anyway).
you should now have twrp 2.8.1.1 (look in the statusbar on top of the screen)
from here it is straight forward:
flash Katkiss, Supersu and gapps in that order.
if things still does not work I find it useful to format data (not just wipe). especially useful when coming from another ROM