So, I made a custom PAC ROM zip for my phone with the pac_i9100-nightly-20150128.zip modded for my phone by removing the device check so it will install on my S959G. And reason for me doing this is the same for OmniRom, all SGH-I777 zips for PAC ROM and OmniROM are deleted for some reason so the I9100 is next in line for me.
Here is my process for installing this rom
Wipe user data/Factory reset
Wipe Cache partition
Wipe Dalvik cache
Installed Mr.Cooks ROM wipe script
Installed pac_i9100-nightly-20150128.zip
Installed Render-KK-03-22-CWM.zip
Installed GAPPS 4.4.4 Pico zip
Wipe user data/Factory reset
Wipe Cache partition
Wipe Dalvik cache
Reboot into PAC
I thought my steps was enough, and I'm coming from Resurrection Remix 4.4.2 KitKat v5.1.5 By SteveMurphy
Is there a step I missed in the flashing process or an app I have installed causing Random Reboot or Reboots in general.
I also checked the last_kmsg file and it said something about rebooting
<0>[ 6993.848196] c1 Rebooting in 1 seconds..
Including a link to the file on my MEGA below
My last_kmsg file
You should be wiping /system before installing the ROM, along with the usual cache wipes. You do not have to do those wipes again after installing. No idea what would be causing random reboots, except the usual suspect being a faulty power button. Try your install again, but wipe /system as well and don't use the ROM Wipe Script. There have been (old) reports of that causing some issues.
One other thing could be the kernel, as Render's kernel is really outdated - could be another cause!
SteveMurphy said:
You should be wiping /system before installing the ROM, along with the usual cache wipes. You do not have to do those wipes again after installing. No idea what would be causing random reboots, except the usual suspect being a faulty power button. Try your install again, but wipe /system as well and don't use the ROM Wipe Script. There have been (old) reports of that causing some issues.
One other thing could be the kernel, as Render's kernel is really outdated - could be another cause!
Click to expand...
Click to collapse
I have CWM recovery installed and it only can wipe data/factory reset, cache and dalvik cache. I could install Omni TWRP to be able to wipe /system. I do have the Shift kernel 1.0 to 5.0 zips as well, i could flash hem but i have no idea if they are compatible with STweaks since I only use it to enable the BLN for the bottom keys. Plus I random rebooted twice today, you want another last_kmsg log from it?
Also logcatting on my Ubuntu 15.04 laptop in terminal with the following command
Code:
adb logcat *:W *:F *:E
for Warnings, Fatal Warnings and Errors until a random reboot occurs
last_kmsg2
Sent from my SGH-I777 using XDA Free mobile app
CWM wipes /system, it's in a sub menu somewhere but I don't remember because I've not used CWM in a very long time. I know it's there because I used to do it! My suspicion is it's kernel related, but you'll need a KK kernel that's updated with the necessary blobs and I don't think there is a newer one for i777.
Unless someone else pops in with another suggestion, I'm out of ideas. Maybe it's time for you to update to LP?
SteveMurphy said:
CWM wipes /system, it's in a sub menu somewhere but I don't remember because I've not used CWM in a very long time. I know it's there because I used to do it! My suspicion is it's kernel related, but you'll need a KK kernel that's updated with the necessary blobs and I don't think there is a newer one for i777.
Unless someone else pops in with another suggestion, I'm out of ideas. Maybe it's time for you to update to LP?
Click to expand...
Click to collapse
I tried CyanideL 5.1.1 ROM for I777 and it would random reboot, but on this PAC ROM, I think I fixed it by turning off Dynamic statusbar colors on screen to disabled and has not rebooted yet but I'm still crossing my fingers still.
Also read about Mr.Cooks ROM Wipe script on Omni 5.1, seen it sticks some S2 phones on the Samsung Galaxy S2 screen for awhile, Not good
Related
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.
So I desperately need help here! Using a GT-i9300 here.
Been at this for like 7 hours or so.
Was running a 4.1.2 rom for quite a while, thought I'd bump it up to 4.4.2 today.
Was thinking about flashing Resurrection Remix rom, so did the usual downloaded the files but noticed somewhere you need a 4.2.2 or above rom already in use to be flashing a 4.4.2. So went to S4 revolution rom (4.2.2). Then decided to flash the 4.4.2 rom.
Did the usual, data wipe, cache wipe, dalvik cache wipe. Flashed the rom. Then Gapps.
Now here's the messed up part, after flashing the phone would boot to the Rom logo. And it hasn't moved since. Thought something was up, flashed it again, did the take battery out thing also.
Thought it would be a ROM problem, so flashed 2 other roms. Neat rom and Gummy rom. Same result.
The 4.2.2 rom is working btw. So any ideas?!
Please! Reallly want the 4.4.2
Thank you!
Prosilicus said:
So I desperately need help here! Using a GT-i9300 here.
Been at this for like 7 hours or so.
Was running a 4.1.2 rom for quite a while, thought I'd bump it up to 4.4.2 today.
Was thinking about flashing Resurrection Remix rom, so did the usual downloaded the files but noticed somewhere you need a 4.2.2 or above rom already in use to be flashing a 4.4.2. So went to S4 revolution rom (4.2.2). Then decided to flash the 4.4.2 rom.
Did the usual, data wipe, cache wipe, dalvik cache wipe. Flashed the rom. Then Gapps.
Now here's the messed up part, after flashing the phone would boot to the Rom logo. And it hasn't moved since. Thought something was up, flashed it again, did the take battery out thing also.
Thought it would be a ROM problem, so flashed 2 other roms. Neat rom and Gummy rom. Same result.
The 4.2.2 rom is working btw. So any ideas?!
Please! Reallly want the 4.4.2
Thank you!
Click to expand...
Click to collapse
Please read the RR thread again. You need a full wipe for it to work. Try a 4.3-based Rom like Omega and then search XDA on how to do a FULL wipe. Then proceed with RR.
~ RazorMC
RazorMC said:
Please read the RR thread again. You need a full wipe for it to work. Try a 4.3-based Rom like Omega and then search XDA on how to do a FULL wipe. Then proceed with RR.
~ RazorMC
Click to expand...
Click to collapse
Thanks for the reply. But could you please elaborate on how to do a full wipe? Kind of a newbie to all this. Thanks!
Prosilicus said:
Thanks for the reply. But could you please elaborate on how to do a full wipe? Kind of a newbie to all this. Thanks!
Click to expand...
Click to collapse
Sorry, I've forgotten the link to the method. Maybe someone else can also shed light on this matter.
But if I remember:
- Wipe Cache,
- Wipe dalvik,
- format /system,
- format /data,
- format /cache.
- Then install the Rom.zip.
PS: Don't do "format /data and /data/media" section or it will delete everything on the internal SD. If you do this, make sure you have an external SD with a ROM placed in it (don't wipe this too) otherwise you will end up in a very difficult situation like i did
~ RazorMC
RazorMC said:
Sorry, I've forgotten the link to the method. Maybe someone else can also shed light on this matter.
But if I remember:
- Wipe Cache,
- Wipe dalvik,
- format /system,
- format /data,
- format /cache.
- Then install the Rom.zip.
PS: Don't do "format /data and /data/media" section or it will delete everything on the internal SD. If you do this, make sure you have an external SD with a ROM placed in it (don't wipe this too) otherwise you will end up in a very difficult situation like i did
~ RazorMC
Click to expand...
Click to collapse
If I am not wrong, formatting data will not erase the root directory. Where u put the rom zip. But just have an ext sd card just for safety.
Sent from my GT-I9300 using xda app-developers app
JellyYogurt said:
If I am not wrong, formatting data will not erase the root directory. Where u put the rom zip. But just have an ext sd card just for safety.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
You're right. "format /data" does not erase the root directoy. But I found "format /data and /data/media and /sdcard" option deleted everything on my S3 and even adb sideload failed for me after selecting it. After that I had to reflash stock via Odin.
+1 to ext SD
~ RazorMC
Usually I would just flash the mega wipe zip to get the device clean (only leaves ext. sd) and then start reflashing from scratch. I find it easier than doing it manually in recovery.
@RazorMC @JellyYogurt
Hey! Sorry got a bit busy but just got around to what you all recommened today and it's still no use.
Did everything this time.
First, I tried flashing the RR rom with the full wipe as you said. Oh and I'm using CWM 6.0.4.7
- Moved the zip file to ext SD
- wipe data
- wipe cache
-wipe dalvik cache
- format /system,
- format /data,
- format /cache.
During this got a status 6 error with the RR rom and I had put a Gummy Rom (4.4.2) just in case so tried the same process with this also but got a status 7 error with this one.
Left both, downloaded CM 11. Did the same process while on the 4.2.2 rom with it. This got stuck on the boot screen. Like the CM logo was going around for 30 minutes.
Finally when I couldnt tolerate it, removed battery, moved to 4.2.2 again and downloaded a 4.3 rom. Again, CM.
You wouldnt believe this but this also didnt work! This got stuck on the same thing. CM logo is still flashing around. Been watching this for 20 minutes now.
So, you guys got any ideas? Really pissing off.
Btw, thanks for the previous replies )
Oh and btw, would it matter if I didnt flash gapps after flashing the rom?
Those are just for the Google services and not related to whether the rom is booting up to home screen right?
Prosilicus said:
Oh and btw, would it matter if I didnt flash gapps after flashing the rom?
Those are just for the Google services and not related to whether the rom is booting up to home screen right?
Click to expand...
Click to collapse
Try other recoveries to see if problem still there try latest PhilZ recovery (this as a setting for wiping and installing new roms)..if that does not work try twrp recovery..
No you don't have to flash gapps after flashing you can do that later..
Prosilicus said:
@RazorMC @JellyYogurt
Hey! Sorry got a bit busy but just got around to what you all recommened today and it's still no use.
Did everything this time.
First, I tried flashing the RR rom with the full wipe as you said. Oh and I'm using CWM 6.0.4.7
- Moved the zip file to ext SD
- wipe data
- wipe cache
-wipe dalvik cache
- format /system,
- format /data,
- format /cache.
During this got a status 6 error with the RR rom and I had put a Gummy Rom (4.4.2) just in case so tried the same process with this also but got a status 7 error with this one.
Left both, downloaded CM 11. Did the same process while on the 4.2.2 rom with it. This got stuck on the boot screen. Like the CM logo was going around for 30 minutes.
Finally when I couldnt tolerate it, removed battery, moved to 4.2.2 again and downloaded a 4.3 rom. Again, CM.
You wouldnt believe this but this also didnt work! This got stuck on the same thing. CM logo is still flashing around. Been watching this for 20 minutes now.
So, you guys got any ideas? Really pissing off.
Btw, thanks for the previous replies )
Click to expand...
Click to collapse
Try a stock-based 4.3 like omega rom after flashing stock 4.1.2
Use Philz Recovery like tallman43 said. I prefer that over others.
If it doesn't work then maybe there's some compatibility issues.
~ RazorMC
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
tallman43 said:
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
Click to expand...
Click to collapse
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Hey
When it bootloops, have you tried to goto recovery and see what us the cwm version??
Also try re-flashing the ROM without wipes..
Sent from my GT-I9300 using xda app-developers app
I just flashed EHNDROIX V (based on CynogenMod 4.4.2 KitKat) last night and it worked just fine.
Rooted the device with Odin, install TWRP from playstore, install TWRP recovery from TWRP, clean dalvik, clean data, clean cache, flash ROM and then flash Gapps (spesific Gapps for the ROM) and voila it worked right away.
Note:
You see, I am not using CWM but TWRP. I dunno if CWM is the one causing the problem.
Most of the weird flashing issues are due to the recovery used, you could also try the latest version of Philz recovery which has an option to wipe for new firmware.
Sent from my GT-I9300 using Tapatalk
divoom12 said:
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Click to expand...
Click to collapse
Quote " Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system" You said nothing about formatting data that is why i suggested it! Next time please include all details on how you flashed the rom then It cuts down on useless post's like mine
Like everybody suggested try a different recovery ( latest one) which if you have flashed roms many times before you should have done anyway
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
divoom12 said:
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
Click to expand...
Click to collapse
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
RazorMC said:
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
Click to expand...
Click to collapse
I said that I've already done that in my First post.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Did you update your bootloader? When I flashed 4.4.2 from 4.4.1 on my s3, I had to update mine to get it to work. http://forum.xda-developers.com/showthread.php?t=2321310 hope this helps.
Sent from my unknown using XDA Premium 4 mobile app
Hi guys! I've been trying for the last hours to install Cyanogenmod 11 on a friend's S3 international (i9300). After some driver problems CM now installs fine, but after the installation finishes and the phone reboots the phone reverts to Samsung's stock firmware. Even though I select yes at the question that should prevent stock recovery from occurring.
I have tested every solution I could find out there to prevent this:
1. After CM setup finishes, I pull the battery and start the phone in Clockworkmod by holding Vol-up+home+power. Then I have wiped the cache, data and dalvik cache and rebooted. Still reverting to stock.
2. I have tried rooting the phone and removing /system/etc/install-recovery.sh using Root explorer before starting the installation. There was however no file /system/recovery-from-boot.p which was also mentioned in som guides.
Nothing seems to work.
I can't understand that I'm the only one having this problem. Is there a solution out there? Thanks!
r243 said:
Hi guys! I've been trying for the last hours to install Cyanogenmod 11 on a friend's S3 international (i9300). After some driver problems CM now installs fine, but after the installation finishes and the phone reboots the phone reverts to Samsung's stock firmware. Even though I select yes at the question that should prevent stock recovery from occurring.
I have tested every solution I could find out there to prevent this:
1. After CM setup finishes, I pull the battery and start the phone in Clockworkmod by holding Vol-up+home+power. Then I have wiped the cache, data and dalvik cache and rebooted. Still reverting to stock.
2. I have tried rooting the phone and removing /system/etc/install-recovery.sh using Root explorer before starting the installation. There was however no file /system/recovery-from-boot.p which was also mentioned in som guides.
Nothing seems to work.
I can't understand that I'm the only one having this problem. Is there a solution out there? Thanks!
Click to expand...
Click to collapse
1.Root your phone.
2.Install latest CWM or TWRP.
3.Boot into recovery.
4.Wipe Data/Factory reset.
5.Wipe cache.
6.Wipe dalvik cache.
7.Install ZIP from sdcard.
8.Choose your downloaded CM.
Good luck
GeekyDroid said:
1.Root your phone.
2.Install latest CWM or TWRP.
3.Boot into recovery.
4.Wipe Data/Factory reset.
5.Wipe cache.
6.Wipe dalvik cache.
7.Install ZIP from sdcard.
8.Choose your downloaded CM.
Good luck
Click to expand...
Click to collapse
Thanks! The reason I did not do this before was that I am not really comfortable installing manually and was afraid to brick the phone (since it's not mine). But I followed your instructions and it worked perfectly
It's a shame that the automatic installer can't handle this though.
r243 said:
Thanks! The reason I did not do this before was that I am not really comfortable installing manually and was afraid to brick the phone (since it's not mine). But I followed your instructions and it worked perfectly
It's a shame that the automatic installer can't handle this though.
Click to expand...
Click to collapse
Haha! Actually you won't brick your device by installing a ROM for your device. You can only brick it by flashing a ROM from other device without porting it, and I think this will be then only soft-bricked. A hard-brick can be done by flashing basebands from different devices. But I hope you won't do that
Actually by installing a ROM only your system(apps, vendor files, tweaks, etc.) and boot partition(kernel, etc.) will be overwritten. And that won't hard-brick your device
But I can understand your fear. I was same as you when I was a beginner
Hi;
So i recently installed CyanogenMod 13.0 on to my Samsung S4 GT-I9505 using the first download link on:
https://download.cyanogenmod.org/?device=jfltexx --> cm-13.0-20160102-NIGHTLY-jfltexx.zip
That all installed fine, but i wanted to get the Google apps installed aswell, which is where i am having some issues.
I have been trying to install the following package:
http://opengapps.org/?api=6.0&variant=nano
but have also tried to install quite a few others as well, and all have exactly the same issue. Basically after the apps have been installed and i boot the device up, i get various error messages like:
unfortunately, Setup Wizard has stopped
unfortunately, google play services has stopped
Any help on fixing this would be much appreciated, as nothing seems to download from the play store thats included in Cyanogen, they just say "your download will begin shortly" but never does.
Thanks in advance
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
audacityandrouge said:
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
Click to expand...
Click to collapse
Thanks for the reply, i gave that a try and it seems to be stuck on a loop now with "installing app # of 22" . it completes the installation and then reboots, after about 5 minutes on the Cyanogen boot screen, it goes back to installing apps again.
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
audacityandrouge said:
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
Click to expand...
Click to collapse
Yeah, i did. Tried it multiple times now
That's about the limit of my ability right there, hopefully someone with more experience than me can point you in the right direction. Good luck.
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
es0tericcha0s said:
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
Click to expand...
Click to collapse
Ive tried that multiple times using twrp (i always wipe everything before i flash CM13 and gapps), i still get the exact same issue. The second the phone boots, i get all these "unfortunately ******** has stopped".
Perhaps try installing 12.1 with gapps, get it all updated then upgrade to 13. I did the accidental upgrade to 13 but have had no issues whatsoever.