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 factory reset my phone because I'm sending it for repairs (screen). I noticed that I lost root and 4G is not connecting. I received a text message so that and calls seem to work. What's going on? I'll try to re-root after I send it and get it back but it's just strange that 4G isn't working. Also, I'm afraid that the MF3 thing downloads, I had updates blocked with titanium back up (forgot what it is that I froze). Another thing, when the phone booted up after the f.reset it gave me this error about com.android.phone not responding. It now appears twice whenever the phone boots up after resetting or turning on.
Thanks in advance
Any clue? Also, I should have said I can't connect to any mobile network, not just 4g.
SRCP said:
I factory reset my phone because I'm sending it for repairs (screen). I noticed that I lost root and 4G is not connecting. I received a text message so that and calls seem to work. What's going on? I'll try to re-root after I send it and get it back but it's just strange that 4G isn't working. Also, I'm afraid that the MF3 thing downloads, I had updates blocked with titanium back up (forgot what it is that I froze). Another thing, when the phone booted up after the f.reset it gave me this error about com.android.phone not responding. It now appears twice whenever the phone boots up after resetting or turning on.
Thanks in advance
Click to expand...
Click to collapse
How did you do the factory reset? If you didn't do it with Odin I would suggest you do that. And then do a factory reset in the stock recovery. Also, you say your sending it in for repair. Are you sending it to Samsung? Because they are going to flash the latest firmware before they send it back so you'll get a device with mk2.
Sent from my Nexus 5
jd1639 said:
How did you do the factory reset? If you didn't do it with Odin I would suggest you do that. And then do a factory reset in the stock recovery. Also, you say your sending it in for repair. Are you sending it to Samsung? Because they are going to flash the latest firmware before they send it back so you'll get a device with mk2.
Sent from my Nexus 5
Click to expand...
Click to collapse
Alright I'll try Odin. It was just a regular factory reset. And no, I'm not sending it to Samsung precisely because of what you mentioned.
Edit: Looks like Odin requires root. Also, I was able to fix the 4G problem by entering the APN information manually. Although I would like not to have to do that.
Maybe it's important that I mention that I did not have any custom Roms installed. Another thing to note is that I still have the old AOSP browser I had installed.
Thank you
SRCP said:
Alright I'll try Odin. It was just a regular factory reset. And no, I'm not sending it to Samsung precisely because of what you mentioned.
Edit: Looks like Odin requires root. Also, I was able to fix the 4G problem by entering the APN information manually. Although I would like not to have to do that.
Maybe it's important that I mention that I did not have any custom Roms installed. Another thing to note is that I still have the old AOSP browser I had installed.
Thank you
Click to expand...
Click to collapse
Odin is a program used on your comp to flash, it doesn't require roots, it's like a clean install.
Almost had a heart attack today. The dreaded update downloaded and I thought I could postpone it indefinitely but it tried to install after I postponed it a few times. It failed, lol. I think my phone's current state won't allow it to install so I'm just going to wait until I get it back from the repair shop to do all the rooting stuff. Thanks for letting me that Odin doesn't require root, I'll do research on it as soon as I get my phone back.
Hi! I am having major issues with my s4 i337 after switching from att to tmobile. The phone was unlocked so I took it upon myself to unlock it. It is unlocked but sometimes or rather most of the time does not pick up the network. When it does have data connection, it is Edge. I flashed the NC1 to root my phone, then reflashed to NJ4 (to unlock) but now nothing works. No wifi, camera fails, no multitasker, no voice assistant. Please help!!!!! I don't know what to do. I should have never unrooted it to unlock. I should have paid the $35 to get an unlock code. Can I fix this?
I have tried multiple APN settings,
Tried reflashing what I found online as att official firmware but it fails on ODIN.
So reflashed to NJ4, it is a bit laggy as well. Tried wifi which is greyed out, Camera still shows failed, pressing the home button to open multitasker and voice assistant brings up a blank grey screen. Phone is no longer connected as a mass storage device, only charges and can connect to ODIN.
I have attempted to factory reset which doesn't go through, unroot through SU which gets stuck on uninstalling and even trying to do an emergency recovery on Kies where it fails and gets stuck on kies failure mode.
I am on 4.4.4
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No I have not tried that one! Should I try it and which version should I use since I am rooted?
jd1639 said:
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I guess I was following outdated information for rooting. =[ Which was dated 2013.... Should have sensed something was wrong.
I flashed this and it worked perfectly as you suggested! THANK YOU SO MUCH. No more sleepless nights combing through forums, thanks to you! Everything works and is back to normal, I was about to just throw away this phone thinking I permanently broke it. AGAIN MANY THANKS! I'm scared to root it now.
Although I have one more question, if you could please answer.
After booting and everything working, in the notification, it says unauthorized access and to restart to reset changes made, if I dismiss it, will this fix be permanent and not revert to the unworkable state it was in? When I reboot manually?
vannicuhh said:
No I have not tried that one! Should I try it and which version should I use since I am rooted?
Click to expand...
Click to collapse
It doesn't really matter since you can root the device in either case. The rootable nb1 can be directly rooted. The other one, you'll have to update to nc1 to root. Flashing with odin, you will lose and will have to re-root. Also, see "Index All things AT&T...." by Gutt13 in the General Forum
vannicuhh said:
Hi! I am having major issues with my s4 i337 after switching from att to tmobile. The phone was unlocked so I took it upon myself to unlock it. It is unlocked but sometimes or rather most of the time does not pick up the network. When it does have data connection, it is Edge. I flashed the NC1 to root my phone, then reflashed to NJ4 (to unlock) but now nothing works. No wifi, camera fails, no multitasker, no voice assistant. Please help!!!!! I don't know what to do. I should have never unrooted it to unlock. I should have paid the $35 to get an unlock code. Can I fix this?
I have tried multiple APN settings,
Tried reflashing what I found online as att official firmware but it fails on ODIN.
So reflashed to NJ4, it is a bit laggy as well. Tried wifi which is greyed out, Camera still shows failed, pressing the home button to open multitasker and voice assistant brings up a blank grey screen. Phone is no longer connected as a mass storage device, only charges and can connect to ODIN.
I have attempted to factory reset which doesn't go through, unroot through SU which gets stuck on uninstalling and even trying to do an emergency recovery on Kies where it fails and gets stuck on kies failure mode.
I am on 4.4.4
Click to expand...
Click to collapse
ODINing to NB1 should definitely help, but as far as mobile data if it still isn't working I thought i read somewhere that T-Mobile needs the AWS bands or something and you'll have to follow the process to enable those. There's a thread somewhere in the General section to do it on 4.4
Flashed stock 5.01 ROM and phone call function stopped working.
When calling, there is a connection but no sound can be heard on either end of call.
It WAS working briefly and briefly managed to 'fix' it. Everything else functions correctly. Wifi calling works perfect. SMS works perfect.
I have searched forums and Googled this (about 9 hours worth so today) so quite at a loss how to proceed.
Tried forums suggestions to:
- disable Google Now/OK Google voice functions
- disable S Voice functions
- removing and replacing SIM/SD card
- wiping cache
- air dusting earphone port
- clear Google Play services cache and data
- clear Drive cache
- boot into Safe Mode, still not working
Additionally tried re-wipe cache/DALVIK/data/entire device and re-installed different stock ROM, same problem
I flashed both BELL and Rogers stock Lollipop ROM from XDA post (http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758) via Odin
Any suggestions???
The only thing that worked briefly was:
In App Info for the Phone App, I did 'clear data' and 'clear cache' for all THREE Phone Apps (yes, there are three, I don't know if this is normal or not as this is first time with Lollipop). This allowed the phone to work BRIEFLY, then problem returned.
Try flashing the latest stock from sammobile.com.
Hi,
Attempting this but both Bell and Rogers Lollipop firmware .ZIP are corrupt from Sammobile.com I've contacted their admin to advise of this as I have tried downloading multiple times with the same corrupt file result.
Are there any other reputable download site?
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse
Anything to be concerned about reverting via TWRP to Kitkat
Tried Emergency Firmware recovery via KIES, no luck, re-wiped cache, did factory reset in stock recovery, still no good.
Tried swapping Sim card tray and Earphone port (had a parts phone kicking around that is stuck on boot logo ((TWRP/ODIN Flashing does not recover this phone sadly)))
Will try to revert to Kitkat via TWRP next.
Note: I AM able to make normal calls as long the device is connected via Bluetooth to my car or to my bluetooth headset. Discovered this after more googling/forum searching.
rogue_element said:
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
Click to expand...
Click to collapse
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Hi,
I'm using Win7 x64 Home Premium. WinRAR to unzip.
Since posting last I have restored Nandroid backup - phone function still didn't work and Google Play Services glitched out.
So, next downloaded 4.4.2 Kitkat from Sammobile, extracted no problem, flashed via Odin (no errors)- still no phone function
Wiped phone yet again, re-installed Kitkat one more time with Odia (no errors) - still no phone function
Used Kies to do Firmware Update and Initialization, (no errors) - still no phone function
Re-wiped again and used Kies once more, this time not doing App Restore function in case there is App causing issues and not signing into Google or Samsung Account to avoid anything restoring - still not working but interestingly there was a OTA update to 5.01 that installed fine - end result... phone function still not working.
If anybody can offer me another suggestion to try, I'll be happy to attempt but at this point I'm prepared to say f**k it and buy another phone.
I've been at this since last Saturday.
audit13 said:
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Click to expand...
Click to collapse
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Yes, I've attached a screenshot. Bootloader and baseband do match. This last round of install was done via OTA update that popped up after installing Kitkat. I just rolled with it as I figured if it's coming from Samsung directly, why not.
When making calls via Bluetooth, there are no issues. It functions as normal. It is just through the Phone App itself.
Interestingly, I discovered I can make outbound call no problem via Google Hangouts dialer as well. This is incredibly frustrating.
audit13 said:
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Click to expand...
Click to collapse
Did you try reflashing the OH1 ROM? Sounds redundant but I'm not sure what else to suggest short of putting the motherboard into another phone and trying it out.
Hi audit13,
Haven't tried installing mobo in another phone, will give that a whirl for sh*ts''grinz.
Been an incredibly frustrating process. Another interesting thing that has been happening is that I notice the boot up sequence takes a lot longer than I recall.
Have been trying to avoid using the phone.
Re-flashed OH1 using ODIN and earlier tonight, Kies. Still not working.
I'm wondering if doing something like reverting to very old ROM may do the trick instead.
Do you happen to know how old I can go? Jellybean? I will check sammobile and see what the oldest they have there.
Phone functions perfectly fine via Bluetooth still, IP calls via WhatsApp and Hangouts Dialer also work per normal. Just trying to place normal calls does not work.
Have also had bootloops lately too I notice.
You can go as far back as 4.4.2 from my experience.
You'r performing a factory wipe right after flashing in Odin?
Initial boot up after flashing and wiping usually takes a long time but it should become quicker as the cache builds up with each reboot.
@rogue_element have you found a solution?
My wife's phone is having the exact same problem.
It started happening like a couple months ago. Haven't flashed anything to it. It just suddenly happened.
Hi ImpheOtus,
No, I'm still searching for a solution. I tried reflashing and then factory reset per audit13 suggestions but still no luck. I even tried swapping the ear piece module from a parts phone and no go. Extremely frustrating. Shopping for a new phone at this point but I'm still trying for a resolution as I'm stubborn and don't like giving up.
Hi audit13,
I'm actually suspecting the something else at this point (virus/malware, etc.) in the bootloader or deeper. There has been other random odd behavior, and while I don't rule out something like a hardware problem either, the behavior has been very strange.
Perversely, my wife's phone briefly experienced the same issue as mine but it cleared up after a reboot.
I will go hunting for a tut on flashing bootloader and kernel only next to see if that helps. If you have any suggestions of where to look for tutorial and/or files please feel free.
I tried flashing 4.4.2 but no luck there either btw
Okay, try flashing with a pit file and the latest stock rom from sammobile.
audit13 said:
Okay, try flashing with a pit file and the latest stock rom from sammobile.
Click to expand...
Click to collapse
Any particular suggestions regarding locating/selecting a pit file?
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
audit13 said:
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
Click to expand...
Click to collapse
Its a Bell SGH-I337M 16gb phone
I attached a 16 GB pit file from my i337m.
Hello, my SM-G935A is rooted, and I have 2 issues with it. Firstly, I'm unable to receive texts or phone calls (I can send them), and I've tried a factory reset and I even got a new SIM, but nothing worked. I think if I flash stock firmware, it might fix the issue. Second problem, when I go into download mode and select my AP in Odin and press start, my phone gets an error and Odin freezes at Initialization.
Any help would be appreciated. I would prefer to fix the texting issue, as I don't want to return the phone to ATT. In either case, the Odin issue needs to be fixed
I'm having a similar issue. This afternoon, 2 apps threw errors and closed. I rebooted, which apparently was the wrong thing to do. The reboot stalled on the AT&T logo and stayed that way for 5 min - the unit became very hot & the power button did not respond, even while holding it down. I got into recovery, cleared the cache and factory reset, then rebooted. The unit came back up and started reinstalling everything. I took it back down into the download status and attempted to reload 935x via Odin, only to stall at "initialzation" [sic] as you did. I got out of that after waiting for some sort of response. SuperSU was still in my apps as was Root Checker. Root Checker indicates the system is rooted. SuperSU indicates it needs the binary updated. BusyBox and TiBu indicate they cannot find root. I deleted all the root apps and tried reinstalling root via adb which completed successfully, but the same outcome with all the root apps. So I'm not sure if I'm still really rooted as Root Checker claims, or not.
EDIT: I just saw that I have 2 "Knox Settings" apps. Clicking on either returns, "Unfortunately, Container Agent2 has stopped."
use the odin from the stock firmware thread to flash it again. if it fails you can flash the u firmware and then the stock again. then you have to use a different odin if you want to flash the root api file the one you flash the firmware with wont work. also there is help in one of the threads about fixing the volte problem so you dont have to turn it off to get calls. i didnt have to do it as using the odin i mentioned fixed it for me when i came from the u firmware.
NovaEDM™ said:
Hello, my SM-G935A is rooted, and I have 2 issues with it. Firstly, I'm unable to receive texts or phone calls (I can send them), and I've tried a factory reset and I even got a new SIM, but nothing worked. I think if I flash stock firmware, it might fix the issue. Second problem, when I go into download mode and select my AP in Odin and press start, my phone gets an error and Odin freezes at Initialization.
Any help would be appreciated. I would prefer to fix the texting issue, as I don't want to return the phone to ATT. In either case, the Odin issue needs to be fixed
Click to expand...
Click to collapse
I was having the exact same problem you had with Odin. It seemed I was able to flash stock firmware using this version of Odin: http://www.mediafire.com/download/2t2sjqxtogbkafk/odin_3.12.3.rar
rob219 said:
use the odin from the stock firmware thread to flash it again. if it fails you can flash the u firmware and then the stock again. then you have to use a different odin if you want to flash the root api file the one you flash the firmware with wont work. also there is help in one of the threads about fixing the volte problem so you dont have to turn it off to get calls. i didnt have to do it as using the odin i mentioned fixed it for me when i came from the u firmware.
Click to expand...
Click to collapse
did you have any problems with the u version of the s7 edge firmware, like the fingerprint scanner not responding? i am on that version and cant get any odin version or any version of s7 edge g935a firmware to flash, tried unrooting and was forced to use the U version of the s7 edge firmware, everything works except the fingerprint scanner, cant get back to full stock firmware, need help!
im having the exact same problem, when i put my phone into download mode and flash the stock at&t firmware, Odin get stuck in "initialization" and my phone screen displays and error message.
Same stuff was happening to me, I went back to stock and took the update. When your phone stops working as an actual phone, it's time to roll it back.
I played with it for a week and my phone was so freaking hot (with hot weather) equals a wait and see if this gets more stable in the near future. I did use the Odin 3.12.3 mentioned by King James III. Honestly, I did so many things to get it back to stock I forget what actually worked (it was the wee hours of the morning and I was spent). Don't give up guys, it will and can work.
edit: It may be as simple as not right clicking Odin and running it as Administrator.
nicetucu said:
Same stuff was happening to me, I went back to stock and took the update. When your phone stops working as an actual phone, it's time to roll it back.
I played with it for a week and my phone was so freaking hot (with hot weather) equals a wait and see if this gets more stable in the near future. I did use the Odin 3.12.3 mentioned by King James III. Honestly, I did so many things to get it back to stock I forget what actually worked (it was the wee hours of the morning and I was spent). Don't give up guys, it will and can work.
edit: It may be as simple as not right clicking Odin and running it as Administrator.
Click to expand...
Click to collapse
I used Odin_v3.12.3_Patched_SHA256 to flash the 935U Firmware then used Odin3_v3.11.2 to flash the June Firmware release.