ICS Home button not working - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I searched in the Rocket, midnote and Criskelo threads but I couldnt really find any solutions. A few people have had same issue but I couldnt find any solutions.
I have tried all of the above ICS roms and they all work great other than the fact that the home button does not work to go home. It will wake up the device however. Am I missing something?

Also searching.
Until yet only got to know its the ICS Pre-Keyboard causing a remapping of the Numbers assigned to functions (Hardkeys)
My homebutton isnt working either anywhere but it can unlock the device (Escape Lockscreen)
Yet trying to find out whats the keynumber in the generic.kl (/system/usr/keylayout) to assign the "ESCAPE" by myself to the correct number. Hope it helps - also heard rumours talking about its a driver issue - i dont hope so ...
Maybe someone with a note (edit: [email protected]) could post his "generic.kl", maybe theres a simple difference and we could easy get rid of it ;-)

I had the same issue even after a full factory reset and reroot. It happened with the chinese leak and with midnote. I'd give anything for a solution to this problem.

The funny thing is:
If i flash the stock buggy ICS "I9220LP1-N7000-ICS-REPACK.tar" via Odin the Homebutton is fully working (But everything else not very well ). I am doing it right now for getting a backup of the whole /usr folder.
After that i will flash the rocketrom again where the homebutton isnt working and going to try to find the difference in these keyboard files. Maybe thats all ...
Hope ill get it soon - maybe even my approach is totally wrong, but hey: try is in the eating. If it is really driver related i cant do anything to get that button working - just wait till some devs get intouch with that issue.

I'm rooting for you, friend.

Call it coincidence, but right after reading your thread, my home button has topped working too
Anyhow, in sec_key.kl, the HOME key is listed with 102. Same in gpio-keys. kl, and qwerty.kl. This value is the same across AOSP v4, v5 and MIUI rev 4a, and ROMOW V1.
In generic.kl, 102 is MOVE_HOME.
This leads me to believe that the key is indeed mapped correctly, and that changing it to ESCAPE won't work. Why? I tried something. In 'melfas-touchkey.kl' and 'sec_touchkey.kl', keycodes for both the capacitive buttons are assigned.
key 158 BACK WAKE
key 139 MENU WAKE
I changed 139 to HOME in both the files, and rebooted. The button itself stopped working, but was able to wake the phone(behaving exactly like the home key). This suggests that the problem has nothing to do with the key mapping, but the HOME action itself.
I haven't tried to change 102 with something else, but I'm about to do just that, to see if the button works if mapped to some other command. If nothing works, I'll flash the whole thing again (GB->CF repack>AOSP) and pray it works

If flashing the whole thing over again ends up working, can you please give us the details of what stock rom you used at the start? I did a full wipe to a stock KK1 rom and went from there and the home button issue persisted. I'll promise to donate to the first person that comes up with a solution

Lance Uppercut said:
If flashing the whole thing over again ends up working, can you please give us the details of what stock rom you used at the start? I did a full wipe to a stock KK1 rom and went from there and the home button issue persisted. I'll promise to donate to the first person that comes up with a solution
Click to expand...
Click to collapse
Yes, flashing the whole thing again works. You NEED to flash Chainfire's ICS repack before flashing any ICS ROM. Get it here : http://www.mirorii.com/fichier/3/501208/I9220LP1-N7000-ICS-REPACK-tar.html
I'm on AOSPv4.
CF's repack can be flashed via mobile/PC Odin(PC Odin will increase your binary count and give you a yellow triangle, mobile odin will NOT.)
What I did was to go to KL3 rootable GB ROM(India), root it with zergrush, install CF root kernel, then Mobile ODIN-ed to CF ICS repack. (Make sure you keep 'enable everroot' UNCHECKED. CF repack is already rooted.)
After that, you have CWM to go to any other ROM. I believe you need to flash a base and the final release for RocketRom, or MIUI.

You are my hero bloodyhippo! Set up a donate link. You've earned it

Lance Uppercut said:
You are my hero bloodyhippo! Set up a donate link. You've earned it
Click to expand...
Click to collapse
Haha
Glad to help Lance! Though this is nothing new, flashing the whole thing in the manner it is supposed to be done removes most all problems that aren't official bugs. So, it's definitely not donation-worthy, but I've added a donation email, just in case ;-)

It's donate-worthy to me! You have no idea how many headaches I've had over this thing. Now I finally get to enjoy some ICS goodness.

Aw, thanks!
Lance Uppercut said:
It's donate-worthy to me! You have no idea how many headaches I've had over this thing. Now I finally get to enjoy some ICS goodness.
Click to expand...
Click to collapse
I really didn't think it was that big a headache for you! You know, I didn't read most of the developer's thread, so I had no idea this problem even existed. And my button stopped working after I updated to AOSP v5, while reading this thread
Anyhow, I'm glad(and lucky ) to have helped you out! Thanks for the $$
[EDIT] I think I'll re-donate it to some dev. Now that's a lot of options

home button working again
I upgraded from Stock Samsung N7000DDLB2 2.3.6 2012 February to (18.05.2012) AlBa XXLPY Full Repack v2.2 with a full wipe.
Everything was working fine in the beginning (i had setup a pattern lock too), till I restored all apps and data. I had restored contacts, sms too after which I noticed the home button stopped taking me back other than waking up the device and there was no pattern lock either. Somehow, that had gotten disabled and reset to back to swype unlock. Now, I setup the pattern lock again and the home button started working again. Went back to swype instead of pattern(without reboot) and home button still works. Any thought on how that happening?

Related

[Q] i9000 ROM + Captivate Kernel

Has anyone tried using the i9000 Froyo rom (like this) with the new Froyo kernel? Could I try it, using the following procedure? I would like to try it, but don't want to brick my phone.
1) Remove SIM and MicroSD
2) Open Odin, load the i9000 Froyo PDA file and the i9000 Froyo CSC file.
3) Leave auto reboot checked and repartition unchecked.
4) Boot the phone into download mode.
5) Flash.
6) After reboot, get back into download mode.
7) Reopen Odin and load the stock Captivate kernel (From this thread) in the PDA box and a pit file (which one???).
8) Ensure auto reboot is checked and repartition is not checked.
9) Flash.
Would this work? Also, what if any PIT file would I use?
Thanks in advance
I'm trying this now. First attempt from the Cappy leaked Froyo failed. I just flashed back to JF6. Gonna try above with the I9000 pit and see what happens.
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
TMC_Sherpa said:
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
Click to expand...
Click to collapse
but i dont think the reorient kernel was NEEDED. i ran the i9000 with stock captivate kernel (as instructed in that post) for a week or 2 and didnt have any problems whatsoever.....BT and HSUPA didnt work, but small price to pay
now that we have a kernel from 2.2 build, we should be able to apply 2.2 captivate kernel with JPK and run it...
i think i will give it a shot today
I just tried it using the steps I outlined above. I would *not* reccomend doing it; it didn't work for me. Once I flashed the kernel, the phone would get stuck at the AT&T "World Phone" screen (formerly the i9000 splash, but I guess the kernel changes that). Being stuck at this screen, it would intermittently vibrate 1-buzz, 2-buzzes, and repeat about every second. I assume that's some sort of error message? After trying to reboot it a few times, I eventually got the "phone-!-computer" screen, and was only able to successfully reflash it by removing the battery, holding volume down, and plugging in USB, and was able to get into download mode to flash with Odin. Heads up.
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
boomerod said:
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
Click to expand...
Click to collapse
Basically, same here. I guess we'll have to wait for someone to figure this out.
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Pirateghost said:
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Click to expand...
Click to collapse
2.2 and 2.1 are different software so its easily possible that Samsung changed whatever allowed it to work.
Sent from my SAMSUNG-SGH-I897
the 2.2 leak is basically an i9000 rom, its not fully tweaked to ATT wants yet... thankfully
yeah I can't understand why on earth you would want to run an i9000 firmware which is at least just as buggy but not designed for your device at all... JPK (latest i9000) was built the same day as JI6...
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
boomerod said:
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
Click to expand...
Click to collapse
I was running i9000 ROM as well with captivate Froyo kernel (in which I noticed a slight increase in performance) but there was no voice while calling only a hiss. I installed the modem.bin from Captivate froyo and it worked.. for 10 sec and then I got reboot loop and decided to go to stock froyo. Wondering if there is a possibility to make it work with a modem from 2.1, but I believe is highly improbable.
Now I am back at the AT&T build but I must say that there are few things which I really don't like. Like the lag when changing home screens. If I go to 7 and press home button it takes 1-2 seconds to get back to the main one.
I indeed found it much faster in opening gallery and loading the thumbnails plus very good results in Linpack. Quadrant still doesn't give me more than 985 which is half of 2.1 with lag fix but that's not relevant.
I want to run i9000 rom because I am from Europe and I would like to have Swype in Romanian for example + that the i9000 rom doesnt mind if I have the "Use wireless networks" On or Off, GPS will still connect in less than 10 sec, thing impossible to achieve with ATT ROM (from my experience).
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
han.azuki said:
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
Click to expand...
Click to collapse
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Pirateghost said:
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Click to expand...
Click to collapse
+2 I love the i9000 rom and I'm not sure I'll update to 2.2 until we get one. I had Froyo on my N1 so I've used it before but after getting rid of the stock rom I don't want to go back. I don't want to update just to update.
Quite an adventure
OK, so even though this is embarrassing at some level, I'm still going to share this experience with the forum (just in case someone else does this to themselves).
So, as the OP posted (had been thinking about it since 3AM this morning after I found that this leaked Cappy Froyo does not have BT voice commands implemented) I decided to try out the I9000 Froyo (most recent posted on samfirmware.com) and then try flashing the Cappy Froyo kernal to see if I could get a working combo. Well, I never got as far as the OP in that I was never able to successfully flash the Cappy kernal.
I ended up stuck (for most of the day) with a very unstable combo: I9000 Froyo with Cappy JF6 baseband. Originally, the problem was I could not get in to download mode using all the normal, well-know methods. I was then able to - see my earlier post - but was unable to get past File Analysis in Odin. I then tried rebooting and then was not able to get back in to download mode to save my life, not even using the method that originally worked for me. So, here is the lesson I learned (other than not screwing around too much with my phone):
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
I still had issues getting past File Analysis; what ultimately worked was JF6 on-click solution. So, after all day screwing around with this, including trying to get into download mode through adb (to no avail), I've learned my lesson. I'm back to where I've been for the past month: really thinking about abandoning AT&T and this crappy, broken GPS, slow to get Froyo Cappy (which otherwise I like very much) and switching to Sprint and the Evo. Sigh...I'm under contract and don't want to pay a cancellation fee, damn!!
Here's a snipped from logcat while the phone is stuck at the AT&T logo. If anyone knows what to do about this...
http://pastebin.ubuntu.com/504711/
boomerod said:
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
Click to expand...
Click to collapse
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
damis648 said:
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
Click to expand...
Click to collapse
Did you ever get back to stock? I think we had a good thought...
I guess I have to admit that I like to tinker. What I need to do is get another phone that I leave alone so I don't loose my communication to the world.
-Edit-
Back at the leaked Cappy Froyo...guess I'll just live with this until we finally get a fully functional Froyo.

Home button not working??

Hey guys! I hope you can help me D:
My Galaxy S:
CM7 latest update #57 or so
Kernel: glitch v11 (also doesnt work with standard kernel)
Since today my homebutton isnt working correctly. It only works for getting into recovery and into download mode.
If i press it in the keytest in cwm recovery it isnt recognized, same when the phone is booted :-S
I reflashed the update with deleting the cache but that doesnt work D-:
Have you guys any idea? :-/
Thanks
Mario (sorry for my bad english *facepalm* ^^)
Sent from my GT-I9000 using XDA App
Does it work when the phone is booted normally?
No it doesnt.....
Should i send it to samsung? :-/
Sent from my GT-I9000 using XDA App
I'm sorry, but I think that's your only choice.. To me, it seems like a hardware-related malfunction..
Hmmm yes i think youre right.
I just tried to get into recovery only with volume up + turn on button... thats working
"
I will flash samsung original firmware, maybe it works ^^
Sent from my GT-I9000 using XDA App
If it does: great!
If it doesn't: RMA must be the way..
you have to send your phone to Samsung services it'll be best solution i think.
Dudeeee, what on earth man? RMA should only be treated as a last resort. Don't give up so easily. He hasn't even tried flashing back to stock roms.
He already said it works for getting into recovery and download mode, which indicates it's working to some degree.
OP, flash that stock firmware and tell us what happens.
snapper.fishes said:
Dudeeee, what on earth man? RMA should only be treated as a last resort. Don't give up so easily. He hasn't even tried flashing back to stock roms.
Click to expand...
Click to collapse
If you read my post correctly, you'll notice that I've suggested to flash the stock-firmware _before_ sending it as a RMA to Samsung..
snapper.fishes said:
He already said it works for getting into recovery and download mode, which indicates it's working to some degree.
(...)
Click to expand...
Click to collapse
Again, read his post correctly - he was pressing "Volume Up" + "Power On" and did _not_ mention any press on the Home-button..
Eagle3386 said:
Again, read his post correctly - he was pressing "Volume Up" + "Power On" and did _not_ mention any press on the Home-button..
Click to expand...
Click to collapse
So how do you think he has access to recovery???.......He mentionned he was able to go into recovery mode,basically,the home button works.
I'm pretty sure it's a software related problem.
Go with the stock rom first and tell us the result.
Nope.
Im on stock rom now..
The home button is not working
I got into Download mode with Volume down and Turn-on-button
I havent touched the home button at all
Dont know why thats working ^^...
Tommorow im bringin it to the Shop for RMA
OR do you have some Ideas
It is as though your home button is stuck to "on".
I fear that the next step is to rma.
duchkata said:
So how do you think he has access to recovery???.......He mentionned he was able to go into recovery mode,basically,the home button works.
I'm pretty sure it's a software related problem.
Go with the stock rom first and tell us the result.
Click to expand...
Click to collapse
The post above, compared to your latter one:
duchkata said:
It is as though your home button is stuck to "on".
I fear that the next step is to rma.
Click to expand...
Click to collapse
Do you find the inconsistency? No?
I'll help you out: at first, you paint me as a fool, because you're too blind to read my post correctly.
Just one post later, you suggest what I was suggesting since my first (or second, can't remember right now) post.
Result: read first, think second, think again, _then_ - and only then - post, but stay polite at _any_ time!
Had the exact same issue with the button working for booting into recovery and download mode.
Sorry to say this is hardware related and I hope your rma is accepted.
I took mine to the repair centre and they told be it is water damaged. I never dropped it in water though.
Also the home button is glued to the whole freaking screen. The samsung part comes as the whole lcd assembly with the buttons with it so I was quoted 245 dollars.
You can buy the button online but I digest you to have a look on YouTube for the dude that disassemble the phone. You will see how hard it is
By the way, my button stopped working for recovery as well although now of o press hard on it it does work (for booting and in the OS).
last but not least, you will learn how to use the phone without the home button
Good luck with the rma
Sent from my GT-I9000 using XDA Premium App
Removed.
................
hello guys! I have the same problem since yesterday and I would like to know how did it end for you? Is it really hardware or it can be solve by software? Thanks in advance
cholabcn said:
hello guys! I have the same problem since yesterday and I would like to know how did it end for you? Is it really hardware or it can be solve by software? Thanks in advance
Click to expand...
Click to collapse
Yes, hardware. No, can't be.

Lock button doesn't work and no download mode

Hey everybody,
A few weeks ago my Captivate lock button stopped working. I am under the impression that it is a software glitch, but I haven't had time to play with it until now. I finally got the phone to show up on my computer (it was stuck booting into ClockworkMOD, but the select button didn't work. So I basically had a useless phone). I used Odin and flashed to 2.3.3 with Master Clear thinking it would fix the glitch and everything would work like normal again, but I was wrong. The lock button still doesn't work, and now I don't have my phone rooted. I want to flash back to stock Eclair, maybe that will fix this glitch, but I can't get into download mode. No button combo, no adb...nothing.
I'm here, because I want to know if anybody else has this problem, or if there is a fix that I can't find searching all over the Internet. Or if anybody knows how to root the Captivate without going into download mode.
Thanks in advance
this is the development section. Do not post questions here.
NO ONE WILL ANSWER YOU!
TRusselo said:
this is the development section. Do not post questions here.
NO ONE WILL ANSWER YOU!
Click to expand...
Click to collapse
Sorry, I will move it.
daleaf said:
Hey everybody,
A few weeks ago my Captivate lock button stopped working. I am under the impression that it is a software glitch, but I haven't had time to play with it until now. I finally got the phone to show up on my computer (it was stuck booting into ClockworkMOD, but the select button didn't work. So I basically had a useless phone). I used Odin and flashed to 2.3.3 with Master Clear thinking it would fix the glitch and everything would work like normal again, but I was wrong. The lock button still doesn't work, and now I don't have my phone rooted. I want to flash back to stock Eclair, maybe that will fix this glitch, but I can't get into download mode. No button combo, no adb...nothing.
I'm here, because I want to know if anybody else has this problem, or if there is a fix that I can't find searching all over the Internet. Or if anybody knows how to root the Captivate without going into download mode.
Thanks in advance
Click to expand...
Click to collapse
the home button also functions as a select button in CWM
How were you able to get into download mode with the power button not working? Just curious, because I am having the same problem. Building a JIG now

[Q] recover bricked Samsung ATIV Odyssey ? HELP !!!!

Hi all,
Wondering if anyone could help me. On the Samsung ATIV Odyssey I have, when it boots, it will show, Windows Phone, Samsung screen then just shows the spinning gears..this will go on forever. I tried to reset and "tried" to hard reset it but could never get the "!" To show up.
Is there any way possible to recover this phone or am I stuck having to send it out to Samsung?
I have not been able to get anywhere with this phone and can't find recovery software like Nokia has for their phones for Samsung models....
Thanks in advance!!
Can anyone help with this issue ?
I ended up calling Samsung, the phone is out of warranty (of course) but, they say they will do a free one time flash to attempt to recover the phone. The provided free shipping and will flash it and return the phone to me at no charge.
Nice, didn't know they offered that....
DavidinCT said:
I ended up calling Samsung, the phone is out of warranty (of course) but, they say they will do a free one time flash to attempt to recover the phone. The provided free shipping and will flash it and return the phone to me at no charge.
Nice, didn't know they offered that....
Click to expand...
Click to collapse
If 'someplace in CT' means 'quacche patte a Catania vicinu a fera o luni' we live in a similar place
Anyway you can get informed better here:
http://forum.xda-developers.com/showthread.php?t=2692049
Take a Flash tool. more infos here(the procedure should be the same for the odissey)
http://forum.xda-developers.com/showthread.php?t=2391138
You can try to flash the fake wolfROM with the customwolfROM.csc(or mbn, I don't remember) for Odissey (You'll find it in the first thread i've linked you)
OF COURSE FOLLOW THE GUIDE NOT TO BRICK MORE YOU DEVICE.
If you have any problems you can ask.
Thanks, does the Odyssey (SCH-I930) can be flashed with the roms for the ATIV S ? Interesting, If I can get this phone up and running again, I might try to go the ROOT route if I can. That is if it can be recovered.
2 computers would not even detect this phone because of it being a reboot loop. So even if I had a rom or something else for it, the computer would not even see it.
Not my primary phone, so no big rush if I have to wait for a week...
DavidinCT said:
Thanks, does the Odyssey (SCH-I930) can be flashed with the roms for the ATIV S ? Interesting, If I can get this phone up and running again, I might try to go the ROOT route if I can. That is if it can be recovered.
2 computers would not even detect this phone because of it being a reboot loop. So even if I had a rom or something else for it, the computer would not even see it.
Not my primary phone, so no big rush if I have to wait for a week...
Click to expand...
Click to collapse
NO IT CAN'T OF COURSE BE FLASHED WITH OTHER PHONES' ROMS BUT IF YOU KEEP READING ALL THE PAGES OF THE THREADS I'VE LINKED YOU YOU'LL LEARN THAT WOLF MADE OTHER CUSTOM CSCs(the smallest,editable part of a WP rom) SPECIFIC FOR YOUR DEVICE AND HOW TO FLASH 'EM
(I wrote with caps lock in order to let you get the importance of the point )
It's normal that every pc doesn't see your phone:something in its os is missing.I would advice you to flash another csc -description in this the customwolf rom thread I've already link to you -(see the specific combination of your model in order to know if your phone turns on in download modus and you can try to flash again it)
EDIT----
Sorry man,I just Thought now to it: You could simplify your life just trying first a Hard reset from buttons combination (I think this is the correct one,but you can search for yourself for the specific combination of buttons of your phone).
Alternate Method
Step 1
Turn off the phone and wait 15 seconds.
Step 2
Press the "Power" button. Press and hold the Volume Down button until an exclamation mark appears on the screen.
Step 3
Press the Volume Up button and then press the Volume Down button. Press the Power button and then press the Volume Down button again. The screen goes black and then the reset process completes.
In this way you should be able to HR your device without turning it on and risking to damage it more with flashing
gidannifico said:
NO IT CAN'T OF COURSE BE FLASHED WITH OTHER PHONES' ROMS BUT IF YOU KEEP READING ALL THE PAGES OF THE THREADS I'VE LINKED YOU YOU'LL LEARN THAT WOLF MADE OTHER CUSTOM CSCs(the smallest,editable part of a WP rom) SPECIFIC FOR YOUR DEVICE AND HOW TO FLASH 'EM
(I wrote with caps lock in order to let you get the importance of the point )
It's normal that every pc doesn't see your phone:something in its os is missing.I would advice you to flash another csc -description in this the customwolf rom thread I've already link to you -(see the specific combination of your model in order to know if your phone turns on in download modus and you can try to flash again it)
EDIT----
Sorry man,I just Thought now to it: You could simplify your life just trying first a Hard reset from buttons combination (I think this is the correct one,but you can search for yourself for the specific combination of buttons of your phone).
Alternate Method
Step 1
Turn off the phone and wait 15 seconds.
Step 2
Press the "Power" button. Press and hold the Volume Down button until an exclamation mark appears on the screen.
Step 3
Press the Volume Up button and then press the Volume Down button. Press the Power button and then press the Volume Down button again. The screen goes black and then the reset process completes.
In this way you should be able to HR your device without turning it on and risking to damage it more with flashing
Click to expand...
Click to collapse
Thanks again for your help here !!!!!!!!!!!!!!! The hard reset is not working. I tried this MANY time before posting (after about a day playing with it, at the point of giving up hope). I can try the key commands but, at no point will I EVER see the exclamation mark. No kidding, I must of tried this 40 different ways, with different timing, I can 100% confirm that something is screwy with this phone.
If I do the Power plus volume down (to try to get the exclamation mark), as soon as a let go of the power button and holding the vol down, the phone will go in a reboot loop.
The phone does not get to a point where the PC will detect it, it will start to boot up and it will show on the display Windows Phone, then Samsung logo, then it will just show the spinning gears(like it had a failed update). It does this for ever (I let it go 24 hours before pulling it). I can do the soft reset but, that is it...
It's packed up ready to go but, I'll hold it for a day, do you think I could actually recover this phone with a rom ?
DavidinCT said:
Thanks again for your help here !!!!!!!!!!!!!!! The hard reset is not working. I tried this MANY time before posting (after about a day playing with it, at the point of giving up hope). I can try the key commands but, at no point will I EVER see the exclamation mark. No kidding, I must of tried this 40 different ways, with different timing, I can 100% confirm that something is screwy with this phone.
If I do the Power plus volume down (to try to get the exclamation mark), as soon as a let go of the power button and holding the vol down, the phone will go in a reboot loop.
The phone does not get to a point where the PC will detect it, it will start to boot up and it will show on the display Windows Phone, then Samsung logo, then it will just show the spinning gears(like it had a failed update). It does this for ever (I let it go 24 hours before pulling it). I can do the soft reset but, that is it...
It's packed up ready to go but, I'll hold it for a day, do you think I could actually recover this phone with a rom ?
Click to expand...
Click to collapse
I really don't know because I don't have the phone in front of me,so I can't 'think' to anything.
I just know that People flashed the custom csc..who knows,that could be Your solution-but could be not-.
I recommend you to read very well and many times the procedure.
Good luck and let me know.
gidannifico said:
I really don't know because I don't have the phone in front of me,so I can't 'think' to anything.
I just know that People flashed the custom csc..who knows,that could be Your solution-but could be not-.
I recommend you to read very well and many times the procedure.
Good luck and let me know.
Click to expand...
Click to collapse
Yea, I tried everything I could find in google and Bing...No luck, I'll send it back to Samsung to see if they can recover the phone....
Thanks again for your help. When I get it back, if it's running, then I will try to interop it....
DavidinCT said:
Yea, I tried everything I could find in google and Bing...No luck, I'll send it back to Samsung to see if they can recover the phone....
Thanks again for your help. When I get it back, if it's running, then I will try to interop it....
Click to expand...
Click to collapse
You're welcome
When the phone will be perfectly working you 'll be able to interop it with wolf's custom csc (the thread I've linked to you)
Cheers
BTW, I have the custom rom for the Odyssey, its definitely got some odd bugs.
Verizon stores can reflash it for you too for free, just need to hit up a Verizon CORPORATE store. Apparently they have the tools and the ROM, instead of waiting for it to be mailed and come back.
Well I used the wolf custom rom and follow the exactly instructions but my phone now say is corrupted, and instead of boat show me a message telling me that!
So, I got another one and now has the same problem, so, somebady knows if there is at day an original rom available?
Still no public Odyssey ROM yet.

Fingerprint sensor error ?

Hi I'm trying to set up my lock screen whit finger print but no matter homw many time i try i keep getting an error has occurred whit the fingerprint sensor if this messages appears repeatedly restart you phone i restarted the phone multiple times and same problem tried diffrent roms same problem any one else has this problem ?
COCODRILO45 said:
Hi I'm trying to set up my lock screen whit finger print but no matter homw many time i try i keep getting an error has occurred whit the fingerprint sensor if this messages appears repeatedly restart you phone i restarted the phone multiple times and same problem tried diffrent roms same problem any one else has this problem ?
Click to expand...
Click to collapse
Interesting, this happened to me as well yesterday along with some incredible lag with keyboard and scrolling pages. Like the phone is doing something, ive Odin flashed stock fw 4 times with full wipes. seems something just suddenly defected my phone..
EDIT: BTW this happened after trying to flash a custom rom to my phone, phone was running great when i got it.
i got it working i had to flash back to stock via odin that's the only way it works for me as soon as i flash a custom rom it will stop working if you figure out how to get it working whit a custom rom let me now pls
COCODRILO45 said:
i got it working i had to flash back to stock via odin that's the only way it works for me as soon as i flash a custom rom it will stop working if you figure out how to get it working whit a custom rom let me now pls
Click to expand...
Click to collapse
Really? flashing back to stock worked for you? hmm wonder if my stock fw from sammy is damaged, but usually if it was it wouldn't flash via Odin it fail.
yea that worked for me im about to flash it back to stock again i just cant get it to work on any rom I keep getting that error i guess ill go stock rooted for now
COCODRILO45 said:
yea that worked for me im about to flash it back to stock again i just cant get it to work on any rom I keep getting that error i guess ill go stock rooted for now
Click to expand...
Click to collapse
Now when you got that fingerprint error, did you experience and hard core lag in scrolling or in the keyboard? like every 3 seconds it pause like it's doing something?
not really im using nova launcher and for keyboard swiftkey running preety smooth im on firekat rom
Having the same issue with Hyperdrive. Restore my stock rooted backup and it works fine. Really looking forward to an answer on this one.
Must setup first time before rooting and flashing roms. This has been discussed in other threads.
Did that, still didn't work.
Diablohtr said:
Having the same issue with Hyperdrive. Restore my stock rooted backup and it works fine. Really looking forward to an answer on this one.
Click to expand...
Click to collapse
Is it just Hyperdrive or have you tried one of the other ROMs? I am Dynamic Kat and do not have the issue although other people do, ones that did not setup before flashing that ROM.
keitht said:
Is it just Hyperdrive or have you tried one of the other ROMs? I am Dynamic Kat and do not have the issue although other people do, ones that did not setup before flashing that ROM.
Click to expand...
Click to collapse
Haven't tried any others yet. Going to wait it out a few days and hopefully we will have a solution.
COCODRILO45 said:
Hi I'm trying to set up my lock screen whit finger print but no matter homw many time i try i keep getting an error has occurred whit the fingerprint sensor if this messages appears repeatedly restart you phone i restarted the phone multiple times and same problem tried diffrent roms same problem any one else has this problem ?
Click to expand...
Click to collapse
I have your same problem but even worse, not going to solve it stock still gives the same result I am losing faith
CapitanFantasma said:
I have your same problem but even worse, not going to solve it stock still gives the same result I am losing faith
Click to expand...
Click to collapse
I tried using odin, I was on NIH firmware with no luck... and then flashed odin with NJ7 with no luck from that, I must of flashed the firmwares over 8 times,
I went and replaced my white note 4 at a corporate near me, with a black note 4.. no one had them in stock, dialing 611 was no help, they said since u bought it at a store, I had to go there, I found a corp store that had 2 left, I rushed over cause they don't hold it for anyone. employee wanted to charge a $50 restocking fee, I told them the phone is defective, and the manager override the sale..
I am having the same problem of the fingerprint scanner not working after flashing a custom ROM. I followed everything to a T & it didn't install (& yes, it is for my N4). I went back to stock using Odin, several times & have not resolved it yet. I do not want to take it back but I do like having the fingerprint scanner. Luckily, I have another N4 cause I bought 2 when they came out cause I planned on trying to turn a profit on 1 of them, but I'll be damned if everybody didn't make it easy as hell for anyone to get one. I guess I can use the 1 that doesn't work right for flashing & playing around on & then when I find "THE" ROM that I'm happiest with, I can flash it on the good 1. IDK. This is BS though. Somebody has to know how to get it back working right. I know that people that helped create this phablet, are members of this site, so I hope that they or someone else that has fixed this problem replies to our question. I flashed this ROM... http://forum.xda-developers.com/note-4-sprint/development/rom-alpha-semper-fi-t2926682 & the fingerprint scanner still worked, but after flashing this ROM... http://forum.xda-developers.com/note-4/snapdragon-dev/25-october-2014-n4-echoe-rom-1-t2917941 it no longer worked & hasn't since. I am going back to stock (again) & hoping this will work. I'll update if it works.
See this post/thread, it worked for me....
http://forum.xda-developers.com/showpost.php?p=56896357&postcount=85
http://forum.xda-developers.com/not...ure-fingerprint-scanner-t2919478/post56896357
Looks like these are for T-Mobile. What about Sprint? N910P
Sent from my SM-N910P
JoeBear1975 said:
I am having the same problem of the fingerprint scanner not working after flashing a custom ROM. I followed everything to a T & it didn't install (& yes, it is for my N4). I went back to stock using Odin, several times & have not resolved it yet. I do not want to take it back but I do like having the fingerprint scanner. Luckily, I have another N4 cause I bought 2 when they came out cause I planned on trying to turn a profit on 1 of them, but I'll be damned if everybody didn't make it easy as hell for anyone to get one. I guess I can use the 1 that doesn't work right for flashing & playing around on & then when I find "THE" ROM that I'm happiest with, I can flash it on the good 1. IDK. This is BS though. Somebody has to know how to get it back working right. I know that people that helped create this phablet, are members of this site, so I hope that they or someone else that has fixed this problem replies to our question. I flashed this ROM... http://forum.xda-developers.com/note-4-sprint/development/rom-alpha-semper-fi-t2926682 & the fingerprint scanner still worked, but after flashing this ROM... http://forum.xda-developers.com/note-4/snapdragon-dev/25-october-2014-n4-echoe-rom-1-t2917941 it no longer worked & hasn't since. I am going back to stock (again) & hoping this will work. I'll update if it works.
Click to expand...
Click to collapse
sorry dude, I don't know what it was, but when it happened to me, I was on NIH, and had the fingerprint saved, i tried everything, and when i deleted the saved fingerprint, it didn't want to work, nothing worked, i tried for 2 days searching and trying out my own stock odex roms and the firmware, it did not work.. sucks i know...
i had to return it to tmobile corporate store, if u have insurance on it, just play stupid and return it, if u have someone you know on tmobile, just let them put it on their account with put the $8 insurance, have them wait 1 week, call 611 and just say the fingerprint sensor went bad, and just pay $5 and have a replacement sent out,
lucky for me it happened less than a week for me, and went to a tmobile corporate store and they gave me a new phone in a box, but a replacement is still good it is not a refurbished phone...
I got it figured out & will post a file once it finally uploads, but in the mean time. If you have registered at SamMobile.com go there, click on the firmware tab, scroll halfway down to where it says FIRMWARE on the left side of the column & search device here on the right side. Type in your model number & it will show up right below the search area. Click & download the newest file. Here is the link for the Firmware site with search field filled in with N910 http://www.sammobile.com/firmwares/ While that is downloading, do a factory reset on your phone, DO NOT backup your info, you will need to restart it, but it's worth it. Once the reset is done, your phone will reboot, don't worry about going into setup, just turn the phone off & go into download mode (while phone is completely off, hold, in this order, VOLUME DOWN, HOME & POWER, press VOLUME UP when prompted. Connect your phone to computer. After the file downloads, open Odin (I'm assuming you already have Odin installed on your computer, if not you can find the link here http://odindownload.com/ I didn't have luck with Odin 3.09, but the 3.07 version works great. Your Firmware file should be done downloading by now, if it is, put it in your Note 4 folder (or whatever folder you have designated for your N910-) & extract it to there. Open Odin & click on the PDA button (& DO NOT CLICK ANYTHING ELSE), click on the file you just extracted & then click Start. Once that loads, your phone will reboot & be just like it was from the factory. Hope this helps everybody. Once the file uploads to my Dropbox, I'll post it on here to save you some time.
Here's the link for N910P https://www.dropbox.com/s/f5f63rb4d8ybsm3/N910PVPU1ANK2_N910PSPT1ANK2_XAS.zip?dl=0
If this was helpful, please hit thanks.
mdiaz33685 said:
sorry dude, I don't know what it was, but when it happened to me, I was on NIH, and had the fingerprint saved, i tried everything, and when i deleted the saved fingerprint, it didn't want to work, nothing worked, i tried for 2 days searching and trying out my own stock odex roms and the firmware, it did not work.. sucks i know...
i had to return it to tmobile corporate store, if u have insurance on it, just play stupid and return it, if u have someone you know on tmobile, just let them put it on their account with put the $8 insurance, have them wait 1 week, call 611 and just say the fingerprint sensor went bad, and just pay $5 and have a replacement sent out,
lucky for me it happened less than a week for me, and went to a tmobile corporate store and they gave me a new phone in a box, but a replacement is still good it is not a refurbished phone...
Click to expand...
Click to collapse
I stuck with it & fianlly got it figured out. What a pain in the a$$ that was, lol

Categories

Resources