Just wanted to know if someone can help with my situation.
Had a completely stock phone and revived the OTA update for 7.0, unfortunately this broke my fingerprint scanner, took my phone to Samsung today and they re-flashed the firmware but still no good! They have ordered a screen and fingerprint sensor in but wont be back till Saturday.
They had to re-flash my phone twice as the first time they stuck on a lock three version even though mine was brought unlocked so they had to flash it again back to that.
Unfortunately i am now not receiving the OTA update it also does not show on Smart Switch. Is everything okay, do I have to just wait or have they messed up?
My Knox counter is still 0x0 and device says official... if I flash the update using Odin will this trip the Knox counter as I still need the fingerprint sensor changing...
Hope someone can help!
I would start with wiping all the data/system via recovery then flashing new 7.0 rom downloaded from sammobile.
Sent from my SM-G935F using Tapatalk
dollar7 said:
I would start with wiping all the data/system via recovery then flashing new 7.0 rom downloaded from sammobile.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Just flash and back on 7.0 and still 0x0! Thanks!
Related
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
mygadgetgeek.com said:
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
Click to expand...
Click to collapse
not yet, but i have a lot of data now on my phone. will try that though. in case that doesn't work, any other advice?
cptnappy said:
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Click to expand...
Click to collapse
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
radicalisto said:
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
Click to expand...
Click to collapse
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
Ah Ok, if it says Official it should be good to go. Seems like maybe the download has gotten corrupt due to an intermittent internet connection.
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
OK, then maybe you should learn a few things before trying to update - Knox is a security system in latest Samsung phones that is supposed to be triggered/set when you root (or install any custom kernel/recovery). Your initial (old) firmware could still let you root without triggering the Knox flag, and then you can update to the latest firmware for your region using Mobile Odin Pro and still keep your root AND without triggering the Knox flag. However once you update using Samsung OTA / Odin / Kies to a firmware more recent than MJ3 you can no longer root without also triggering your Knox warrany flag - read more about this in the Universal Root De La Vega thread!
i gave up after several tries, since i'm on 4.3 i think that would do for now. maybe it's just downloading a stability update or something? everytime i do an OTA update, it tells me that the download of the new firmware is complete then reboot. when i get to 32% the droid falls flat on its back and shows the red triangle on its chest, over and over. i don't lose my phone data or anything. just won't update. i'll wait for 4.4 Kitkat instead. hope i'll be able to update to that when it comes out.
EDIT: i tried going into recovery mode, wiping cache, and factory reset.. still no dice. maybe Odin's the only way i guess. problem is my internet connection lol
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Sent3 said:
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Click to expand...
Click to collapse
i managed to update mine using Samsung Kies3 (not Kies, but Kies3). Hope updating OTA is fixed in the future with the update i just did
I had my S5 rooted a few months ago, but then the update came out that was supposed to fix the bluetooth (last July), and my phone automatically downloaded and tried to install it. My phone was still rooted, so the updated failed. However, my root also failed as well. I could no longer access root applications like Titanium Backup, and towel root told me that it was unable to root my phone. Basically, my phone became frozen in time and was unable to update or do root-level things since this update last July. Now that Lollipop is out, I really want to upgrade, but factory resets do not solve my problem and I do not know of any more permanent way to get my phone back to basics so thatr I can receive OTA updates and have them actually work. Any help is greatly appreciated, as I really do want to upgrade my phone.
Start by downloading your firmware from sammobile, then flash it with Odin......
You'll then be fully unrooted and should be able to receive OTAs......
BTW.....Some people on here say that if knox has been tripped, that can affect OTA too.......
If that is the case, simply download the lollipop firmware from sammobile and Odin flash that instead......no need to OTA upgrade then...
Sent from my rooted kn0x0 SM-G900F S5
keithross39 said:
Start by downloading your firmware from sammobile, then flash it with Odin......
You'll then be fully unrooted and should be able to receive OTAs......
BTW.....Some people on here say that if knox has been tripped, that can affect OTA too.......
If that is the case, simply download the lollipop firmware from sammobile and Odin flash that instead......no need to OTA upgrade then...
Sent from my rooted kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Thank you for this advice. I used to flash stuff from my computer with my old phone, but haven't done so in years and didn't know which program to use. I was unsure if it worked at first, because my phone was the exact same after running Odin and I was expecting a factory reset, but I downloaded and ran the 4.4.4 update and it worked! Again, thanks so much for the help. I didn't really mind hitting "skip download until tomorrow" every day, but I wanted to upgrade to Lollipop.
Glad you got it sorted fella.......If it turns out that lollipop isn't all you'd hoped for, you can use odin to downgrade back to KitKat..........
.....but I think you have to remember to factory reset after the flash, otherwise you'll get bootloops and stuff......
Sent from my rooted kn0x0 SM-G900F S5
Hi there! Recently I updated my phone after using KitKat for quite a while as I grew a bit bored of KitKat and thought Lollipop would do some good. Previously, I had KitKat then went to Lollipop but I didn't like Lollipop so I flashed to KitKat. Then, after some time I am where I am now, stuck on Lollipop. So I am trying to revert back to KitKat again, but on my computer after I load KitKat into Odin and press start, the console log gets stuck on aboot.mbn. Everything works fine until that point, which it then just sits there. My phone also displays a loading bar on the download mode, but sits at the very beginning. Something is wrong here. I would really appreciate any help.
Somethings you may need to know:
- Yes I have successfully gone back to KitKat before on the same phone.
- I have the correct Verizon Retail KitKat Software
- I have Odin 3.0.9
- I am running 5.0.1
- I have done a factory reset and cleared cache partition as well, but nothing seems to work.
Thanks, I look forward to your feedback!
Did you update OTA or flash the safe 5.0.1 update using odin? If you took the OTA upgrades then you are stuck, you will NOT be able to flash that phone again.
Sent from my Galaxy Note 4 using Tapatalk
outcasted2003 said:
Did you update OTA or flash the safe 5.0.1 update using odin? If you took the OTA upgrades then you are stuck, you will NOT be able to flash that phone again.
Sent from my Galaxy Note 4 using Tapatalk
Click to expand...
Click to collapse
I did download a security update after the initial 5.0.1 update, so I'm guessing that's what's doing it? Right after I posted my thread I saw the warning in this forum area, so I think that may be the case. I guess oh well, think there maybe a solution in the future for KitKat? Lollipop isn't too bad after a reset but I would prefer KitKat over time.
Well i rooted my note4 an everything went well but then out of the blue i cant play back any video when ever i try it instantly reboots does any one know what could be the problem......i unrooted phone an flashed back original firmware plus factory reset .....
Sm-n910 said:
Well i rooted my note4 an everything went well but then out of the blue i cant play back any video when ever i try it instantly reboots does any one know what could be the problem......i unrooted phone an flashed back original firmware plus factory reset .....
Click to expand...
Click to collapse
Did you reinstall the stock firmware via ODIN? Did you download the last firmware via SAMMOBILE?
Seems like you might have flashed the wrong firmware mate
Sent from my SM-N910T3 using Tapatalk
Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
That's very unusual to trip knox via Odin, was second hand phone?
Maybe try flashing 6.0.1 firmware and hold off updating until 7.0 is sorted.
It was an upgrade on my contract in October so it was brand new.
I'll try to flash 6.0.1 again and see if I have any more luck with it.
I'm tempted to go back to the store and ask for a replacement but I know they'll question the warranty void counter. I'm just so confused as to why it's tripped it.
Sent from my SM-J320FN using Tapatalk
Perhaps is a bad flash reverting back to MM should fix issue but certainly not knox counter.
I'm also awaiting long overdue nougat update and was going to flash via Odin until I read your post. Slightly nerves now wonder if anyone else has had the same issue of tripping knox.
I've just updated via odin and no knox trip, void counter remains the same.
I reverted back to 6.0.1 and the issue still happened which is making me wonder whether or not it's a hardware issue.
I'm going to download a ROM (probably superman rom) and try flashing that through TWRP and see if that fixes it. I won't be able to do it until I'm home tonight but I will get back and update you on how I get on.
I'm glad you successfully flashed 7.0 without any issues, hopefully I'm the only one who has this problem.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
I reverted back to 6.0.1 and the issue still happened which is making me wonder whether or not it's a hardware issue.
I'm going to download a ROM (probably superman rom) and try flashing that through TWRP and see if that fixes it. I won't be able to do it until I'm home tonight but I will get back and update you on how I get on.
I'm glad you successfully flashed 7.0 without any issues, hopefully I'm the only one who has this problem.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
If the problem occurs on the official ROM, flashing custom one won't help at all. I would recommend you flashing again nougat after wiping all data, system, cache via recovery mode
Sent from my SM-G935F using Tapatalk
dollar7 said:
If the problem occurs on the official ROM, flashing custom one won't help at all. I would recommend you flashing again nougat after wiping all data, system, cache via recovery mode
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I'll give this a go tonight and see how I get on.
I find it very odd that both 7.0 and 6.0.1 gave the same restarting issues which is why I'm worried it's a hardware issue and not software.
I do have the TWRP file so could flash that, do a dalvik and normal cache wipe too after installing nougat again.
Sent from my SM-J320FN using Tapatalk
So I installed 7.0 again and it is still crashing and becoming a completely unresponsive phone with a black screen. Again, left it over night and plugged in this morning to charge and it's on again. I have absolutely no idea what to do to fix this issue.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Hey buddy it might be because of wrong varient rom flashed so knox may be tripped
Try downlaoding and flashing the original variant and original country rom from samfirmware.com and it might actually do the trick
As for your battery problems, it might be a charger or port problem based on maybe if the cord might be streched more than required accidently or maybe the charger has encountered a fault or power surge so its circuit might have failed to safeguard your phone from over surge of current and over heating.....try using original but substitute charger of someone else
SHREYSTARK said:
Hey buddy it might be because of wrong varient rom flashed so knox may be tripped
Try downlaoding and flashing the original variant and original country rom from samfirmware.com and it might actually do the trick
As for your battery problems, it might be a charger or port problem based on maybe if the cord might be streched more than required accidently or maybe the charger has encountered a fault or power surge so its circuit might have failed to safeguard your phone from over surge of current and over heating.....try using original but substitute charger of someone else
Click to expand...
Click to collapse
Hey mate. Unfortunately I've definitely got the right variants for UK Vodafone, I did use sammobile so I'll give samfirmware a go and see if that fixes it.
The charging thing is an odd one, once the phone boots and is used for 10 or so minutes it will crash, the screen will go black and no matter what trying to reboot, go into recovery or download mode, nothing responds. The only way I've found to get it responding again is if I leave it overnight and plug it in to charge the next day, then it'll start charging and I've tried both mine and my partners cables in both plugs.
I might just take it back to carphone warehouse and tell them whatever has happened during the update has tripped knox and completely ruined my phone, it's only 3 months old to ? they must have a way of finding out if I'd tried to root because if they did, they'd see I've never tried it.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
Hey mate. Unfortunately I've definitely got the right variants for UK Vodafone, I did use sammobile so I'll give samfirmware a go and see if that fixes it.
The charging thing is an odd one, once the phone boots and is used for 10 or so minutes it will crash, the screen will go black and no matter what trying to reboot, go into recovery or download mode, nothing responds. The only way I've found to get it responding again is if I leave it overnight and plug it in to charge the next day, then it'll start charging and I've tried both mine and my partners cables in both plugs.
I might just take it back to carphone warehouse and tell them whatever has happened during the update has tripped knox and completely ruined my phone, it's only 3 months old to they must have a way of finding out if I'd tried to root because if they did, they'd see I've never tried it.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Return it. If Stock ROM doesn't fix a problem, the phone is good night
Galactus said:
Return it. If Stock ROM doesn't fix a problem, the phone is good night
Click to expand...
Click to collapse
Since installing Superstock Rom, the phone has, so far, been completely crash free and no random reboots when trying to do something simple like uninstall an app. Fingers crossed it stays this way!
Sent from my SM-G935F using Tapatalk
Search 1st b4 post!
LukeC981 said:
Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
There's already a thread about this!
Nougat known bugs thread *Updated*