Related
As the subject says I just got through rooting, NvFlash/OneClick, and installing the CM7 mod for the G2x. I used update-cm-7.1.0.1-G2x-signed.zip and am now looking to add my Google account and get the apps.
I downloaded http://cmw.22aaf3.co...talk-signed.zip and installed it from recovery but I see no Google apps nor do I see anywhere in the mod settings to setup my Google account. Any help would be appreciated.
I was at stock.
Then I flashed Clockwork via NvFlash/Oneclick
I immediately performed a factory reset, partition clear, dalvik clear, battery stats clear
After that I installed CM7.
For previous ROMs I remember needing to run an "update.zip." Is this what I have overlooked?
This might sound dumb, but did you flash the gapps RIGHT after you flashed the rom? Or did you start up the rom and then decide you wanted gapps?
Cause that's a no-no.
SefEXE said:
This might sound dumb, but did you flash the gapps RIGHT after you flashed the rom? Or did you start up the rom and then decide you wanted gapps?
Cause that's a no-no.
Click to expand...
Click to collapse
That's exactly what I did. ;(
Wiped all and installed CM7 again then rebooted to recovery then installed latest gapps pack from http://goo-inside.me/gapps/. It appears that I have market now and it asked me to sign in with my gmail account, which I did but market won't connect.
The clock is effed up too. Clicking on google apps renders a force close. I just removed the apps panel icon from the launcher and have no idea how to get it back. WTF is happening?!
The phone is NvFlashed with Clockwork Recovery and the only two files on my "gold" card, if you will, are the CM7 zip file and the gapps file I got from goo-inside.me/gapps. As of now I've wiped EVERYTHING again and have ONLY installed CM7. Nothing else. No update.zip during flash process either. Just Stock > Clockwork > CM7. When flashing to previous mods on my old myTouch there was a need for the update.zip file is this not applicable here?
What's odd is on install #1 of CM there was no market. But now ~3 full wipes and installs later there is...
I fixed it!!
By installing Weapon... lol
l0lcats said:
I fixed it!!
By installing Weapon... lol
Click to expand...
Click to collapse
If you still want CM7...I believe you used the wrong gapps. The correct file is named "gapps-gb-20110828-signed.zip"
I think I read somewhere that the newtalk file is an update that u can flash after installing the original gapps file.
Sent from my LG-P999 using xda premium
I've been playing around with a Nexus S 4G that I have lying around and never used, and I've ran into a few problems, but you've all been helpful. I rooted all my old EVO 4G's without any problem, but the other day I rooted my NS4G using a one click/simple root and downloaded ClockWorkMod etc. But now for some reason It seems like I've almost lost my root? Is that possible? I still have the little unlocked symbol when booting up.
I've searched this forum and Google and haven't found anything, which could possibly be because I don't know what to look for. I've never had this happen :/
Currently running the stock 2.3.7
Nobody? I just need a little help.
Did you flash a superuser.zip after you installed clockworkmod?
SeeNah said:
Did you flash a superuser.zip after you installed clockworkmod?
Click to expand...
Click to collapse
I thought I had... But no lol
Thank you. Sorry for pretty much making a useless thread :/
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
SeeNah said:
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
Click to expand...
Click to collapse
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Slap-Yourself :) said:
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Click to expand...
Click to collapse
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
SeeNah said:
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
Click to expand...
Click to collapse
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Slap-Yourself :) said:
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Click to expand...
Click to collapse
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
stellar said:
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
Click to expand...
Click to collapse
I'm not sure if I'm supposed to post links to videos or not. But I'm in love with some of the features this guy has on his NS4G
https://www.youtube.com/watch?v=IKdyAm3CgHc
He said it was a nightly etc.
The hidden status bar and bottom menu hidden is amazing. I also like the inverted G-Mail and Facebook. Is this all separate from the Nightly ROM?
Hi All,
I have posted this on the GooManager thread but there hasn't been much activity there recently so asking here as well. Noob question on GooManager...I have the AOKP rom installed on my Sensation and GooManager notifies me of updates to my ROM every now and then. I just want to know if updating my ROM build with GooManager will reset all my custom ROM settings and preferences or will they all be preserved? I'd like to keep my ROM up to date but if it means spending all the time again to setup my preferences and icons/widgets/home screens etc. then I'd rather stick with what I have.
TIA!
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
lolmachine4 said:
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
Click to expand...
Click to collapse
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
freddysensation said:
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
Click to expand...
Click to collapse
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
lolmachine4 said:
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
Click to expand...
Click to collapse
Thanks lolmachine, for the benefit of anyone who might have the same question as me the following worked:
- Downloaded latest build of my AOKP Rom via GooManager
- Downloaded latest gapps package for my ROM via GooManager
- Boot to Recovery
- Flash new ROM file and then gapps package
- Restart.
My only question is, I didn't wipe davlik and cache so should I, and what difference does it make if I don't?
I used Goo the other day to flash, ummm, bugger, can't remember if it was an update or a new rom.
Oh now I remember, the latest one was an update to Bruce's Rom. I do believe when I tapped flash rom it booted to recovery (the one it installs) and I may have had to select "Install" from there, don't think so though. Either way, I used Goo to handle the install.
I didn't do a wipe. From what I've picked up, wiping is a good way to cover your butt. So if you're having issues and didn't wipe, you go back and do it all again with a wipe. Doing the wipe to start with means you can eliminate those types of issues from the start.
Someone can correct me if I'm wrong (which I probably am )
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
thisisadamh said:
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
Click to expand...
Click to collapse
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
AndroidSupporter318 said:
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
Click to expand...
Click to collapse
Thanks very much, downloading it now.
Help
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
all3rd said:
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
Click to expand...
Click to collapse
sorry man but i think you are talking for a samsung device am i right?
if yes then this is only for sensation/XE/4G devices
yasho170 said:
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
Click to expand...
Click to collapse
Simple.
Go to recovery.
For s-on you must enable smartflash.
Do a nandroid backup.
Dirty flash the update (meaning flash over the previous rom without wiping).
Dirty flash gapps (signed only).
Wipe cache + dalvik.
Reboot.
If it can't boot/run properly then you can just restore the backup or do a clean flash.
First off I'm not experienced in any way, got my Sensation unlocked, rootet and installed Sultanxda's 4.4.2 ROM for sensation. I'm on S-On, too, if anyone wonders.
Updating didnt affect my apps as far as I can tell. Everything seems to be the way as before and everything seems to be working.
What I did was download the ROM manually since the download with goomanager didn't work. I downloaded gapps as backup because I didnt have the zip on my SD, just in case anything would go wrong.
You only need to boot into recovery, with S-On make sure smartflashing or something like that is on, select the zip, flash it and then select wipe cache +dalvik.
It's pretty much what AndroidSupporter318 wrote, just wanted to give feedback and say what I did in detail in case anyone was still wondering.
LxMaD
I guaranted 4EXT Recovery for this type of problem. U don't need to boot into recovery and work with 4ext is very simple.
Hi all!
First off, I apologize in advance if this is a dumb question. But basically, I'm running a rooted One and I've been waiting for the official nightly builds for CM12, but now that they're finally here, I can't seem to flash them. I keep getting random errors when I try. I'm currently running on the latest 11s update that was OTA with TWRP, and I've unlocked my bootloader and everything. Anyone have any input? I've read in some places that you can't update to the CM12 nightly from 11s, and if that's the case, what's the best way to go from 11s to 11 without losing any data?
Thanks in advance!
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
timmaaa said:
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
Click to expand...
Click to collapse
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
CaptainBlackbeard said:
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
Click to expand...
Click to collapse
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
timmaaa said:
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
Click to expand...
Click to collapse
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
I'd wipe even going from CM11 to CM12.
Transmitted via Bacon
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
No, can't, unless you wait for CM12s. But I guess you can backup everything with Ti Backup then restore it back, No harm doing that though.
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
dirty flash
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
dd2 said:
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
Click to expand...
Click to collapse
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
timmaaa said:
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
Click to expand...
Click to collapse
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
dd2 said:
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
Click to expand...
Click to collapse
If you're just updating the same ROM (flashing a newer build of the exact same ROM) you can usually dirty flash. Any other time you must clean flash.
timmaaa said:
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
Click to expand...
Click to collapse
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
CaptainBlackbeard said:
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
Click to expand...
Click to collapse
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
timmaaa said:
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
CaptainBlackbeard said:
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
Click to expand...
Click to collapse
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
CaptainBlackbeard said:
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
Click to expand...
Click to collapse
Did you read the second part of my post??
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
The new version you linked worked!
Now I'm attempting a restore through TItanium. How long does it usually take? It's been sitting at 0% on the first app for a little while now.
Hey everyone,
Thank you all for reading this...
Today, I wanted to update my phone from cm-12.1-20150429-NIGHTLY-bacon.zip to cm-12.1-20150502-NIGHTLY-bacon.zip and after optimizing all 199 applications the lock screen appeared and everything seemed fine. However a second later, a pop-up appeared delivering the crash of the google play services. After pressing on "ok" (the only option), the phone switched off and began optimizing the apps again and again, showing the boot sequence in-between. After a while, I tried to install the update again through TWRP and I failed again. Then I tried to restore my backup from the 19th April I had probably made with Nandroid Backup (not exactly sure) and I failed again. Now I have turned off my phone entirely so that it won´t get too hot.
Does anybody know how to fix this issue (preferably without wiping)? And do you think, should I stay with the nightlies or switch to Cyanogen OS 12 (how?)
Best regards from the android newbie,
George (ambach10)
Try reflashing slim's gapps package.
Edit: Link to thread: http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Follow this steps to first turn on your phone https://forums.oneplus.net/threads/guide-how-to-revert-back-to-cm11s-from-oxygen-guide.290605/
It's CM11S.
Easy way to revert back.
ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
I've had this issue before. To fix it, I used these gapps, did a full wipe, then flashed everything all over again and it was working without any problems.
Also, I ended up just switching over to COS12 and am still running that. If you want, you can get that here.
ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Also, make sure you are running latest version of TWRP recovery (or whatever recovery you are using)... there are compression incompatibilities with some of the older versions.
Thanks everybody!
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
ambach10 said:
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2766186 Here is the TWRP thread 2.8.6.0 is the latest. You can update using the TWRP Manager app available on the play store.
ambach10 said:
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Click to expand...
Click to collapse
I wiped everything other than Internal Storage, flashed the rom, flashed the gapps, and then rebooted and it booted just fine.
ambach10 said:
Thank you all for helping me out:
frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
It works for all lollipop based ROMs.
I hope now your device is working fine.
Sorry for replying late.