Hi folks,
I know there have been other threads on this, but I've read everything I can find and still can't figure it out.
I have a factory stock AT&T Note 3 N900A that has never had root or anything else attempted on it. I've had it for about 2 years. When I got it, it had 4.4.2 or 4.4.4 on it. While I've had it, I have updated only through OTA when they were available. It has been running OC1 for the past year or so without a problem.
My son has now moved to another phone and I took this Note 3 today and did nothing more than a clear cache/factory reset from the recovery menu. Phone came up clean into the AT&T setup under lollipop OC1 with everything fine except now the back/soft button doesn't work. Menu soft and Home button work fine. Nothing but a factory reset????
I've since pulled down NC2 and NL1 and loaded them via Odin. Under NC2 and NL1, the back button again works just fine... so not a hardware issue. I've reloaded OC1 (from the file made available by Walter White - thank you!) and the back button stops working again.
I'm now in the process of going through them in order one more time... downgraded to 4.4.2/NC2 - back button works again, upgrading to 4.4.4/NL1 - back button still working. Now moving up to 5.0/OC1 again (in process and taking the time to post this message being the pessimist that I am). ...and same thing. Boots up into 5.0/OC1 and all looks good EXCEPT THE BACK BUTTON DOESN'T WORK AGAIN :-/ ugh...
Assuming this again leaves me with a non-functional back button under lollipop... It's not working again... Can anybody tell me what I am missing? The phone was used with OC1 from the AT&T OTA update for over a year without this problem. I would love to understand what makes it basically "change it's mind" after a factory reset was done.
Thanks in advance for any help and sincere apologies if I missed the answer to this in all of my research.
Best regards,
rjb
I was in the same boat as you, had a Note 3 that was updated to 5.0, back button worked fine. Bought a replacement Note 3, back button worked on 4.4, then stopped once I upgraded to 5.0, but magically started working again once I downgraded to 4.4. I ended up returning the replacement for a new Note 3 that had 5.0 pre-installed, back button working this time around. Really weird that an official software update could cause such a problem on certain phones. I guess your best option is buying a new Note 3 with 5.0 pre-installed. Best of luck
Related
I used the towelroot method last June (I think) to root my AT&T Note 3. Stupid me, accidentally deleted Magazine rather than freezing it. Ever since, I keep getting Touchwhiz has stopped working with the OK prompt at various intervals. no matter what; when I receive a new email, It gives me the email has stopped working routine. I can hit the OK button and tap my email icon and access my email without a problem.
I tried reinstalling Magazine and Lounge, but that didn't help. Now; as of Friday; the latest update of Kies fails to read my phone.
I've read so many different causes and solutions, and tried nearly all of them that made any sense, but to no avail. I've searched the forum, and Googled it for months now, but haven't found a solution.
Last ditch effort is to be scolded and told how stupid I am (which I already know) and to search the forum, which I have and found multiple hits. Most with a different solution, but, so far; no fix.
Sorry. Edited to include: AT&T Note 3 SM-900A Ver. 4.4.2 N900AUCCUCN2 Build KOT 49H.N900AUCUCNC2
Any ideas?
Thanks in advance!
Fix
So I would suggest a complete wipe and using Odin to go back to a full stock install. The link below will walk you through it and you have to use the individual files and not the all in one, but it should fix the issues. You wont have Root anymore but I have found you can get a lot of the things you wanted root for without it now.
http://http://forum.xda-developers.com/note-3-att/general/kitkat-4-4-4-n900aucudnl1-odin-tars-t2999317
Link appears to be broken.
I need root access. If I flashed back to stock ROM, couldn't I re-root with towelroot and be a little more careful this time?
I've done that exact thing before
I searched and found nothing exactly like what I was experiencing and nothing I hadn't already tried. Hopefully someone has seen this before. I HAD a nice rooted stock SM-G900A 4.4.4 and now I have a flashy gold brick (soft). I rooted by downgrading the kernel to use towelroot then flashed stock kernel back. Everything worked fine for about a week or so. I'm not sure at what point I started having issues exactly so I'm not sure if an app or mild mod could have caused my issues. The only thing I had done was use SuperSU to block Knox and change the terrible TW stock sounds to standard ogg clicks and what not. The trouble started with the camera. I opened my camera and the screen would flash green then I would have red ghost images in a pattern on the screen. The pictures I took had the same effect when viewed in the gallery. If I switched modes the problem would go away with the camera until I closed then opened the camera app again so I assumed it was a software rather than hardware problem. I couldn't find any info on a fix so I did a factory reset. The problem persisted. I decided finally to flash back to stock. That's when it really got bad. After flashing to stock the phone will boot to the Samsung animation with the swoosh, freeze there for a few seconds without completing the boot animation then the screen shuts off and the phone becomes unresponsive. The only signs of life is the blue LED is constant lit. I have to do a battery pull to start over. I have flashed just the PDA and I have flashed the whole shootin match (except for BL) and I get the same results. I have tried stock tar files from a couple different sources. It will go into download mode as well as stock recovery where I tried a factory reset after flashing. PLEASE HELP!
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Acer904 said:
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Click to expand...
Click to collapse
Go here and flash back to NCE. Then take the OTAs.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Acer904 said:
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Click to expand...
Click to collapse
If you take the 5.0 ota you won't be able to root. Just FYI. There is no root for it yet. There is a pay however in the general section on how to upgrade to 5.0 and keep root.
I'm currently stuck at the s5 active logo screen and then it boots into recovery. I've tried flashing the full odin.rar (yes I extracted it) and it fails everytime. I get the message "Sw REV CHeck Fail: [aboot]Fused 2> Binary 1. I've already tried wiping the data from the recovery menu. Nothing is working.
We need more info. What were you attempting to do and from what ROM. Are you sure you are using the proper ROM 900 or 870?
I was attempting to downgrade back to stock from 5.0 and hit the stock kernel instead of the firmware accidently when in odin. And yes I am absolutely sure i'm using the 870 rom.
Edit: What if I use a stock img and a PIT file for the phone? OR is it because I need a 5.0 lollipop firmware to flash through odin?
Edit number 2: okay I'm stupid, im on G870AUCU2BOF3. I'm going to have to reflash the of3 zip aren't I?
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
if you loaded the 2400258.cfg you probably loaded the OF3 bootloader as well and now you can't go back. No root at this time and it doesn't look good for the future.
Cloudsdabomb said:
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
Click to expand...
Click to collapse
At command prompt type without the qoutes.
"getprop ro.bootloader"
Then paste output.
Sent from my SAMSUNG-SM-G870A using Tapatalk
If you took the of3 ota or are otherwise on the of3 bootloader your stuck there....no downgrade or root as of this time.
Me too
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
pgross41 said:
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
Click to expand...
Click to collapse
How long did you have to wait for your phone to boot all the way up from the ATT logo? Mine is doing exactly the same thing and I've flashed all kinds of kernels via odin and heimdall with no affect. None of the various fixes I've found have helped, including trying to re-apply the OTA file (system just won't do it). All I wanted was to unroot. Awesome.
The first boot can take a while but if it lasts more than 10 minutes it's probably not going to happen. I've gotten it stuck there twice since my last post and I'm always able to salvage it by going into recovery mode (vol up, home, power while powered off). Wipe the cache and data reset and it should be a fresh start like out of the box new.
Hm. So the only real two options are take it in to AT&T and hope they have the full stock G870AUCU2BOF3 image to flash over (since Samsung locked down their bootloader so hard, so downgrading is impossible :good: ) or hope they release G870AUCU2BOF3 on SamMobile/Kies/Smart Switch. This is like the new hard brick... potentially it's salvageable but the company (I'm guessing AT&T here since this is an AT&T exclusive phone) is just screwing us. Guess I'll try the walk of shame to AT&T. Or maybe putting in a claim like that one person did, get a whole new phone because of a mysterious cut on the rear panel seal...
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
retro486 said:
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
Click to expand...
Click to collapse
It's not Samsung that locks down the bootloader, it's AT&T. the T-Mobile Version doesn't have a locked bootloader and is easily rooted . Just have to SIM unlock it and you can use T-Mobile phone on AT&T network.
Delete
My note 4 was bought used, no warranty. When I bought it, it was rooted, but no custom rom, worked great. Once lollipop came out, I wiped and returned to non-root and was able to get the update through tmobile. Didn't bother rerooting as things were ok. Marshmallow udpate came, and I noticed a lot of screen lag. Less than a week ago, tmobile did some sort of update and now, the phone shuts off and restarts on it's own, has very slow screen response (nothing, and then tries to do the same function 10 times in a row, messaging is very slow, types the same words several times over). I did a factory re-set twice. Once, I reloaded all my favorite apps, etc. still bad, so then I did factory reset but did not add anything or bring in my contacts, etc. I am planning on buying the note 7 in a 3-4 months, but in the meantime, would like to continue to use my note 4. I tried doing the rooting method using odin, it appeared to work ok (got the successful notice), triggered the knox thing, but..when I use a root checker, it says phone is not rooted. I am hoping that by rooting and putting a new rom on there I can fix this thing in the interim. So..suggestions on what to do next? Let me know what additional information you need. Could it be the phone itself and not the software? Suggestions on a cheap interim phone? links to relevant threads also appreciated. Is there a better way to wipe everything and start new that I am did not do? I did a factory reset. I have two batteries, which I changed out intermittently to see if it as a bad battery. Android version 6.0.1, security patch level july 1, 2016 Kernel 3.10.40-7804088
Knox version 2.6
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
more info
goosa23 said:
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
Click to expand...
Click to collapse
No to supersu? it's sm N910t, I think what finally worked what odin 3.9 version and flashed the stock that is meant to go with this particular phone to downgrade it down to lollipop. The first few times, I got fail with Odin, but realized that I had marked the option on the phone to keep it from being wiped/flashed if someone found it, once I got that off, I got a successful message. I used the following link and did all of the things mentioned on a link that I am too newbie to be allowed to post, apparently.
but it goes with 3.7 odin, flash the stock firmware from the phone model, and get to the reset button, if successul and then supersu appears.
I got as far as step 8, with odin showing the green 'reset'. But when I went back to the phone, I did not have supersu.
I've tried to do it again, but I get 'fail'
Try out the toolkit that is in the forum. https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
The link takes me to a 404 page not found, is part of it missing?
send me the link by private message so i can see what you are doing?
Hello
So I have a sm-g925a build nrd90m.g925aucu7erb1 , android version 7.0
I'm wanting to root the phone because all of a sudden the back and recent app keys stopped working completely. They light up but don't do anything.
I cleared the cache and that did nothing. Then I did a factory reset, and that made the back key work again temporarily, but now it's not working again.
So I'm looking to root the phone because I have the feeling those keys actually do work. I'm seeing a lot of things about rooting from android 6, and I saw something about going odin mode full stock, I'm guessing that's to root from there?
Hoping somebody could tell me the best way to root from 7, I would really appreciate it.
Thanks