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
Related
Hi,
Last night my Galaxy S was low on battery, and I kept trying to turn it on for it to die right away (it was working as expected I guess)
This morning after I charged my phone it wouldn't turn on at all! It loads to the logo screen, makes that jingle sound and then holds and doesn't turn on.
I can get to recovery and download mode.
I put OCLF on like 2 months ago, but haven't modded/flashed ANYTHING since. It is very bizarre how it just died.
I'm wondering what my options are now. Obviously I would rather not loose all my personal files. Since I can get into download mode, can I just flash a new firmware? I'd like FroYo anyway, but I haven't got a clue what to do.
Great start to the year – !
Cheers,
Mitch
EDIT: I just decided to try the "Clear User Cache" option and then reboot to no avail. Now I can't get back into recovery mode!?!? Download mode still works. Huhh?? Is this expected? Have I lose Recovery Mode entirely now? Crap.
seeeems like an odin flash via the download mode is the only way. There are a few tutorials on this site and even tut vids on youtube so you should be fine if you just follow everything they do (as long as it works for them of course)
How do I know what version to flash? I have read a few tutorials and they all have started with "Dial x and check you have y" etc. Obviously I can't do any of that.
What is the *safest* firmware I can flash?
My phone currently has some optus variety.
Please forgive the noodish question.
Mitch
Where are you located? And who is your provider?
Hi,
I'm in Sydney Australia and my provider is Optus.
Thanks
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
m1tch37 said:
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
Click to expand...
Click to collapse
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Sounds like you'll need to do a flash of a stock rom..
By the way, the old oclf had some issues that might lead to system corruption (unfortunately I'm not very sure exactly what it does, or whether it could lead to this problem). I'd suggest getting one of the newer lag fixes available here when you do get your phone running again
tragusman said:
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Click to expand...
Click to collapse
tragusman has got it right. Depending on what the issue is, you'll either recover nicely or your phone is toast. Flash the above stock firmware and give it a shot. Note that you'll likely loose your data and settings.
If you're new to flashing firmwares, check the great reference guide on where to find Odin and how to use it (this is the app you'll use to flash the above firmware).
http://forum.xda-developers.com/showthread.php?t=723596
After flashing, try getting into recovery mode. If you can look for an error message under the standard menu. Can't get to d/l mode? You're probably in trouble. Get into recovery and see an error msg? Post the error here or google it for a solution. No error msg? You're probably ok - restart the phone.
Good luck.
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
m1tch37 said:
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
Click to expand...
Click to collapse
If it's broke, you can't break it any more I've sent phones back in for support after flashing back stock firmware (flashing it after it "died").
So I was retarded and followed the instructions (or started to) on androidadvices dot com/how-to-update-samsung-galaxy-tab-to-stable-gingerbread-2-3-3-firmware
My Tablet will not boot past the T-Mobile logo.......... they are being assholes and telling me i need to deal with samsung ......... who told me it would be 6-8 weeks for a replacement........ is there ANYONE out there that can help me with just resetting it???
If you can get to the T_Mobile logo, you probably have a working bootloader and that mean you just need to flash the correct firmware for you device.
In short words, go to samfirmware.com and download the right firmware for your tablet model.
Once you have the firmware, flash them to your tablet with 'odin' (flash software, that you can also get in the mentioned website).
This should solve the problem.
If this works I will love you.
So i am obviously more retarded than I thought pedrohfsd ........ I have an SGH-T849 and i cannot FIND the firmware on that site..... seriously? UGH
pm me i'll tell you what to do , with th stock firmware for Tmobile , i helped someone before 2days he had same tab with you ) and same problem
pedrohfsd said:
If you can get to the T_Mobile logo, you probably have a working bootloader and that mean you just need to flash the correct firmware for you device.
In short words, go to samfirmware.com and download the right firmware for your tablet model.
Once you have the firmware, flash them to your tablet with 'odin' (flash software, that you can also get in the mentioned website).
This should solve the problem.
Click to expand...
Click to collapse
You sir, are brilliant.
I wasn't able to locate the firmware on the samfirmware.com but I DID find it on XDA from another user. Put phone into download mode... waited till the little box in Odin turned yellow and loaded that badboy on there. After about 5 minutes it was back into the 2.2 OS again. The only problem that I had was with programs that had been installed before and loaded at boot (Just had to uninstall / reinstall) But for the most part its back to the way it was.
Thanks so much for your help!
You too Kosh, as I am sure you were going to walk me through exactly what I fumbled through on my own (I'm lucky I didn't blow anything up haha)
NO more attempts to get 2.3 on this badboy!
Thanks again all <3
I'm glad to hear that KalKainen, the first time i soft bricked my phone i got desperate too.
But after some weeks i saw the inumerous progressions that people develop in custom roms here in xda, and flashed the whole thing again =P.
pedrohfsd said:
I'm glad to hear that KalKainen, the first time i soft bricked my phone i got desperate too.
But after some weeks i saw the inumerous progressions that people develop in custom roms here in xda, and flashed the whole thing again =P.
Click to expand...
Click to collapse
Amen man..... desprate is about right.. haha... now if i could only figure out why i have to CONSTANTLY reboot it in order to restore network service (Even though I have 3g and full bars... no text messages send / come in and programs that use data error out... ) I would be happy. This has been happening for the last 4 months badly enough that I can have to reset it 10 times in a 2 hour period >.< I cant even put it into flight mode.... but after I TRY putting it into flight mode and then reboot it... it comes BACK in flight mode.... I hoped the reinstall of the firmware would fix it.. but alas..... still plagued. AT LEAST IT WORKS THOUGH!!
The story so far...
Bought a new Optimus Black and gave it to my girlfriend for her birthday a couple of days ago. After playing with it for about an hour she put it down, I picked it up and decided to have a tinker. I installed Cyanogen mod 3.5.1 after rooting it with Gingerbreak. So far so good but I didn't really like the look of the ROM and the absence of a Market seemed like hassle so I used ClockworkMod to restore the backed up stock ROM.
It's still working fine but now I see there is an official update from inside the phone. I presume it's the upgrade to Android 2.3 so run it and reboot the phone. That's when it all goes wrong. I'm now stuck in the CWM recovery screen. I try all the options, following any online guides I can find that were supposed to have worked for people. I try restoring the backup, restoring cyanogen, clearing the cache, dalvik, everything but nothing happens and I keep booting back into the CWM recovery screen.
Next day I try the LGUnitedMobileDriver and the phone recovery option but despite trying several times I can get no further. A friend tried to use Odin to restore it but got no success. Finally, we tried restoring with a KDZ file with
KDZ_FW_UPD_EN, Windows Enabler and LG B2CTool and now the phone got stuck in yet another loop - a black screen with 'updating firmware'. The LEDs flash for a minute and it reboots and does the same again.
What's more, the phone will now no longer charge or turn on without being connected to the mains.
What are my options here?
Follow the tutorial given below.
http://forum.xda-developers.com/showthread.php?t=1275315
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
pickarooney said:
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
Click to expand...
Click to collapse
have you tried the CS_EMERGENCY option in R&D TOOLS? Wait I'll find the link..
Here >>> http://forum.xda-developers.com/showpost.php?p=18841596&postcount=8
http://forum.xda-developers.com/showpost.php?p=18740082&postcount=45
The CS_EMERGENCY is the only thing worked, he used a german V10A ROM. If you managed to unbrick it, you can flash it again with your desired KDZ, or use CS_EMERGENCY and flash directly your desired KDZ. TRIAL AND ERROR.
Emergency c-section... nope, I will try that now!
Said that it will get stuck at 4% but it is still flashing. Just wait for the phone to reboot by itself.
It just crashes with a fatal error as soon as it gets to the second tab (downloading) on both PCs I tried it on. I tried several KDZ files with the same result.
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
pickarooney said:
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
Click to expand...
Click to collapse
Does it have warranty? Why not RMA it, I think it has a hardware problem now since you mentioned it doesn't charge anymore. Also, have you tried a different USB cable?
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
pickarooney said:
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
Click to expand...
Click to collapse
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
gabwerkz said:
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
Click to expand...
Click to collapse
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
darkzorn said:
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
Click to expand...
Click to collapse
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
Fingers crossed for you !!!
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
IT will mostly work..Good luck though and please do reply here and let us know if it worked..
Morning all,
I apologise if this is in the wrong section but I am new to the forum and in a bit of pickle.
Around a week ago I rooted my lovely new note 3 to hopefully one day install some nice new ROM to get rid of the horrid touch wiz and actually see the full potential of the phones power. However, for some silly reason while I was using titanium backup on my phone I thought it would be a good idea to uninstall touch wiz thinking it would magically go back to basic android however it didn't. It is completely broken now, woops. The first issue I had was it would boot up and stick to the Samsung logo and just glow so I thought it would be an idea to install stock ROM via ODIN to try and revert it back to normal. Once I downloaded the correct stock ROM it was uploading through download mode however at the last minute it failed with a ext4 error which I think it means it's bricked? Not sure, completely new to this. I am now a bit stuck as I am not 100% sure what to do next.
The phone will only boot into either the firmware upgrade has encountered an issue, basically Odin mode or download mode. I have tried recovering it through kies however it cant connect to it. It knows it is there as it will start searching for it when it's connected however says it can't find it.
My phone is a note 3 SN SN-9005. The system status is custom, reactivation lock is off, Knox kernel lock 0x0, Knox warranty void 0x1 and write protection is enabled.
Obviously I would like to get the phone back to normal, I don't care if it has to be completely wiped and brought back to normal I would like it to just work. I've been an complete idiot and fiddled with something I'm not 100% sure on and I would like to not have a 600 quid paper weight hehe.
I will greatly appreciate any help or feedback.
You won't get the best feedback for a 9005 model here. We are the 900A version stuck on AT&T. Yes, however, we have plenty of intelligent people here. It's best to post your question here in the main Samsung Galaxy Note 3 thread next time:
http://forum.xda-developers.com/galaxy-note-3/help
Next, since you've voided your warranty as Knox being 0x1 - you're pretty much screwed for a refund or replacement based on PRESENT development from what I have read all over the AT&T threads. Understand this. Now, that being said, did you install a custom recovery or have your original recovery?
Here's my input/help. Forget about ODIN. You don't need that if all you did was remove your touch wiz.
Take out your battery, put it back in and hold VOLUME UP, POWER, and HOME together until you reach a recovery. Then if it's the stock recovery, wipe your cache partition, then wipe data/factory reset. Then reboot and you're good back to starting over. Check with a rooting application to see if you still have or not. If not, then obviously reroot
Also, don't ever do anything like that again without thinking what it could do, lol . Always tread carefully whenever you are new to something. Just my two cents for you. If you came here to root and learn it, don't be afraid to ask questions about applications and expanding your knowledge. No one will ignore you if you ask a simple question in the right manner/thread.
Good luck!
Thank you for the feedback. I have defiantly learnt from my mistake with this one. I have usually been lucky diving into things blindly hehe. I have tried to put it into recovery mode however it just vibrates like it should and then comes back up to firmware upgrade issue with the two computer screens an a attention sign in the middle. Is there anyway to get recovery mode back.
apdnote said:
Thank you for the feedback. I have defiantly learnt from my mistake with this one. I have usually been lucky diving into things blindly hehe. I have tried to put it into recovery mode however it just vibrates like it should and then comes back up to firmware upgrade issue with the two computer screens an a attention sign in the middle. Is there anyway to get recovery mode back.
Click to expand...
Click to collapse
Wish you had come here when you deleted touchwiz only instead of playing with Odin. Looks like you messed it up even further and have to now use Odin to reinstall your firmware. I'm about to go to sleep, but do this.
1) Take out battery and put it back in. Then press and hold VOLUME DOWN + HOME + POWER at the same time until you reach DOWNLOAD MODE.
2) Follow the steps here and use your odin or latest odin (shouldn't matter):
http://www.androidrootz.com/2013/10/how-to-unrootunbrick-galaxy-note-3.html
Oh, and google is your friend. It's how I learned things over the years...READING, then tinkering....you're welcome .
I wish I did as well. I will try this when I get back from uni this evening and post back results.
Thank you again.
apdnote said:
I wish I did as well. I will try this when I get back from uni this evening and post back results.
Thank you again.
Click to expand...
Click to collapse
You're very welcome, bro.
opasha said:
You're very welcome, bro.
Click to expand...
Click to collapse
I used what you have said to do and downloaded the correct firmware however when I try and install it via odin in download mode I get a FAIL(SIZE!) message at the end. Its not an ext4 error anymore but im worried at what is going on now. I have tried searching it up on google however nothing has come up. Looks like ive completely broken it... ='(
apdnote said:
I used what you have said to do and downloaded the correct firmware however when I try and install it via odin in download mode I get a FAIL(SIZE!) message at the end. Its not an ext4 error anymore but im worried at what is going on now. I have tried searching it up on google however nothing has come up. Looks like ive completely broken it... ='(
Click to expand...
Click to collapse
You have the 9005 right? I think you have the wrong file to odin. What is the exact model number of your phone and where are you located in the world? (reason I ask is there are different regions to choose from)
agent929 said:
You have the 9005 right? I think you have the wrong file to odin. What is the exact model number of your phone and where are you located in the world? (reason I ask is there are different regions to choose from)
Click to expand...
Click to collapse
SSN: SM-N9005GSMH
S/N: RF1D96B6ELB
United Kingdom Vodafone.
Im sure I downloaded the 9005 for samsung in the uk but I wil try again from a different site that specficly says what country and code.
If not would you be able to post me a link to the exact one?
Many thanks
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Good to hear!
apdnote said:
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Click to expand...
Click to collapse
Your welcome, don't forget to hit the thanks button for anyone that helped you!
apdnote said:
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Click to expand...
Click to collapse
Hi, I am using same SSN. Can you please confirm the working rom download URL? Appreciate your help.
Thank you.
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.
I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.
thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.
I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button