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
Related
So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Note: I accidentally posted this in the Android Q&A section, so I apologize for the double post. I just think this is probably the best place to get my answer.
Did you flash the boot.img?
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
jon8105 said:
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
Click to expand...
Click to collapse
if they are backups from sense, that *MAY* cause problems, but don't quote me on that. I don't use sense, can't say for sure
OK, maybe that is why. Not a big deal since I haven't had the One X too long. Thanks for the help guys.
Good to know
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
intelligentduck said:
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
Click to expand...
Click to collapse
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Trozzul said:
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Click to expand...
Click to collapse
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
intelligentduck said:
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
Click to expand...
Click to collapse
might want to try flashing a stock rom via odin cause it sounds like you have stock recovery now, i dont know if anyone will pick you up in the q&a section, since yours is us cellular i dont think they have a forum for that specific contractor just only t-mobile at&t and verizon would have one. you can ask them in their q&a but tell them your situation and that your on us cellular. good luck mate. if ya have any questions just ask right here.
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
Hey,
i have samsung sgh-t699, i once updated my phone to cm 11 via its settings panel and in the middle of update it failed and said error.
so i had to find a way to fix and i downloaded cyanogenmod cm11 nighty and installed it via install zip from external sd card and it was sucessfull but i could no longer install any of the previous softwares i had cause it said software already exist on your phone.
so i decided to start all over again i wiped data/factory reset, wipe cache, wipe davik and re installed cm 11 and gapp and the cwm said installation from sdcard sucessfull. but when i rebooted system nothing hapens i just see the cyanogen mode animation going round and round and my phone wont boot any futher step than that it just heats up untill i switch it off. i did the reinstallation several time , flashed a new odin all the time untill my download binary count reads 15 and the same thing happens.
i dont know what else to do, please anyone any idea....please help
farhakassim said:
Hey,
i have samsung sgh-t699, i once updated my phone to cm 11 via its settings panel and in the middle of update it failed and said error.
so i had to find a way to fix and i downloaded cyanogenmod cm11 nighty and installed it via install zip from external sd card and it was sucessfull but i could no longer install any of the previous softwares i had cause it said software already exist on your phone.
so i decided to start all over again i wiped data/factory reset, wipe cache, wipe davik and re installed cm 11 and gapp and the cwm said installation from sdcard sucessfull. but when i rebooted system nothing hapens i just see the cyanogen mode animation going round and round and my phone wont boot any futher step than that it just heats up untill i switch it off. i did the reinstallation several time , flashed a new odin all the time untill my download binary count reads 15 and the same thing happens.
i dont know what else to do, please anyone any idea....please help
Click to expand...
Click to collapse
It might be the specific nightly you are dealing with that is faulty. My advice would be to try another nightly version build from a different date. Do a full system wipe like you did before, Wiping Data, cache, and Dalvik. Then try installing a nightly from another date, until you get one to work for you properly. One is bound to work eventually. My brother had issues similar on his tablet, we ended up discovering that the specific build that day was to blame. Lastly as a tip for the future, a question like this is supposed to posted in the Q/A section under your specific device. Here's the link http://forum.xda-developers.com/galaxy-s-relay-4g/help. If you have further questions here's a link to the CM11 forum for your specific device. http://forum.xda-developers.com/showthread.php?t=2779975. Since they actually have the device, they can offer you better answers if my suggestion didn't work. It never hurts to shoot them a message. Best of luck, hopefully you can get CM 11 to work properly on your device.
ZekeAdebayo said:
It might be the specific nightly you are dealing with that is faulty. My advice would be to try another nightly version build from a different date. Do a full system wipe like you did before, Wiping Data, cache, and Dalvik. Then try installing a nightly from another date, until you get one to work for you properly. One is bound to work eventually. My brother had issues similar on his tablet, we ended up discovering that the specific build that day was to blame. Lastly as a tip for the future, a question like this is supposed to posted in the Q/A section under your specific device. Here's the link http://forum.xda-developers.com/galaxy-s-relay-4g/help. If you have further questions here's a link to the CM11 forum for your specific device. http://forum.xda-developers.com/showthread.php?t=2779975. Since they actually have the device, they can offer you better answers if my suggestion didn't work. It never hurts to shoot them a message. Best of luck, hopefully you can get CM 11 to work properly on your device.
Click to expand...
Click to collapse
thank you soo much i am trying up your advice...and i'll try also reposting on the right forum.
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