Anyone installed Open GApps on CM 12.1 CAF version?
Today I decided to update ROM, I installed first cm-12.1-20150530-NIGHTLY-hammerheadcaf.zip then open_gapps-arm-5.1-20150529.zip stable build, when flash completed and press reboot button Nexus 5 stuck on Google logo.
Then I restored my backup and just flashed cm-12.1-20150530-NIGHTLY-hammerheadcaf.zip and now everything works perfectly.
I wonder if anyone try Open Gapps with CM12.1 CAF version and if it happened only to me or this is bug of Open Gapps?
Clean install resolved my problem.
Wipe data, system, flash ROM then GApps...
cm-12.1-20150601-NIGHTLY-hammerheadcaf.zip + open_gapps-arm-5.1-20150601.zip
Related
Hi!
My shieldtablet is running CM 12.1 (latest 20160807 build)... That works fine. It has latest TWRP 3.0.2-2 installed. And latest open GAPPS 5.1 (mini arm).
I am trying to get it to run CM 13 I've tried the first builds... didn't work... I tried today with the very latest nightly build 20160909... I do this by booting to recovery (TWRP 3.0.2-2) then going to install, and installing cm-13-20160909-NIGHTLY-shieldtablet.zip, and also open_gapps-arm-6.0-mini-20160912.zip (using the install multiple ZIPs feature of TWRP). Then I wipe DAVIK and cache and reboot.
Device stays forever at the nvidia logo.
I turn it off. Boot to recovery, reinstall CM 12.1 and opengapps 5.1 with same process... and that works fine. Machine reboots like a charm.
Any idea if I am missing a step? And what step that would be?
Thanks in advance,
Gilles.
Have you done the firmware update?
http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
Firmware Update:
If you have not installed the latest stock ota, then some firmware files need updated. The following flashable zips will update the bootloader and the dtb corresponding with the listed stock version. Only the latest one listed here will be supported by recent CM builds.
3.1.1 (L)
4.2.0 (M)
Ah... No. I'm confused, though. What's the difference between L and M files? Do I need to flash both? Or just one?
I'm running CM 12.1 (Android 5.1.1 Lollipop)... So I could imagine having to flash L? But since I'm updating to 6.0.1... Would that mean M?
I imagine I download the ZIP, boot into TWRP, flash the right version. Then flash CM 13. Then flash Open GAPPS?
Or in a different order?
Thanks,
Gilles
I'm on stock, so it's just a shot in the dark - but i think this sounds logical:
L - Lollipop - 5.x, flash this when you are on 13.0 and want back to 12.1
M - Marshmallow - 6.x, flash this when you are on 12.1 and want flash 13.0
and then cm + gapps of course
regards,
wakko
All in one shot? Boot to TRWP, flash M, CM, GAPPS then reboot?
Hopefully - you'll only find out, when you try
So... that's exactly what I did, and it worked.
So steps : log into the SHIELD (CM 12.1 / Android 5.5.1)
Reboot to recovery (configured advanced reboot in developer options)
From recovery, selected the M drivers, then added the CM 13 zip, then added the Open GAPPS (6.0 ARM MINI) ZIP.
Then clicked FLASH
Then rebooted (I was impatient, didn't think to clear DALVIK and cache).
Machine rebooted and all seems well (SD card was detected and I said use as portable storage, Avast asked for a few more permissions, only Viber got confused and requires relinking to mobile account).
All nice.
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
ggravier said:
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
Click to expand...
Click to collapse
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Steel01 said:
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Click to expand...
Click to collapse
Thanks! Solved! So far, I love it!
ggravier said:
Thanks! Solved! So far, I love it!
Click to expand...
Click to collapse
I am having the exact same issues as OP. Not tried this fix yet, but seems promising. Question is, does any of those L or M files wotk with Nougat? or is there one for that too?
I have wiped the data, cache, dalvik cache and system partition and format them to ext4 (recovery TWRP 3.0.3-2 by TugaPower). After that I have flashed the ROMS and the mini GApps. Then when I tries to boot, and it takes more then 20 minutes to boot (and the OS still doesn't booted).
I tried the unofficial LineageOS, RR 5.8, AICP but I stuck in bootloop in every Nougat ROM. The Marshmallow version of each is working, just the Nougat have bootloop issues.
Only the AOSP Nougat for OnePlus One succeeded to boot...
How can I solve this? Why all the CM14 based ROMs are not booting in my phone?
I'm having the exact same issue. Tried Lineage and Tugapower. Had to revert back to Sultan's CM13.
I tried with nano gapps for cm14.1 & pico gapps for tuga 13.1 works fine.
ppp99 said:
I have wiped the data, cache, dalvik cache and system partition and format them to ext4 (recovery TWRP 3.0.3-2 by TugaPower). After that I have flashed the ROMS and the mini GApps. Then when I tries to boot, and it takes more then 20 minutes to boot (and the OS still doesn't booted).
I tried the unofficial LineageOS, RR 5.8, AICP but I stuck in bootloop in every Nougat ROM. The Marshmallow version of each is working, just the Nougat have bootloop issues.
Only the AOSP Nougat for OnePlus One succeeded to boot...
How can I solve this? Why all the CM14 based ROMs are not booting in my phone?
Click to expand...
Click to collapse
nuuro said:
I'm having the exact same issue. Tried Lineage and Tugapower. Had to revert back to Sultan's CM13.
Click to expand...
Click to collapse
I had a similar problem with all the ROMs you mentioned failing to boot too when coming from CM13. What worked for me was to first flash a nightly from this thread.
http://forum.xda-developers.com/oneplus-one/development/lineageos-unofficial-nightly-t3528587
Afterwards I was able to flash and boot into AICP and TugaPower. Don't know if it will work for you guys, but give it a try.
I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom
Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.
I had the official Lineage 15.1 installed with gapps pico, it was upgraded from 14.1 lineage with gapps pico + magisk 16 . Today I wanted to downgrade back to 14.1 so I flashed the latest 14.1 lineage with gapps 7.1
After booting it shows com.android.phone has stopped working and it restarts again to show the same thing.
I am able to get into TWRP recovery , can anyone please suggest me what should I do?
I dont have previous backup
Mmodi said:
I had the official Lineage 15.1 installed with gapps pico, it was upgraded from 14.1 lineage with gapps pico + magisk 16 . Today I wanted to downgrade back to 14.1 so I flashed the latest 14.1 lineage with gapps 7.1
After booting it shows com.android.phone has stopped working and it restarts again to show the same thing.
I am able to get into TWRP recovery , can anyone please suggest me what should I do?
I dont have previous backup
Click to expand...
Click to collapse
I did a factory reset using TWRP . Lost all the data but the phone started, able to use it now
Mmodi said:
I did a factory reset using TWRP . Lost all the data but the phone started, able to use it now
Click to expand...
Click to collapse
Always do a clean wipe (wipe everything except internal/external storage). Always back up your previous system just in case. Sometimes it is better to flash Gapps right after flashing the ROM, sometimes it's better to flash the ROM, boot and then flash the Gapps.
I hope someone can help me here. I recently moved from CyanogenMod 13.1 to LineageOS 14.1 (fully wiping my phone). I haven't had any issues with LineageOS until I try to dirty flash a nightly build. I never had issues dirty flashing with CM, so I'm not sure what's going on. I just tried flashing the 7/25 build from the 7/18 build and the latest gapps. Upon rebooting, my D850 just sits at the boot screen (13 minutes now). When I restore from my TWRP backup, my phone will boot back up after about 3 minutes (for the first boot). Am I missing a step when flashing nightlies?