I'm sorry if I put this in the wrong thread. But I'm not sure where to put it.
Anyway,
>Nexus 6
>Rooted
>Custom rom (euphoria)
>Lollipop 5.1.1
I've had a nexus 5 and trust me, I've done my fair share of soft bricking. Over 50 times. Not even kidding. So I'm not new to rooting or anything like that. And I've rooted my nexus 6 properly. I've even unrooted it and lock the OEM and redid all of it. Thought I did something wrong so looked up a video and I did everything right. Ive tried the PNF Root (and no root) Notification fixer (even both of them together) and they don't work. I've uninstalled greenify because I know that can mess with it, I've tried removing my account and adding it back, I've honestly done anything I can think of. The only thing I haven't tried was to flash stock and see what it does. But before I had Xenon rom and before that I had liquidsmooth and before that I had Purity and they all did the same. So I don't think it's the rom. I've tried to look around and all I've found was delayed notification. They're not delayed, I'm not getting them at all.
Problem has seemed to be fixed when I flashed a different kind of gapps. I flashed Blackout gapps and they started working again. I'm not sure if that was the problem or not.
Related
Picked up my NC 1.0.1 today. Rooted without issue. After having a Google Talk conversation, I lost access to Marketplace, and all Google Apps? Can't log back in?
Anyone else having similar issues?
P.S. My wallpaper was changed as well ?!?!?!?!?!
p.p.s. My browsing history and favorites are gone too? Please tell me an update or something was just pushed out. I feel like I just wasted a few hours of my life here.
My rooted 1.0.1 nook has problems as well. Gets authorization error and resets data. After restoring through the clockwork recovery, had it up just for 5 minutes before it automatically reset again. Lost all my apps, market access, youtube, etc. Don't know if this issue has been discussed before. May just have to go back to stock.
It appears that something is amiss. I cannot sign back into any Google Services.
Can't establish a reliable data connection to the server
This could be a temporary problem or your phone may not be provisioned for data services. If it continues call Customer Care.
Click to expand...
Click to collapse
Would a simple re-rooting solve the issue?
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
abexman said:
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
Click to expand...
Click to collapse
I might add that I got my device it was at 1.0.0 and I rooted then reflashed to stock to upgrade to 1.0.1 and rerooted. Then I noticed after today's unexpected reboot/data wipe (the status screen during the reboot says it was wiping data) it again gave a message that it had just upgraded to 1.0.1 so I initially thought this was an issue with the device thinking the firmware upgrade was not quite done...
Mine quit working as well. Mine is a 1.0.0 that was auto-nootered. Everything was fine and I used it daily. Now it is a brick, nothing I do seems to make it boot. Every once in a while I can get the backlight to come on but nothing else and it just goes off again in a few seconds.
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
If your NC dosen't boot at all. Try doing a dd of snowfox's boot.img in dev section. See thread for more info. You'll need to boot into NF from SD.
Sent from my HTC Desire using XDA App
scottfish said:
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
Click to expand...
Click to collapse
I have tried rerooting, and restoring through clockwork...it seems to always revert and bootloop. Although the reroot lasted a week and clockwork restore hasn't lasted 24hrs twice now.
Not sure what to do but My wife is ready to kill me! I'll have to go stock till someone finds a way to bust up this authorization or just wait I read some ROMs are being developed.
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
I hadn't realized I should be doing this. I will try it. I am actually thinking that my first store purchase came w/ an update (my issue seemed to start right after a magazine trial purchase was made).
Thanks.
>DARKMAN< said:
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
Click to expand...
Click to collapse
Thank you, I will try that. All the searching I did was for disable OTA NC and such but actually searching for OTACerts brought out many many threads that were archived on this subject... I can't wait to get home to try it!
I did not rename the ota file.... will give it a go.
hi all,
i'm experiencing a weird problem. i've been flashing lots of roms (cm10.x, omni, stock-based ones), and suddenly my phone's camera started not working. however, if i turn the device off completely, start charging it, and turn it back on, the camera is fine until a reboot (even after unplugging from the charger). removing the sim card and rebooting also helps sometimes.
i've tried:
- factory reset
- flashing different roms
- revering to stock
- some forum post on the 'net about deleting the 'dcim' folder on both sd cards (wtf lol)
- disassembling the phone (my warranty is void anyways) and checking the main, battery and the camera's ribbon cable connection (they're fine)
i'm pretty sure it's not a hardware problem, but i can't be certain, of course.
anyone had this issue before? any suggestions? something else i forgot and should try?
thanks,
bamdad
update: somehow, after installing the new 4.3 firmware, it was alright for a while, then it started happening again. since my back cover was in quite a rough shape, i ordered a new one; after putting it on, the camera started working normally.
now i really don't get this, because i've taken the device apart dozens of times. it might have something to do with those little copper contacts being corroded on the old back cover, someone correct me if i'm wrong. the strange thing is that the camera seemed to work fine with the back cover off.
well, it's fixed now, but for how long? :/
this is just insane. yesterday i tried omnirom again, played around with it, then restored my backup of the official .199 firmware, and some time later tried to take a photo - boom, camera and flash hasn't worked since. now that i think of it, i distinctly remember trying a previous build of omnirom before the last time my phone went bonkers.
now i'm not hinting at that it's omnirom's fault directly, since apparently lots of people are using it without similar issues, and at the end of the day custom roms aren't responsible for damaging a device, but it's strange.
if someone has any pointers as to what should i do, i'd be really appreciative. i'm going to try flashing from an original ftf file, maybe this has to do with some firmware stuff that's reeeally over my head. fingers crossed..
the funny thing is that it works great after restoring my backup of omni. bloody hell. : ) i mean what am i missing here? : )
okay, so i managed to (maybe) fix it. the trick was to *not* use omnirom's cwm recovery to restore the stock rom, rather flash the stock kernel with philz touch, *then* restore the backup. man.. hope this lasts.
started again this morning on dark lord's blackxt (stock .199-based), torch went too. rebooting and the other tricks didn't do diddly-squat. however, a trip to recovery and back fixed it. i did install doomkernel, but it's probably not the one that helped, because i've been using that last time the problem started.
btw, i know i'm spamming this topic all alone, but maybe someday this will prove useful to, or someone who knows what's going on will laugh and tell me to idk reformat the whole device or flash some obscure firmware file or something.
To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.
Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.
I recently flashed Paranoid Android 4.6 BETA5. Everything is fine except I now have a horrible problem with dropped calls. I've had my phone for close to a year and never had this issue. I am rooted, was previously on CM11. Prior to flashing PA, I had to return to stock, get the KitKat update, re-root and then flash. I'm afraid I may have messed something up. Again, everything else is fine except for this.
Any help is appreciated.
liquidamber said:
I recently flashed Paranoid Android 4.6 BETA5. Everything is fine except I now have a horrible problem with dropped calls. I've had my phone for close to a year and never had this issue. I am rooted, was previously on CM11. Prior to flashing PA, I had to return to stock, get the KitKat update, re-root and then flash. I'm afraid I may have messed something up. Again, everything else is fine except for this.
Any help is appreciated.
Click to expand...
Click to collapse
Try a different rom to rule out if it's your phone or PA...
mjones73 said:
Try a different rom to rule out if it's your phone or PA...
Click to expand...
Click to collapse
May have to go that route, sadly. Although, I think I may have narrowed it down to an issue with the proximity sensor. I've been able to complete calls without dropping when on speakerphone or using my FM transmitter in the car.
Flashed Bliss since my last post and no issues with dropped calls. Was on Optimus prior to PA and had no problems. Last night, I did a Nandroid backup and flashed PA again. Same problem. In a 6 or 7 minute conversation with my dad, the call dropped 3 times. Can't figure this out to save my life. Really wanna run PA, but can't live with this issue. I've done a search in different forums and nobody else is reporting this issue. It's gotta be something I've done.
If anybody else has any ideas, I'd appreciate it.
When I plugged my phone into my computer today, I noticed the autoplay window displayed my phone as being "SM-N900s" or galaxy note 3. I checked my build.prop, and ro.product.model was indeed set to sm-n900s, for some reason. So I checked my original build.prop that I saved over a year ago, and it was set to "HTC One". So I pulled the .prop file from my phone, changed it to HTC One, pushed it, and rebooted. my phone hung on a black screen during boot, no charge light or anything.
I went into recovery, changed the file back to SM-N900s and it booted fine. Can anyone think of a reason my phone wont boot unless it thinks its a note 3?
bbmaster123 said:
When I plugged my phone into my computer today, I noticed the autoplay window displayed my phone as being "SM-N900s" or galaxy note 3. I checked my build.prop, and ro.product.model was indeed set to sm-n900s, for some reason. So I checked my original build.prop that I saved over a year ago, and it was set to "HTC One". So I pulled the .prop file from my phone, changed it to HTC One, pushed it, and rebooted. my phone hung on a black screen during boot, no charge light or anything.
I went into recovery, changed the file back to SM-N900s and it booted fine. Can anyone think of a reason my phone wont boot unless it thinks its a note 3?
Click to expand...
Click to collapse
What rom do you have installed?
I'm using insertcoin 8.1.3 (sense 5.5)
bbmaster123 said:
I'm using insertcoin 8.1.3 (sense 5.5)
Click to expand...
Click to collapse
I would do a full wipe and refresh the rom from scratch cause something is defiantly wrong
Thats a lot of work though. I have a lot of apps, and mods, and other stuff that would take hours to redo. Almost everything else on the phone works fine as far as I can tell. no lag, no FC, no random reboots etc. The only bug I have is the control buttons dont work for the lockscreen music player.
It doesn't really bother me that much, I was just wondering if someone has encountered this before.
bbmaster123 said:
Thats a lot of work though. I have a lot of apps, and mods, and other stuff that would take hours to redo. everything else on the phone works fine as far as I can tell. no lag, no FC, no random reboots etc
It doesn't really bother me that much, I was just wondering if someone has encountered this before.
Click to expand...
Click to collapse
I doubt it because having the build prop stating the wrong device can lead to apps showing incompatible and not updating like a bunch of sense apps and things like that.
The apps are not a big deal if you have TIBU.
I would look at all the mods you have installed. Nothing should touch the build prop other then the rom.
well don't doubt it because im telling you I don't have major issues with my phone. Maybe it CAN but it hasn't so far. BTW, sense apps will never update for me since 5.5 was deprecated a bit over a year ago.
bbmaster123 said:
well don't doubt it because im telling you I don't have major issues with my phone. Maybe it CAN but it hasn't so far. BTW, sense apps will never update for me since 5.5 was deprecated a bit over a year ago.
Click to expand...
Click to collapse
Very true. Well as long as you ok with it then I would sweat it. If you wanted you could pull a logcat when you put the proper build prop in
I've never taken a logcat before, I guess I'll have to research how to properly do that first.