Related
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
markkal123 said:
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
Click to expand...
Click to collapse
How did you flash it? Did you do it through ROM Manager? Did you wipe data and cache? Something's not quite right, the bloatware should be gone.
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
phatjames167 said:
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
Click to expand...
Click to collapse
Hmm. Count me in on this one too then: http://forum.xda-developers.com/showthread.php?t=1069980
count me in as part of the galactically stupid. (worse than nube)
go to here http://forum.xda-developers.com/showthread.php?t=1027804
download and install
BAMF Remix v1.6:http://tinyurl.com/3wkpmh3
MD5: CF461768DBC8A729CB7D28B97D5B8717
download and install
BAMF Remix Patch 1.6.2: http://tinyurl.com/3ntawj6
MD5: d45d597d42d40ca31319786cfb9450dc
i was only installing BAMF Remix Patch 1.6.2 not realinzing it is only a patch to BAMF Remix v1.6!!!
i booted into ClockworkMod
everything now appears to be as expected for the ROM
thanks for your help.
it looks like this worked. when it first boots though the wallpaper is black with a red streak but then changes to the default wallpaper from stock. is that normal?
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
aerojad said:
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
Click to expand...
Click to collapse
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
aerojad said:
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
Click to expand...
Click to collapse
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
devindpotts said:
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
Click to expand...
Click to collapse
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
aerojad said:
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
Click to expand...
Click to collapse
Not a problem at all, enjoy.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I had the same issue and this worked for me. I just reflashed 1.6.3 directly from CWR (after wiping everything 3x) and everything worked correctly (notification widget, etc.)
thanks for the help
I am glad I found this, I had this same issue and it was driving me nuts. I'm reinstalling now and hopefully everything just comes out perfect.
I am adding this to my list of why I don't like RM.
I am trying to swich ROMs. I am currently on Jellybro and really want to try Helly Bean. Has anyone tried/had issues going from Jellybro to Helly Bean? I followed the flash instructions and I am getting a status 7 error. Any ideas how to fix? I've searched the Helly Bean thread in the development forum, but I'm too much of a n00b to figure out what they are saying most of the time. Do I need to start from scratch (Odin back to stock)?
If I have to Odin, I'll do some more searching to figure out how to get from stock to Helly Bean.
Thanks in Advance!
Check this out. Seemed to work with previous build.
I just tried the Glitch kernel fix and I am still getting the same status 7 error: symlinks failed. I got the same error last week, but I had assumed it was the updater.sh script as described by hurtz777.
It always fails on the vibrant install, the initial and the base work just fine. Do I need to reflash the glitch kernel after the base installation?
Any other ideas?
HellsBells said:
I just tried the Glitch kernel fix and I am still getting the same status 7 error: symlinks failed. I got the same error last week, but I had assumed it was the updater.sh script as described by hurtz777.
It always fails on the vibrant install, the initial and the base work just fine. Do I need to reflash the glitch kernel after the base installation?
Any other ideas?
Click to expand...
Click to collapse
Did you follow the steps directly.
1.flash base
2.reboot recovery.
3.flash helly bean initial
4.flash hellybean xxx(device name)
5. Flash add on.
6. Go into advanced. Fix permissions.
7. Reboot
Sent from my SGH-T959 using xda app-developers app
skinzy98 said:
Did you follow the steps directly.
1.flash base
2.reboot recovery.
3.flash helly bean initial
4.flash hellybean xxx(device name)
5. Flash add on.
6. Go into advanced. Fix permissions.
7. Reboot
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Yes, but it gives me the status 7 in step 4. I did a factory reset, wiped cache/dalvik, flashed glitch kernel, flashed initial, reboot recovery, flashed base, flashed vibrant rom, then i get the status 7 error about half-way through the install.
What about formatting system partition?
Sent from my SGH-T959 using xda premium
rcsredmage said:
What about formatting system partition?
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I thought about starting over completely. Reformat everything and reflash stock with Odin and start with a blank phone. I don't want to loose any info but at this point I don't think I care anymore.
I have Titanium back up, but if I reformat, it will not reinstall my apps correct? If you can't tell, I'm new to the game here.
Reflash your kernel.. trust me
asvantypography said:
Reflash your kernel.. trust me
Click to expand...
Click to collapse
Still getting the error. I flashed the glitch kernel, flashed initial, reboot, flashed base, flashed glitch, flashed base again, then flashed vibrant rom and boom... status 7 error some symlinks failed.
WTF this is frustrating...
Reflash the kernel then flash the rom
asvantypography said:
Reflash the kernel then flash the rom
Click to expand...
Click to collapse
Same error. ugh...
Youre supposed to wipe data, wipe dalvik cache and cache, format system, and then install the initial package. After that, reboot recovery, then flash the base. After that, flash the file made for your device (hellybean vibrant 0807) and then flash the addon. After all that, reboot. I dont think you're supposed to get a status 7 error, because thats how the developer says to do it.
+1 ^^^^
sent from my magic box to yours
They have been getting a status seven on that thread. They said it was a sy link error. I can't remember how to fix it though
Sent from my SGH-T959 using xda app-developers app
Actually that was on some of the earlier builds such as 0804 and 0805 and perhaps 0806 as well. 0807, I can say that it is working. I just checked the thread, and another user reported that he was on 0807 and it runs fine. Just putting this out there for you all to know.
Hobbesfed said:
Youre supposed to wipe data, wipe dalvik cache and cache, format system, and then install the initial package. After that, reboot recovery, then flash the base. After that, flash the file made for your device (hellybean vibrant 0807) and then flash the addon. After all that, reboot. I dont think you're supposed to get a status 7 error, because thats how the developer says to do it.
Click to expand...
Click to collapse
That's what I did, but I can't get past the vibrant flash file. I get the status 7 error in the middle of the install (symlinks failed).
I didn't format the system partition. I can try doing that too. I won't lose my backups or apps (titanium backup) will I? I suppose i could back them up to the external SD and remove it.
I'll try that this evening. I'll let you know how it goes.
Thanks for everyone's input.
i googled the problem and i got here .. i had the same issue with captivate, rebooting after installing the base solved the issue for me .. don't forget to fix permissions after flashing the addons
bobo122 said:
i googled the problem and i got here .. i had the same issue with captivate, rebooting after installing the base solved the issue for me .. don't forget to fix permissions after flashing the addons
Click to expand...
Click to collapse
Same error.
I haven't gotten around to formatting the system partition yet. That will only affect the OS right, it won't delete any other data?
i fixed it with flashing stock kernel from odin..
Sent from my GT-P1000 using xda app-developers app
It Worked!
I finally got it! Formatting the system partition is what did it! Thanks for everyone's suggestions!
Now to play a bit...
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 was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
gautam_k said:
Hi,
I was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
Click to expand...
Click to collapse
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
ShoaibAhmed said:
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
Click to expand...
Click to collapse
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
gautam_k said:
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
Click to expand...
Click to collapse
Reboot once and then try to turn off NFC , it will work.
ShoaibAhmed said:
Reboot once and then try to turn off NFC , it will work.
Click to expand...
Click to collapse
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
gautam_k said:
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
Click to expand...
Click to collapse
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
ShoaibAhmed said:
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
Click to expand...
Click to collapse
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
gautam_k said:
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
Click to expand...
Click to collapse
Found the shortcut in Settings> Notification Drawer> Quick settings panel> Tiles & layout> Network mode
For some reason i was thinking that this will lead me to the GSM/WCDMA switch.
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.