Installing ROM kills data? - Nexus 5X Q&A, Help & Troubleshooting

Hello, all. Long time Android user here, no stranger to rooting, ROMing, all that good stuff. I ran into sort of a weird issue that just started to happen quite consistently over the past few days. It all started when I tried to flash the new XtraSmooth Factory Image ROM when it went up. Everything went smooth, except, for some reason, it kills my data connection. FYI, I'm on Sprint, but I don't think that has anything to do with the issue. But it gets weirder. Even if I try to flash a different ROM, a ROM where I had data working before, data is still mucked. No connection whatsoever. If I try to restore a nandroid backup, even weirder things happen. Like for instance, the restoration process stopping at 20-25% and automatically rebooting back into Android (Which just happened an hour ago), or the backup going into a bootloop. Only solution to these problems are going back to stock and re-rooting everything all over again. It's really weird. Am I alone with this issue? Thanks for any help.

Yes your alone sadly. Restore to stock and root again/unlock bootloader, etc

Related

Crazy and extremely anooying reboots

I have a dinc running skyraider 3.3final and each time i reboot, i get the setup when i unlock
i tried skyraider, virtuous, and cyanogenmod and they all took me to setup after reboot and uninstalled all apps
~~~~please help~~~~
this happens even when you don't wipe?
I haven't tried not wiping
but everytime i do a full install and wipe everything, i still get the problem when i reboot. I've been going all day and everything has been working fine, i just don't want to reboot because i won't have anything
any suggestions
I had this happen to me also not too long ago, never tracked down what was causing it. No matter what ROM i flashed, or nandroid restored, I would end up with the setup screen and a multitude of FC's.
I ended up just returning to stock with the official RUU, and re-rooting. Haven't had an issue since. Make sure you back EVERYTHING up though.

[Q] Multiple Reboots

Today I was playing a game on my phone, all of a sudden, starts rebooting, then again, then again...After about four times, I had enough. Went into recovery, wiped all user data, cache, and davlik. Rebooted from there. Phone turned on, then started doing the same thing. At that point I tried a nandroid I made a couple days ago, but it still kept rebooting. Tried reflashing Synergy, of course I wiped everything again, but kept rebooting. Finally I ran a PC36IMG of the stock rom that I kept when I first rooted my Evo. Seems to have worked out because I'm not rebooting anymore. Now for my question, Can somebody explain what may have caused that to happen? I've been running Synergy for about two months and have had no problems. I generally don't overclock, but underclock when screen is off, and other big battery drainers. I was also running Freedom .9
Oh yeah, almost forgot. I've been lurking around your site for months and many of you have helped me out and don't even know it. So...THANK YOU!
Ok. Well I apparently do need help. Was able to run the 4.54 stock OTA rooted. Then tried Synergy, then MikG. Both are restarting non stop. I'm about to throw this thing through the window, go to Sprint, and get a cheapo phone.

[Q] I am absolutely stumped, please help

Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though

WiFi going nuts

I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Re-Install your Rom, first.
Update your Radios.
Simple.
alexdz said:
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Click to expand...
Click to collapse
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
vdude8 said:
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
Click to expand...
Click to collapse
I failed to mention initially, but I did try updating the radios as well. Regardless, I'm not having the problem anymore, and it's possible that there was simply something in my Titanium backups (done while on ICS) that it didn't like. I started thinking back on the timing and realized that the issue was showing up only after I went through the batch restore process, so this time I only restored a few apps that had data I didn't want to lose, and nothing else. So far so good.
Except of course that I'm now having a new problem that may be associated with a2sd, but I'll post that in that Deck's Reloaded thread...
Thanks!
I had a lot of force closes after restoring ICS backups in GB. Don't think the backups are backwards compatable...not all the time anyway.

Nexus reboots on its own constantly on multiple roms

Ok, I'm at a total loss. For some reason my gnex running liquidsmooth started rebooting randomly today. I tried wiping cache/dalvik and that didn't work, so I did a factory reset. That also didn't help, as soon I was asked to choose a wifi network the phone froze and rebooted. So I tried restoring to a previous working version of liquid. I still had the same problem. It rebooted every 5 minutes! Then, I tried wiping everything and installing a fresh copy of liquid,but I still couldn't get past choosing my wifi network w/o a reboot. So I finally tried restoring to a really old aokp backup and it STILL is rebooting. what the heck is going on? Can anybody give me any help? Is this a hardware issue? I've also tried two different batteries by the way.
Some more info. It seems to be tied to notifications. I got it running on the AOKP rom on airplane mod, but when i received a text from my wife it rebooted 3 times. I only got it to stop by putting it back into airplane mod. Could it be a radio issue? I'll try flashing some.
why dont you flash back to stock and see if that works fine. that will tell you everything.
Zepius said:
why dont you flash back to stock and see if that works fine. that will tell you everything.
Click to expand...
Click to collapse
Good point. I'll probably try flashing muzzy's rom really quick, since it's supposed to be so stable to see if that does the trick. If not I'll try going back to stock. I've never had to go back to stock with this phone, so I wouldn't mind avoiding it if I can, but anything is worth a shot at this point.
I really just need to nurse it along until the VZW one or Moto X come out. I'm holding out for those at this point.
I wouldn't recommend flashing another custom ROM. You should flash the factory images.

Categories

Resources