Hello
I used WugFresh's awesome Nexus Root Toolkit to unlock, root and install custom TWRP recovery. I have 2.8.2.1 version installed. I am unable to do any tasks with this TWRP, however. It throw error when I try to Wipe Cache, make backup or anything else for that matter.
I tried to update using fastboot but I haven't figured that part out yet.
Can anyone provides some assistance as to what the cause of error could be? I am on 5.0.1 build, encrypted.
Thanks
Try:
Code:
fastboot flash cache cache.img
From your 5.0.1 factory image, keep extracting until you see all the .img files including cache.img.
I didnt have any issues with 2.8.2.1 but i have since switched to 2.8.2.0 since its the official version.
Download 2.8.2.0 from their website. Boot into bootloader and type fastboot flash recovery recovery.img where recovery.img is the downloaded twrp file.
I was able to flash cache.img, but TWRP is still giving error when I try to do any action. It keeps saying unable to mount storage.
JManekia said:
I was able to flash cache.img, but TWRP is still giving error when I try to do any action. It keeps saying unable to mount storage.
Click to expand...
Click to collapse
Flash the 2.8.2.0 twrp img
Thanks. It was the encryption doing its job. I had to put in the password to get it going. Appreciate all the help here
I can't seem to flash new ROMs - get an error message "E:Error executing updater binary in zip". Tried both slimRom and Liquidsmooth
I'm rooted on 5.0, decrypted, busyboxed, with the latest TWRP v2.8.2.1. Any ideas?
Any ideas?
I'm having the same issue, did you ever get it resolved?
i am also having this issue....I have a thread going. "HELP i cannot flash any custom roms"
The TWRP 2.8.3 is out and has been for a little while I would try the newest version (the one I said above) it seems to be working better for me than the earlier ones.
Related
I don't remember if I deleted it or what but I only have TWRP 2.6.1 on my device as a recovery and I would like to reinstall CWM on my device. However, every "flashable" CWM zip I have tried through TWRP has failed and I'm not sure why. Don't nwant to brick my device and don't necessarily want to WebOS doctor it if I can avoid it, as my device has run fairly well (I am on 4.2.2). Any/all help is appreciated. Thanks!
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
bananagranola said:
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
Click to expand...
Click to collapse
Not yet, although I managed to get a workable CWM running by moving an image to the boot folder and then updating to the latest working version (couldn't get the "touch" version to work via touch, however).
However, I may try flashing via fastboot if something unexpected happens. Thanks for the help
So I decided to install cyanogenmod WhiteNeo ROM on my xperia T
did the entire process alright.
for recovery, CWM din't work so downloaded app from playsore and got TWRP from there.
the followed the steps from here to reach till step 8 from wiki.cyanogen guide.
stuck at step 8. DOn't get how to perform it because it is confusing.
altenrately sentthe zip package to sd card and tried there but says Error executing updater binary in zip.
I am stuck.
5%battery left.
and I dont know what to do.
can't even get out of Recovery mode.
device is unresponsive when connected to USB and is powered off.
can anyone please sort this out and explain in simple words how to get out of this mess?
p.s: if battery expires,then what happens?
tried installing stock firmware using flashtool
but
07/014/2015 19:14:54 - ERROR - Error in processHeader
all the time
googled all the solutions
none works
help please?
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
WhiteNeo said:
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
Click to expand...
Click to collapse
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
aber96crombie said:
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
Click to expand...
Click to collapse
Reverting to stock FOTA and getting official CM recovery (which won't flash anything but official CM builds and gapps) can be done with flashtool and a suitable ftf or using a Terminal command that you will find on the last pages of my CM12.1 thread for Xperia T.
TWRP version should be visible in settings or what one would call a "status bar".
And the force-closing gapps are just the result of a broken or outdated recovery. I've already been reported the same issue after creating a FOTAKernel TWRP for a friend.
You should be able to flash official CM12 gapps from Cyanogen Recovery.. Just google those.
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I have it here: https://drive.google.com/drive/folders/0B4tnYt16-NAUQm02dHhDaWlyQUE
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I believe if you re-lock your phone, the phone can factory reset and get re-flash stock recovery itself. btw,have you check the OTA zip file and make sure it was not damage when you downloaded it.
can you help me man i need that file but seems to be that link in not correct, can you give me the correct link pls i am stuck
Can't you just download the stock firmware and flash through ODIN? Then you will have stock recovery and everything.
EDIT:
Cancel my suggestion. ODIN is only for Samsung phones. My bad!
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.
manor7777 said:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.
Click to expand...
Click to collapse
that link doesnt work, when i try to download it states no file attatched
Hello,
I have always been on root but somehow something changed.
Since I tried to flash the newest stable stock (5.0.1), nothing works anymore.
No matter if I flash dm-verity disabler, supersu or magisk, dm-verity gets triggered everytime and my phone just says "decryption unsuccessfull" and won't boot.
I've tried everything to fix this, including: different versions of supersu/magisk, reflashing TWRP recovery, even going completely back to stock, locking the bootloader and everything.
Also I read somewhere that you can flash dm-verity disabler and wipe data to completely remove the encryption, but TWRP showed an error message, something like "failed to wipe, cannot mount /data".
In the end I got stuck with no ROM and I couldn't even access stock recovery anymore because it had the weird password bug, so I had to use the unbrick tool to get it working again.
Can someone tell me what I'm doing wrong?
I have always been on root since the early Nexus 5 days, but now I feel really stupid because I must be missing something obvious, so thank you in advance for any help.
Cheers
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
If by chance you are trying to flash OpenBeta 21, I have yet to avoid my data getting encrpyted when trying to flash. And personally, I must have been doing something incorrect ever since I got the phone, because almost every time I've flashed a stock OxygenOS ROM I have triggered encrpytion. In my situation it never seemed to matter if I flashed Magisk, SuperSU, a custom kernel, or even just a modified boot.img along with the disable encryption file... I don't know the steps you're taking, but what I do is this: once I get the "Encryption Unsuccessful" message when trying to boot, I just reboot to fastboot and type "fastboot format userdata". And since flashing stock OxygenOS usually overwrites TWRP with the stock recovery despite my best efforts to avoid it, I tend to go ahead and flash TWRP while I'm booted into fastboot. After, I boot into TWRP; at which point encryption has been removed, yet the total amount of storage available to me is less than 30GB (I have the 128GB model.) You have to go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data. That restores my device back to 111GB free of 113GB. I then transfer over and flash Magisk and whatever other mods I wanted. After that my device is no longer encrypted and works just how I want it to. Hope that helps with your issue.
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
Click to expand...
Click to collapse
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data.
Click to expand...
Click to collapse
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
kaeptn1 said:
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're not using Blu Spark 8.61 TWRP, then I suggest you install it and try again.
If all else fails, do as @lordcheeto03 suggested and format userdata in fastboot - but note that this will completely wipe your data, including internal storage. Then install TWRP, then flash 5.0.1 and anything else you want.
Sent from my OnePlus3T using XDA Labs
kaeptn1 said:
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're getting the encryption unsuccessful error, I don't think you format data in that manner, you gotta use fastboot and fastboot format userdata to remove encryption THEN boot into TWRP to do that.