Database Info

[Q] BlackBean (BAKED) ROM - apps stopping

I wanted to post this in the BAKED thread in the developer section but I don't have enough poststo do it there, so hopefully someone here can help.
I just flashed crespo BlackBean 7 (BAKED) ROM (on my Nexus S) and inverted gapps. It seems to have installed properly but whenever I reboot I get a message that several processes have stopped such as YouTube and GMail, and when I go in to system settings -> storage I get a message saying "Unfortunately, Settings has stopped". I get that message every time consistently. I've tried re-flashing the ROM but to no avail. When I installed the ROM I wiped "Dalvik cache", wiped "Battery Stats" and wiped "Cache partition".
It appears I've not done something or done something wrong, so if anyone here can help I'd appreciate it.

Did you full wipe before installing the rom? That means factory reset/data wipe.

polobunny said:
Did you full wipe before installing the rom? That means factory reset/data wipe.
Click to expand...
Click to collapse
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?

volan1 said:
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
Click to expand...
Click to collapse
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.

volan1 said:
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
Click to expand...
Click to collapse
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S

anshumandash said:
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
Click to expand...
Click to collapse
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?

volan1 said:
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
Click to expand...
Click to collapse
There isn't any boot issue with the ROM. If you decide to try this ROM again, try to do a clean install.
Boot into recovery, do a factory wipe, go to advanced & wipe dalvik cache, go to mounts & format /systems. Flash ROM & gapps, reboot.
Sent from my Nexus S using xda app-developers app

[Q] Constant app lock ups - even after reinstalling

Hi all. I've had an issue for a few weeks now. I have apps that are constanly locking up and force closing on my phone. I'm currently running Jelly Beans 11 with a rooted and unlocked GS3.
All different apps force close: gmail, play store, kik messenger, system processes. It seems it's not centralized to gapps for instance.
I've installed Beans 5, 6, 8, 9 once. 10 about 2 times, and version 11 i think 3 times. Each time I do a delvik cache wipe, a cache wipe, and a factory reset via CWM. Some times even the initial setup wizard will lock up after first boot.
I've tried flashing different modems as well, and i'm currently on the newest verizon one, the K3.
If anyone has any information on how to fix this it would be much appreciated. Even a full phone wipe or something... I'm going to try clean rom and CM 4.2 tonight.
In a seperate issue, that may or may not be related:
I'm currently in iraq and i'm using the world phone exploit to get cell service and data here in Baghdad. It used to work great, but now the data connection will be connected, but no data will upload or download for long periods of time. For example i could send a kik message while connected to EDGE network, but it might take an hour for it to actually send. It didn't used to do this...
All things considered i'm wondering if I actually physically damaged the phone somehow...
If I haven't provided enough information, please let me know and i'll be happy to reply.

Ok, i tried CM 4.2 and there weren't any lockups. But i couldn't keep the rom, doesn't seem to be any way to get cell service. it won't let me change the band to global.
Going to try clean rom now.

Clean rom works fine as well...
So why would Jelly Beans ROM, that's worked fine for quite a while for me, through various versions of ICS and JB, to suddenly cause apps to force close and general instability?
I've checked MD5's and they're correct...
I think i still need a few more posts before i can post in the dev section as well.
Any help is appreciated, thanks

Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app

bobAbooE said:
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1
fixing permissions is a must after a flash/restore.

ok i'll try installing beans again and using fix permissions afterwards.
Thanks

still not working
Ok, i've tried fixing permissions and i'm still having problems. Gapps has stopped working... System UI has stopped working... I followed the above posts exactly.
Any other suggestions?

Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app

bobAbooE said:
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
gapps was the term that the phone said when it crashed. But no i'm not flashing the gapps, they're included on most of the roms like Jelly Beans 11. I've had a few different gapps force close, like the store and gmail. but i've also had the system ui and kik force close.

Sorry man, it's beyond my knowledge. Never had a bunch of apps stop working that fixing permissions or a clean install didn't fix.
Sent from my SCH-I535 using xda app-developers app

How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.

SlimSnoopOS said:
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
Click to expand...
Click to collapse
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?

Icewolf69 said:
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Click to expand...
Click to collapse
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.

SlimSnoopOS said:
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
Click to expand...
Click to collapse
I just did a fresh install of 10, including cache, delvik, factory reset, system partition, and after first boot i went back and fixed permissions. I'm still getting force closes. media service, google play, etc. I don't have many apps on it yet to see what else will force close since i'm not using titanium backup to restore anything. Everything is fresh and coming from the play store...
I should be hitting 10 posts soon so i'll be able to try and post in the beans thread, or the dev section. But any other ideas would be appreciated. Thanks.

I also seem to be getting a lot of "invalid file" and "file couldn't be downloaded" when i try to install apps from the store. Not sure what this means

Beans 12 came out today and I tried installing that and i'm getting the same issue.
Tomorrow i'm going to do a full wipe to stock verizon image. and go through the unlock and root motions unless someone has any more ideas.
Thank you for the help so far, i appreciate it.

I did a complete stock OTA flash last night to verizon's jelly bean, and went through the root and unlock process again. flashed beans 12, and i'm still getting the same error.
I'm on beans 6 right now and it's working great. Going to try changing a few settings in 12 to see if it works and then maybe see if 10 works.

"Unfortunately, Phone has stopped working" error after factory reset

Guys, I'm running Purity room with Franco kernel and PA GAPPS. I've had this problem recently, where my room is running perfectly. But when ever I do a factory reset through CWM 6.0.4.5 and reboot, the error "phone had stopped" pops up and all I can do is long press the power button to reboot into recovery and restore a backup.
Any ideas guys?
Sent from my Nexus 5 using XDA Premium 4 mobile app

I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.

mistahseller said:
I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.
Click to expand...
Click to collapse
Thanks for the reply, however, Ive already done the following:
1- Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
2- Wipe Data/Factory reset > Install Purity (with/without GAPPS) > Reboot: "Phone has stopped" Error
3- Wipe Data/Factory reset > Install Puroty (with/without Franco kernel) > Reboot: "Phone has stopped" Error
4- Wipe Data/Factory reset > Installed other ROM> Reboot: "Phone has stopped" Error
5- Wipe Dialler/SIM toolkit > Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
Cache/Dalvik Cache cleared every time.
The old backup still works, I even dirty flashed the new Purity version over it and works ok. The problem only arises after Wipe Data/Factory Reset.
Couldn't find any other solutions, any other suggestions?

Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.

I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).

OK try to install cyanogen mode and let me know what happened
Sent from my Opal 800 using xda app-developers app

mistahseller said:
Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.
Click to expand...
Click to collapse
Will try resetting and well then install twrp ... let's see. Can't let it be coz I need to be able to test other roms and stuff.
Sent from my Nexus 5 using XDA Premium 4 mobile app

es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
Yeah that would be an easier option to try before resetting... Will try twrp as well.
Sent from my Nexus 5 using XDA Premium 4 mobile app

You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
What does TWRP not do that CWM does?

mistahseller said:
You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
What does TWRP not do that CWM does?
Click to expand...
Click to collapse
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.

es0tericcha0s said:
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.
Click to expand...
Click to collapse
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?

Ad.Shk2 said:
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?
Click to expand...
Click to collapse
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.

es0tericcha0s said:
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?

Ad.Shk2 said:
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?
Click to expand...
Click to collapse
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.

es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
Nope no pin.... Will try the permissions thing and shall let you know.
Sent from my Nexus 5 using XDA Premium 4 mobile app

es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Ad.Shk2 said:
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It looks like at this point, it's time to try another rom or update the Purity one. That, or maybe try this: http://forum.xda-developers.com/showthread.php?t=2526844

Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Ad.Shk2 said:
Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're welcome. Glad all is well again.

I had the same problem. But i did not make a backup..
How can I unninstall phone apk from recovery?

Just rooted, froze apps, and now stuck on Verizon screen

I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!

Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?

Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.

You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache

andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.

dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....

Apps stop working

Hello everyone
I broke my phone so I took one of my friend's old Nexus 5 which was not working and I tried to make it work.
However, I'm a complete noob. The phone wasn't turning on, so I used Nexus Root Toolkit in order to flash Android 6.0.1 M4B30Z
I had a lot of troubles, got stuck in booting loops and I couldn't solve it, even by wiping the phone over and over. So I finaly decided to flash Pure Nexus Hammerhead, and the phone finaly turned on.
However, all the apps are crashing (I'm not talking about store apps, but the one on the phone. Let's say I want to go in my settings, then the "settings" app will crash.
Sometimes, apps don't crash but the phone just freezes.
I don't know what to do anymore, that's why I resquest your help. What should I do to have a working phone ?
Thanks

Anyone can help me and tell me what to try ?

Mouchoir said:
Anyone can help me and tell me what to try ?
Click to expand...
Click to collapse
Sounds like you need to clean flash, factory reset as well as wipe system in advanced wipe in twrp before flashing ROM and gapps (I recommend Beans gapps minimal, not the full package) Make sure to wipe caches after flashing. Also make sure you're flashing an up to date build of Pure Nexus https://forum.xda-developers.com/google-nexus-5/development/rom-pure-nexus-substratum-t3477787
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192

Hello,
So I went to TWRP and clicked "Wipe", checked everything and restarted. Now I only have the "Google" screen displaying, and I'm not sure what to do to solve that