Database Info

Help! Device won't recognize internal SD card. :(

Okay so I have a problem, I was on CM10 nightlies and realized I hadn't updated in awhile so I went to flash another nightly. Being the careless person I am I clicked the link and downloaded and flashed the most recent ROM uploaded without realizing it was CM9. This put me into a bootloop. I went into fastboot and did a factory restore to fix the bootloop but the restore restores me to CM9. That's not the main problem though, my internal SD card isn't recognized by the phone so I can't even flash another ROM. Please help. :3

m0n3y0n7r335 said:
Okay so I have a problem, I was on CM10 nightlies and realized I hadn't updated in awhile so I went to flash another nightly. Being the careless person I am I clicked the link and downloaded and flashed the most recent ROM uploaded without realizing it was CM9. This put me into a bootloop. I went into fastboot and did a factory restore to fix the bootloop but the restore restores me to CM9. That's not the main problem though, my internal SD card isn't recognized by the phone so I can't even flash another ROM. Please help. :3
Click to expand...
Click to collapse
Does recovery recognize your internal storage? Try factory reset, format system, install cm10 and gapps and try to reboot

absolutelygrim said:
Does recovery recognize your internal storage? Try factory reset, format system, install cm10 and gapps and try to reboot
Click to expand...
Click to collapse
Nope, that's the problem. I formatted everything already. Also, I don't have CM10 on my internal SD. I don't have any ROMs actually.

m0n3y0n7r335 said:
Nope, that's the problem. I formatted everything already. Also, I don't have CM10 on my internal SD. I don't have any ROMs actually.
Click to expand...
Click to collapse
Have you tried going into the storage settings and make sure sdcard is mounted? And have you tried to USB Mount from recovery to your computer to verify that windows sees it and it isn't a hardware failure

absolutelygrim said:
Have you tried going into the storage settings and make sure sdcard is mounted? And have you tried to USB Mount from recovery to your computer to verify that windows sees it and it isn't a hardware failure
Click to expand...
Click to collapse
Whenever I hit the settings app it crashes lol, but I tried mounting in recovery its just not recognized. I USB mounted too, no luck, it wasn't recognized either.

m0n3y0n7r335 said:
Whenever I hit the settings app it crashes lol, but I tried mounting in recovery its just not recognized. I USB mounted too, no luck, it wasn't recognized either.
Click to expand...
Click to collapse
That leads me to believe it may be a hardware issue. I'll see what I can find out
When you say settings app, you mean inside of recovery, right?
Can you see if you can mount the storage in adb

absolutelygrim said:
That leads me to believe it may be a hardware issue. I'll see what I can find out
When you say settings app, you mean inside of recovery, right?
Can you see if you can mount the storage in adb
Click to expand...
Click to collapse
Oh I thought you meant the actually settings app. But mounting in recovery doesn't work either. And it shouldn't be a hardware issue, it was working just fine yesterday before I got stuck in that boot loop. And my phone isn't recognized in adb. :3 Everything is broken! Haha

So you can boot into your ROM, you can boot recovery, but you can't access storage..
What happens if you do 'adb devices'? If nothing shows up go install the aokp/cm10 drivers. It may work for cm9
http://forum.xda-developers.com/showthread.php?t=1852614
Sent from the abstraction layer.

absolutelygrim said:
So you can boot into your ROM, you can boot recovery, but you can't access storage..
What happens if you do 'adb devices'? If nothing shows up go install the aokp/cm10 drivers. It may work for cm9
http://forum.xda-developers.com/showthread.php?t=1852614
Sent from the abstraction layer.
Click to expand...
Click to collapse
Nothing shows up and those drivers aren't working. Is there anyway I can do a complete factory reset and then work my way back from there?

m0n3y0n7r335 said:
Nothing shows up and those drivers aren't working. Is there anyway I can do a complete factory reset and then work my way back from there?
Click to expand...
Click to collapse
You can RUU 1.85
Sent from the abstraction layer.

If you did a factory reset in hboot (as opposed to in recovery) it wipes your SDCard without formatting it. I did this once too, and if you're in the same boat, try the solution in this thread:
[Q] E:Can't mount/SD card
http://forum.xda-developers.com/showthread.php?t=1751803

Bootloop after Factory reset

Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:

Natural_born_chilla said:
Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:
Click to expand...
Click to collapse
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.

gee2012 said:
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.
Click to expand...
Click to collapse
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291

Natural_born_chilla said:
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291
Click to expand...
Click to collapse
Go into recovery and clear the caches and do a data factory reset and see if it boots, if it doesn`t go into fastboot and flash a Google factory image. A good advice = DO NOT USE TOOKITS. Good luck bro

[Q]Pretty sure TWRP just bricked my N5 [RESOLVED]

So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.

_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
Click to expand...
Click to collapse
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.

leblvin said:
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
Click to expand...
Click to collapse
All I did was flash a zip to change the dpi of my navbar. I've flashed the same zip a couple times before. Wiped cache + dalvik and it hung up for a while, screen went black for 5 minutes then the phone rebooted into its current state. I realize that wiping the caches doesn't touch the IMEI or anything like that, but what if the version of TWRP I have is buggy?
So knowing that yes, that is all I did, is there any way to fix it?

After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.

Always run the very recovery latest version.
a hammerhead wrote this.

Might be worth backing up your EFS partition to be on the safe side!

Nandroid backup is your best friend

beekay201 said:
Always run the very recovery latest version.
a hammerhead wrote this.
Click to expand...
Click to collapse
Yup, didnt bother to check before.
EddyOS said:
Might be worth backing up your EFS partition to be on the safe side!
Click to expand...
Click to collapse
Agreed. First thing I'm gonna do when I get home from work.
gd6noob said:
Nandroid backup is your best friend
Click to expand...
Click to collapse
I have a recent nandroid. What good is it though if recovery can't see my storage where the nandroid was saved?
Sent from my Moto X

_MetalHead_ said:
After a bit of googling I got it fixed.
Click to expand...
Click to collapse
Well, whatever you do, don't share your find here in case someone else ever has the same problem.

GldRush98 said:
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
Click to expand...
Click to collapse
I did share it. Read the rest of the post you quoted. Derp.
Sent from my Moto X

_MetalHead_ said:
lApparently sometimes TWRP will cause some havok with the partitions when wiping cache
Click to expand...
Click to collapse
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
It's a TWRP exclusive feature.

_MetalHead_ said:
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Click to expand...
Click to collapse
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).

reynwrap582 said:
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
Click to expand...
Click to collapse
Yeah man, I was certain I was gonna need a new phone. Glad this helped you. I'm going to update the OP with a link to your post so more inexperienced users can benefit. Thanks for typing it out.

_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
Click to expand...
Click to collapse
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk

MrGriffdude said:
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey now, it wasn't my fault! Lol
Sent from my Nexus 5 using XDA Premium 4 mobile app

Nexus 5 stuck in boot loop animation (MMB29V Marshmallow)

no power button problem
without any reason the phone rebbot itself and stuck in boot loop animation....stock MMB29V Marshmallow , no root, only unlocked
tried:
-wipe cache and data
-reinstalling all singles images files
-reinstalling with flash all bat and finally it works...
what's the problem???
and now? there is something to check? have to change the phone???
tnx

Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.

Ok but i need ti know if is possible to check the health device status

What do you mean by health? You mean each component?

I mean if is possible that something hardware is defective or going to be defective.
can I run some tests?

I know of no tests that are available to the public.

Ok

audit13 said:
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Click to expand...
Click to collapse
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace

WallaceLau said:
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
Click to expand...
Click to collapse
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?

audit13 said:
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
Click to expand...
Click to collapse
First time I did a wipe it took over an hour, then the phone rebooted to the dead android screen. So I tried to wipe again, and it seems like all subsequent wipe took anywhere between 3-5 minutes. No error on each wipe (can't say on the first one, since by the time I got back to the phone it has already rebooted). And yes, I did flashed everything - boot, cache, recovery, system, userdata, bootloader, radio - not exactly in that sequence, but all of those partitions are flashed with the image that comes with the Google download package. Then factory reset and reboot.
Thanks,
Wallace

Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.

audit13 said:
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
Click to expand...
Click to collapse
Did a "fastboot format cache" and "fastboot format userdata", no error. Still won't boot... are those the commands you are referring to?

Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.

audit13 said:
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
Click to expand...
Click to collapse
Tried all those, and yes same result... also, I flashed a different recovery (TWRP) and thereafter I can't even flash new ROMs anymore. ADB Sideload error our (forgot to write down the error message), and if I copy the file to internal storage and flash from there, TWRP will get stuck for hours.
How common are eMMC corruptions?
W.

The emmc problem is not that common, but it does happen. I'm not sure if it is partition or software corruption or a physical defect.
Other xda members have encountered emmc problems too that could only be fixed through a motherboard swap.

I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk

Sarvesh.huddedar said:
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk

The constant boot looping could be a power button problem?

kenbrownstone said:
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk

Sarvesh.huddedar said:
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Maybe im mistaken but evertime i had to put in a password in ttwrp i had gotten encrypted...you get it fixed? My friends started bootlooping for no reason and wouldnt stop til the battery was dead.. Never seen a stock phone do that..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
Reasearch it.... It totally sounds like what happened to me...
Sent from my Nexus 6P using Tapatalk

[SOLVED] Google Apps Not Working And Recovery Refusing To Open

About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat

Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.

acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.

NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.