Hello,
I've been trying to install CM13 with gapps using TWRP (using fastboot boot, because my device is S-ON), and though cm goes through ok, flashing gapps returns Updater process ended with error: 2 and I can't seem to be able to google this problem out. Anyone knows what that means or where I can find TWRP error code meanings?
nvm, was wrong platform gapps
Related
Ok so I got my E980 rooted via towelroot, then used the freegee app to install loki, then I used flashify to install the CM recovery listed below, planning to flash the matching cyanogenmod rom:
snapshot Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980.zip (243.15 MB)
sha1: 9a4773d2fca0658edb2683079ce96307863a9fd0 Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980-recovery.img
sha1: 1095ea774ff2347fb3a2884045aa4a47e6833893 2015-10-07 02:08:36
I rebooted into the recovery and it wouldn't flash the cyanogenmod 12.1 rom at first, saying that I had an incompatible system installed, so I did a factory reset and then tried again and it installed the CM 12.1 ROM without errors, however it wont boot into it. All I can access is the CyanogenMod recovery and the factory wipe screen, I cant seem to boot into a rom even when it installs without errors, I cant get into download mode no matter what combo of keys/plugging in I do, even though it worked fine before.
Any thoughts or Ideas? I am totally lost here.
When turn on the phone it says:
Secure booting Error! Cause : Device Unlock!, so Boot Success!!
When I try to flash the TWRP zip that is floating around (2.8.1 I think) it says:
Finding update package.....
Opening update package...
Verifying update package...
E:Footer is wrong
E:Signature verification failed
Installation aborted.
When I turn on ADB mode through CyanogenMod recovery
Adb devices: Lists the device (99d3b89c sideload)
Adb usb: Error : closed
I have tried CyanogenMod 10.2.0, 11-20141115, and 12.1-20151007, and tried them before and after every kind of wipe available through this recovery, and they all install without error then reboot back to the recovery.
Is there another flashable recovery around for this phone I could try? I just don't see many in zip format.
Finally got it working. Threw every flashable recovery I could find at it, finally got Phillz touch to install and work from the CyanogenMod recovery. Phillz wouldnt install a working rom, but Phillz did allow me to flash CWM 6 something, which allowed me to install 2.8.1 TWRP, which couldnt see my microSD card, but it did allow me to copy 12.1 CM to my internal SD card from my computer via USB and to flash it and have it actually work. After I booted into CM 12.1 I had to fight gapps for a while, the open gapps pico and nano for 5.1 arm didnt work, but I got the Gapps from the slim rom to work after rewiping the system to remove the open gapps.
After that I finally manager to get flashify, supersu, and busybox from the store. Used flashify to upgrade to 3.0 TWRP. I still cant get into download mode, but pretty much everything else is working now.
Hi all, I'm not really sure if this is correct section to post this but has anyone else had issues with installing the latest (2016-03-16) CM13 release on their Nexus 7 flo device?
The steps I used to flash are as follows:
1. I used WugFresh NRT "Root" option with "Also flash custom recovery selected" to root my stock android 6.0.1 install and install TWRP 3.0.0.0
2. I then booted into recovery and copied over the CM13 zip and the (2016-03-16) version of OpenGapps Micro to the device.
3. I then did a factory reset from within recovery and flashed the CM13 zip which installed as expected.
4. Then I tried to flash the openGapps zip. I selected the zip and swiped to install and it stayed on "no md5 file found" for about 15 minutes. After this it installed and everything seemed to be fine until I rebooted into the OS.
5. When the tablet booted up for the first time and finished optimizing 96 apps* it came up with the CyanogenMod setup has stopped working error.
I know there is a work around for this but, as I had CM13 installed on this device before with no issue, I decided to dig a little deeper...
1. I downloaded TWRP 3.0.0.0 manually and flashed using fastboot. RESULT: Exact same thing with the long pause when installing Gapps followed by the CM setup error
2. I downloaded CM Recovery and manually flashed using fastboot. RESULT: Cannot install Gapps at all this time due to it not be compatible with CM recovery
3. I tried to ADB sideload using TWRP 3.0.0.0. RESULT: CM13 installed normally, but again, the same long pause with Gapps install followed by the CM setup error
4. By this point I'm fairly sure there is some issue with Gapps so I check the MD5 of the file and its fine so I download an older version and try to flash that... RESULT: Same thing as before
5. Next step, different Gapps version... So I download the "mini" version of Gapps instead of the "micro" one, check the MD5 and then try to flash. RESULT: Again huge pause during install follow by "Error 70: Insufficient space"
6. I setup a gapps config file on the tablet to tell the Gapps installer to install the Micro package in test mode so nothing should change. RESULT: This file is apparently completely ignored and I get the same result as before.
7. Finally I decide to fastboot flash TWRP 2.8.7.0 and voila! RESULT: CM13 installs and the Gapps micro install loads straight up installs everything at the expected speed. When the tablet reboots there are no error and everything seems to perfectly okay.
* As an aside I have a LG G3S/Beat which has been flashed with CM13 and OpenGapps Mini using TWRP 3.0.0.0 with no issue as all. When this device booted up it only optimised something like 24 apps. Can someone explain why my nexus 7 has to optimize 95 and the LG G3S only has to do 24?
TLDR; TWRP 3.0.0.0 doesn't like Gapps on the Nexus 7 flo
So has anyone else had any issue like this with their devices?
Regards
Nathan
TL;DR: After rebooting to slot b with TWRP following a failed LineageOS flash, my XA2's screen is broken: showing only flashing vertical lines. This problem persists after an attempted reversion to stock firmware and software using Emma.
Apologies for the long post, but I'm at a total loss even after a lot of reading, and would appreciate any suggestions to turn this £180 paperweight back into a phone. I'm not trying to blame the LineageOS or TWRP teams here; any error is my own
What I've done to install TWRP on my XA2:
Installed the newest system updates (including an update to Android 9)
Unlocked the bootloader
Enabled developer options and USB debugging
Installed TWRP as per the instructions on TWRP's XA2 page (i.e.: not flashing TWRP using fastboot)
Happily rebooted into fully-functional TWRP
I then tried to flash LineageOS using TWRP:
Formatted data
Wiped system, cache, and internal storage partitions
Attempted to flash LineageOS (lineage-16.0-20190916-nightly-pioneer-signed.zip)
Flash failed with "ERROR: 1"; "Error applying Update: 18 (ErrorCode:: kdownloadPayloadPubKeyVerificationError)"
After some reading I found a post which suggested rebooting into slot b to fix this problem
Used TWRP to reboot into slot b
Screen is now glitching: flashing vertical lines on a black background; Sony splashscreen doesn't show during boot, nor does the unlocked bootloader screen
Here's what I've tried to fix it:
Flashed stock firmware, and then software, using Emma (which showed both operations as being successful)
Attempted to reboot to slot a using fastboot
The current state of the device:
Broken screen showing only flashing lines and colours (no splashscreens)
Boots to voice-assisted setup (!?) despite the broken screen. From what voice assist is saying, there seems to be a system there (e.g.: I can take screenshots)
Can be powered on and off, and put into flash mode (green LED)
Is still recognised by (and can be controlled using) fastboot
Thanks for reading. Any help is much appreciated
Update: I've tried using Newflash to flash stock firmware downloaded via Xperifirm.
The operation complete successfully, and the device boots (thankfully not to voice-assisted setup), but the screen is still broken, as described in my OP.
Does anyone have any suggestions?
Alright, on the off-chance that anyone comes here with the same problem (i.e.: XA2, broken screen), I seem to have fixed it by:
Powering off the device
Putting it into flash mode (green LED)
Fastbooting a special TWRP .img with "fastboot boot /path/to/twrp.img"
Rebooting the device normally
I have no idea whether my previous step of using Newflash is a dependency of this working, or whether it works on its own
Now my screen works again, but every attempt to flash LineageOS zips with TWRP fails as described in my OP:
Error applying update: 18 (ErrorCode: : kDownloadPayloadPubKeyVerificationError )
Updater process ended with ERROR: 1
Error installing zip file
This happens:
With several different nightly pioneer builds
With several different versions of TWRP
Trying to flash the .zip from SD card
Trying to adb push the .zip
Trying to flash from the fastboot booted .img
Trying to flash from different versions of the TWRP .zip, flashed from the fastboot booted .img
Despite having already flashed the older firmware version (50.1.A.13)
So I am again at a loss
Google Translate
did you see this guide?
https://forum.xda-developers.com/xperia-xa2/how-to/guide-flashing-lineageos-16-0-sony-xa2-t3944964
bane.twit said:
Google Translate
did you see this guide?
https://forum.xda-developers.com/xperia-xa2/how-to/guide-flashing-lineageos-16-0-sony-xa2-t3944964
Click to expand...
Click to collapse
Hi Bane, thanks for your reply
The guide you've linked is the guide I was attempting to follow. However, I get "Error applying update: 18 ..." at step 22.
Do you know how I can fix this error (perhaps bypassing verification)?
Google Translate
works with me with twrp-3.3.1-1-pioneer.img
bane.twit said:
Google Translate
works with me with twrp-3.3.1-1-pioneer.img
Click to expand...
Click to collapse
Interesting; I encountered the error using either twrp-3.3.1-1.img alone, or using twrp-3.3.1-1 to flash twrp-install-pioneer-3.2.2-0.zip
I've also tried various combinations of twrp.img and twrp.zip, but to no avail.
This was despite: flashing the Oreo firmware to both slots, formatting data, and wiping the system partitions.
Is there something I'm missing? Following the guide you kindly linked, everything works, until step 22 when I encounter this error and can't flash lineage.
Google Translate
- follow the guide instructions...
- via ADB, only twrp-3.3.1-1-pioneer.img ...
- adb sideload lineage ... the latest build ...
bane.twit said:
Google Translate
- follow the guide instructions...
- via ADB, only twrp-3.3.1-1-pioneer.img ...
- adb sideload lineage ... the latest build ...
Click to expand...
Click to collapse
Amongst other things I've tried:
-Flashing Oreo firmware (with Emma or Newflasher)
-Rebooting to fastboot (?); blue LED
-"fastboot boot ./twrp-3.3.1-1-pioneer.img" to boot TWRP
-Formatting data and wiping system partitions
-Trying to flash lineage, either from SD card or by sideloading
...but I always run into error 18, and flashing fails
Am I missing any steps here?
i can't help you
bane.twit said:
i can't help you
Click to expand...
Click to collapse
Ah OK, thanks for your help though
I'll try again in a week or so (I'm away from home for a while) and if I get it working I'll post the solution here.
No matter what i do im unable to install lineageOS on my razer phone, constantly getting "update error: 255".
All the guides just say click install and select the zip and it never works.
What recovery are you using?
Can also confirm this is a current issue. Using TWRP 3.2.2-0
I had the same problem with TWRP. Switched to Lineage recovery instead and everything went smooth.
Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.