Related
I see the update is failing for a lot of people on the Samsung Captivate. Mine was reflashed using Odin3, and the update failed like so many others. I reflashed using Odin3 again, tried the update, and the same exact thing happened. The update fails at 50%.
The first time around, I was rooted and lagfixed, I tried it that way, then unrooted and tried again.
The second time around, I made absolutely no changes to the phone whatsoever, except signing in to my google account, and upping the screen timeout to 30 mins.
Doubt that this information is helpful to anybody, but was hoping maybe these symptoms would point to a trend as to why so many people's Captivates can't update.
Also, how many of you that failed used an Odin3 reflash any time before it failed?
I just flashed back to stock using the Odin One Click program and my updated failed at 50%. I tried 4 different time with the same result. I even reflashed a second time, did a Master Clear, and a Factory Reset. Stil no joy.
This morning as soon as I saw the news of the release I immediately hit the software update in the settings menu. Downloaded and just before I went to install I decided maybe it would be smart to do a rom backup with rom manager. Did that, and went ahead and then attempted to install it. It got to 100% and then said update failed, rebooted, said the same thing, update wasn't successful. However, if you checked about phone, it said it was jh7, but none of the jh7 stuff was there. The phone was rooted, sideload enabled, clockwork installed, and bloat removed, that's it. Never flashed a rom or lag fix or anything like that.
At this point I decided to try using the odin one click to stock jf6. Installed it, and tried to update again. Now, I'm getting what most people are getting, update fails very quickly at 50%, the phone reboots with no changes.
So I decided to use my clockwork backup, and restore my phone back to what it was before all this started this morning. Of course, since I remembered to do the backup AFTER downloading and postponing the update, it's sitting there waiting to go. Decided to try it and see if it acted the same as this morning, and now it's doing what it did right after the jf6 one click, gets to 50% and then fails with no effect.
How complete a wipe/restore of the phone is using rom manager? Because the update behavior on mine is different now after messing with odin than it was before, even after restoring it with rom manager.
Rooted with Sideloading on JH2. Not much else done to my phone. It has always worked well.
I didn't even get a percentage when trying to install. Just reboots and says "Update Failed".
Same issue here. Flashed back to JF6 using Odin one click. Update fails at 50%.
Only thing i can think of its that, that particular fw in odin is not the original fw flashed on the phone when bought and it does some sort of checksum or some kind of check.
50%, puke, and now when I click on update it tells me no firmware which I think is funny.
has anyone tried the firmware from
http://forum.xda-developers.com/showthread.php?t=777291
?
I don't have a PC at work (or even a x86 Mac) to play with.
Mine did the samething. I've used the the one click reinstaller a few times after trying out different roms. Maybe the one click installer changes something and it's blocking the update from totally completing. I hate to reinstall everything again but maybe theres a better way to do a total factory restore so we can get the update.
I'd guess that if it's doing a difference update (just applying the new stuff, not a full ROM) it needs a checksum match to be sure it doesn't bork the phone. Failing that (i.e. anything different from a pure stock phone) it will abort at some point.
There is a pure JF6 stock rom linked somewhere here on the forum--I'll see if I can find it, but it was never stickied or anything. Some guy just uploaded it because the one-click wasn't "pure" so to speak.
I guess this is their way of saying "you don't like our firmwares in the first place, you don't get this one either!"
Mine did all the same as you guys , failed at 50%. So I just got a new phone from att , told them it keep failing update. Did update right in store on new phone and boom installed no problem. On top of that gps is dead on, on new phone with update. Didn't get to try with out update. Already made sure I can get into download mode, no problems there. Note just scared to flash any roms since gps is perfect lol.
Sent from my SAMSUNG-SGH-I897 using XDA App
Omg and no xda force close lol . Also rf cal date is 7/10/2010 , old phone rf cal date was 8/07/10
Gps couldn't lock to nothing.
Sent from my SAMSUNG-SGH-I897 using XDA App
I tried using the Samsung Kies program and it says "this device's version cannot be updated". I'm wondering if that one click installer is not what it should be. Maybe if we flash to a different Captivate firmware the Kies program will update it.
I agree, I just like the way the one click installer worked. I know there's other roms/kernels posted, and I guess I'll have to do some legwork here. Here's hoping.
Just reflashed back to stock for the third time using Odin3 One Click and now when I check for updates it It says No Updates Available. Prior to this, it would dwnload the updated and reboot the phone and fail at 50% while installing. Frustrating!
I never use the 1click odin, I always put the .pit and the JF6 file into the 'normal' odin and use that -- haven't seen if anyone has tried that yet anywhere? Maybe that'll work.
BTW I still have no update available even after calendar trick :/
Hey guys, I did root my captivate. My question is do I need to un-root the device to apply the gps update or it does not matter.
Just downloaded JF6
how would I flash this back to my phone?
sorry if thats a stupid question but I cant find an answere seraching
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
cellgeek said:
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
Click to expand...
Click to collapse
Let me know how that goes. (Have family up in FloMo, very great place btw).
cellgeek said:
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
Click to expand...
Click to collapse
Tried this a little while ago. I went to run the update and now it's saying that no updates are available.
I spent about an hour on the chat window with ATT support and they can't seem to find a way to reset it to push again. The guy on the other end was knowledgeable as far as I could tell.
hell - he even mentioned froyo. He said they have ALOT of information on it for the captivate but no release date yet.
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
K-alz said:
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
Click to expand...
Click to collapse
basicaly what he said.. and since you said you did dynamic kat and alliance.. sounds like you are on the nc2 with Kitkat..
So, best bet is going to be make sure you have ss 3.75 and only flash the kitkat roms.. Dynamic kat, Alliance, Tweaked, Firekat, and you should be fine.. just dont try and flash any that are JB
From my Fired-up Note Pro 12.2!
Thank you. A combo of Android version AND baseband at the end?
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
bodycode said:
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
Click to expand...
Click to collapse
yeah if you are seeing 4.4.2 and nc2 you are on KK.. just make sure you are on 3.75 and all should be ok with flashing..
if for some reason it is borked,, go down to carls thread for odin files and how to odin back to stock nc2 and then start over and you should be fine
From my Fired-up Note Pro 12.2!
NO good. 3.75/stock slot/Alliance ROM fails.
Same ****. Black screen.
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
NO good. 3.75 fails!
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
AFter creating another slot and wipe, system mounting errors.
System mount errors all over the place after creating another slot, and installing Alliance. What's going on here? Something's really screwed up.
e: unable to mount '/system'
e: unable to mount '/systemorig'
over and over again
Can't check permissions after FActory reset. Please boot rom and try again after you reboot into recovery.
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
How to restore to Mj5?
How do I downgrade to Mj5 from KK4.2?
Thanks
warfenix said:
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
Click to expand...
Click to collapse
David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559715
I know what your problem is brother. This same crap happened to me. To a T! For some reason when u wipe system in safesteap, it wipes everything out. EVERYTHING. except data. I learned the hard way,like u. So when u flash roms, don't wipe system, only factory reset. I wipe it 3× every time. Then install your Rom. You will b fine. I haven't had one problem ever since I stopped wiping system. And no random reboots or anything, Roms now flash, and boot as they should. Hope this helps.
David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
K-alz said:
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
Click to expand...
Click to collapse
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
zounduser said:
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
Click to expand...
Click to collapse
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
Oh I agree. I've had to do it. I'm saying going forward so it doesn't happen again.
4 files in odin flash, done that 15 times.
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
David Sanborn said:
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
Click to expand...
Click to collapse
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Not a block screen on Odin and no trips.
Did I mention Odin works fine? Knox is not tripped. All is well right after Odin upload to phone in Download mode. It's only when I flash anything that blackscreen curses me again. heh heh.
K-alz said:
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Click to expand...
Click to collapse
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.
Ok so I get a brand spankin' new warranty swap and its a N910T3 with 5.1.1 etc. Awesome right? Well not so fast.
I seem to be encountering several strange problems I wanted to see if anyone else had these issues.
First off I started having some issues with the fingerprint scanner. Not reading or scanning as its has been flawless. It occasionally has thrown a "Scanner not working" error and makes me use my backup.
Next occasionally there's some strange lag here and there. I don't mean usual android or sammy lag I mean like something just isn't right lag.
Not sure if the lag is the same but on occasion in the middle of doing something like texting or emailing it will just show the background wallpaper freeze for a few secs and then eventually lock itself.
Also if my phone screen is off and locked and I get some form of notification unlocking the phone acts strange.
All of the issues seem to be more annoying then anything. I have not had any kind of FC at all just pauses and freezes and lags.
This is night and day from my old phone that I used for almost a year. I am just trying to find out if this is perhaps a hardware defect or bugs in this Android version. I am kind of hoping its bugs this phone is squeaky new and it would be a shame to lose this shiny new phone for a old refurb.
Has anyone experienced any issues with their N910T3 while on the latest stock?
DeeXii said:
it will just show the background wallpaper freeze for a few secs and then eventually lock itself
Click to expand...
Click to collapse
That looks exactly like a typical SystemUI FC... (without the FC message in your case) I guess you are not rooted right? If you are... try wiping Data/Cache/Dalvik x3 via TWRP, and Odin the latest stock firmware... DOG1 ... If you are not rooted... simply reset to factory and do the same... Odin DOG1. and re-test your Note 4... if problem persist... then you might have a Real Hardware issue.
TEKHD said:
That looks exactly like a typical SystemUI FC... (without the FC message in your case) I guess you are not rooted right? If you are... try wiping Data/Cache/Dalvik x3 via TWRP, and Odin the latest stock firmware... DOG1 ... If you are not rooted... simply reset to factory and do the same... Odin DOG1. and re-test your Note 4... if problem persist... then you might have a Real Hardware issue.
Click to expand...
Click to collapse
I am not rooted and I have never rooted yet. I was considering it just to test how it was. So that means I have not been able to wipe the Dalvik. Does that get wiped when I Odin? I did indeed tried Odining the DOG1 a few times and still the same results. I am thinking it was hardware but wasn't sure. Do you have a T3? Any problems at all on stock?
It seems its an issue to try to obtain another T3 as now they still have some old regular N910T refurbs back in stock. Plus the IMEI still just populate with "Note 4" and do not differentiate between the two.
Thanks for the reply.
I also got a N910T3 as warranty replacement and had the same issues on non-rooted phone.
Rooted the phone installed custom rom and all those issues gone. Your best best is to root the phone and install custom 5.1.1. ROM
pvsgh said:
I also got a N910T3 as warranty replacement and had the same issues on non-rooted phone.
Rooted the phone installed custom rom and all those issues gone. Your best best is to root the phone and install custom 5.1.1. ROM
Click to expand...
Click to collapse
Ya, I just did that. Flashed Twrp, Rooted, and then Wiped the dalvik and cache.. Seems stock now is running better. Strange.
What rom and kernel are you on? Sucks that this is so different then the N910T.
Anyone else?
Sent from my SM-N910T3 using Tapatalk 2
I have the T3 I'm honestly not experiencing those problems at all. When it was stock. Stock rooted nor cm remix. To me the t3 seems to run smoother than any other the 910t I've had
Sent from my SM-N910T using Tapatalk
I kinda wonder of one of the partitions are messed up. Anyone here familiar with using Odin to erase the band and load the FW back? It could be hardware I guess but if it's just some software glitch I hope I can just figure it out. It's odd that some people experience the same problems and some dont.
Sent from my SM-N910T3 using Tapatalk 2
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
PanchoPlanet said:
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
Click to expand...
Click to collapse
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
jackler1 said:
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
Click to expand...
Click to collapse
Ok, I think I have found it but now I need to know how to fix it. Currently I have as follows in the about device screen:
Model SN-N910T
AHHA ------!!!!! - ANDROID VERSION 5.0
Baseband - N910TU1ANK4
Kernal version - 3.10.0-2796035 [email protected] #1 Thu Nov 13 18:01:07 KST 2014
Build number - KTU84P.N910TUVU1ANK4
So it seems the android version is wrong. Again forgive my stupidity but what exactly IS the android version. Meaning is that the baseband, the modem, what part of the stock rom is flashed wrong and where do I find that part to flash it correctly. I think I am making some progress just need input. Thanks Pp for getting me on track, now I just need a little shove to get this train rolling and maybe learn something in the process. If I fix it I then intend to write a proper write up for those lost souls out there who don't have to spend days....
So why does it say my android version is 5.0 when it should say 4.4.4?
Thank,
Freddy is getting nervous
First verify what version of the note 4 you have, Sm-N910T or Sm-N910T3 and flash proper firmware. Look under your battery.
Once you root you jumble up the phones ability to install firmware properly, and flashing stock firmware once with odin does not always secure components thus leaving you with unofficial status, "custom" and you think you went back to stock with no root but not official yet.
You need to make sure everything flashes and sticks, Model nunber, Android version, Basedand version, Kernel version, Build number.
Any of the modified components can stick and not be overwritten by stock odin flash.
Sometimes multiple flashes, or individual component flashes are required to go back to "official" stock form.
At this point you can verify that your fingerprint scanner works properly and leave it alone or proceed cautiously if root is really required ??? .
I only run stock and save myself all the headaches, I used to root back when Samsung phones where simple and less complicated without kernel security from Samsung.
I suggest latest 5.1.1 lollipop update, kitkat is primitive and outdated, you will be amazed at how well your note will run with latest firmware (with junk apps disabled).
Pp.
Here's a sample of my stock Note 4 running latest update.
Pp.
PanchoPlanet said:
Here's a sample of my stock Note 4 running latest update.
Pp.
Click to expand...
Click to collapse
Nope, I have wiped this phone a million times, reinstalled factory rom over the top of itself a dozen times, installed the baseband and bootloader separately after that and NOTHING changes it still will not work. I have read the complete internet from front to back and it seems nobody knows but the shadow.....Thanks for taking the time for trying to help me out though...
When you say wipe, do you mean factory reset?
Several resets in a row should wipe it clean. Something is stuck, could be the kernel, that will prevent a clean install.
You need to find a way to wipe partitions individually using ADB on the PC, that should allow for a clean install.
Pp.
jackler1 said:
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
Click to expand...
Click to collapse
try doing this...
1st - run chainfire triangle away v3.26
2nd - boot into recovery and wipe everything 3 times except external sdcard.. especially data...
3rd - boot in download mode and ODIN whatever firmware u wanna use... 2 times...
happened to me when the note 4 first came out... I had to exchange to a new note 4...
also whenever u do a nandroid.. U MUST REMOVE ANY SAVED FINGERPRINTS... so u can use that backup again..
if u restore a nandroid with a saved frintprints, it won't work, u must delete data and start fresh..
I don't know if u messed it up by restoring a nandroid from a previous phone and with saved fingerprints stored...
will do thanks for the advice will advise
Nope, nothing I do including stock or otherwise works. When you hit +#0*# it says null and 0.0.0.0 unless someone knows something I don't, it's borked. The thing is even if I used a nandroid and it overwrote my fingerprints where the ones in the nandroid so you would think it would work. Chalk it up to who knows....thanks anyway. Still looking if anyone finds solution....