Related
if this is in the wrong area im sorry i just need to know my buddy used ace kit to root my phone and it went fine then we updated rom manager and did a backup on there. then he flashed cm7 not sure which one but it was took one that said stable. now my phone is just booting cyanogen mod7 over and over. what should i do? am i screwed? sorry im new and i thought i had help but he doesent know lol.
pull the battery for like 30 sec. put it back in now hold volume down button while you press the power button the phone will go into bootloader. it will search for pd98img. once it does you will see option that says recovery click on recovery. once there do a factory wipe then restore your backup. once it boots then retry cm7 but you need to wipe the phone goin g from a sense rom to aosp . also look in the general section of inspire forums., there is a stickie that explains all about this kind of stuff
t just keeps having the cm7 bootscreen over and over again been like 20 minutes and i cant figure out if i should pull battery? am i screwed? please anyone help a poor inspire user
thanks i will try that does it take longer then 20 minutes for first boot on cm7?
str8killinya said:
thanks i will try that does it take longer then 20 minutes for first boot on cm7?
Click to expand...
Click to collapse
no ten minutes is pretty normal. if its bootlooping usually your phone will try to load past the boot animation then reeboot instantly
Take your sd card out and put cm7 and gapps on it then put it back in, mind you while the phone is off.
Pull the battery, reinsert it, power on w/ volume dn+ power button as instructed. Let it go through the search process, when you're presented the option to select recovery, do so at that time. Once in Clockwork Mod, select wipe data/factory reset, now select install zip, select the rom and flash it, once it's done flash gapps then reboot.
All should be well in your world...
sorry confused about one thing when i hold volume down and power then click recovery do i pick backup/restore and use my backup or do i do factory wipe to get back to how i was before i flashed? sorry for the newbishness
i just want to go back to the way it was right after root till i figure out what he did wrong
factory wipe first that will wipe all of cm7 stuff off of there then restore your backup
I dont use rom manager i seem to always have problems with it just find a rom here you like.(i use virtuous unity ) download it move it to the root of your sd card and then wipe and flash it in recovery. if you like the stock look try leedroid or rumrunner there both very stable roms as well
Thank you guys so much im back to sense and without the helpless help from my buddy i will read alittle before i flash again. Thanks Again you saved a very happy Inspire 4g user!
no problem. but dont let it discourage you ive been boot looped more than once. best thing you can do is read,read,read.
Just got cm7 rc1 working finally and now my Inspire is fast as I've ever seen it. Can't wait to start really enjoying android.
str8killinya said:
Just got cm7 rc1 working finally and now my Inspire is fast as I've ever seen it. Can't wait to start really enjoying android.
Click to expand...
Click to collapse
Don't forget to wipe dalvik cache every time your flash roms or any major system file for that matter
If I restore from backup and then put in a new SD card I just got then I can just stick new SD card in right? It do I need to transfer stuff cause of the goldcard?
Str8, unless you like running an outdated build, I suggest you move up to the latest nightly. It has quite a few features that the stable build doesn't and is stable itself. It's all I ever use.
Hello guys, I have updated to cm7 recently and notice I can't do screen captures anymore, does anyone know if they rerouted it to another button or anything?
Hold power, hit screenshot
Mister Hat said:
Hold power, hit screenshot
Click to expand...
Click to collapse
I hold power and just the profile, airplane, reboot, power off options pop up.
I use to only have to press home button and powerbutton together but its not working now
RC1 doesn't have the option Mister Hat describes, the nightlies do.
Use Screenshot ER if you don't want to update to the nightlies.
wewoapsiak said:
RC1 doesn't have the option Mister Hat describes, the nightlies do.
Use Screenshot ER if you don't want to update to the nightlies.
Click to expand...
Click to collapse
Ok which nightly would I need? I'm new to this, is it a update or would I have to flash a whole new Tom again? Don't really want to do that as I have my phone setup real nice.
mikejones999 said:
Ok which nightly would I need? I'm new to this, is it a update or would I have to flash a whole new Tom again? Don't really want to do that as I have my phone setup real nice.
Click to expand...
Click to collapse
The newest nightlies are all fine IMO, as one comes out almost everyday, flash the newest one.
You have to flash it, but you do not have to wipe prior to; so you don't have to worry about losing your setup.
Edit:
Btw, the search function, if it is working, would have landed you these answers.
Also there is a Q&A forum for posts like this.
Good luck.
Oh, he said he flashed it recently, I assumed he meant the most recent. My badd.
Yea the newest nightly is ten times better then the rc1 since then we've had touch to focus in camera data is faster better battery, screen shot when u hold down power u see it in menu, newer kernel converted to ext4, just download the latest nightly, and all u have to do because it is the same rom is wipe cache, then go to advanced and wipe dalvik cache then flash nightly on top of ur rom (rc1) now because u didn't wipe data everything will still be the same way u left it nothing will be erased and u will be updated to newest nightly, now whenever u wana update u do just that, wipe cache and dalvik then. Flash
sarni84 said:
Yea the newest nightly is ten times better then the rc1 since then we've had touch to focus in camera data is faster better battery, screen shot when u hold down power u see it in menu, newer kernel converted to ext4, just download the latest nightly, and all u have to do because it is the same rom is wipe cache, then go to advanced and wipe dalvik cache then flash nightly on top of ur rom (rc1) now because u didn't wipe data everything will still be the same way u left it nothing will be erased and u will be updated to newest nightly, now whenever u wana update u do just that, wipe cache and dalvik then. Flash
Click to expand...
Click to collapse
Thanks for the tips, but I had just flashed it before I saw your reply, I didn't wipe anything though :/ I hope it will be ok? So far so good and I see the new menu for the screen shot
The basic deal is I got bored of the software and decided that I should root an install some custom ROMs on my Nexus S.
I used the One click method posted I believe in the general forum and everything went smoothly. I downloaded the latest AOKP and CM zips, put them onto my phones memory and went on with my day.
So today I began to put on the AOKP ROM and it got stuck at the initiating swagger screen. And was stuck there for a good 20minutes. I didn't know what to do, so I battery pulled.
I thought I had some backup saved from the day before, but that wasn't the case. So now I'm essentially stuck in thee boot menu for clockwork and my phone has been rendered useless. If any of you guys know what I should do, please tell, I'm extremely pissed off at myself for letting this happen.
I deleted the Cache partition and Dalvik thing when I was first getting ready to put on the ROM. I didn't to a factory wipe, so that might be an issue? I don't know. I've also tried plugging the phone into my computer, but because I cant turn on USB mass storage, I can't look through that either.
Any help would be greatly appreciated. Thanks
Hi,
If ur in the bootloader screen scroll down until u see recovery. Then press the power button.
From recovery scroll down to mounts and storage to connect to computer via USB.
From here u have a few options bjt i would just download another ROM and its gapps or a ROM that already contains them.
Just be careful to get the correct zips for ur type of phone
Good luck
Vs Nexus S4G using tapatalk2
Wow. Thanks a lot. Do you think I should do a factory reset before I install a new rom?
EDIT: Hey vidaljs, thanks for the help! I got the CM10 ROM up and running, apparently I was running some really old version! That USB mount thing really helped!!
Chillingly Based said:
Wow. Thanks a lot. Do you think I should do a factory reset before I install a new rom?
EDIT: Hey vidaljs, thanks for the help! I got the CM10 ROM up and running, apparently I was running some really old version! That USB mount thing really helped!!
Click to expand...
Click to collapse
No worries
Next thing u should do is make a backup of this working ROM so u can always go back to it in a pinch.
And always follow what the developers suggest in their thread since they created it.
But when I go to a new ROM, I always do a factory reset, wipe cache and wipe Dalvic.
If u haven't found it yet, use titanium backup for ur apps so its easier to apply them to ur newly flashed ROM. The free version is fine but I've heard that paid version has some extra useful benefits.
Good luck and happy flashing.
Vs Nexus S4G using tapatalk2
vidaljs said:
No worries
Next thing u should do is make a backup of this working ROM so u can always go back to it in a pinch.
Click to expand...
Click to collapse
Yeah I should have done it first
Hi guys,
Almost same stroy, I tried to Root & install Cyanomodgen 10 on my Nexus S, but boot isn't working quite well, and I'm stuck at a circling image preparing the launch.
Recovery isn't working I got stuck at the image with the robot and the back and the exclamation mark on top of it and like 5 minutes later it launch the cyanomodgen ring again - and can't get in download mode.
I pretty don't get what I should do.
Any idea?
I feel I lack some info on my problem, I'll create a fresh post for it
thanks
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
kanjigirl said:
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
Click to expand...
Click to collapse
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
LS.xD said:
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
Click to expand...
Click to collapse
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
kanjigirl said:
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
Click to expand...
Click to collapse
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
LS.xD said:
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
Click to expand...
Click to collapse
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
kanjigirl said:
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
Click to expand...
Click to collapse
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
LS.xD said:
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
Click to expand...
Click to collapse
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
kanjigirl said:
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
Click to expand...
Click to collapse
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
LS.xD said:
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
Click to expand...
Click to collapse
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
kanjigirl said:
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
Click to expand...
Click to collapse
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
LS.xD said:
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
Click to expand...
Click to collapse
That looks great, thanks very much!
I'll post back here once I get my phone straightened out in the next couple of days to say what happened, in case it helps someone later.
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
kanjigirl said:
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
Click to expand...
Click to collapse
Kernel is always included in the new "rom". So everytime you flash a rom, you automatically flash the kernel with it. PIT is the partition table of the phones partition. As long its not clearly necessary, DON'T ever change it!
Got it, thank you for your help!
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
kanjigirl said:
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
Click to expand...
Click to collapse
Sounds great
Quick question - if this thread is still open. The phone's been fine since I flashed CM 11 and Pico GApps, until this morning, when it now does 'Android is Upgrading' every time I boot and every user app crashes as soon as it's opened. I have all auto-syncs and auto-updates disabled, and haven't added any user apps to the phone since Wednesday.
Do I need to flash again, and then have to go through the restore process all over? Or could it be an app causing this? I'm not sure where to look for a source of the problem.