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.
how can i fix this and its frustrating phone was working fine and when i update it does nothing but reboot...when i am in safestrap, the "install" tab is not lit to be able to select, so i can not even install a different rom on there....is there a way to fix this
If you are stuck in a bootloop, probably going to have to flash the .246 fxz to get you to stock OTA untouched and then roll from there. I went through this back in ancient days of yore with the DroidX and Froyo, had to fxz(sbf) the phone.
scottyd035ntknow said:
If you are stuck in a bootloop, probably going to have to flash the .246 fxz to get you to stock OTA untouched and then roll from there. I went through this back in ancient days of yore with the DroidX and Froyo, had to fxz(sbf) the phone.
Click to expand...
Click to collapse
It would boot up to the normally then a minute later it will automatically reboot I had flashed .246fxz and still the same issue...I did noticed that the baseband build was "unknown"......so makes me think that something was not flashed or updated right...the reception bar has a red circle with a line thru the center....so I hope somebody understands this and can help me out...
vk4559 said:
It would boot up to the normally then a minute later it will automatically reboot I had flashed .246fxz and still the same issue...I did noticed that the baseband build was "unknown"......so makes me think that something was not flashed or updated right...the reception bar has a red circle with a line thru the center....so I hope somebody understands this and can help me out...
Click to expand...
Click to collapse
Redownload the file from another source and flash it. You also might want to boot into the stock recovery and do a complete factory reset if you haven't already. I also have had to do this on previous phones I've owned when updating.
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Philpro said:
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Click to expand...
Click to collapse
I think you need to find the lollipop kernel. But I'm not 100 percent sure.
try opening kies with your phone connected and look for a menu option to the effect of restore/repair device
sent from my galaxy a5 (SM-G900AZ) on Cricket
I'm not sure if this helps you or not, but I did the same thing, trying to downgrade. I did not take the OTA update when I went from KitKat to Lollipop, instead I flashed one of the Lollipop ROMs, so be wary of that. If you took the OTA update, I don't know if this will work for you.
Anyways, I spent the better half of a day trying different kernels and stock ROMs using the factory recovery etc and nothing was working, each time I would either end up frozen at the Samsung screen or the initial splash screen when you power the phone on. I found this thread here:
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
Under "notes", step 4 I downloaded the file G900A_Downgrade_to_NCE.tar and flashed through Odin. This is the file that got me out of this hole, so maybe it will work for you as well. After flashing, it rebooted and went past the Samsung screen to the initial first time setup screen. Looks like this put me back at stock UNrooted 4.4.2.
Good luck, hope this helps someone else out.
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Its_Tim said:
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Click to expand...
Click to collapse
I flashed through Odin, but yes I was rooted when I went from KK to LP.
I purchased an AT&T sm-g900a that was supposed to come with 4.4.2 according to info on site and sticker on the box indicated it originally had 4.4.2 on it too. I have no way of knowing if someone flashed it with the whole 5.0 file or just updated it. It was sold to me as a new and unlocked phone, and I got a good deal. The phone looks new with an AT&T screen cover attached, packaging, etc. and contents were still in sealed packaging. Will this work? https://www.androidpit.com/how-to-downgrade-galaxy-s5-from-lollipop-to-kitkat ? Is this the same file as the downgrade one referred to? Sammobile only has the 4.4.2 file. There is a significant cost difference in this model and the t-mobile version. Otherwise, I would just return it. I do not like the newer software at all.
I had the same thing happen today with my g870a. I tried 5.0, and 4.4.2 kernels, 4.4.2 firmware (which I knew wasn't corrupt) in Odin but nothing worked. The whole reason was to go redo my Alliance Rom and use FF beside Safestrap (the LP kernal would get rid of the SS). What I ended up doing was going into stock recovery and went to where it says "install update from ext SD". Then I went into my FF backup and found twrp.zip and selected it. It's did some things, said some stuff failed, then booted up enough to get me to FF to get it straight. One problem...my g870a thinks it's a 900, wtf?
Sent from my SAMSUNG-SM-G900A using Tapatalk
Hey fellas,
I recently flashed a new rom and wiped my entire phone. Ever sense then my "touch" has been off about a half inch, it always think I am lower than what my finger actually is. I returned to stock and it was fine, I flash everything over again and the problem comes back. The issue seems to be flashing CF Auto-root 78542, has anybody ran into this issue before?
I found a more up to date (78557) version, I will try that and report.
Nope thats not it either.
Make sure you are using the correct version. Normally this occurs because you flashed the wrong model number.
Sent from my SM-N910T using XDA Free mobile app
Thats what I thought but I don't think so. I am going to double check and maybe re download everything
As far as I can tell, everything is good.. N910T
Hell-Razor said:
Hey fellas,
I recently flashed a new rom and wiped my entire phone. Ever sense then my "touch" has been off about a half inch, it always think I am lower than what my finger actually is. I returned to stock and it was fine, I flash everything over again and the problem comes back. The issue seems to be flashing CF Auto-root 78542, has anybody ran into this issue before?
Click to expand...
Click to collapse
Don't worry, here is the fix for it.
I had the exact same problem a few weeks ago.
Go to the dialer screen and click in:
*#2663# screen fix works perfect, it will display a menu, select re-calibrate
or update or something to that effect, ( I forgot the exact wording)
But when you see that menu screen you will know which one to click.
You might have odin flashed the wrong twrp for the phone, but either
way this will fix it.
I would suggest that before you do this, odin flash the n910t
stock samsung firmware, that way twrp will get over-written.
Good luck,
Have a great day!
Will do. I really want to go back to the fire kat rom but I am tired and dont feel like messing around with things anymore. Just want a WORKING phone lol
Its defenetly CF AUTO ROOT. I tried an older and newer version with nothing, what the hell ive never had this issue.
And the *#2663# isnt working.
Hell-Razor said:
Its defenetly CF AUTO ROOT. I tried an older and newer version with nothing, what the hell ive never had this issue.
And the *#2663# isnt working.
Click to expand...
Click to collapse
We both have the identical phones N910T (I am assuming).
If that's the case perhaps you should try it again, be sure to do a
full wipe first and then odin flash the official stock COG2 firmware
before entering the code.
Be sure NOT to odin flash twrp recovery or cf-autoroot
after odin flashing the firmware, don't flash anything
except the odin flash official COG2 firmware until the
problem is solved.
It has to work because it worked for me and I had the
identical problem as you are having now.
Good luck!.
I am almost done downloading the 5.1.1 official t-mo zip. If this doesnt work I will try that.
Thank you by the way
Sweet it worked. Now I just need to figure out how to root the sob so I dont run into this issue anymore.
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....