Whenever I flash TWRP with the AIO Toolkit from Hasoon2000, TWRP recovery will load, but the internal SD (/data/media) is blank. The files are there when it boots to the system, but they're not showing up in TWRP. CWM won't boot at all when flashed (it just goes to back to fastboot). I tried flashing the generic TWRP in the AIO Toolkit and the Sprint version, both seem to behave the same. Also if I try to flash a ROM, it always fails (CM fails immediately, Viper installs then says failed, InsertCoin says it succeeded, but then it never boots). I tried flashing TWRP 2.7.1.0 as downloaded from the TWRP website and it won't flash ("BootMagic failed" error). And GooManager doesn't find the right file to flash for my M8. Does anyone know how to fix this? I like the stock ROM alright, but I want to try some others. Oh, also when I try to do a backup it fails, saying it can't mount /data/media.
Related
I followed the steps from this thread:
http://forum.xda-developers.com/showthread.php?t=1952038
I successfully unlocked my phone and installed TWRP recovery, but that's as far as I can get. I tried to flash the latest CM10 nightly but hit an error when I run the zip, saying that the MD5 file is not found. I also tried to separately flash the boot.img from the CM10 zip, but it didn't help.
I've cleared my cache and factory wiped (through recovery), but I'm still stuck in the boot loop and can't get to the OS. Please help!!
I think the problem might be that I never actually rooted the phone, despite having unlocked it. Is there a way to root my phone via recovery, since I can't actually boot into it?
I tried to install RebelMod, but i hit an error saying "Unable to mount /data" -- I'm assuming that's because it's unrooted?
you want to root a stock ROM?
flash superuser downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
update: i managed to flash RebelMod successfully (according to TWRC) by running the zip file, but I'm still stuck in the boot loop even after doing a Factory Reset thru TWRC.
am I missing something?
wait a sec -- I got it working after I flashed the boot.img with fastboot.
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
On my ME301T I unlocked it and flashed twrp 2.5.0.0. I put the latest OMNI rom on an SD card and I can mount the card but when I try to install the ZIP it fails. also tried CM11 rom. all the roms I try to install fail! My computer wont recognize the tablet when booted to fastboot. Anyone know how to get ANY rom on this and working through TWRP?
Not sure what did the trick, but I flashed TWRP 2.7, wiped again, made sure to mount everything, used TWRP file manager to copy the ROM and moved it to the internal storage and then when I flashed it worked! Probably would have worked if I'd followed directions but it seems ROM wont flash fromexternal SD
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
I would also suggest starting over with the RUU for your model. Once you get TWRP back however you may want to take a look at this thread http://forum.xda-developers.com/one-a9/development/rom-a9-base-roms-recovery-flashable-t3282335 for some pre-rooted stock ROMS. I'm running the Sprint one with Xposed/GravityBox right now and it's great.
CSnowRules said:
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
Click to expand...
Click to collapse
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Did you try re-installing drivers and flashing new recovery with fastboot?
PHYN1X said:
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Click to expand...
Click to collapse
I believe SuperSU 2.46 was your problem and that a RUU is not required to fix this. The older SuperSU broke the dm-verity for your system partition, which is enforced by your kernel. Flash SuperSU 2.76 (the latest stable release). This will automatically patch your boot partition. You will not be able to take an OTA until flashing the stock system image, though.
You just need to fastboot flash TWRP back to your device, first (fastboot flash recovery twrp.img) just like the first time from download mode--not the bootloader. Unlike ADB, your phone doesn't need to trust your computer.
If fastboot doesn't work, check what creusset said.
creusset said:
Did you try re-installing drivers and flashing new recovery with fastboot?
Click to expand...
Click to collapse
i currently have twrp 3.1.1.0 multirom and wish to remove this and install the latest 3.4.0.0 as i am unable to install any roms.
Not sure if bug in the custom twrp but i cannot use it and have already tried wiping and cant get latest lineageos to install.rp
keep getting error 6 error 7. so i think twrp needs updating
I tried putting the .img file onto phone storage and off usb and install via "install image"
however i get
"select partition to flash image:"
Boot
it doesn’t list recovery for some reason so now im stuck with this
I have no images working i have tried getting old os to install but they are unable to work now and have already wiped the phone to make sure its clean install but i keep getting error.
wbb1 said:
i currently have twrp 3.1.1.0 multirom and wish to remove this and install the latest 3.4.0.0 as i am unable to install any roms.
Not sure if bug in the custom twrp but i cannot use it and have already tried wiping and cant get latest lineageos to install.rp
keep getting error 6 error 7. so i think twrp needs updating
I tried putting the .img file onto phone storage and off usb and install via "install image"
however i get
"select partition to flash image:"
Boot
it doesn’t list recovery for some reason so now im stuck with this
I have no images working i have tried getting old os to install but they are unable to work now and have already wiped the phone to make sure its clean install but i keep getting error.
Click to expand...
Click to collapse
There's no need to put the img file into the internal storage of the phone. Just flash it with fastboot:
Code:
fastboot flash recovery twrp.img
Or, if you are rooted, use the official TWRP app, it should be even easier.