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
Related
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Zink6 said:
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Click to expand...
Click to collapse
try a re flash of another ROM preferably a stock ROM then start all over again, similar thing happened to me earlier, i am quite new to all this but i dont know if its the kernel or lagfix i had what caused this...
i re flashed back to froyo and then installed darkys ROM then re installed my kernel last.. all is good (for now)
worked for me first time but when i went to sgs tools to upgrade your apps ie gallery, camera, it said no busybox installed but went ahead and done fine in v8.0 and i see that cwm changed from red to green too went to market for busybox to download it but when it goes to install phone just reboots all the time mmmm...
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
stepsch said:
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
Click to expand...
Click to collapse
YES !!! i agree, it is a pain.. but we love our phones and we would do anything for them its always best to flash back to standard FW if you ever get a problem...
I myself experienced this. Whenever I installed a new software, it would just boot. I got fed up because darky's forums are also down and there is no discussion. flashed doc's rom. Now everything is fine.
...mh... but it's not caused by Darkys ROM. This cycling boot feature may appear at all ROM, at all lag fix actions and so on. It depends how proper you interact with phone- and ROM-features while configuring. A lil disturbance during your session (by you or battery issue or whatelse) or a not so well prepared basic from where you start and your unlimited-feature-wishlist-and-paint-it-golden-one-click-action is enough to interrupt the whole thing and run into trouble.
It was and is all the same - since DOS or C64. And it will be the same, even when iPhone is on level 12.x or Android will be able to beam you elsewhere thru the barcode scanner.
It's a game. Nothing more. And game means lot of fun - and in the beginning a certain thrill when your phone stuck first time and you are thinking: "... f*ck... bricked..."
yup same for me
cycle boot thing
didnt enable download mode before that....
can get into debug screen thou but wiping it doesnt help
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
Just tell the warranty guy darky screwed it .
OR
http://forum.xda-developers.com/showthread.php?t=853950
jje
cant even boot the phone mate
so ehm i dont get it....how can odin help me ?
is there any way of getting it into download mode still when it doesnt boot up? i heard about that JIG thing they made themself...isnt that just like the microusb cable that comes with it to the pc? i dont get it sorry if im trippin but im maddd at myself for even trying this lockscreen thing
http://forum.xda-developers.com/showthread.php?t=819551
jje
Thanks guys for all the replies. Now I did try flashing a stock rom but with no results. Was still having the same thing happening to me. If you guys can give me the link to the files you used to solve this problem, that would be great. Also just for your information I have a Bell i9000m unlocked running on fido. And NO its not an sd card failure lol.
As for DarelSteilz85, I did make one of those JIG usb for myself. It easy, just get the micro usb and strip it bare to the point you can see the pins on the usb which usually are connected to the wires and get a resister to connect one pin to another. Now for which pins, I remember it was 4 and 5 that you had to connect through the resistor but double check as I am not sure. Also the resistor has to be a certain level which I forgot so double check that also. Good luck.
http://forum.xda-developers.com/showthread.php?t=853950
What i use for problems .
jje
I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.
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
I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.
Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T
I have it as well. Have you flashed yet?
I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?
I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates
Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899
I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.
I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences
Can i root after upgrade?
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.
Soooo..... Is this rootable or not?
sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242
I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick
ok, thanks for the suggestion.
Anybody have a link for the firmware?
thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911
Can I autoroot with EQC1?
I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.