Related
I just installed PSX for my galaxy and installed the all roms app...(forgot name) but i was downloading a game and then i left my phone alone to let it download.
10 minutes later my phone wouldn't go onto the lockscreen aka froze. so i decided to take the battery out...(mind you the download wasnt finished) and now when i boot up the phone it just goes the the "S" logo and either turns off...or freezes.
note* I can access ADB through 3 button reset.
However i do not want to wipe data. as i have important pictures on my internal sd and videos. i was thinking of using the "wiping cache option" cause my theory was that the frozen app was still in memory or something....can anyone give me suggestions to fix this issue?...try to avoid "wipe data option"
thanks.
edit** have got into download mode and tried to use ODIN but odin doesnt see my phone....however kies does. but kies cant connect to it. keep saying connecting to device....any helP??
flashing a rom doesn't delete your pictures I think
just contacts, sms, apps etc
but it is better if someone else also verifies it
edit: oh sorry I just saw you wrote cache... i am not sure what that does. I don;t think it deletes your data.
allotrios said:
flashing a rom doesn't delete your pictures I think
just contacts, sms, apps etc
but it is better if someone else also verifies it
edit: oh sorry I just saw you wrote cache... i am not sure what that does. I don;t think it deletes your data.
Click to expand...
Click to collapse
i am waiting for someone to clarify that i can "wipe cache". By the way, i do also require my SMS messages, there is some delicate information within them. i am currently googling wipe cache. any other help is greatly appreciated. thanks for the quicky reply allotrios
just wiped cache. phone still wont boot to main homescreen it freezes, and/or shuts off. last resort is wipe data. anyone offer a suggestion other than that?
WTH? i just wiped date/factory reset and hit reboot and it STILL doesnt load. it goes to the "S" symbol and shuts off or freezes.
edit* trying to find firmware for i9000M canada version. Attempting to use odin but cant find links
just got pit file! where can i get the pda phone and csc files? what else do i need to flash it using odin? im constantly googling and trying to do this before i sleep
edit** just tried to use odin with a different firmware with all correct files. when pluggin in usb cable in download mode, Odin doesnt see my phone.
kies sees the device but keep saying "connecting to device"
welcome to my world........flashes fine, wiped data/cache, still freezes at the 's'. i just sent my phone in after i couldn't get it going after flashing 40 times.
it would seem your sdcard is corrupted or fried.........try flashing some more roms (jg9 or jh2) with different pits (512 and 803) and wipe data/cache. samfirmware.com for the roms.
as well, if you do not have the 3br fix to get into download mode (since you said you get into download mode via adb), i would suggest you flash the fix asap before you lose the ability to use adb.
wang1chung said:
welcome to my world........flashes fine, wiped data/cache, still freezes at the 's'. i just sent my phone in after i couldn't get it going after flashing 40 times.
it would seem your sdcard is corrupted or fried.........try flashing some more roms (jg9 or jh2) with different pits (512 and 803) and wipe data/cache. samfirmware.com for the roms.
as well, if you do not have the 3br fix to get into download mode (since you said you get into download mode via adb), i would suggest you flash the fix asap before you lose the ability to use adb.
Click to expand...
Click to collapse
ive been sitting here for 3 hours...have a exam tommorow and am fed up. Problem is i bought this phone from a friend, so warrranty is out of the option.
The other problem WHICH can be solved somehow...is that my computer sees my phone. (kies does..but wont connect)..i can "technically" use odin if i can somehow get my phone to work with it.
If the case that my internal sd card is fried....i dont have warranty, do i have manufacturer warranty?. aka samsung?. i dont know just a thought.
can you get into download mode? i assume no as i had the same issue, and adb wouldn't work unless the phone had fully booted up. odin will only recognize your phone in download mode.
the only options you have are:
make a jig with 301k resistor to get your phone into download mode and try flashing
send your phone out to be repaired (some other thread mentioned repair shop in ontario)
go into bell and see if they will take your phone in for repair (samsung 1yr warranty)
wang1chung said:
can you get into download mode? i assume no as i had the same issue, and adb wouldn't work unless the phone had fully booted up. odin will only recognize your phone in download mode.
the only options you have are:
make a jig with 301k resistor to get your phone into download mode and try flashing
send your phone out to be repaired (some other thread mentioned repair shop in ontario)
go into bell and see if they will take your phone in for repair (samsung 1yr warranty)
Click to expand...
Click to collapse
i CAN get into DOWNLOAD MODE. but problem is ODIN doesnt see my phone
edit* could you give me a link to that store?
ah, ok...........i had the same problem, but after i installed the drivers for it, no more problems.
you should try that before you send your phone in.
edit: found the link
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
If you're phone can get into download mode then it should work. However, Odin is somewhat temperamental, have you tried Heimdall?
Benjamin Dobell said:
If you're phone can get into download mode then it should work. However, Odin is somewhat temperamental, have you tried Heimdall?
Click to expand...
Click to collapse
i have just woken up. my phone is now dead, i cant turn it on. i have tried connecting the charger and it wont charge my phone......anyone have any ideas? is it bricked? internal SD card fail?......i dont have Bell warranty, would samsung canada cover this issue? as internal sd cards area known to fail?......thanks.
edit** never mind, it is now charging. i will keep this thread updated when i finish my exam today and let everyone know where my phone stands. So far i think it is a internal sd card error. But i am hoping after a full charge it may work again.
hmm still same thing, i load to "S" screen and it shuts off, i can still access 3 button recovery and download mode. i just called samsung too, they said to call my service provider, but problem is i bought the phone second-hand.
Have just flashed JH2 firmware and JG5 firmware on phone with ODIN, phone still boots up to "S" logo and then shuts off .
edit** only JH2 firmware will go through to my phone on ODIN, i have tried a 2nd time, it goes to the S logo....looks like it will load to phone, and then just doesnt and shuts off.
So is it safe to say the phone is bricked?.....i have heard of someone in this forum saying there was a unofficial samsung store somewhere in Ontario that fixes galaxy phones?....anyone can link me to this?. I don't have warranty as i bought it 2nd hand. hmm..now idont know what to do, besides, i guess, save up and buy a new phone.
edit** it cant be bricked if i can still access recovery and download mode? right.
Phone is OFFICIALLY bricked, tried flashing a 803 pit file, now it wont power on, or charge through wall charger. thanks to all who helped in little ways. but looks like ill have to buy a new phone.
jark99 said:
edit** it cant be bricked if i can still access recovery and download mode? right.
Click to expand...
Click to collapse
that would normally be true........with one exemption to the rule.......if your sdcard is corrupted/fried.
if you have flashed back to 2.1 with repartition and wiping multiple times with different PITS, and still the same issue, then nothing will help (at the moment) aside from sending it in.
I Had this exact same issue a week ago. My guess is that your internal SD is dead and you will need to send it out for repairs. Im still waiting for mine from bell to see if they only reflashed or replaced the whole motherboard.
Light
Problem is i dont have Bell warranty....so i am kinda a goner. unless someone has a suggestion?
Just because you don't have warranty doesn't mean you can't pay to get it repaired (at least get it inspected and a quote). Should be much cheaper than saving up for a new one!
If you bought it from your friend, they should be able to send it on your behalf.
Sorry to hear about your issues :/
JimiJam said:
Just because you don't have warranty doesn't mean you can't pay to get it repaired (at least get it inspected and a quote). Should be much cheaper than saving up for a new one!
If you bought it from your friend, they should be able to send it on your behalf.
Sorry to hear about your issues :/
Click to expand...
Click to collapse
In Ontario, the only way to get our phone repaired is through Bell sending it to a service center, Problem is my friend doesnt have the receipt. He bought it from a friend. Its past through 3 hands to get to me. Friend's Friend > My Friend > ME.
So...i am currently looking at cell repair shops to see if they can fix this problem....BUT i am assuming alot of them use Odin or some sort of flashing, WHICH i have already done .....
I also called 5 bell stores to see if i could get the receipt printed out using the IMEI code, all of them said this information cannot be provided due to "privacy issues." They told me to call Samsung or talk to a 3rd party cell repair center.....fml.
Since I got the Samsung Galaxy S 2 it kept rebooting itself every once in a while.
This seemed to happen only after doing something.
For example:
After opening an app.
It even happened once when I got a phone call.
I've reformatted the device the 2nd day I got it (for another reason) and it still happens.
Does this happen to anyone else?
What can I do?
What is the your device?
Sent from my GT-P1000 using XDA App
Galaxy S 2.... Thought it was pretty obvious since I posted in the GS2 thread
I'll update it though
If it still happens after the update I'd return it. Mine have been rock steady since day one, had it for 10 days now.
Sent from my GT-I9100 using XDA Premium App
matanc1 said:
Galaxy S 2.... Thought it was pretty obvious since I posted in the GS2 thread
I'll update it though
Click to expand...
Click to collapse
Not always .
But i would install latest firmware first .
Either via official Kies update or unofficial Odin method .
Or return it to seller .
http://forum.xda-developers.com/showthread.php?t=1075278
jje
I had random rebooting after moving apps to SD. Dolphin HD seemed to be the main offender.
I moved all the apps back to phone and then, just for good measure, formatted my internal storage & SD card (after backing them up). All seems happy again now.
maddoguk said:
formatted my internal storage & SD card (after backing them up).
Click to expand...
Click to collapse
Do this and then a hard reset. If it's still rebooting exchange the phone.
No, I didn't need to hard reset but it is worth a try. Mine has now settled down again.
What version of the software are you on? If you still get problems then get it exchanged.
I'm on the 2.3.3 version Kernel 2.6.35.7.
When I go to Setting> About> Software update it says that there are none.
What do you mean by hard reset?
In the Settings> Privacy there is a Factory Data Reset option. Is that what you mean?
matanc1 said:
I'm on the 2.3.3 version Kernel 2.6.35.7.
Build number is required for firmware version .
What do you mean by hard reset?
In the Settings> Privacy there is a Factory Data Reset option. Is that what you mean
Yes wipes all data so back up
jje
Click to expand...
Click to collapse
The build number is
Gingerbread.XWKDC
Also, in the Kies software it says that this version of the device cannot be upgraded. Why is that?
So should I reformatt the device again? How can I back everything up including my contacts and the way I synced them with facebook etc? Can I also back up widgets?
Edit: When I try to use the Backup option in Kies, it keeps showing 0% and doesn't change.
What can I do?
Also, in the Kies software it says that this version of the device cannot be upgraded. Why is that?
Because their is no update supplied by the phone supplier to Kies .
XWKDC old firmware .
How can I back everything up including my contacts and the way I synced them with facebook etc?
KIES or and back up contacts to Sim Card or Google mail
Can I also back up widgets?
Yes Titanium pro from the market .
A factory reset and wipe all data.
Or return to seller /service centre .
Or use unofficial method and upgrade firmware yourself but that wont fix hardware fault .
jje
JJEgan said:
What do you mean by hard reset?
In the Settings> Privacy there is a Factory Data Reset option. Is that what you mean
Yes wipes all data so back up
Click to expand...
Click to collapse
Factory reset doesn't wipe the SD card, I believe. Hard reset wipes everything including SD card. Type *2767*3855# on the dial pad to do this
matanc1 said:
Since I got the Samsung Galaxy S 2 it kept rebooting itself every once in a while.
This seemed to happen only after doing something.
For example:
After opening an app.
It even happened once when I got a phone call.
I've reformatted the device the 2nd day I got it (for another reason) and it still happens.
Does this happen to anyone else?
What can I do?
Click to expand...
Click to collapse
Happened to me, same instances; could be micro SDHC compatibility problem. Seems that the Apacer 16GB micro SDHC I was using was causing the reboot. Formatting the micro SDHC on the phone doesn't help. Popped another Transcend 32GB micro SDHC into it and the rebooting just went away, didn't happen no more.
JJEgan said:
Also, in the Kies software it says that this version of the device cannot be upgraded. Why is that?
Because their is no update supplied by the phone supplier to Kies .
XWKDC old firmware .
How can I back everything up including my contacts and the way I synced them with facebook etc?
KIES or and back up contacts to Sim Card or Google mail
Can I also back up widgets?
Yes Titanium pro from the market .
A factory reset and wipe all data.
Or return to seller /service centre .
Or use unofficial method and upgrade firmware yourself but that wont fix hardware fault .
jje
Click to expand...
Click to collapse
If XWKDC is old firmware, and Kies won't let me upgrade it, how do I upgrade it?
When you say phone supplier you mean my carrier? Because the SGS2 isn't out yet where I come from. I got it from the UK.
When you say unofficial methods, what does that mean? Does that require rooting?
I'm having a similar problem when i connect to pc with USB, after disconnecting the phone and usb cable the media scanner starts, completes and then phone reboots?
Anyone else experienced this?
matanc1 said:
If XWKDC is old firmware, and Kies won't let me upgrade it, how do I upgrade it?
When you say phone supplier you mean my carrier? Because the SGS2 isn't out yet where I come from. I got it from the UK.
No the phone supplier .
When you say unofficial methods, what does that mean?
http://forum.xda-developers.com/showthread.php?t=1075278
Does that require rooting
Rooting not required .
jje
Click to expand...
Click to collapse
So just to make it clear:
I've got an old software version and I need to upgrade it and it might solve my rebooting problem?
I have the same problem. At least 10 reboots a day. Have now removed the sd card and it's run 2 days so far without problems
Sent from my GT-I9100 using XDA App
so will removing my sd card sort it out? Do i have to take it out permanently? i've only just got it
I just purchased this phone used. The previous owner reported this phone for having some "minor" software issues, such as freezes and losses of sound.
This phone is on stock MF3 ROM. From what I see, tt is having some random issues, mainly random freezes and I have to hard shut it down. I successfully rooted it with Kingo, but this does not change anything.
Today I got some time to test a couple of SIM cards, one active AT&T one and a Verizon SIM. The phone failed to read either cards. It just reports "no SIM card".
Since this phone is on MF3 ROM, there is not much I can do to re-flash with any other ROM. Do you think this is a hardware issue? or just software issue? Thx.
If you tried resetting the phone back to factory settings via Settings -> backup and restore or by samsung recovery you shouldn't be having problems such as freezes or losses of sound. It might sound like a hardware issue, but I can't be 100% sure without actually examining the device. Check if any of the water indicators went off, which includes the ones located inside the device.
emckai said:
If you tried resetting the phone back to factory settings via Settings -> backup and restore or by samsung recovery you shouldn't be having problems such as freezes or losses of sound. It might sound like a hardware issue, but I can't be 100% sure without actually examining the device. Check if any of the water indicators went off, which includes the ones located inside the device.
Click to expand...
Click to collapse
I tried again by removing battery and this time the phone reads the SIM card!. So the previous owner is correct.
I reset the phone at boot recovery (stock 3e). But I could not wipe the cache (common problem with MF3). Now the phone is better, but still sluggish.
The phone does not show any sig of moisture. It looks like new. I really want to reinstall the ROM, but I can't....
Look up Safestrap. Need root first. Kingo root is the easiest method.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
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.