Database Develop

[Q] Cannot install TWRP anything higher than ver 2.7.0.0

I managed to get TWRP 2.7.0.0 using AutoRec. I'm trying to get it upgraded to version 2.8.x.x but can't do it manually using adb or with TWRP manager, or any other methods.
I'm trying to install CM11 and it fails every time, from what I've read, I need a higher version of TWRP to achieve this without getting the error executing update binary in zip msg.
Anyone else running into this problem?
Verizon LG G2
VS98026A baseband
4.4.2 stock rom
EDIT: One thing I noticed, the only versions that show up as compatible using an app like TWRP Manager are the one's labeled with g2vzw
Example - The techerrata downloads for twrp
All the downloads that work are the g2vzw downloads. All the new downloads labeled vs980.zip won't work. I've tried renaming and still have the same problem.

centrix said:
I managed to get TWRP 2.7.0.0 using AutoRec. I'm trying to get it upgraded to version 2.8.x.x but can't do it manually using adb or with TWRP manager, or any other methods.
I'm trying to install CM11 and it fails every time, from what I've read, I need a higher version of TWRP to achieve this without getting the error executing update binary in zip msg.
Anyone else running into this problem?
Verizon LG G2
VS98026A baseband
4.4.2 stock rom
EDIT: One thing I noticed, the only versions that show up as compatible using an app like TWRP Manager are the one's labeled with g2vzw
Example - The techerrata downloads for twrp
All the downloads that work are the g2vzw downloads. All the new downloads labeled vs980.zip won't work. I've tried renaming and still have the same problem.
Click to expand...
Click to collapse
You should be able to flash the version posted here in recovery.
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705

mjones73 said:
You should be able to flash the version posted here in recovery.
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Click to expand...
Click to collapse
That did it, thanks!
Nightly build of CM11 still won't install, know anything about that?

centrix said:
That did it, thanks!
Nightly build of CM11 still won't install, know anything about that?
Click to expand...
Click to collapse
Nevermind, I forgot to wipe first. All is well.
Thanks again!

TWRP flashing

Hi guys, I'm experiencing a message "error updating binary zip" thing while trying to flash a liquid smooth rom on my nexus 6. Please help me. Thanks

You might need to update TWRP; what version do you have installed? It should be listed at the top in recovery.

trieo007 said:
Hi guys, I'm experiencing a message "error updating binary zip" thing while trying to flash a liquid smooth rom on my nexus 6. Please help me. Thanks
Click to expand...
Click to collapse
Download this App from PlayStore and you'll be able to find the latest TWRP here It'll automatically flash the recovery and give a try to flash the ROM again

Tried it now and I still have the error while flashing. My version is 2.8.5

trieo007 said:
Tried it now and I still have the error while flashing. My version is 2.8.5
Click to expand...
Click to collapse
Might be they use an old update binary in the zip. Ask in the ROM thread.,

Completely wiped OS during reset :(

Hello, I'm new to these forums and have come to them under some unfortunate circumstances.
I went to update my device (MOTO G 2014) and had an error (cant remember what it said), anyway I rebooted my device and it wouldnt load after the 'BOOT LOADER UNLOCKED' warning screen. I went into TWRP and went to reset my device and wiped the system. (feel like an idiot, then again I am..) So then I downloaded all the USB drivers and Android SDK along with adb+fastboot and attempted to sideload. during the sideload I got this error..
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
EDIT: the error is no showing up at * failed to write data 'protocol fault (no status)
I have swapped USB ports and tried a different USB cable, does anybody have any tips or do I have a paperweight on my hands?
Thanks in advance

Flash stock firmware.
motofirmware.center
Sent from my XT1031

If I understand, right now you have wiped system, and bootloop in Motorola logo.
If you can boot in recovery, then transfer a ROM to an microsd and flash from there.

UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?

PJT95 said:
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
Click to expand...
Click to collapse
Lemme guess u tried to flash "titan" CM and not "thea" one?

LuK1337 said:
Lemme guess u tried to flash "titan" CM and not "thea" one?
Click to expand...
Click to collapse
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?

PJT95 said:
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.

LuK1337 said:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
Click to expand...
Click to collapse
Thanks for your help and thank you to everyone else who replied to the thread. To anybody else who will maybe see this thread and who are stuck with the same errors, I fixed this by simply flashing the latest recovery using 'fastboot flash recovery [NameOfRecovery].img' then proceeded to install the ROM compatible with my device which I downloaded to my external SD Card.
Again, thanks

No further update of CM13 via TWRP possible

Hey folks,
after hours of reading around I have almost no idea left how to update my CM13 (13.0-20151213_nightly-titan) currently installed to a newer version. I tried with TWRP 2.8.6.0 and even 2.8.7.0, but it's all the same: I choose the zip file to install, the filesystem is detected correctly - but the installation just won't continue (usually the detection is followed by "patching the system unconditionally"). TWRP doesn't freeze, but just nothing happens . When I brake up after some time (usually an installation is done very quickly) with pressing the power button, my phone boots in the old version normally.
I tried another TWRP, wiped cache and dalvik, fixed permissions, set root in phone options, tried several CM13 builds... But I'm afraid of wiping data and system as it's a lot of work to get everything right again afterwards :crying:. Do you have any idea why TWRP doesn't want to install the new build?
Thanks a lot!

First always take a nandroid backup before you make any changes.
Even thought TWRP 2.8.7.0 is released, For Moto G 2014(titan)
only 2.8.6.0 is official https://dl.twrp.me/titan/
Try doing a clean installation(Wipe the data & System). That should do the trick.
just for the record the recovery is stopping you from installing a new build

Seems to be an issue with TWRP. You could give a try using CWM PhilZ Touch recovery. I have flashed using this recovery numerous times without any problem.

Thank you two for your replies !
Maddy, I know that 2.8.7.0 is unofficial for titan, but nevertheless it's working (for others). I want to avoid a complete reset, but in the end this could be a solution. But as I reflashed twrp (and tried another version also) I'm really wondering why twrp could be the problem ...
pank, I will take a look on CWM PhilZ, but until now I was really happy with twrp (and of course with its backup function). I hope it's possible to flash CWM using twrp and vice versa .

Unfortunately CWM PhilZ Touch Recovery shows the same behaviour than twrp - installation of new zip file just doesn't work (without any error) . If someone has an idea (except of a full wipe) please give me input !

Update the bootloader to the latest version. Had a similar problem a few months back that resulted in lots of hair tearing This solved it.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007

Great hint - just checked your link already this morning and everything seemed to make sense... But I figured out that bootloader 4883 (newest version) was installed at my phone . Downgrade to 4882 should not be possible, and I'm also afraid of that .
I think I have something to do around Christmas - full wipe and a clean install! Damn...

Try installing this app called "CyanDelta" from playstore. What it does is it downloads the necessary files to upgrade from cm latest build (not the hole file) it's could be around 30 mb only. Totally legit!!... And it would dirty flash after download....
Do let us know how it turns out ?

I already tried CyanDelta, great tool! But as it's just creating a script for TWRP it has the same behavior . Oh, and I discovered that the nightly I'm using is no more available on cyanogenmod's official website ^^.
By now I think I've spend more time on searching for a solution than a full wipe including everything would need :laugh: ...

For me TWRP gives this behaviour only when Downloaded zip has some problem in it.
when it's not downloaded correctly it stuck at patching System
Have you tried latest zip?
also check SHA1 after download, doing that will confirm zip is downloaded correctly

Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...

No_Future said:
Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...
Click to expand...
Click to collapse
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.

mwalma said:
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.
Click to expand...
Click to collapse
Yes, you can try Cyanogen Recovery
download it and from fastboot
you can either just boot once and try it or flash the recovery replacing TWRP
Code:
fastboot boot recovery.img
Code:
fastboot flash recovery recovery.img

Great, I didn't know that it's possible just to boot once with a special recovery image. I'll try cyanogenmod recovery today !

Great news: With use of Cyanogenmod Recovery I was able to flash the newest build :victory:! I'm looking forward to try one day with TWRP, but for now I'm totally up to date . Thank you all again and have some nice days !
Edit: A full wipe and clean install solved this problem completely . Now the flashing with TWRP works again.

Phone not booting after FlashFire flash.

Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.

Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.

irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.

irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/

Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:

ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.