Updated to 38R via OTA but i got the CM Lockscreen has stopped when i booted the phone. So i had to factory reset and delete all my data before my phone worked again :/ now i still get the error when i download and change my wallpaper.. So it seems like i am unable to change it otherwise my phone bugs...
Anyone who can help me? This is really stressing me, because I am really happy for my OPO
Were you completely stock before the update?
Transmitted via Bacon
This exactly happened to me just now too. I changed the wallpaper and it says CM Lockscreen has stopped. Anyways to fix? I wiped the davik cache, but it did not work. It was really difficult to get the the recovery mode too. Please help thank you.
I don't know what you mean by completely stock but I have wipe the dalvik cache and the update.
By compete stock I mean did you have any modifications at all before taking the update? Any modified lockscreen, mixer paths, anything at all?
Transmitted via Bacon
Try erasing and re-flashing your persist partition as per here this helped me, and has help many on the OPO forums with the same issue.
Related
I've had my Nexus S for a year now and it's been pretty problem free... When it had Gingerbread it had the odd reboot glitch but since ICS it's been solid. I have the bootloader unlocked and had root. I had tried out a couple of custom ROMs and had gone back to stock ICS in anticipation of JB rolling out in July. I got the OTA push of JB in mid July and after a factory refresh have had no problems with the phone until yesterday.
I was typing a text message and my phone rebooted in my hand. It never did complete booting and left me at a prompt that stated "Type password to decrypt storage" and nothing would make this phone boot! Also, since the JB update I no longer had root and Clockwork Recovery no longer worked because I didn't have root... which I wasn't worried about up until now. I had to tether the phone to my laptop reset Recovery using the SDK tools and then wipe everything and reset the phone and reinstall all my apps. Funny thing is I've not been able to find much about this from any of the forums I read frequently... seems there aren't many who have experienced this.
Just wondering if anyone else has run into it...
it's happend for me too. i had to wipe cache and fixed.
Same thing happened to my Nexus S. I have no idea how it came into this "type password to decrypt storage" damned state. I'm trying all passwords and PINs I know but none is working! I'm trying to avoid a factory reset.... Isn't there a way to log in and override this thing, something like forgotten password in emails???
still no solution for this? i've wiped data and cache and still no fix!
I'm facing the same issue: woke up this morning to find my phone asking for a password in order to decrypt storage. Very annoying, since I don't have a very recent backup.
Running CM10.1 nightly 0210 with stock CM kernel. I tried reinstalling CM and wiping cache, but that didn't help. I'll see if I can fix it and and will repost here if/how I fixed it.
gearjunkeez said:
still no solution for this? i've wiped data and cache and still no fix!
Click to expand...
Click to collapse
If you can boot into bootloader (fastboot), try to flash Google factory image.
untar (unrar/7-zip) the tar file and flash the update zip within. This should wipe everything including system.
Code:
fastboot -w update image-soju-jzo54k.zip
kooske said:
I'll see if I can fix it and and will repost here if/how I fixed it.
Click to expand...
Click to collapse
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!
HELP!
I just had the same thing happen to my phone. Can you please dumb down what you just said for me? The only part I care about is how to recover my pictures. I haven't done the factory reset yet as I've been trying every password I can think of and now see that it is a bug and not something I have done. Anyway, I have 3 gigs of pictures of my 18 month old that I will cry if I lose so if you can help me recover them I would really appreciate it. I have tried hooking my phone up to my computer in it's encrypted state and it does not register. Please explain what you did in simplified terms for me as I have no idea what ROM or CWM means. Thanks!
kooske said:
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!
Click to expand...
Click to collapse
Hello there !
I can't toggle on Bluetooth in my GT-P3110 recently.. I'm not on airplane mode.. but WiFi works though...
I even flashed a CM ROM(10.1.3 right now) to see if it works.(may be an silly deed.. I'm just new to these android things)
I have uploaded two videos which shows what really happens when trying to turn on bluetooth...
When I was using the stock rom
After flashing CM
I think that I'm having some hardware failure (i.e. dropping the unit - I never dropped myself.. idk if it happened actually as I share this tablet with my family )
I want to know whether this can be repaired ?.
Is there a seperate accessory inside for Bluetooth which can be replaced ?
Thanks in advance !
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
katsika said:
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
Click to expand...
Click to collapse
Thanks for the reply... I noticed the issue when I was on stock stock ROM. I may have to send it to Samsung.
Thanks for the support :highfive:
Is it possible you have another kernel other than stock?
Sent from my XT907 using xda app-developers app
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.
alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk
i dont use this forum as i have a different phone and i dont particularly want to sift through every thread to find an answer so i thought id ask to find out for myself
my partner owns a stock unrooted totally unmolestered original moto g running android lollipop and earlier today it started to lag and flashed up with an error she didnt have time to read, not long after it completely froze so i tried to turn it off and on again. after trying to turn it on again it has gone in to a bootloop and will not start properly.
any help on a solution would be much appreciated if anyone can help me ASAP.
cheers
Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.
audit13 said:
Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.
Click to expand...
Click to collapse
any guides on how to wipe the cache without rooting it? im assuming id have to use fastboot or adb or whatever but the internet hasnt exactly helped me with any solutions
Just wipe by booting into stock recovery.
http://www.android.gs/enter-recovery-mode-motorola-moto-g/
So, I installed a CyanogenMod Nightly and started to get a "System UI has stopped" error message , so I proceeded to do everything possible to fix it like wipe cache and data etc. I tried to side-load and push a newer nightly to TWRP but it would comeback with device not found (or connected) so in a last hurrah I went back into recovery and did a Advance Wipe of everything including System ( I know, I want to punch myself right about now). So after wiping System now I am stuck because I have a NEXUS 5 and no other way to flash a ROM, so did I royally just screwed myself or is there a solution to this? Please I will truly appreciated if anyone could help me with this.
I most clarify that ABD and Fastboot where working fine (before the last update I did). And also I was using Cyanogenmod Nightly CAF.
el_daYa said:
So, I installed a CyanogenMod Nightly and started to get a "System UI has stopped" error message , so I proceeded to do everything possible to fix it like wipe cache and data etc. I tried to side-load and push a newer nightly to TWRP but it would comeback with device not found (or connected) so in a last hurrah I went back into recovery and did a Advance Wipe of everything including System ( I know, I want to punch myself right about now). So after wiping System now I am stuck because I have a NEXUS 5 and no other way to flash a ROM, so did I royally just screwed myself or is there a solution to this? Please I will truly appreciated if anyone could help me with this.
I most clarify that ABD and Fastboot where working fine (before the last update I did). And also I was using Cyanogenmod Nightly CAF.
Click to expand...
Click to collapse
Tried flashing a factory image?? That might help I guess to bring ur mobile back to life
Thank you I followed your advice and everything is fine now. LOL, that was a real scare.
Good to know everything went fine press Thanks If my advice helped u