Updating rooted Lollipop device to Marshmallow/installing TWRP - Nexus 5 Q&A, Help & Troubleshooting

Hi,
I have a rooted Nexus 5 running a modified AOSP 5.1.1 and CWM Recovery. I wish to update it to the official 6.0.1. I got an update notification and went ahead and downloaded/installed the update, but after the download and upon reboot, CWM recovery informed me that the zip is invalid (signature verification failed or something), and the update was aborted, so the device is still stuck at 5.1.1, and subsequent system updates checks after reboot shows that the device is up to date.
I also wish to change my recovery to TWRP instead since ultimately I want to run Chainfire's suhide.
What do I need to do to go from my current environment (CWM Recovery with modified AOSP 5.1.1) to the new one (TWRP with official 6.0.1 with SuperSU/suhide)?

Download and and flash the official Google ROM using fastboot commands, set up the ROM, run all OTA updates, flash TWRP via fastboot.

Related

Problem with TWRP

Hi i got a Problem with TWRP. I just installed 2.5.0.0 now I know its not updated. I get a error message everytime want to install the new CM: error executing updater binary in zip twrp.
Now I cant install any rom and i wiped my device already any ideas?
start from the beginning
you are going to need to flash the asus stock rom over top , Root it then flash the TWRP from the OP:
http://forum.xda-developers.com/showthread.php?t=2691886
and then flash CM 11.

Help updating XT1032 to official motorola 5.0.2 (custom recovery)

I've just finished flashing the stock motorola 4.4.4 EU rom and updating it after using CM 12 and having it become very unstable on my device due to the recent nightlies. I downloaded the official ota update to 5.0.2 the system reboots into TWRP (Version 2.8.5.0) and displays:
E: Error executing updater binary in zip '/cache/Blur_Version.210.12.40.falcon_umts. EURetail.en.EU.zip;
E: Error installing zip file '/cache/Blur_Version.210.12.40.falcon_umts.EURetail.en.EU.zip'
As soon as i select reboot into system, the boot loads fine and stays on for a while, but then automatically restarts to attempt the install again. Im assuming this error is because I'm running a custom recovery, but any help would be great! I know exactly where the zip is on my phone storage too, so would it be a matter of installing manual (however when I checked it displayed a message saying it could be incompatible and render my device unstable, and I really dont want to have to reinstall the rom again.
Also I have not updated to a custom boot loader, its running the kitkat boot loader from motorola.
Thanks in advance

cannot install CM12

My system is now KK 4.4.2 with unlocked bootloader
I download CM12 (nightly) from download.cyanogenmod.com - XT925 KK bootloader
I intended to install CM12.zip via Phil Touch recovery but it failed and this message appeared:
This package is for device: xt925, vanquish_u; this device is .
E: Error in /storage/sdcard1/....CM12.zip
(Status 7)
Installation aborted.
Then I used TWRP recovery instead of CWM.
The installation was successful, but in a short time (faster than installing gapps)
I made the phone rebooted.
When the system was on, it showed an error dialogue and self-rebooted to boot animation graphics immediately. Then, it became an endless loop
I had to reflash stock KK system via RSD
What happenned to my XT925????
Try flashing CM11, factory reset, then CM12 nightly dirty flash. That way I got it to work. You need to remove the first line "assert..." in a file inside the zip to make it work with philz. Normal install or update of CM12 nightly works only with current cyanogen recovery for me.
The problem is the gapps file
I've only installed the CM rom via TWRP and the system is now running without gapps
Yes you need gapps for 5.1, best from the CM wiki

Ota flash not working

I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
I've come across this today (my OPO was rooted and I had TWRP installed), I was able to install the OTA via returning the OPO back to an unrooted stock build. You can easily do this via getting the 'Fastboot' zipped version of your current .....1NO build.
Once you have this, you only need to fastboot flash the following: - boot.img, recovery.img and system.img
After flashing just these three images, yes you'll loose root but you'll be able to OTA update to the ......2QL build via the normal phone method - hten if you want, you could then reflash a TWRP recovery and re-install a supersu.zip
One thing I forgot to add, which maybe helpful to others as it took me a moment to realise, both boot.img and recovery.img flash without issue, but due to it's size to flash the large system.img you'll probably need to brake it down into flashable chunks, notice the change in fastboot commands: -
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot -S 512M flash system system.img​
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
OTAs can only be flashed through stock recovery..applicable to all devices
Hello,
on the same subject, I am looking for explanations on how to create twrp flashable files for ota updates. Do you know where I could find any resources?
Thx
I had the same issue while installing the incremental update (I got root and TWRP); I solved it simply installing the signed zip of ...2QL version which was pulled out yesterday afternoon. My only concern was about root that could be wipe away with the new installation, so I directly installed SuperSU via zip. Everything works fine till now
Sent from my A0001

Nexus 5 in Bootloop after unlocking and installing TWRP 2.8.7.1

Hello,
I wanted to install a custom Rom on my Nexus 5 running Android 6.0 so I downloaded TWRP latest and unlocked the Bootloader and installed TWRP.
Now the OS doesn't bootup anymore and the TWRP starts but gets rebooted all the time.
Tried to install an older TWRP version 2.8.70 and sideloaded and installed Pure Nexus Rom but this doesn't fix the problem.
Wiping anything from TWRP gives error messages...
Anyonw can help please!?
OK I have the stock recovery now installed from Android 6.0 and the OS boots up with Pure Nexus... looks OK,...
Anyway what's the problem with TWRP now!?
I don't think so. TWRP 2.8.7.1 is working fine for months. Did you full wipe before flashing your custom rom? Did you flash something else?
U need to install twrp 2.8.4.0 first because twrp 2.8.7.1 can only re-write on twrp 2.8.4.0 or higher..its work fine for me at official google M
gessi2000 said:
I wanted to install a custom Rom on my Nexus 5 running Android 6.0 so I downloaded TWRP latest and unlocked the Bootloader and installed TWRP.
Now the OS doesn't bootup anymore and the TWRP starts but gets rebooted all the time.
Click to expand...
Click to collapse
That happened to me way back when I first used TWRP. From the official TWRP thread:
"If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP."
I think if you don't boot fully once before trying to install TWRP, it loops like that.

Categories

Resources