Database Users

[SOLVED] What recovery should I use with CM 10?

I got bored today and decided to pull out the old N7, 2012 version. I update recovery to TWRP 2.8.7.0, installed CM 12.1, realized this tablet crawls with any version of Android other than shipped version, so I went and got CM 10 and GApps for JB, wiped and flashed them back on. I didn't see any errors when flashing them, but when rebooting after, it just boot loops. I see the Google logo with the unlocked icon at bottom, then reboot and back to Google/unlocked again. So I wipe and reflash cm12.1 and it's GApps and all boots and works fine, other than being slow. I'm assuming the recovery is the problem as I've run into something similar before on another device, but in that case, the recovery was too old and needed updated, but it makes sense that a recovery could be too new as well.
Am I correct that the recovery is the problem? If so, what should I run for CM 10 to flash and work?

Try cwm recovery

iwjosi said:
Try cwm recovery
Click to expand...
Click to collapse
I don't' know if it was using CWM or that I also tried CM 10.2 at the same time, but it's working now. On CyanogenMod's own page, there was no MD5 for CM10, but there was for CM10.2, so it's possible my copy of CM10 was a bad download. Either way, it's working now, so thank you good sir, or madam, or person on no specific gender.

Galaxy S4 i9500 - CM 12.1 Nightly (20160110) - GApps crashing constantly

So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik

Chikyu Tenshi said:
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Click to expand...
Click to collapse
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
Try these gapps:
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
You need to perform a full wipe though.

Lennyz1988 said:
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
You need to perform a full wipe though.
Click to expand...
Click to collapse
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik

You need 5.1 gapps then.

Chikyu Tenshi said:
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
Click to expand...
Click to collapse
My bad. Here is also another gapps
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Lennyz1988 said:
My bad. Here is also another gapps
Click to expand...
Click to collapse
Still :c I only flashed the base tho, Am I supposed to flash the add ons too?

I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)

CHIN3S3_N00B said:
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
Click to expand...
Click to collapse
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card

Could you try GearCM? Official CM for i9500 had lots of issues.
Sent from my GT-I9500

Chikyu Tenshi said:
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Click to expand...
Click to collapse
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?

CHIN3S3_N00B said:
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
Click to expand...
Click to collapse
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.

Lennyz1988 said:
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Click to expand...
Click to collapse
I think that i didn't express myself very well. Yes it's advisable and strongly recommended to use lastest builds of any recovery available as stable build.
But once i had to use Philz to flash a MIUI ROM because TWRP 2.8.6.0 was unable to execute the installation script didn't know why and that's why i said about different recoveries, and oh.... I forgot to say that after successful install rollback to TWRP because it's pretty new , stable and more user friendly than others.(CMW and the rainbow Easter egg was fine but having to use vol and power keys..... NO THANKS!)

Flashed CM13, Cannot find Gapps package that works, help?

Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.

trent4071 said:
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
Click to expand...
Click to collapse
Same here I tried it, and it did the same for me also...
Sent from my SM-N920F using Tapatalk

These are the Gapps that worked for me
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842

Thank you for the help wikked26, but it didn't work. Those Gapps still crash for me. I think it's something incorrect in the way my phone is configured, not a case of downloading the wrong Gapps.
If anyone has any other ideas, please share them! I haven't cracked the case just yet

I know I was having issues with the Slimroms version where I booted into CM and set it up before installing Gapps. Fixed it by reinstalling/wiping the cache and installing Gapps before booting anything. Don't know if that helps, but I'm running fine now.

I'm hoping this is similar to the issue I'm having. Do you get it where you can factory reset in TWRP, then flash CM13, but when you go to flash Slim Gapps? Because I figured out that after factory resetting TWRP will only successfully flash 1 zip file. I also tried to wipe the cacher, dalvik, data, and system, then flash cm13 but Gapps still wouldn't flash. Maybe its a bug with TWRP 3.0.2? I'm going to try to use a different version of TWRP and I'll update with my results
EDIT: TWRP 2.8.5 did not do anything different

Wow, thanks for all the great responses. I made sure to try and install CM13 and Gapps at the same time, before boot, after wiping everything one last time. It worked flawlessly, and I can now use Google Play Services.
I hope this thread helps anyone else who is also a little stuck. I also found that TWRP didn't have any issues flashing multiple zips at the same time, not sure whats going on with you, Orange Officer. Perhaps try removing your battery after CM13 flashes, and then boot into TWRP again and flash Gapps without booting up CM13 at all?

Best way to upgrade to CM14 from CM13?

Just recently the CM14 nightlies have been put up for this phone. I'm currently running CM13 and was wondering if it's possible to "dirty flash" CM14 or alternatively wipe everything and flash a backup of my data?

Do a full backup with cm
13 in twrp then try a dirty flash up to cm14.1 if it doesn't work do a full wipe and Flash cm14.1 then do a restore of data from cm13 backup
Sent from my iPhone 4s using Tapatalk I also own a g900v

[email protected] said:
Do a full backup with cm
13 in twrp then try a dirty flash up to cm14.1 if it doesn't work do a full wipe and Flash cm14.1 then do a restore of data from cm13 backup
Click to expand...
Click to collapse
Okay, thanks!

The guide Says To Flash Gapps At The same time.It's a little buggy though. I'm having screen rotation issues.

It is in nightly status right now it won't be stable till a snapshot build comes out
Sent from my iPhone 4s using Tapatalk I also own a g900v

I can't enable wifi after Updated to CM14, clean install (cm13 to cm14.1).. Flash CM14.1 rom and then reboot to recovery mode again and installed GAPS, but wifi couldn't be enabled by any trial.. I went to back to CM 13.... Will wait some more time...:crying:

You did it wrong you flash ROM then immediately nougat gapps in custom recovery do not reboot in between
Sent from my Nexus 4 using Tapatalk

Win0416 said:
I can't enable wifi after Updated to CM14, clean install (cm13 to cm14.1).. Flash CM14.1 rom and then reboot to recovery mode again and installed GAPS, but wifi couldn't be enabled by any trial.. I went to back to CM 13.... Will wait some more time...:crying:
Click to expand...
Click to collapse
There's a new nightly and wifi "works", but if you reboot after the initial boot after installing the zip it doesn't work anymore. Using cm-14.1-20161130-NIGHTLY-kltevzw.zip

Phone stuck on Android is starting. Running lastest PureNexus Rom

My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.

SHINee2 said:
My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.
Click to expand...
Click to collapse
Even i had faced this issue on 6.0.1 build, Dont remember exactly how i got it resolved .
But you may try this
flash vendor image
wipe
flash rom
wipe
reboot
just try it out :good:

ramrock007 said:
Even i had faced this issue on 6.0.1 build, Dont remember exactly how i got it resolved .
But you may try this
flash vendor image
wipe
flash rom
wipe
reboot
just try it out :good:
Click to expand...
Click to collapse
Thank you I will try it out.

SHINee2 said:
My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.
Click to expand...
Click to collapse
Did you flash a GApps package? I believe Pure Nexus recommends Dynamic GApps... Check the PN thread for the download link.
Wipe
Flash ROM
Flash GApps
Flash vendor (although you shouldn't need to do this again)
Reboot system

SHINee2 said:
My TWRP is 3.0.3 and whenever I flash the latest PureNexus Rom, only thing that appears on my screen is Android is starting after I complete the setup.
Click to expand...
Click to collapse
You should search the Pure nexus thread. This is a known issue with the latest build and there are workarounds for it.