Related
Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?
Depends...are you using the CM10 gapps?
Also, what version of TWRP are you using?
Yes, CM10 (tried others too) and TWRP 2.
sleep_debt said:
Yes, CM10 (tried others too) and TWRP 2.
Click to expand...
Click to collapse
2.0? 2.1? 2.2?
Also, are you checking the md5s? It's a longshot but worth looking into.
Which version of gapps are you using?
TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?
sleep_debt said:
TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?
Click to expand...
Click to collapse
Make sure it's this version.
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Sent from my Nexus 7 using Tapatalk 2
TWRP 2.2 is still quite new and it is yet unknown of all the bugs that may come with it. Have you tried an earlier version?
Did you find a solution to your problem yet?
sleep_debt said:
Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?
Click to expand...
Click to collapse
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
vmallder
vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.
vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
nmaiorana said:
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.
Click to expand...
Click to collapse
Not sure what this issue is, still - have tried every gapps & TWRP version I could find, but TWRP also throws an error when trying to flash gapps.
Also, sideloading the gapps just doesnt work, either, making me think the actual OS flash might be damaged? Been busy lately but plan on just flashing another OS and seeing if that clears it up.
If anyone has any other tips, it would be much appreciated!
Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?
What errors do you get when trying to flash gapps or ROMs?
sleep_debt said:
Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?
Click to expand...
Click to collapse
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.
callmeshulah said:
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.
Click to expand...
Click to collapse
That's the version of TWRP I'm using; the error I'm getting when flashing anything is:
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip 'whateverthefileis.zip'
TWRP errors
I agree with nmaiorana, cm-10 from linaro is not throwing errors like you seem to be running into. Latest version I am using is: 10-20120831-2228. the gapps v that works with this rom is: gapps-jb20120726. In TWRP after clearing cache and dalvik cache, goto to Install, click on the ROM you want to install, then go back to install and click on the gapps file, then slide the button to the right. You can install multiple flash files this way in TWRP. See if that works.
[email protected]@dog
If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.
Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.
soupmagnet said:
If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.
Click to expand...
Click to collapse
kinfauns said:
Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.
Click to expand...
Click to collapse
will try these in the next few days and see if anything works.
btw, ive tried every recent rom/gapps with no luck, so it doesnt seem to be a version-issue.
I've been running albinoman's AOSP JB Rom for a while now.
However, when upgrading from RC2 to RC3, I receive an error pretty early in the installation.
Installing AOSP Android 4.1.1
Creating symlinks
Setting permissions
set_perm: some changes failed
E:Error in /sdcard/clockworkmod/download/jellbeanrc3/Jellybean-Inc-RC3.zip
(Status 7)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I've been installing roms for a long time, and haven't run into this problem until now.
Tried the installation several times, and always run into the same problem. The error makes it impossible to boot, so I have restore my RC2 backup.
I really want to run this, and it's been the cause of quite a bit of frustration this past week. Thanks for your time.
Did you re download and check md5?
PonsAsinorem said:
Did you re download and check md5?
Click to expand...
Click to collapse
I re downloaded twice. And I thought it always checked md5, it's at least never had a problem when it did..
Hypherism said:
I've been running albinoman's AOSP JB Rom for a while now.
However, when upgrading from RC2 to RC3, I receive an error pretty early in the installation.
Installing AOSP Android 4.1.1
Creating symlinks
Setting permissions
set_perm: some changes failed
E:Error in /sdcard/clockworkmod/download/jellbeanrc3/Jellybean-Inc-RC3.zip
(Status 7)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I've been installing roms for a long time, and haven't run into this problem until now.
Tried the installation several times, and always run into the same problem. The error makes it impossible to boot, so I have restore my RC2 backup.
I really want to run this, and it's been the cause of quite a bit of frustration this past week. Thanks for your time.
Click to expand...
Click to collapse
Install from twrp cwm is a broken recovery
Sent from my ADR6300 using Xparent Red Tapatalk 2
Status 7 usually means there is a problem with the updater script in the rom file. What recovery are you using? Try TWRP if thats not what your using. Either the rom developer made an error in the rom zip, or the file is getting corrupted during download.
Also the md5 is not automaticly checked, you must check it your self.
Thanks very much for your assistance fellas. Unfortunately, I have an entirely new problem on mis manos.
So, after the most recent failure of the rom to install, I restored my backup of my RC2 rom.
It wouldn't get past the nexus boot animation. (I waited for 15+ minutes, I don't know why) So I
went back to recovery, and attempted to install RC3 again.
No problems installing. When I booted up however, after it had notified me that it was "Finishing installation" and that Android was "upgrading"
I was met with a plethora of errors. android.process.acore has stopped etc.
So, I ended up doing a factory reset/wiped user data.
The reinstallation of RC2 as well as the upgrade to RC3 went off without a hitch. So thanks guys, but I did something I didn't want to do, and it worked out in the end.:good:
cmlusco said:
Also the md5 is not automaticly checked, you must check it your self.
Click to expand...
Click to collapse
Depends on how you get it. If downloaded from the Goo Manager app, the app auto checks md5.
Hypherism said:
The reinstallation of RC2 as well as the upgrade to RC3 went off without a hitch. So thanks guys, but I did something I didn't want to do, and it worked out in the end.:good:
Click to expand...
Click to collapse
Good to hear it worked out for you.
Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
Dear Community,
this is my first post on XDA-devloppers.
I ask you for help as y have a serious promlem with CM 9.1 on my xperia arc.
I flashed CM on my phone using the latest stable rom downloaded from the official cyanogenmod website (cm-9.1.0-anzu.zip)
Everything worked perfectly and i was delightet.
Unfortunately, after two days my phone crashed.
By crashed i mean that it first reacted very slow then froze. After this, the screen went black (backlight on) an then dark.
no button could get me back to lockscreen.
then suddenly the phone rebootet.
this happened every time about one minute after booting my phone.
As the problem didn't seem to get away i decided to reflash it:
wipe SD
delete davlik cache
reseting to factory
and then istalling the same rom and gapps from zip
everything worked fine again, but after one day i got the same problem again.
what can I do to fix this?
I would appreciate any kind of help
and excuse me if this isn't the right forum (search also, didn't help)
sincerly,
PraetorAce
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
popthosegaskets said:
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
Click to expand...
Click to collapse
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
PraetorAce said:
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
Click to expand...
Click to collapse
You can try the nightly versions if the stable doesn't work for you.
Take out the boot.img inside the ROM zip and flash with fastboot. Then put ROM zip onto SD card and flash with CWM.
僕のLT18iから送られてきた
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
PraetorAce said:
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
Click to expand...
Click to collapse
Odin is for Samsung devices only. If CM9.1 doesn't work for you then you might want to try CM10.
僕のLT18iから送られてきた
Hi,
a few days ago moved from stock to twrp-3.0.2.2-klte, lineage-14.1-20170125-nightly-klte-signed and open_gapps-arm-7.1-micro-20170125.
So far I'm facing issues with APK installations. I always get the "parsing problem message" during manual installation. The files are not corrupt, I enabled untrusted apps as well as USB-debugging.
I went through some posts. Reinstalled GAPPS (micro and full), wiped everything, reinstalled the whole ROM and even tried last cm-14.1-20161225-NIGHTLY-klte but always get stuck with the same message... there is a problem parsing the package.
UPDATE: Same situation with lineage-14.1-20170131-nightly-klte-signed.
Has someone an idea? Would really appreciate some help. Thanks.
Device: Samsung Galaxy S5 (G900F/ klte)
MDAman said:
Hi,
a few days ago moved from stock to twrp-3.0.2.2-klte, lineage-14.1-20170125-nightly-klte-signed and open_gapps-arm-7.1-micro-20170125.
So far I'm facing issues with APK installations. I always get the "parsing problem message" during manual installation. The files are not corrupt, I enabled untrusted apps as well as USB-debugging.
I went through some posts. Reinstalled GAPPS (micro and full), wiped everything, reinstalled the whole ROM and even tried last cm-14.1-20161225-NIGHTLY-klte but always get stuck with the same message... there is a problem parsing the package.
UPDATE: Same situation with lineage-14.1-20170131-nightly-klte-signed.
Has someone an idea? Would really appreciate some help. Thanks.
Device: Samsung Galaxy S5 (G900F/ klte)
Click to expand...
Click to collapse
How exactly did you "move from stock"? Clean/dirty flash? Use migration build? Details please.
I just installed lineage-14.1-20170131-nightly-klte-signed with open_gapps-arm-7.1-stock-20170131, rebooted, setup all my settings (Declined the restore from previous backup on first start) and went to Play to install all my apps. Rebooted to flash addonsu-arm-signed, then rebooted again and flashed SuperSU-v2.79-201612051815.
All working fine for now on my G900T and I had CM13 prior to this. From TWRP wiped all but the ExternalSD, rebooted to recovery and wiped again all but ExternalSD, then did a Factory Reset and installed LOS. The only thing not working is FolderMount, but I was expecting that until the next update.
Sent from my SM-G900T using Tapatalk
jhedfors said:
How exactly did you "move from stock"? Clean/dirty flash? Use migration build? Details please.
Click to expand...
Click to collapse
I've flashed TWRP using Odin3, booted into recovery, fully wiped stock (sys, data, cache, int sd, etc.) and installed LineageOS rom + GApps.
Reflash again and check md5 of your dowload rom agains the rom provided by lineage website.
This is md5 of the latest rom version 20170131
7305fd079020c0f872148241b437ceaa
md5sums are provided to verify the file download was successful. If you'd like to verify the file has not been tampered with, check its signature instead.
hanzaz said:
Reflash again and check md5 of your dowload rom agains the rom provided by lineage website.
This is md5 of the latest rom version 20170131
7305fd079020c0f872148241b437ceaa
md5sums are provided to verify the file download was successful. If you'd like to verify the file has not been tampered with, check its signature instead.
Click to expand...
Click to collapse
Done that. Still the same error.
Installed lineage-14.1-20170207-nightly-klte-signed (MD5 is fine). APKs still can't be parsed.
First I updated. Afterwards I wiped and tried clean install. No difference.
I have the exact same issue. Moving the apk from external to internal storage solves the problem though. Seems to be a hickup in the binding of the SD memory.
_-M-_ said:
I have the exact same issue. Moving the apk from external to internal storage solves the problem though. Seems to be a hickup in the binding of the SD memory.
Click to expand...
Click to collapse
simple yet elegant.
Thank you very much.