Database Develop

Ok. Whaaaat? Rooted NC stopped working? (will re-rooting help?)

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.

[Q] Kingo Root Question

I used the Kingo Root method to root my Note 3 that was running 4.3. When I decided that I was ready to go ahead with the AT&T 4.4.2 FOTA; I used it to un-root so my phone would accept the update. Both processes indicated that they were successful. However; my Note 3 will not accept the update under any circumstances. It downloads the FOTA - which takes close to an hour - and gets to the 25% install point after rebooting and fails with "Invalid Signature" appearing for a few seconds after the "Installation Failed!". It then unceremoniously does a factory restore and I'm left with, yet, another setup procedure and reinstallation of all of my apps, passwords, etc.
This has happened twice with two different phones - the other being my Samsung S4. Exactly the same sequence. I took the S4 to Best Buy, after AT&T forced an update to it, and it, too, failed. Samsung did a direct flash to the S4 and it indicated that it took the 4.4.2 successfully. However, when the phone rebooted, it was still 4.3. Samsung scratched their head and couldn't figure it out. I see no sense in try to do the same with the Note 3 since it will likely be the same experience.
Neither phone show the KNOX trigger having been tripped, and both show "Official" as though nothing had ever been done. I never did any modifications to either phone, other than the root / un-root to stall the FOTA, until I was sure that I was comfortable with the update.
I sent an email to the same effect as this post to Kingo, with no response.
Has anyone had the same experience?
I know that for a while, there was a great deal of concern over the Kingo Root method, but thought that it had been resolved and that any myths had been debunked.
Did I shoot myself in the foot?

Hey friend, this has been asked A LOT in this forum. All you had to do what look through the first page and you'd see this topic.
However you're scared and our phone are probably our more personal and needed device so I understand your impatience and panic.
How to fix: http://forum.xda-developers.com/showthread.php?t=2701062
Be well, relax, everything is going to be ok. You're not alone . We're with you my new friend.
Sent from my SM-P600 using Tapatalk

Sorry for posting in the wrong thread. I searched over the weekend, but didn't see what looked like an answer.
Thank you so much for posting the direct link! And, thanks for not mountain climbing me about the gaffe.
I'm still fairly new to this, so I genuinely beg everyone's pardon for the mis-post. I'm still trying to learn how to navigate through the different sub-forums. I'll try to be more courteous in the future.

Now, I'm in a REAL pickle! AT&T is trying to cram KK down my throat on my Note 3 and I have about 4 hours (according to their website) to respond before they force it. On the AT&T variant; there is no way that I know of to block the update; except temporarily. Then; it's back to the wash, rinse, repeat cycle of having to restore my phone and apps - EVERY time the update fails!
I still haven't done the downgrade; because after rooting and installing a custom 4.4.2 ROM on my kid's phone least night; I decided that I want to re-root my Note 3 and install KNOXRAID as a custom on my Note 3.
My dilemma is; if AT&T crams the update down my throat - as they did with my S4; it's going to fail again, and I'm going to have to start from scratch again, and again until I find a solution.
I tried re-rooting my Note 3 with Kingo, but it fails every time, now.
So; what should I do? My hunch is that I'm going to have to do the 4.3 fix and restore it back to factory, but then it would allow AT&T to actually force THEIR KK into the N3, and I'd be screwed, until a root method is obtained for KK.
PLEASE! Any suggestions? I suppose, for the short term; I could cut off my N3; install my SIM into my S4 and use it until I'm able to resolve the issue with the N3. I need Total Recall to work on my N3, and KK will definitely kill it.
*UPDATE* I turned the N3 off, removed the battery and SIM and installed the SIM in the S4, and am using it for the short term. Unfortunately; my S4 already has the AT&T KK update installed, and I need to resolve the issue with the N3 as quickly as I can. My hunch is; to avoid them doing it again; I'm going to have to turn off Wi-Fi and place the N3 in "Airplane" mode and leave the SIM card out of it until I'm comfortable - and have a clear method of installing KNOXRAID.
Still hoping for a solution. At this pint; I'm not that concerned about tripping the KNOX sensor on the N3, but would prefer to be able to flash back if I needed to enforce my warranty.
Thanks!

Lollipop causing phone to turn off

Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?

I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.

MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.

W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.

Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.

MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.

What's wrong with my Note 4? Slowdowns galore and freezing

DOK2 all stock firmware here.
Got my phone back in december. My phone has been chugging alone fine until yesterday. not sure what happened but the lock screen takes minutes to come back. I tried doing a factory reset via software and when I did that the phone was still sluggish. Tried a stock recovery reset, and afterwards when i tried signing into my account and connecting to wifi at the initial setup the phone just rebooted back to the start screen again which i thought was real odd. It's currently restoring apps from the app store right now and it intermittently reboots itself while doing stuff. all while it's completely stuttering if i try to use it...
Is my phone starting to have internal memory failure? no SD card in the phone at the moment.
Should I try reflashing the DOK2 firmware via odin and then doing a reset again? Is that even possible with all the restrictions?

used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed

Check this thread for a workaround. I use an app to keep my phone from going into deep sleep.
http://forum.xda-developers.com/showpost.php?p=64584244&postcount=39
dtrinh4000 said:
used it for about 30 minutes on my way to work and then it rebooted on me with the following error :
ddi: mmc_read failed
Click to expand...
Click to collapse

Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.

Bruce lee roy said:
Wouldn't hurt to reflash stock. Google usually restores apps when you check box at first boot for backup and restore. I'm wondering if you installed an app that doesn't agree with your phone... if so, you may continue seeing this issue so long as app is installed.
Click to expand...
Click to collapse
Did a factory reset and cleared cache, reflashed stock DOK2 from sammobile website using odin, cleared cache. things were going a little bit better at first but now just stuttering all over the place and randomly rebooting still. I only have very few apps downloaded, including facebook updates, instagram, all the samsung and google crap that forces updates...
Also want to add that booting into recovery takes a very long time, longer than i've ever noticed it taking... 7 min+ sometimes it will say "installing system updates" with the android guy chugging along, other times it will just have the android guy chugging....
Is there anything else I can try? Is there something I can test to verify that it's a hardware issue and not a software problem, like a flash memory checker?
This phone is out of warranty, and knox has been tripped so I have very limited options here. Would the Tmobile store let me do an exchange for a fee?

bump... anyone? am i really screwed?

dtrinh4000 said:
bump... anyone? am i really screwed?
Click to expand...
Click to collapse
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822

cuteman said:
Sprint user here. I thought it might be a carrier issue, but it would seem It's at least Tmo & Sprint
Can't seem to find any complaints on the Verizon/ATT forums but that doesn't mean it isn't happening.
Could it be Touchwhiz?
Here is the Sprint post:
http://forum.xda-developers.com/note-4-sprint/help/random-shut-freezes-download-mode-stuff-t3302822
Click to expand...
Click to collapse
I do get some touch wiz crashes and random app crashes . since I'm on dok2 is there any other rom or recovery I can flash ? Or so some super duper erase method? I'm pretty much ready to cut my losses and sell it for parts on eBay.

i'm not alone it seems
http://forum.xda-developers.com/note-4-tmobile/help/note-4-major-slowdown-bugs-boot-loops-t3311297
http://forum.xda-developers.com/note-4-tmobile/help/looping-screen-t3319204
http://forum.xda-developers.com/note-4-tmobile/help/reboot-shutdown-wont-removing-battery-t3316875

I am having same issue. Was running stock until 3 days ago, when I got fed up with the stock reboot and slow-down. I guess it's time to save up and get a new phone.

Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....

dtrinh4000 said:
Samsung must have activated some self destruct feature on their hardware to get people to upgrade to the galaxy s7 i guess....
Click to expand...
Click to collapse
Well, fool me once.... Having spent $800 on a phone that broke in just over a year, hell would have to freeze over before I give Samsung any money again.

Need help in rooting samsung galaxy s5 for at&t

Hi Everyone,
I wanted to reach out to this group to seek urgent help. I have the samsung galaxy s5 from at&t and it has the latest update of 6.0.1 in installed in september. After that started the issues. My phone got extremely..i mean literally hot while charging and a complete charge never lasted more than a few hours with battery draining like crazy. I thought it could be apps and i disabled location, bluetooth, removed apps that i dont use, stopped some apps that i felt not needed, yet the battery drain and heating persisted. I did a factory reset multiple times and it did not help. I did the wipe cache partition too yet even that did not help. Few days ago another issues started. My NFC enabled automatically and the option to disable it was greyed out and i was not sure on how to switch it off. the last straw was Wi-Fi which got switched off and the option was greyed out with me having no chance to enable it and connect it to Wi-Fi. I was totally flumoxed on what was happening. I reached out to samsung and also at&t and essentially they disowned me saying the phone is out of warranty and they can not help. I still owe 3 more EMI to at&t and i hold a $650 brick technically.
I tried rooting it through "towelroot" but the app said its not compatible with this phone. i tried Odin and run the stock rom but the process was always stuck at connection even though the driver was all identified. I wanted to install the CM13 or CM14 to see if i can get my phone back but without the phone being rooted, i was in no position to run the custom ROM or install the recovery. I have been searching google for the last 2 days to see if there is any method which will help me but i was not able to get any. I knew XDA Developers was a group of members who are experts in helping android users realize the true potential of the smart phones.
Can anyone please help me in resolving the issue. My phone model is SM-G900A and it has the knox and android 6.0.1 update.
Thanks &regards
KC
Email - [email protected] / [email protected]