Trouble installing themes on CM 13 6.0 - Moto G Q&A, Help & Troubleshooting

Hello, as you can tell, I have Moto G 1st generation with CyanogenMod 13, the problem is that of all of the themes I've downloaded, only 2 could be installed, I tried to see on CatLog but can't find the specific problem and now I think it's driving me crazy, I'm kinda noob at these things so please if you can give me a simple explanation I'll be really grateful, thanks in advance!

Hi,
Could you give us some examples of themes you're trying to install ??? It could be helpful to know them...

Any theme I try to install, it really doesn't matter which, they all say cm13 or 12.1 but it always says failed to install x theme

Ok,
so it seems something is corrupted in your CM, probably Theme engine...Don't know precise solution for that, sorry. You can make some research in that way but even not sure if it's the real issue (theme engine)
Imao, better to choose a more radical solution...
Make a backup of your datas, even of the entire firmware (like that, you have an entire backup solution, without theming, for sure, but ready to go for the rest), make a full wipe and install fresh CM.
You can also install, after a first full wipe, stock LP 5.1 from here : http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510, let it boot once and do your wipes again before installing your CM13, it always worth it...
Don't forget to wipe your Cache/Dalvik Cache after each installation.
Recommended GAPPS here : http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
Pico or Nano are enough but it's your personal choice
Keep us informed

Related

Little Help[droidx roms]

Hello Everyone,
So Yesterday i finally decided to give roms and themes a chance . So i downloaded different types of roms and themes but each had atleast one issue in them or didnt have correct files or wouldnt let me backup my contacts and apps with backup assistance & google. I have wiped off my data atleast 10 times in the past few hours.
So today i come here to ask if you guys could help me by giving me the download link [With instructions if possible] to a rom that looks
-Clean
-Pretty Fast
-Has No Bugs / Issues With it
-Will Let Me Restore Things i need
If anyone could help me out i will be ever so thankful ! i just want a better look for my droidx.
It's going to be hard finding one with out bugs but must bugs around are minimal that most people don't notice when I made the jump from stock to rooted I went with liberty and am still with liberty take a look at liberty google searching droid x liberty will take you to the main forum for it and the way to install it
Sent from my DROIDX using XDA App
Sure
IERICI said:
Hello Everyone,
So Yesterday i finally decided to give roms and themes a chance . So i downloaded different types of roms and themes but each had atleast one issue in them or didnt have correct files or wouldnt let me backup my contacts and apps with backup assistance & google. I have wiped off my data atleast 10 times in the past few hours.
So today i come here to ask if you guys could help me by giving me the download link [With instructions if possible] to a rom that looks
-Clean
-Pretty Fast
-Has No Bugs / Issues With it
-Will Let Me Restore Things i need
If anyone could help me out i will be ever so thankful ! i just want a better look for my droidx.
Click to expand...
Click to collapse
I will help where I can and I am sure others will be chiming in soon..First what version are you on Froyo or the GB Leak? Are you rooted, I assume you are but you know what they say about assuming...In the forums that these exist I assure you there is much help...I will add some others once I know your setup no need to post something that will not work for you....
ROMS:
Darkslide 4.2 ( my personal favorite for Froyo)http://www.mydroidworld.com/forums/droid-x-roms/6155-darkslide-v4-2-a.html
Apex Latest version for Froyo and he has a Aplha 2 out for GB but you have to follow him on twitter to get it as he doesn't want it posted out any place as far as I know of
http://androidforums.com/droid-x-all-things-root/277224-rom-apex-v1-4-1-droid-x-droid-2-refinement-ease-use-2-22-2011-a.html
my preference is still fission 2.6.1
google "team defuse"
donate and get fission rom manager (it is an apk, you will have to put the download on your sd card and use a file manager from on the phone to install the apk and run it).
donwload fission 2.6.1 be (black edition)
figure out where it is on your sd card
boot into clock work (recovery) and go to advanced, wipe dalvick, wipe battery stats
back out and wipe data and wipe cache
mounts; mount system and mount data (will say unmount when done)
install zip, chose zip, fission 261
after done reboot and set up.
reboot phone again for good measure.
find a theme

[Q] Trying different roms

I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.
Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.
NeverToLate said:
I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.
Click to expand...
Click to collapse
By all means go for it! I have a few tips for you, as one flasher to another
As redpoint said, each time you flash a new ROM you are starting from scratch. This only refers to your personal data and ROM settings, though. There are a few ways to guarantee that you won't be spending a long time configuring each ROM:
Cloud Storage is your friend! I personally use Dropbox to save anything important to my daily use since I can easily pull up documents stored there from anything connected to the internet. There are much more secure options to store files on the cloud, but you have to pay for the more secure options, and security is not of top importance to me (since I just store homework assignments and basic documents).
Use Google Backup! When you flash new android ROMs, there is a prompt that asks you if you would like to backup your phone to Google's servers. I usually hit yes to this prompt. After you have done this once, when you flash a new ROM and enter your Google account, any Play store apps you had installed will be redownloaded (including any personal data associated with the app, IF it's developer has enabled this feature). It's not a perfect way of restoring your apps, but it sure beats re-entering all of your data each time you want to try a new ROM.
Use services to store your contacts! I took a few days to enter ALL of my contacts into my Gmail account, and it was one of the best decisions I have ever made. Each time I restore my phone, I have all of my contacts available. People who complain about losing all of their contacts along with their phone need to learn about this point.
Remember that your SD card partition stays intact between ROMs! Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Avoid using tools like Titanium Backup to restore apps! For a while I decided to use Titanium to restore apps. After a while I realized that all of the errors I was experiencing was the result of mismatched phone IDs, cache errors, and a bunch of other small glitches caused by Titanium backup. It is not the fault of TB and it is still a useful tool, but using Google backup to restore your apps is much cleaner and will result in fewer errors.
Save your text messages! Titanium Backup has the option of saving your text messages as a .xml file, but this is more complex than just using play store applications like SMS Backup & Restore. If you don't back up your SMS, you will look totally unpopular when you keep flashing your phone (and have no text messages at all)!
I hope this list helps you out in your flashing journey. Don't be afraid to try new things, and remember that if you can get into recovery mode, you will be fine (ESPECIALLY if you back up your data in the ways I described).
Thanks for tips
As far as saving everything as you posted. I don't have really that many documents I need and I am a big fan of dropbox haha. As far as my contacts any contacts I put in my phone automatically go to my google account so they always transfer over for me.
I usually delete most text messages at night and that's when I will flash these ROMS as I will not be texting anyone later in the night so, no worries there.
I really only have a few apps that I use, so even if they don't reinstall it doesn't take long to find em.
My main focus of now is just downloaded the roms I want and putting them all on my sd card. Whenever I have time to flash em all I will set them up kind of the way I want em with my apps, then set up the next ROM.
When that process is complete I'll just test each one for a few days/weeks till I find the perfect one for me haha.
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?
redpoint73 said:
Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.
Click to expand...
Click to collapse
I don't have to do reset between nandroid backups do I?
NeverToLate said:
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!
NeverToLate said:
I don't have to do reset between nandroid backups do I?
Click to expand...
Click to collapse
Going between nandroids? No, recovery is going to overwrite the user data with the user data from the nandroid, so I don't think you need to worry about it.
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
gridlock489 said:
Remember that your SD card partition stays intact between ROMs![/B] Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Click to expand...
Click to collapse
In theory, that is supposed to be true. But many people (including myself) have had instances of some or all of the SD contents erased or corrupted. The exact cause has still not been found, but possibly just a bug of the phone. I've had it happen several times now. If you have anything irreplaceable on the SD, I would suggest backing it up to your computer, Dropbox, or whatever, before flashing anything. This includes photos of videos that you took, and anything else not easily replaced. Backing up one known good nandroid is not a bad idea, either, just in case.
gridlock489 said:
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!
Click to expand...
Click to collapse
I don't plan on flashing any radios. As I did with the inspire, and it messed up my service bad and I didn't know how to fix it again. I didn't now too much about it then. Which I still don't but I know more now than I did then.
NeverToLate said:
Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Be sure you are using TWRP, and not Clockworkmod. CWM has known problems, as our device is not really supported (its just a port) and also USB mount is not working (which may be relevant if you run into problems such as the SD corruption I've mentioned).
I will be using TWRP. If I'm not mistaken I did a nandroid back up of stock rooted. I plan on copying my sd card to my computer external hd just for safety. I have a HTC One X Folder that I will put my roms in stuff in as well.
I will try to take screenshots of battery life for each day I use a certain rom. The battery probably won't go below 30% but screenshots would give a good idea to other people. And I will try to update my thoughts on each rom. Not promising I will get to but I will try.
I am going to download and check md5s today.
Idk if I will flash one tonight or not.
Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.
NeverToLate said:
Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.
Click to expand...
Click to collapse
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though
gridlock489 said:
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though
Click to expand...
Click to collapse
Blue is actually my favorite color lol. Could you point me to the CM10 rom?
Here are the roms I am downloading as of now:
KingCobra
Nocturnal Special Edition
Viper
Clean Rom 5.0
Any other ideas on maybe one or two more roms?
I bookmarked that link you posted. I prob won't do much with themes until I find the right ROM. Even then the most I usually do is wallpapers lol. But will look more into after finding a ROM.
What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.
NeverToLate said:
What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.
Click to expand...
Click to collapse
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.
gridlock489 said:
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.
Click to expand...
Click to collapse
What's the different in the Nightly and Experimental? I would like to try a CM since I never have before. Probably will be the last one I download
Also on the CM10 forum it says something about find Gapps? Is that something I search for and download and flash?
Update
Downloaded Roms with md5 checked and now on my sim card:
Clean Rom 5.0
CM10
King Cobra
Nocturnal Special Edition
Viper
Just need help on what I need to download for Gapps to install CM10
What Rom should I test first?
King Cobra
Viper
Nocturnal
I'm on nocturnal and loving it.
Sent from my HTC One X using xda premium

[GUIDE][ROM FLASHING][WALK THRU][WIP] Easy to do!

This should help anyone who keeps having flashing issues.
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON SDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)(OR WHATEVER YOU USE)
apps.zip not included. Create your own.
Flashing the rom:
1. Backup current rom (to the sdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues
[FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR SYSTEM]
3. Flash the rom
4. [TW roms this step is not needed] Flash gapps for aosp roms if applicable.
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
TIPS:
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
reserved
What's quick about this it's pretty much the same as any rom op
Not for the old timers, this is basically a quick ref for the newer peeps.
Most of us know these things, but there are others that don't.
Don't worry, the post will get buried sooner or later.
Thanks
thanks for writing this up.
maybe this would be a decent sticky for the QnA section?
maybe add a touchwiz section? an explanatinon of what aroma installer is? With a warning that some of the roms are close to 1gb in size? (at least when i tried some a while ago, not sure if they slimmed down.
adding that the OP is always a good source for info of any rom
TheAxman said:
Not for the old timers, this is basically a quick ref for the newer peeps.
Most of us know these things, but there are others that don't.
Don't worry, the post will get buried sooner or later.
Thanks
Click to expand...
Click to collapse
Hey Didn't you say your wife has an s3?
if so... what have you tried you like best?
1. Rom
2. kernel
3. Other/mods etc...
Thanks...
sloanster said:
Hey Didn't you say your wife has an s3?
if so... what have you tried you like best?
1. Rom
2. kernel
3. Other/mods etc...
Thanks...
Click to expand...
Click to collapse
Its mine..g4 hers. Roms. Running M.O.A.R for the last few months on it. Modded heavily.
ddurandSGS3 said:
thanks for writing this up.
maybe this would be a decent sticky for the QnA section?
maybe add a touchwiz section? an explanatinon of what aroma installer is? With a warning that some of the roms are close to 1gb in size? (at least when i tried some a while ago, not sure if they slimmed down.
adding that the OP is always a good source for info of any rom
Click to expand...
Click to collapse
Your saying that people may think this is a aosp type flash?
TheAxman said:
Your saying that people may think this is a aosp type flash?
Click to expand...
Click to collapse
just saying that the process is slightly different and the extra info would help
gapps not required mostly. buti t seems as if you added that, or i missed it earlier when i posted.
hehe I added it, by all means, if anyone wants to participate in adding anything to the guide, feel free to jump in with some advice, good things come from others.
[updated: 07-12-2013]
Recovery differences?
Does anyone have any opinion/knowledge on the differences between CWM and TWRP? I mean, I've used them both. I know the difference in appearance, and use. But is there any difference in reliability? Is one better for TW or AOSP? Is one more reliable? Better at different things? Some devs recommend one and some another. Opinions? Experiences?

[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw)

LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05
reserved
Hallelujah!
Is this the eighth or ninth life of this great phone?
@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
Nice job! Wich partitions can I mount as f2fs?
Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!
Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs
Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.
Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good:

No space in system partition.

I had my oneplus one unused for a while and wanted to make some use out of it.
So i installed twrp and tried flashing lastest custom rom into it.
I was successful in flashing official Lineage and rr remix to it,but whenever i try to install gapps,it says no enough space in the system partition.
I tried resizing it through the wipe menu but that somehow doesn't work,i.e. the size of system remains the same,which i tried after installing os.
I hope this info can atleast give you a brief idea what i am talking about,any help is appreciated.
Use recommended by Lineage OS team MindTheGapps.
Opengapps doesn't fit anymore.
ImmortAlex said:
Use recommended by Lineage OS team MindTheGapps.
Opengapps doesn't fit anymore.
Click to expand...
Click to collapse
This was pretty straight forward,how did i miss that.This worked for me,installed with Lineage OS.Thank you very much.
I tried installing lineage 18 onto one of my other device for which i was able to install open gapps pico,i don't know why it won't work for opo.
As i am not able to increase my system partition from twrp,i think there is some different issue aswell,i don't have enough understanding of these stuff to understand what the problem is.
I tried installing open gapps with rr remix aswell,but recieved the same error.
Anyways, thank you so much,i really appreciate your help.
Hi, i making this video showing to how to resize system partition on opo u can check it out here:
alprtewwqfr said:
Hi, i making this video showing to how to resize system partition on opo u can check it out here:
Click to expand...
Click to collapse
I will try this after some time,i don't have enough time right now for this. Thank you
ok! If you have any problem fell free to ask me!
Have a look at guide to re-size system partition at: https://forum.xda-developers.com/t/...system-partition-and-maybe-even-more.4153599/
Only issue I had was being able to install Magisk. Couldn't use TWRP and patched boot.img method which worked a treat.

Categories

Resources