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.
Related
hi, im new to rooting. i've just rooted my desire with cyanogenmod 7, and the android market doesn't seem to work? i can't download google map or any other apps from it. any help? thanks alot.
any help? thanks
i guess you tried rebooting? that worked the last time I had problems with cyanogenmod, that being said i don't use it daily so I'm no expert
yup, i tried rebooting but it didn't work too..
Try wiping the cache, if that doesn't work, do a factory reset and wipe everything, do a fresh install and put gapps on.
does that mean i have to flash it back to stock rom and start all over again?
Have you tried to flash the G-apps again? Here's the link of the newest one: Google apps choose the CyanogenMod 7 (Gingerbread) version and flash it with Rom Manager or Recovery.
have you modified the .zip file , deleting some files for exemple?
I done it, and removed "Package Installer.apk" one time, so downloads were beginning but stopped each time immediately
Market download issues
I'm having similar issues using GingerVillain 1.9. Small market updates are downloading without issue, larger ones such as the latest Google Maps update are giving the message "download unsuccessful". I had similar issues when the market was updated from the old style, and wonder whether google are tinkering in the background.
Fraize1 said:
Have you tried to flash the G-apps again? Here's the link of the newest one: Google apps choose the CyanogenMod 7 (Gingerbread) version and flash it with Rom Manager or Recovery.
Click to expand...
Click to collapse
i had tried to flash it again before but it doesn't work.
fabulous69 said:
have you modified the .zip file , deleting some files for exemple?
I done it, and removed "Package Installer.apk" one time, so downloads were beginning but stopped each time immediately
Click to expand...
Click to collapse
i don't think i've removed any of those files..
I am having similar problems. I have installed the gapps, but it only installs a couple of google apps. When I try to install from the market some install fine but others (angry birds for example) don't. I see the downloading icon for split second then it goes away and the download stops.
Any ideas?
Well installing DarkTremors script did the trick
http://forum.xda-developers.com/showthread.php?t=715940
cb8rwh said:
Well installing DarkTremors script did the trick
http://forum.xda-developers.com/showthread.php?t=715940
Click to expand...
Click to collapse
how does it help?
i have the same issue , it's stuck with ( Downloading... ) what ever the app is
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.
Hi guys, please direct me to the correct place if this is not it. I am currently running revolt and I want to flash a new ROM. I had a status 7 error, which I have had before and I fixed that by updating CWM. But here is where I get hung up. I get an error that I thought was related to ROM manager not having the correct permissions. I went to update my supersu and give it the correct permissions, but I decided I wanted to change to Superuser and uninstalled supersu. I have now having an error where I can not download anything from he play store because my memory is full. When I check my memory it does not add up. I have 12gb of space and a I am using roughly 4 gb of that. If anyone knows of a way that I can fix the issue so that I can update my CWM and flash a new ROM it will be greatly appreciated!
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Guynan said:
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Click to expand...
Click to collapse
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
eviltweak said:
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
Click to expand...
Click to collapse
That is really confusing. When it says wrong permissions, it won't mean the root managing app has the wrong permissions, it means that the system has wrong permissions somewhere. This cannot be fixed through Supersu or Superuser. If you can still go into recovery, go into advanced, and then 'fix permissions' and that should fix issues if that is what it pertains to.
Because Android it is based off a Linux kernel, it is very picky with the permissions you give it. Too little and it doesn't work. Too much, and it doesn't work.
Let me know how you go.
I don't think I explained this very well in my first post. My issue lies when I try to flash the new version of cwm. I get this screen.
I went into recovery and advanced and I don't have an option that is fix permissions?
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Guynan said:
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Click to expand...
Click to collapse
I am running CMW 6.0.3.7. When I go to advanced all that I see is Reboot recovery, Reboot to bootloader, Power Off, Wipe Dalvik Cache, Report Error, Key Test, Show Log, *******Go back*******.
My recovery works, its just not up to date so when I go to flash a new ROM I get a status 7 error. I have had this issue before and I fixed it by updating my recovery. BUT this time when I go to flash an updated version of CWM I get the screen that I posted above.
the status seven error is usually to do with the updater-script. So make sure the ROM you want to flash is for your device, if it isn't (which may be why you have run into issues) don't flash it. But if you are sure it is, go into the ROM, META-INF>Android>Google>Updater-script (the android and google may be the other way round, it won't take you long to find it) And then open the updater script in a text editing program and remove the first few lines of stuff. It will have the words "assert" "getprop" and looks different to the rest, so just delete that section, and rezip if you have to, and try reflashing. But if that doesn't work and the issues are becoming intrusive, a full reset might be in order.
So last night i flashed a rom and when it installed i tried to add a google account. I tried to add an existing account. when i added my information it says that i couldn't sign in" there was a problem communicating with google servers." this means that i can't go into the play store. so i went into the TWRP menu to reflash a rom and it doesn't recognize the .img file that is on there. so basically right now i an app-less. any help is welcomed
i still can make calls and text, and my wifi still works. just no connection to google
my device is HTC One M8 AT&T (rooted and boot loader unlocked)
and i have a Mac computer if that helps
Delet your existing Google account from your phone.
Go into Settings > Apps > All and clear cache and data on all Google services:
Play Store, Play Services, Maps, G+ - the works.
Then restart and try again to add your Google account.
berndblb said:
Delet your existing Google account from your phone.
Go into Settings > Apps > All and clear cache and data on all Google services:
Play Store, Play Services, Maps, G+ - the works.
Then restart and try again to add your Google account.
Click to expand...
Click to collapse
I just tried that and it didn't do anything different. still can't connect to google
rps13jp said:
I just tried that and it didn't do anything different. still can't connect to google
Click to expand...
Click to collapse
Which rom did you flash? Did you clean install? Does that rom require you to flash gapps?
berndblb said:
Which rom did you flash? Did you clean install? Does that rom require you to flash gapps?
Click to expand...
Click to collapse
I put Android Revolution HD as the rom i tried to install. Its not the first time i installed this particular rom. I didn't have an issue last time. I'm not sure i did a clean install as I'm pretty new to this
rps13jp said:
I put Android Revolution HD as the rom i tried to install. Its not the first time i installed this particular rom. I didn't have an issue last time. I'm not sure i did a clean install as I'm pretty new to this
Click to expand...
Click to collapse
That could be it then. Something left behind from another rom install.
As a general rule, if you switch between roms - even from the same base - I would always clean install. Only updates of the same rom are ok to dirty flash.
For a clean install (if you have TWRP) just choose Wipe and swipe the button, then re-flash the rom. You will have to install your apps and tweaks again, but that's a small price to pay for everything working.
berndblb said:
That could be it then. Something left behind from another rom install.
As a general rule, if you switch between roms - even from the same base - I would always clean install. Only updates of the same rom are ok to dirty flash.
For a clean install (if you have TWRP) just choose Wipe and swipe the button, then re-flash the rom. You will have to install your apps and tweaks again, but that's a small price to pay for everything working.
Click to expand...
Click to collapse
if it was that simple I would have done it when I go I to twrp it doesn't recognize the .img file soit won't load ir. S o it's pretty stuck. I need to get rid of everything and start fresh
rps13jp said:
if it was that simple I would have done it when I go I to twrp it doesn't recognize the .img file soit won't load ir. S o it's pretty stuck. I need to get rid of everything and start fresh
Click to expand...
Click to collapse
What are you trying to flash? As far as I know TWRP can only flash zip files....
berndblb said:
What are you trying to flash? As far as I know TWRP can only flash zip files....
Click to expand...
Click to collapse
ill try re-downloading the file directly to my phone instead of transferring it from my comp to the phone. (which would automatically un zip the file.
how do i ensure a clean install
rps13jp said:
ill try re-downloading the file directly to my phone instead of transferring it from my comp to the phone. (which would automatically un zip the file.
how do i ensure a clean install
Click to expand...
Click to collapse
Read post 6
berndblb said:
Read post 6
Click to expand...
Click to collapse
I figured it out. Basically because I used my Mac to transfer the ROM to my phone it was unzipped and that made twrp not see it as a ROM its all fixed now
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