Back button not working after software update? - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi everyone. I just flashed back to stock (Koodo official firmware) to sell my Note 3 and now my back hardware button isn't working. I have searched the web and to no avail. Could someone please give me an idea of what I can do to fix this? Thank you!!

Which note 3 is it?

SM n900W8

I have the same model. I haven't used it for a while. I powered it on a few days ago to take the update from doc4 to doh1. I just tried the back and menu buttons using the doh1 ROM and they seem to work fine.
A friend of mine has the same phone and he flashed the doh1 ROM from sammobile.com over a rooted doc4 RIM and he also has no problems.
Both of us were using custom ROMs with a 4.4.2 bootloader and we both flashed back to stock using sammobile.com's doc4 ROM before moving to doh1.

I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!

Glad you got it fixed but I'm not sure I was much help.

Partially solved..
Hi.
I have done everything trying to solve this and can confirm the next:
1st: If you go back to Kit Kat, the capacitive buttons start to work again. Then you are offered a couple of OTAs (one after the other to get you to DOH1). After the first OTA, the buttons stop working again.
So first solution: stay on Kit Kat (probably not what we want).
2nd: Flashing a custom Cyanogenmod based firmware works, I used latest temasek's build, I am testing it to see if I can keep it.
3rd: I tried erasing almost every single partition (system/cache/dalvik(art?) cache) and flashing from scratch DOH1... wont work.
According to what I have read all around there is a system file that controls the capacitive buttons, probably that file is getting weird with the upgrade, I still need to install a official rom, root it and try to edit such file.

It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.

audit13 said:
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
Click to expand...
Click to collapse
I wasn't running anything custom. I was on Official ROM (no root no anything, just Stock Samsung Software) as always with my Note 3. It was just that the DOH1 update make the damages.
Now I think I gotta stick to Cyanogenmod given this problem, unless Samsung says something and fix the thing.

Does this happen with TW-based custom ROMs too?

Dont know. As of now, I am trying to flash DOH1 again on top of KitKat 4.4.2

[/COLOR]http://www.askmefast.com/I_have_a_n...art_any_idea_what_can_be_done-qna1982335.html
They say clearing the Cache of the Samsung Keyboard fixes the thing. Wont be able to test by myself til tomorrow

Edited
I have N900W8 bell version, using it on Virgin network.
worked flawlessly with KitKat (either with Bell or Virgin version).
I've only experimented with Note-based custom roms (KitKat only), since I need the pen functionality.
First attempt:
I have experienced the same, not properly working menu button and not working back button.
I was on rooted stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version), rooted with Chainfire CF-auto root (Build ID:KOT49H.N900W8VLUCNB7) using Odin. (all the buttons working properly)
Upgraded to Lollipop 5.0 (N900W8VLU2DOH1) with Odin, rooted same way with CF-auto root (Build ID:LRX21V.N900W8UBU2DOL1). (Buttons do not work)
Second Attempt (No rooting involved what-so-ever):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version, clean flash), all the buttons working properly.
Did OTA update through Wifi to, assuming, N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
For both of above attempts, buttons are working properly with KitKat, whether it was rooted or not, and not with Lollipop, whether it was rooted or not. I'm thinking it's just the lollipop issue.
Third attempt (using N900W8VLUCNB7 Firmware Bell version):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Bell version, clean flash), all the buttons working properly.
Did OTA update through Wifi to N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)

wy2sl0 said:
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Click to expand...
Click to collapse
Do you have the link for the stock Tom zip?
Sent from my SM-N900W8 using XDA Free mobile app

Ok. Pretty much tried everything while staying on stock firmware.
However, everything else seems to work okay other than the touch button.
So now im gonna root the stock lollipop and use xposed and gravitybox to manually remap the 2 touch keys. Will update

Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.

rocked_out said:
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
Click to expand...
Click to collapse
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.

SS604 said:
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
Click to expand...
Click to collapse
Hey , has anyone firgured out how to get rid of the "unfortunately Knox has stopped working" ? I had the same issue with the softkeys not working. This fix works but I get this message. I was also told to try flashing a PIT file with stock firmware to fix the softkey issue, but this did not work.

Maybe flashing supersu from TWRP will allow supersu to disable knox?

not to bring back a dead thread, but this is exactly what I needed. I needed to root to fix screen mirroring so I just used root uninstaller to delete knox.

Related

[Q] Help reverting to stock... usual steps not working

Goal:
Latest firmware info from SamMobile
GT-I9505 Galaxy S 4 LTE
PDA: I9505XXUBMGA
CSC: I9505OXXBMG3
MODEM: I9505XXUBMGA
Previous set up:
Custom Recovery. Philz Touch
ROM http://forum.xda-developers.com/showthread.php?t=2352258
I has also attempted to update the base band when on this rom to MGA to the About device Baseband version stayed at XXUBMEA
Situation: I was getting lots of force closureswouldn'tentually it just wouldnt reboot, thenre-flashedvery failed. I reflashed the recovery and restored from wouldn'thowever it still wouldnt boot. (About 90% of the way through the bSamsungmation the audio samsung logo sound died. The Samsunghen went to the "samsung" static image with the blue LED light on and just stayed there... for about 30 mins before I force shutdown the phone.
I the attempted to flash stock ROM (listed in Goal above) downloaded from SamMobile. The same thing happened again. Boot gets stuck. I got into stock recovery and wre-flashedactory reset and reflashed. The ROM installed but I had no wifi. I then flashed the I9505XXUBMGA modem. Reboot and I had wifi. However About device still shows XXUBMEA baseband.
I wanted to see if I was able to get OTA updates from Samsung however Samsung update app is saying that the device is modified... so something isnt quite right yet. Im guessing it might be to do with the modem / baseband but to be honest I am a bit lost.
Screen shot of my current About Device Information. Also Device Status is showing as custom..
Thinking outloud here... would a Root->TriangleAway->reset counter etc->flash philz touch->full wipe for new ROM->boot to download->Odin flash stock fix it? Or could that do any further damage?
First install chainfires triangle away to reset your flash counter. For this you need root.
Then do a factory reset in recovery and flash stock with odin.
You wont get ota when flash counter >0 so give it a try.
Hopefully this helps
EDIT: If the new modem wont appear after a odin flash then uncheck the auto reboot option in odin and flash the modem twice, that helped for me.
Device Status is showing as custom, because you had flashed non-stock rom...
so the wifi not working, but can you make call??
The first time I flashed OMEGA ROM, wifi did not work, but flashed Adam kernel fixing the issue.
Look at his attachment, mobile connection seems working
@polcup please report back if it worked.
cellegg said:
Device Status is showing as custom, because you had flashed non-stock rom...
so the wifi not working, but can you make call??
The first time I flashed OMEGA ROM, wifi did not work, but flashed Adam kernel fixing the issue.
Click to expand...
Click to collapse
Wifi is now working after I flashedlashed the I9505XXUBMGA modem. Rebooted and I had wifi. However About device still shows XXUBMEA baseband.
Calls and mobile date is fine.
_sebha said:
Look at his attachment, mobile connection seems working
@polcup please report back if it worked.
Click to expand...
Click to collapse
Yep, I will try that over lunch and see if it works. Not sure that will get me to the XXUBMGA modem though but its certainly a step in the right direction.
I really appreciate both your replys. Thanks.
Look at my edit in first post.
Uncheck auto reboot in odin and flash only the modem twice (manual reboot to download mode after first flash) after second flash reboot device.
That worked for me
_sebha said:
Look at my edit in first post.
Uncheck auto reboot in odin and flash only the modem twice (manual reboot to download mode after first flash) after second flash reboot device.
That worked for me
Click to expand...
Click to collapse
Superb! I will try that as well. Thanks!!
Update
I was unable to root I9505XXUBMGA. CF-Autoroot didnt stick. I tried a couple of installs. One through Odin and one through CWM. Neither took.
I flashed an older pre-rooted stock rom I had XXUBMEA and then ran Triangle away. It returned the counter to '0' and brought the status back to official.
So now im back to stock MEA and to be honest I am happy to stay here for a bit. I will maybe move up to MGA if I find a pre-rooted version.
Thanks for your help.
Sorted!

No Signal after 4.4.2 update

Hey Guys,
Today I updated my i9505 from Cynogen Mod 10.3.1 to the new "[AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1" by Jamal, but I read that you needed to update to the leaked 4.4.2 before flashing so that the modem and bits are upto date before flashing any 4.4.2 ROMs or else you could end up with no wifi after flashing.
So I followed these instructions to flash the leaked 4.4.2:
INSTRUCTIONS
- Extract (unzip) the firmware file
- Download Odin3 v3.09 (From here or here)
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add AP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to AP
- Add BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to BL
- Add CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CSC
- Make sure re-partition is NOT ticked
- Click start button, sit back and wait a few minutes.
Which all went well but I couldn't get Wifi after flashing, and (probably not important) but the default language it choose during the setup was Dutch??? Seeing as I couldnt get the wifi to enable I decided to flash Philz Touch Recovery v6 and then put Jamal's "S4 Google Edition - Final-R1.1" by putting it onto the SD card and flashing through Philz recovery.
Flashing went without a problem.... only thing is now I cant get Vodafone (UK) signal 80% of the time, the other 20% I do get signal and can make calls, just seems strange as previously 80% I WOULD get signal!
Did I do something wrong? I had a really bad feeling that flashing the CP, BL and CSC has somehow messed things up......please help!
Same problem, bump.
ColdIce23 said:
Same problem, bump.
Click to expand...
Click to collapse
I just fixed the problem, ColdIce23, check your Baseband Version under Settings > About Device, I bet yours is still set to the original baseband version like mine was...
1) Re-Download the Baseband for the leaked 4.4.2 rom (Here)
2) Open Odin 3.09 and do the following:
Ok it worked.
If anyone else is having issues with the baseband not changing, do this.
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Click to expand...
Click to collapse
Now I have FULL SIGNAL! .....so far..... will report back once I have left work but this is a good sign as I had no signal what-so-ever 5 minutes ago!
Flasing a 4.4.2 Modem works well with the Kit Kat based roms. Two to choose from NA1 or NA5, depending on what bootloader your on flash the appropriate modem files.
I've got NA5 on the 4.4.2 GE Rom with Three and no signal issues as of yet.
treesmoker said:
I just fixed the problem, ColdIce23, check your Baseband Version under Settings > About Device, I bet yours is still set to the original baseband version like mine was...
1) Re-Download the Baseband for the leaked 4.4.2 rom (Here)
2) Open Odin 3.09 and do the following:
Now I have FULL SIGNAL! .....so far..... will report back once I have left work but this is a good sign as I had no signal what-so-ever 5 minutes ago!
Click to expand...
Click to collapse
My I9505 baseband version is I9505XXUFNA5. Is not it the updated one?
kamrul.auntu said:
My I9505 baseband version is I9505XXUFNA5. Is not it the updated one?
Click to expand...
Click to collapse
Yes you the latest baseband available.
treesmoker said:
Hey Guys,
Today I updated my i9505 from Cynogen Mod 10.3.1 to the new "[AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1" by Jamal, but I read that you needed to update to the leaked 4.4.2 before flashing so that the modem and bits are upto date before flashing any 4.4.2 ROMs or else you could end up with no wifi after flashing.
/QUOTE]
I think u missunderstood something. For the Kitkat Google Edition u do not have to flash the leak before. Its only for the Samsung Touchwiz Version of Kitkat
tapatalked by an Echoenian
Click to expand...
Click to collapse
nikzDHD said:
Flasing a 4.4.2 Modem works well with the Kit Kat based roms. Two to choose from NA1 or NA5, depending on what bootloader your on flash the appropriate modem files.
I've got NA5 on the 4.4.2 GE Rom with Three and no signal issues as of yet.
Click to expand...
Click to collapse
I flashed the NA5 modem which seems to have failed the first time round, as it didnt actually change the baseband version in settings. Since flashing a second time (when it actual flashed properly) I now have full signal...... but I have another problem now:
When I click the dailer and select a person to call, the screen goes black and I dont see/hear any indication that a call has initiated. I tried with my wife and her phone rings and she can answer the call, but my screen is still black with no sound....
I have tried wiping data / davlik / cache and installing the rom from scratch, but I still get the same issue?
UPDATE:
Right so I just flashed CM11 as a test, and still can't make calls, so obviously not a ROM fault..... does the BL, CP or CSC have anything to do with the making calls procress?
I've got a similar issue.
I've got a M919V running Jamal's 4.3 GPE rom, but after flashing Jamal's 4.4.2 GPE i get no signal. After going into settings and selecting network the signal lasts, but after the screen goes off signal is once again lost.
Is there a procedure to follow that will fix this? This is found when when flashing many 4.4 roms.
-Thanks
Well, I get signal when I'm near a cell tower...
No changes tho. Still same problem.
Hi guys,
I'm wondering if you have resolved your modem problems?
I flashed to Jamal's 4.4.2 version 1.2 and I don't have a signal now.
I flashed the modem to NA5 but styill no signal. Also I can't even check my CSC using *#1234# as "Mobile network not available"
Any suggestions?
Thanks.
Hi Duskin,
For me, I think it's releated to the phone itself as I got a screen replacement. I haven't solved the problem yet because I got to get back to the store where I got my screen replaced.
Sent from my LG-P880 using Tapatalk

[Q] How to root Samsung Galaxy Note 3 N900?

I've been searching on how to root my note 3 N900, but the videos said that it only works on a specific type of model/firmware version. I have the N900UBUENH1, will I be able to root using this method: http://www.galaxynote3update.com/root-galaxy-note-3-sm-n900-4-3-4-4-2-kitkat-updates/ ? I have Android 4.4.2. I searched up my firmware version and it's not very common. Could my phone be fake?
maybe you can try cf-auto-root by chainfire
NH1 can use it to root.But it's said NI1 can't
duhvietboy said:
I've been searching on how to root my note 3 N900, but the videos said that it only works on a specific type of model/firmware version. I have the N900UBUENH1, will I be able to root using this method: http://www.galaxynote3update.com/root-galaxy-note-3-sm-n900-4-3-4-4-2-kitkat-updates/ ? I have Android 4.4.2. I searched up my firmware version and it's not very common. Could my phone be fake?
Click to expand...
Click to collapse
I have the same one. Well my gf does and we need to root it. I tried CF Auto Root and it won't finish, it just hangs at a certain point. Afterward the bootloader was like gone and it would not boot. Trying to flash TWRP fixed it and I can boot not ( It also does not boot into TWRP---weird right?) What works for this? I am also not sure which ROM is actually on the phone. I see a few on there that match but not sure which exact firmware is on the thing. I think Samsung has some typos on their site. I am seeing there are some with 2 "U"s in the name. In the bootloader though it says the CSC chosen is TTT...
Update: Well I figured out finding the CSC and given that it can be either: Uruguay, trinidad and tobago, chile, panama, Argentina. The box also says to only use American SIMs on it. Well it has that sticker on it. I assume you still can use it. Anyways how do you root the thing?
I rooted N900UBUENH1 succesfully installing TWRP first (I use twrp-2.8.6.0-ha3g.img.tar file) using Odin 3.09. The key is to uncheck Auto Reboot (uncheck all items under Options) and when Odin finish flashing TWRP (tells you to reset phone), take out battery. Put battery again and restart in recovery mode:
- Press vol.up+home+power and hold Galaxy logo appears and disappears several times
- When displayed for the third time, release the power button and wait
- Release vol.up and home when TWRP logo shows up
Now, from TWRP, you can install SuperSU (latest version from download [dot] chainfire [dot] eu [slash] supersu).
Quick guide: HERE.
Joku1981:
The method described there use CF-Auto-Root and didn't work for me (freeze at 30% aprox in phone's progress bar). Searching in forums I found a lot of people with this particular phone that also CF-Auto-Root didn't work.

[Q] Update official DOC4 Firmware

I would like to get a little help here.
I am trying to update to the new LP Doc4 firmware, it works fine flashing thru AP in odin.
But once I got in into the setup screen I am getting cont. pop up msgs "com.google.process.gapps has stopped" during the setup screen and wifi cant be turn on. So bascially I am stuck here.
A few questions.
How do I wipe the system so that I can flash it again in a clean state?
What are the required files and steps in order to flash the new firmware? I download the offical LP firmware which is like 1.3gb only.
I am on Canadian n900w8.
Thanks.
D810Noob said:
I would like to get a little help here.
I am trying to update to the new LP Doc4 firmware, it works fine flashing thru AP in odin.
But once I got in into the setup screen I am getting cont. pop up msgs "com.google.process.gapps has stopped" during the setup screen and wifi cant be turn on. So bascially I am stuck here.
A few questions.
How do I wipe the system so that I can flash it again in a clean state?
What are the required files and steps in order to flash the new firmware? I download the offical LP firmware which is like 1.3gb only.
I am on Canadian n900w8.
Thanks.
Click to expand...
Click to collapse
Switch off your set. wait for few second. Press VOL Up + Power Button + Center Button for few second. you will be in recovery mode. you can wipe from here.
Don't Forget to Press Thanks.

Best route to downgrade to kitkat

I have a uk unbranded 900f. I got it a month ago agony almost straight away it upgraded from kitkat to lollipop. I find it can lag when pressing the home screen, the recent app button and starting he camera. Also firefox is buggy and can lag and he text will blur at times. Previously I had a htc one x running viper rom. I don't find the S5 on lollipop to be any faster than my one x running jellybean viperx.
I heard that the s5 on kitkat has less problems so want to down grade to find out. I want to try kitkat stock first so want to know he easiest way to do this? Ie factory reset, odin flash etc. Also I need to know if there are any problems to look out for or special prep I should do. I am rooted, have twrp installed and have the reactivation unchecked. Alao whicj version of kitkat would bw the best to go to? Any advice is appreciated Thanks.
Factory resetting after upgrading to Lollipop solves a lot of issues, Id try that first
Latest KK G900F Stock ROM here and ODIN to flash it
Extract ROM
Load it into AP or PDA in ODIN
Stick phone into download Mode (Volume down & Home & Power)
Connect to USB PC
Hit start once ODIN says it's happy
Thanks Detection. I'll try the reset first then and go from there.

Categories

Resources