im sure theres a very simple solution im missing and this can be chalked up to a noob post, but im currently at a loss. I recently got a nexus 5x and unlocked the bootloader. everything went smoothly and i successfully flashed purenexus onto it. however, upon setting it up, i ran into some problems.
1: wifi cant connect. trying to connect to my wifi results in the error message "Unfortunately, settings has stopped.
2: going to settings > security results in the same error message.
3: opening camera results in an error message saying camera has closed.
ive tried factory resetting, wiping everything, and formatting data from twrp, but every rom i flash still has these same problems.
ive tried pure nexus, chroma, tesla, bliss, and xtrafactory, but these same problems persist. ive tried flashing the corresponding vendor images over all roms but pure nexus, because i cannot get the pure nexus vendor image (MTC20F) onto my nexus via adb push command. this isnt my first phone ive rooted and customized before but id still classify myself as very noob. i apologize if this was a dumb thread or if i broke any rules.
TL;DR: "unfortunately settings has stopped" error occurring no matter what rom i flash.
capmorrow said:
im sure theres a very simple solution im missing and this can be chalked up to a noob post, but im currently at a loss. I recently got a nexus 5x and unlocked the bootloader. everything went smoothly and i successfully flashed purenexus onto it. however, upon setting it up, i ran into some problems.
1: wifi cant connect. trying to connect to my wifi results in the error message "Unfortunately, settings has stopped.
2: going to settings > security results in the same error message.
3: opening camera results in an error message saying camera has closed.
ive tried factory resetting, wiping everything, and formatting data from twrp, but every rom i flash still has these same problems.
ive tried pure nexus, chroma, tesla, bliss, and xtrafactory, but these same problems persist. ive tried flashing the corresponding vendor images over all roms but pure nexus, because i cannot get the pure nexus vendor image (MTC20F) onto my nexus via adb push command. this isnt my first phone ive rooted and customized before but id still classify myself as very noob. i apologize if this was a dumb thread or if i broke any rules.
TL;DR: "unfortunately settings has stopped" error occurring no matter what rom i flash.
Click to expand...
Click to collapse
Your best bet is to run the fastboot command with the MTC20F (or MTC20K for September 6.0.1 based roms) vendor:
fastboot flash vendor /path/to/vendor.img
Boot into TWRP, factory reset and wipe system, then flash your rom and their recommended gapps package.
For adb push, could you post a screenshot of your command prompt? One quick tip is that the file path to the phone is case sensitive.
Sent from my Nexus 5X using Tapatalk
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
Some time ago, I've tried to download some game from android market, but shortly after it finished, "process.google.acore has stopped" appeared. After showing up rapidly a few times, the error forced my phone to shut down.
After rebooting (CM 11 installed with 6.0.4.8 CWM) and unlocking the screen lock, the error showed up again. After dismissing it, I got another "google.process.gapps has stopped" and then "google Keep has stopped". Some seconds later, there was an error notification in the status bar (backup account needed) and another bunch of errors. I was unable to even get to the drawer, because the erorrs were showing one after another instantly. Finally, the phone crashed (I think...) by suddenly displaying cyanogenmod boot screen (it was stuck this way for 3 hours before the battery ran out). I tried rebooting it again a few times, but with the same outcome every time.
My first guess was to re-flash CM11. After full wipe and install from zip (no errors) the phone booted up... right into the system I was using minutes before, with the same wallpaper, pattern lock, theme and problem described above. Then, I tried some solutions found online such as:
1. flashing CWM (no effect; even worse, when I tried flashing older version to see if anything changed, it was still the newest one!)
2. flashing diffrent ROM (liquid-smooth, no effect, still CM11)
3. flashing stock kernel
4. flashing stock ROM
I gave up for two weeks, but today I tried again flashing CM11, but I received status 7 error (liquid-smooth got "some syslinks are missing")
I'm slowly running out of ideas, now I just want my phone to run ANYTHING. Please help me, because I think I tried every solution from XDA and nothing worked.
what happen when you flash stock rom via flashtool?
stalin.sk2 said:
what happen when you flash stock rom via flashtool?
Click to expand...
Click to collapse
No effect, CM11 still shows up after boot
Isn't the syslinks problem due to a broken NAND memory? That's what I've gathered from the problems cropping up recently.
The best thing to do is contact the ROM developer.
Sent from my C1905 using XDA Premium 4 mobile app
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
Hello,
I'm having a weird issue with my Note 7 that I didn't have at all until tried to root for the first time....
It randomly restarts, sometimes is very often and sometimes it take a few hours to do it, but when it does it just restarts out of nothing and when Android loads again it asks me for a password that doesn't even exsits
"To start your device, enter your password" (Picture attached)
This started to happen after used the rootable kernel that was published before SuperSU 2.77 Beta but even reflashing the stock firmware, bootloader, modem, CSC it keeps doing it even when my Android is not yet configured (at the first Welcome screen before setting the phone up), so there is no password at all at this point. I've tried my Google account password, but it doesn't work.
This message is the same that comes up when you select "Secure Boot" so you need to enter a password or PIN to decrypt your data and be able to load it, but I don't have that option checked, and could not be checked when the phone is not even configured.
The way to work around this issue is flashing the no-verity-opt-encrypt mod that is not supposed to be needed anymore after SuperSU 2.77 has been released. So flashing this mod will get me into my Android home screen but it will eventually restart again and I need to flash this mod again.
This is what I've tried so far and it keeps happening:
- Flashed the rootable kernel when it was published and the no-verity mod. I formated data as indicated in the post. Then this problem appeared.
- Flashed stock firmware, bootloader, modem, csc thinking this would remove any trace of the mods I flashed, but kept happening.
- Factory reset from the Samsung recovery, had the "no verity" errors sometimes and sometimes not.
- Flashed other firmwares, bootloaders, modems, csc from other countries but for the same model N930F and kept happening.
- Flashed custom ROMs, formated system, data, everything.
- Flashed stock firmware again.
- Flashed custom ROMS again with the new SuperSU 2.77 and keeps happening.
I have done every single flash that actually exists for the Note 7 and formated everything with no luck....
Has anyone have this issue or had it at all at some moment? If so... How did you manage to get rid of this message?
I hope someone can help, If it was faulty phone I think it would restart at any point even in Recovery or Download mode, but only happens inside of Android.
Seems a common problem I think?
http://forum.xda-developers.com/showthread.php?t=3444510
Sent from my Nexus 6P using Tapatalk
Yep, saw that post... But never seen anyone complaining about the phone asking for a password when reboots (only when it crashes) its like it was asking for a password to decrypt the phone.