Korean Note 4 keeps resetting after Lollipop 5.0 upgrade - Galaxy Note 4 Q&A, Help & Troubleshooting

Just did the Note 4 software upgrade and my phone keeps resetting every few minutes ... I did a wipe cache partition and that resolved it temporarily, but now the problem is back again.
It seems to be completely random, but the reboot always puts me back to the exact view I had before the reset (i.e. same browser view, websites that were loaded, etc etc)
Anyone else experiencing this or could suggest a solution? Since I am now based in New York City, I doubt Samsung will service my phone here...
Thanks

Connect to Kies and try to do a "emergency firmware recovery". Hopefully that will help

bimmerboii said:
Connect to Kies and try to do a "emergency firmware recovery". Hopefully that will help
Click to expand...
Click to collapse
Thanks, what does that do exactly?

This will reinstall your firmware. Anything that went wrong with your device software-wise when you updated will get fixed.

Related

Stuck on Samsung Galaxy S5 screen when turning on phone

Hello everyone,
My phone just recently started having this issue, where the screen freezes when it first turns on. If I try plugging it in to charge, it freezes on the battery charging screen; there is no animation that indicates that it is charging. I've tried going into recovery mode but all there is is something that says "MMC: mmc_read fail Movinand Checksum Confirmation Fail". I can, however, go into download mode, where I can install a custom OS. It seems that this screen functions fine and my instinct is telling me that if I want to continue to use my phone, I'll have to reinstall the firmware. I'm not interested in installing a custom OS but I do just want to get my phone back. I did not do anything to my phone, I turned it off for a flight and when I landed, I turned it on and it started freezing when I tried using it. I was able to send out a few texts before it froze and I had to restart the phone but then it just wouldn't get past the Samsung Galaxy S5 screen.
Thank you for your help.
If I understand correctly your phone is not rooted ? Then only a factory reset will help you I think ...
In my experience, a factory reset will fix that, but wipe data also. On S3 and Note 3, I have Odin'ed stock firmwares over stock firmwares before and it has retained the data while fixing the problem. You may want to look into this method.
BCSC said:
In my experience, a factory reset will fix that, but wipe data also. On S3 and Note 3, I have Odin'ed stock firmwares over stock firmwares before and it has retained the data while fixing the problem. You may want to look into this method.
Click to expand...
Click to collapse
I've sort of looked into the Odin method but I'm still slightly confused and a little reluctant do so without clear instructions. Do you know of a particularly good tutorial that could help me with this? I do want to retain some of the data.
Thank you for your help, if this doesn't work, I'll probably just factory reset it.
allsheneedewassome said:
I've sort of looked into the Odin method but I'm still slightly confused and a little reluctant do so without clear instructions. Do you know of a particularly good tutorial that could help me with this? I do want to retain some of the data.
Thank you for your help, if this doesn't work, I'll probably just factory reset it.
Click to expand...
Click to collapse
Its quite simple. Donwload your region firmware from sammobile or from the firmware thread, open odin 3.07 (later versions have issues). Don't change any settings but do make sure "repartition" is NOT checked as this may cause brick. Click on "pda". Select the firmware you just downloaded. Now boot phone into download mode, I believe its vol down home and power pressed altogether. Dismiss the warning and connect your phone. Finally once it says "added" press start. Thats it, good luck!
@non4 said:
Its quite simple. Donwload your region firmware from sammobile or from the firmware thread, open odin 3.07 (later versions have issues). Don't change any settings but do make sure "repartition" is NOT checked as this may cause brick. Click on "pda". Select the firmware you just downloaded. Now boot phone into download mode, I believe its vol down home and power pressed altogether. Dismiss the warning and connect your phone. Finally once it says "added" press start. Thats it, good luck!
Click to expand...
Click to collapse
This is correct.

N9005 OTA Update failed

Hi, I've downloaded the lollipop OTA firmware update several times now and it fails every time and tells me to try using Kies. I'm away from home for an extended time and only have my phone and tablet for the next few weeks so Kies is a no go. I've noticed the firmware upgrade fails on 27% every time and have googled the issue but only found a similar issue with the KitKat update (never had this issue) my phone is stock though I did root and unroot using TR a while back.
Could somebody point me in the right direction as googling leads to many mixed answers and usually from sites that aren't as credible as XDA.
I'm on 4.4.2 currently and baseband is N9005ZHUENJ1 if that helps.
I have same problem too
Plz someone help us
Bump, anyone?
Try clearing the Data and Cache on the two Software Update entries in Settings> Application Manager > All. Do the same for MDMApp, LocalFOTA, Downloads and Download Manager.
Then reboot and try the update again.
I remember having this issue on my S5 with an update, this solved it. (But I don't know which specific one was the culprit.)
Sent From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Thanks for the reply, trying it now.
No luck, had same 27% error again.
Got to a PC and it worked first time via Kies. I suggest anyone else with issues try this.

S4 i337M - No sound on calls (in/out) after flashing Stock 5.01 Loliipop ROM

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.

Oreo update bootloop

Can anyone give me a little guidance:
UK Vodafone supplied S7 Edge, not rooted. Received Oreo update this morning, phone is now stuck in a bootloop - it will get as far as the "Android is starting... optimising applications", that goes away and then it just reboots.
I've been in to the recovery menu and tried wiping the cache partition - to which it reports "could not find /misc partition". Attempting to mount system partition reports the same thing.
Do I have any chance of resurrecting this? the firmware isn't yet on sammobile but I was wondering if updating via ADB or sdcard would help.
Grateful for any help!
install again via odin or directly on the Samsung page. with me it works super well
Can't get the ROM for Oreo as yet. Downloading 7.0 from sammobile and will try flashing that via adb and see if I can resurrect it. Anyone want to guess the chances of this working ?
Crafty77 said:
Can't get the ROM for Oreo as yet. Downloading 7.0 from sammobile and will try flashing that via adb and see if I can resurrect it. Anyone want to guess the chances of this working ?
Click to expand...
Click to collapse
That should work... download de 7.0 and install via Odin with mobile in download mode.
I always wake up my brick mobiles like this.
Have 'updated' my Ş7 with Oreo and now stuck with the boot logo.
Will they f***ing idiots from Samsung ever make a normal software without causing troubles?
My UK Vodafone supplied S7 also is stuck in a bootloop after the Oreo update.
My phone s7 is stuck in bootloop too. Don't know what to do. Nearest Samsung support is 36 miles away.
Its so hot to touch. Pressed all buttons to reset as advised but no luck.
wipe all in recovery or flash firmware through odin ,,
hope this helps.
here is the Oreo factory image for Vodafone https://androidfilehost.com/?fid=890278863836283079
only works with the latest Odin https://odindownloader.com/wp-content/uploads/Odin3_v3.13.1.zip
Galaxy S7 Vodafone here. Bootloop as well...
This update needs to be pulled. There will be thousands of people with the S7 on Vodafone most of whom won't be interested in using Odin to fix a problem caused by Samsung/Vodafone.
Just updated mine and wished I hadn't S7 edge, UK, Vodafone. Won;t leave the bootloop and cant get it to wipe cache or data. Can get it into download mode and shall be trying to reinstall
Updated my S7 Edge Vodafone - bootloop. Tried reinstalling with Odin and same result - still bootloop. This is unbelievable. Is this vodafone forcing this update or Samsung?
Any other ideas as I really don't want to wipe my phone completely? Have tried Odin reinstall twice just in case.
AndyBurmey said:
Updated my S7 Edge Vodafone - bootloop. Tried reinstalling with Odin and same result - still bootloop. This is unbelievable. Is this vodafone forcing this update or Samsung?
Any other ideas as I really don't want to wipe my phone completely? Have tried Odin reinstall twice just in case.
Click to expand...
Click to collapse
I had to wipe my phone.
Is this the only fix so far? Really don't want to do that if I don't have to as my SD encryption key is stored on the phone and I didn't decrypt it before updating...
Lammy696 said:
Is this the only fix so far? Really don't want to do that if I don't have to as my SD encryption key is stored on the phone and I didn't decrypt it before updating...
Click to expand...
Click to collapse
Hey Lammy696,
My mother is on Vodafone UK with the S7 Edge and is experiencing the bootloop. I would advise not to update for the time being.
I would strongly advise decrypting your SD card prior to updating.
I have tried wiping cache etc as per normal update process but that failed. Only options I have is to flash a custom recovery, mount the storage and backup (if I can do this) or to wipe it completely.
If you want to keep your warranty and support, do not use the custom recovery option.
Good luck.
Unfortunately I've already updated and have probably lost all that data now
Is it safe to update now?

No voicemail notifications S10+ no root

Just got the S10+ yesterday. No root and no plan to root at present (it's my husbands phone and he's weird lol)
His voicemail isn't giving him a notification. Nothing on the icon on the home screen and nothing when I open the app. I've cleared cache and data, app is up to date, rebooted phone, searched sprint and searched XDA and can't find an answer.
Anyone have any ideas what I need to do?
Have you tried updating the phone via the OTA updates? You might need to do a factory data reset or flash the latest stock firmware with Odin if all else fails.
StoneyJSG said:
Have you tried updating the phone via the OTA updates? You might need to do a factory data reset or flash the latest stock firmware with Odin if all else fails.
Click to expand...
Click to collapse
I'll double check to see if an OTA was done or not. I was thinking my next step would be to do a factory reset. Weird thing is my note 10+ doesn't have VM either. It's not activated yet so I didn't know if that could be why.
I also tried to download the app from the play store (on my husbands phone) and it would get to downloading 2%, say it was installing then give an error of "this application cannot be installed"
Sounds like you need a factory reset and if that fails reflash the firmware with Odin. I have voicemail on my S10+ here running the AT&T firmware. Some firmware like Version or others might have visual voicemail. I have the icon for it on my phone, but never use it.
StoneyJSG said:
Sounds like you need a factory reset and if that fails reflash the firmware with Odin. I have voicemail on my S10+ here running the AT&T firmware. Some firmware like Version or others might have visual voicemail. I have the icon for it on my phone, but never use it.
Click to expand...
Click to collapse
I have no idea what I did but it just suddenly started working. Thank you so much!

Categories

Resources