Related
I got CM9 to install just fine. Went to install gapps in CWM, the same way that I instally CM9, and I got a sigature verification failed error. If I turn off signature verification the installation "completes" but upon booting back into CM9 nothing has been installed.
I checked the md5 of the recommended gapps pack and it was fine. I also tried the most recent gapps pack (02/07) and got the same result.
Roisen said:
I got CM9 to install just fine. Went to install gapps in CWM, the same way that I instally CM9, and I got a sigature verification failed error. If I turn off signature verification the installation "completes" but upon booting back into CM9 nothing has been installed.
I checked the md5 of the recommended gapps pack and it was fine. I also tried the most recent gapps pack (02/07) and got the same result.
Click to expand...
Click to collapse
Grab the most recent Gapps from the CM9 Epic-MTD site. It says signed in the file name. Reflash CM9 Alpha 2 and flash the gapps immediately before rebooting.
Roisen said:
I got CM9 to install just fine. Went to install gapps in CWM, the same way that I instally CM9, and I got a sigature verification failed error. If I turn off signature verification the installation "completes" but upon booting back into CM9 nothing has been installed.
I checked the md5 of the recommended gapps pack and it was fine. I also tried the most recent gapps pack (02/07) and got the same result.
Click to expand...
Click to collapse
Maybe a bad download as well maybe you dropped a packet or 2 when you downloaded it. Try a different one again match the MD5sum again put it on your SDcard then re-flash it clear your caches as well. Hope this might help out. If not post back
maybe this can help yah out
http://forum.cyanogenmod.com/topic/33065-cannot-install-cyanogen-signature-verification-failed/
I know they speak of other phones in that thread but maybe it can lead you in the right direction.
Thanks for the replies.
I'm beginning to think it's something wrong with CWM. I tried reinstalling the CM9 rom and it "completed" in about 10 seconds.
Roisen said:
Thanks for the replies.
I'm beginning to think it's something wrong with CWM. I tried reinstalling the CM9 rom and it "completed" in about 10 seconds.
Click to expand...
Click to collapse
Yeah, sounds like a trip back through the Halls of Asgard is needed.
Unfortunately for me neither of my computers will recoginize my phone regardless of any combination of cable, driver, and USB port used.
/cheer?
I am unable to install the following ROM, continue to get this error (E:error (Status 7) Installation Aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
The ROM I choose is the'd2spr' and I have used several other (d2spr) ROMs that work, for my 'Sprint Samsung Galaxy S III' (SPH-L710).
Anyone able to advise/assist?
Things already attempted..
1) Updated to the latest CWM recovery
2) Updated to the latest PHILZ recovery
3) Toggled 'signature Verification' to "on"
4) Tried several other ROM's from the same developer that were d2spr
..all resulted in the same error, above.
matg55 said:
I am unable to install the following ROM, continue to get this error (E:error (Status 7) Installation Aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
The ROM I choose is the'd2spr' and I have used several other (d2spr) ROMs that work, for my 'Sprint Samsung Galaxy S III' (SPH-L710).
Anyone able to advise/assist?
Things already attempted..
1) Updated to the latest CWM recovery
2) Updated to the latest PHILZ recovery
3) Toggled 'signature Verification' to "on"
4) Tried several other ROM's from the same developer that were d2spr
..all resulted in the same error, above.
Click to expand...
Click to collapse
Which baseband you currently running?
sent from my GS3
matg55 said:
i am unable to install the following rom, continue to get this error (e:error (status 7) installation aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
the rom i choose is the'd2spr' and i have used several other (d2spr) roms that work, for my 'sprint samsung galaxy s iii' (sph-l710).
Anyone able to advise/assist?
Things already attempted..
1) updated to the latest cwm recovery
2) updated to the latest philz recovery
3) toggled 'signature verification' to "on"
4) tried several other rom's from the same developer that were d2spr
..all resulted in the same error, above.
Click to expand...
Click to collapse
joeyhdownsouth said:
which baseband you currently running?
Sent from my gs3
Click to expand...
Click to collapse
l710vpucmk3
matg55 said:
l710vpucmk3
Click to expand...
Click to collapse
I am also having this issue
Which recovery are you guys using? If it isn't Philz Touch, switch NOW! Then, under Wipe Data/Factory Reset, choose Clean to Install New ROM, and then flash whatever version of Carbon you want. If it helps to get you started, here is my download of the very first KitKat nightly that Carbon released, the assert lines have been removed in order to make it compatible for Virgin Mobile/Boost, and it is guaranteed to flash if all else is equal (as in you are using Philz Touch and did a proper wipe; I flashed this version just fine, otherwise I would not post it).
http://d-h.st/KTA
And the link to the Philz thread:
http://forum.xda-developers.com/showthread.php?t=2446393
Make sure to give @Phil3759 a "Thanks" while you are there!
Mr. Struck said:
Which recovery are you guys using? If it isn't Philz Touch, switch NOW! Then, under Wipe Data/Factory Reset, choose Clean to Install New ROM, and then flash whatever version of Carbon you want. If it helps to get you started, here is my download of the very first KitKat nightly that Carbon released, the assert lines have been removed in order to make it compatible for Virgin Mobile/Boost, and it is guaranteed to flash if all else is equal (as in you are using Philz Touch and did a proper wipe; I flashed this version just fine, otherwise I would not post it).
http://d-h.st/KTA
And the link to the Philz thread:
http://forum.xda-developers.com/showthread.php?t=2446393
Make sure to give @Phil3759 a "Thanks" while you are there!
Click to expand...
Click to collapse
Thank You.. I do have the latest Philz Touch installed and did the full "new rom" wipe while trying the other Carbon ROM's, with the same error.
However, the ROM link you shared does work.. just hoping to be able to maintain the latest nightlies; wonder if I just have to remove the assert lines. Anyway, thanks again!
matg55 said:
Thank You.. I do have the latest Philz Touch installed and did the full "new rom" wipe while trying the other Carbon ROM's, with the same error.
However, the ROM link you shared does work.. just hoping to be able to maintain the latest nightlies; wonder if I just have to remove the assert lines. Anyway, thanks again!
Click to expand...
Click to collapse
Which carrier are you on?
Mr. Struck said:
Which carrier are you on?
Click to expand...
Click to collapse
Sprint... and have tried the latest 'd2spr'
matg55 said:
Sprint... and have tried the latest 'd2spr'
Click to expand...
Click to collapse
That is strange; as a Virgin Mobile user, I have to modify or delete the assert lines for any Sprint ROM that is AOSP based, but for a Sprint user the ROM should have downloaded and flashed just fine. That's a shame too, because in my opinion, Carbon is the best ROM available.
https://download.lineageos.org/crackling
The First One!
Do we need su for arm or su for arm64?
Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64
What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs
kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite
M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs
AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.
Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"
Can this be installed over the top of cm13.0 nightly?
Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.
M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.
Wifi
Installed tonite smoothly however no wifi - anyone else with this?
Same here, just reported a bug to the bugtracker.
Make a clean install three days ago, all works fine
pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-
Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.
M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.
I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.
ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English
hi,
today, i tried to update my op3 from lineageos 14.1-201703202 to the new lineage-14.1-20170309 with twrp. but i when flashing, i get error 7.
i already had the same issue the last time and could solve the issue with first flashing oxygen 4.0.3.
i guess when i flashed oxygen 40.3, i got the newest firmware and modem (and still have it, of course). why do i get this "error 7" again?
i thought it was because of the "false" twrp (i have 3.0.4-1) and then i made the big mistake to update twrp to 3.1.0.0. this version of twrp wiped my phone. thanks good, i had a one day old full nandroid backup to restore phone including going back to twrp 3.4.0-1.
but what should i do to get the newest lineageos flashed?
i am a absolute beginner and dont have deeper knowledge, but i am already a little bit angry that everytime i want to flash an lineageos update, i get into trouble. is this normal with oneplus3 and lineage? what am i doing wrong?
thanks a lot for your help.
best regards,
flotsch1
I have a similar issue with LineageOS updates.. I flashed LineageOS14.1-20170208 nightly on my Oneplus 3 with twrp-3.0.4-1, however I cannot upgrade to newer nightly releases. For some reason they always fail to install, it actually boots on recovery mode but installation using twrp quickly fails and I cannot even see the exact error it throws. Any ideas?
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
jim262 said:
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
Click to expand...
Click to collapse
It isn't, it is a check for firmware... Could be that lineage is using OB12 firmware now..
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309.
But there's new fw/modem here https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Install latest and flash new lineage. No error 7 here!
kebeil said:
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309. But theres no new fw/modem ... https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Click to expand...
Click to collapse
The fix is mentioned in the official weekly lineageos thread. basically you need to factory reset, flash the zip file attached in the thread and then flash the latest lineageos nightly/weekly image, followed by wiping dalvik and cache. It worked for me anyway, although everything got wiped so I had to restore my apps from backup (I use titanium backup).
flashing the betafirmware was the solution for error 7, but please see my other tread explaing my gapps-problems after successful lineagos update.
Here is how you fix error 7 in TWRP. You simply edit the first Two lines in the updated script by deleting them. https://youtu.be/XkwSO_I9GfE
For quite awhile now, I have had a nexus 7 (2013) wifi 16GB (flo). CM13 was my first custom rom. Since then, I have upgraded to the latest official Lineage 14.1 build. Now, I never use my old nexus.
Yesterday, I wanted to put together a little game station with it, centering around Wii remote support. I've read that the last android version to support the WiiMotes was 4.1. Unfortunately the N7 was launched with 4.3, so there is no official 4.1 build for the phone. I then read that CM used to have their own support for the controller. Can anyone verify if this is true? From the wayback machine, I downloaded and installed CM13, which worked fine, but while the WiiMote would "connect", it didn't actually do anything, and all for lights on the controller flashed indefinitely. Next, I went to the oldest stable build of CM available: CM10.2 (android 4.3). When I went into the latest version of TWRP to install it, I wiped everything except internal storage, and flashed the zip. I've tried this several times, and it always leads to one of 2 outcomes: either succeeds with the following output:
Code:
updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/cm-10.2.1-flo.zip'
Checking for digest file...
Skipping digest check: no Digest file found
updating partition details...
...done
This results in an unbootable system.
Usually successful OS flashes have a lot more output than this, right?
Other times it fails. (Using the exact same file)
I'm having trouble reproducing this error wile I write this, but it was something along the lines of
Checking symlinks...
some symlinks failed.
I know the file was downloaded correctly, because it matches the checksum on the backup of the site.
I would post a wayback machine link but XDA won't let me.
LineageOS and CM13 install just fine, so the tablet isn't bricked.
So, can anyone
-help me install this old build of CM10
-Tell me a way to use wiimotes with a newer OS
-direct me to some obscure build of android 4.1 or older (WiiMotes used to work perfectly in 4.1 for all devices) for flo (I doubt this exists but maybe)
Remember, my N7 is otherwise useless to me, so I don't really care what it takes to make this work.
rondnelson99 said:
For quite awhile now, I have had a nexus 7 (2013) wifi 16GB (flo). CM13 was my first custom rom. Since then, I have upgraded to the latest official Lineage 14.1 build. Now, I never use my old nexus.
Yesterday, I wanted to put together a little game station with it, centering around Wii remote support. I've read that the last android version to support the WiiMotes was 4.1. Unfortunately the N7 was launched with 4.3, so there is no official 4.1 build for the phone. I then read that CM used to have their own support for the controller. Can anyone verify if this is true? From the wayback machine, I downloaded and installed CM13, which worked fine, but while the WiiMote would "connect", it didn't actually do anything, and all for lights on the controller flashed indefinitely. Next, I went to the oldest stable build of CM available: CM10.2 (android 4.3). When I went into the latest version of TWRP to install it, I wiped everything except internal storage, and flashed the zip. I've tried this several times, and it always leads to one of 2 outcomes: either succeeds with the following output:
This results in an unbootable system.
Usually successful OS flashes have a lot more output than this, right?
Other times it fails. (Using the exact same file)
I'm having trouble reproducing this error wile I write this, but it was something along the lines of
Checking symlinks...
some symlinks failed.
I know the file was downloaded correctly, because it matches the checksum on the backup of the site.
I would post a wayback machine link but XDA won't let me.
LineageOS and CM13 install just fine, so the tablet isn't bricked.
So, can anyone
-help me install this old build of CM10
-Tell me a way to use wiimotes with a newer OS
-direct me to some obscure build of android 4.1 or older (WiiMotes used to work perfectly in 4.1 for all devices) for flo (I doubt this exists but maybe)
Remember, my N7 is otherwise useless to me, so I don't really care what it takes to make this work.
Click to expand...
Click to collapse
You have to wipe internal storage. To go back from anything 5.0 and up to anything lower.
Format data along with wiping internal storage.
So it looks like you tried everything except the actual solution... LoL.
Good luck
madbat99 said:
You have to wipe internal storage. To go back from anything 5.0 and up to anything lower.
Format data along with wiping internal storage.
So it looks like you tried everything except the actual solution... LoL.
Good luck
Click to expand...
Click to collapse
I didn't mention it, but I actually did wipe internal storage, and then transferred the zip from the computer via twrp.
rondnelson99 said:
I didn't mention it, but I actually did wipe internal storage, and then transferred the zip from the computer via twrp.
Click to expand...
Click to collapse
Format data (simple wipe usually isn't enough) and type yes in TWRP
madbat99 said:
Format data (simple wipe usually isn't enough) and type yes in TWRP
Click to expand...
Click to collapse
OK so I tried that, but it still doesn't work. Gets stuck on the Google screen when I reboot. I am supposed to wipe system first, right? Do I need to flash a 4.3 system image as well or something like that?
Thanks for all your help!
rondnelson99 said:
OK so I tried that, but it still doesn't work. Gets stuck on the Google screen when I reboot. I am supposed to wipe system first, right? Do I need to flash a 4.3 system image as well or something like that?
Thanks for all your help!
Click to expand...
Click to collapse
Wipe everything. Format data, and flash the ROM of choice. If it sits for a while on Google, force a reboot by holding power.
If that doesn't work try flashing a 4.3 factory image and then Boot it up then flash to CM10 ROM you want to use
make sure you haven't resized your partitions or anything crazy like that make sure your data is formatted to ext4 not f2fs. basically undo any changes you've done as you've been flashing ROMs for the life of this tablet
madbat99 said:
Wipe everything. Format data, and flash the ROM of choice. If it sits for a while on Google, force a reboot by holding power.
If that doesn't work try flashing a 4.3 factory image and then Boot it up then flash to CM10 ROM you want to use
make sure you haven't resized your partitions or anything crazy like that make sure your data is formatted to ext4 not f2fs. basically undo any changes you've done as you've been flashing ROMs for the life of this tablet
Click to expand...
Click to collapse
where can i get a copy of a 4.3 factory image ?
https://developers.google.com/android/images
Sent from my Asus P027 using XDA Labs