This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
re: bootloops
whitebloodcell said:
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Go into settings>developer's options and ENABLE OEM UNLOCK then
go into settings>general management>reset>factory data reset and
reset the phone.
Once you have done that the phone will work properly without rebooting
provided that you have successfully odin flashed the official samsung
G935F S7 Edge firmware prior to doing a factory data reset.
Good luck, have a great day!
Thanks for replying. Unfortunately I can't get into the phone at all. Only screen I have access to a recovery and downloader.
So I left the phone alone for a while and tried booting into safemode. This time it worked - sort of. It is asking me for a password, but I have never set one. I only ever set a pin and fingerprints. But since wiping everything that doesn't seem to apply anymore. What is the default password? I am referring to the phone password, rather than a google account obviously. I am not at that stage of the boot up.
Update: found the password (default_password), still boot looping on the optimising apps screen.
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
I have flashed stock rom (initially the version that matches my carrier, although my phone was bought sim free and unlocked, and then the version for unlocked phones (BTU in sammobile I think)) but it still just boot loops. The phone can remain in download mode as long as it wants, and previously, when it was asking for the password, it was able to remain on that screen indefinitely. I would have thought if it was a hardware problem the boot looping would happen regardless of the action on screen. Immediately after flashing the stock rom, it did start to load before ooting. Now it just boots immediately at the Samsung Logo.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
Just to be clear, do you mean repartition here? I have not checked that option before, will try it.
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
vsn4 said:
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
Click to expand...
Click to collapse
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
You can wipe your phone by entering recovery. Default recovery has the wipe option.
alehawk said:
You can wipe your phone by entering recovery. Default recovery has the wipe option.
Click to expand...
Click to collapse
Was the first thing I tried. Didn't help.
I got the bootloop thingy and was the cache, I wiped and the phone booted up
alehawk said:
I got the bootloop thingy and was the cache, I wiped and the phone booted up
Click to expand...
Click to collapse
Thanks for trying to help, but, again, already tried that.
whitebloodcell said:
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
Click to expand...
Click to collapse
Hope all goes well, let us know if you get it sorted out.
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
AnubuRe said:
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
Click to expand...
Click to collapse
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
whitebloodcell said:
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
Click to expand...
Click to collapse
For those perhaps in similar situation in the future, Samsung didn't care that it was purchased second hand, despite what the fine print says. They just looked at the serial number. In the course of trying my own repairs I flashed a custom rom, which of course tripped the knox warranty void bit. When I took it into the service centre they saw this and then wanted to charge £225 for an out of warranty repair. I refused at the time. I later called Samsung support and explained the situation (I said a phone repair shop must have done the flashing). Again on the phone I was told it would be an out of warranty repair, and this time I agreed. They collected my phone and returned it to me today however, with no invoice or mention of charges, so it looks like they just did the repair no questions asked.
I have the same issues, so far I'm getting by with flashing a stock rom with pit file and doing repartition and nand erase, normal cache/ factory reset doesn't help, it sometimes even boot loops while in twrp.
Somehow Odin flashing helps for a random amount of time, but it has thus far, crashed after a month, or a couple weeks since the last flash, etc. So far it's been my 5th boot loop event in the last 6 months
It sucks but as I got mine from another country (/win), didn't get the warranty ;( plus I tripped Knox by rooting.
sounds hardware related to me..
i had a friend with a note 4 who had similar problems it would hardly ever boot sometimes boot straight into download mode..
if by chance it did boot it would boot once the device was locked for a short time it would reboot and start over again bootlooping..
it was the emmc flash memory that was failing...
a workaround i found for this was the first thing i did when finally getting it to boot was install "Wake Lock - CPU Awake" and set it to never let the device sleep and to startup on boot...
this "fixed" it as long as your phone does not turn off... he had insurance though and sent it off and they sent him a new refirb
again this note 4 was untouched never rooted or anything
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
im having pretty much the exact same problem except ive been unsuccesful at flashing the stock firmware for my galaxy s7 active (SM-G891A). the active series isnt the most saute after, so finding the right firmware is alil more difficult. which im pretty sure is how i got into this situation! my question is what exacly does checking the "reparation" option do. i read to leave to leave it unchecked/unticked. maybe thats why ive been unsuccessful. and someone told me awhile ago not to fill in the "bt" box becuz i have a locked bootloader. this correct or no?
Related
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
xijar said:
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Click to expand...
Click to collapse
Yes, it's under standard warranty. I bought it sim-free without being tied to a network. I have already contacted Samsung and they said they'll email me details of the service centre to return it to, but I was hoping for a solution before needing to do that.
Nothing you can do without odin picking the phone up.
I use 64bit windows and it picks up fine, make sure you have the drivers installed (see the link in my sig, for my 4shared, where you can get them) or if you have kies installed you have them but make sure to kill all kies processes first in task manager.
But in the end, best bet is just to send it in, to make sure you dont void your warranty
Sorry this is a mistake.
darkixion said:
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Click to expand...
Click to collapse
How did you erase user data?
Sent from my GT-I9100 using XDA Premium App
inkyadrian said:
How did you erase user data?
Click to expand...
Click to collapse
When it was switched off, I held down Vol-Up, Home and the power button. There was an option in the menu called "wipe data/factory reset". There's also a "wipe cache partition" option, the action of which is performed in the wipe data option anyway.
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:
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
Hello all,
Earlier today, I was browsing a website for a game on my phone when it rebooted. It continued into a reboot loop at which point no matter what I did, nothing worked. TWRP wasn't working, and I wound up flashing the phone several times with both stock Android as well as Pure Nexus. While I was able to fix TWRP, whenever I attempt to flash Beans G'Apps, the phone reboots again and stays in the reboot loop. I'm unfortunately unable to flash the image using that means. I feel like I've made progress on this issue, but everything else isn't working.
Does anyone have any suggestions on what I can do in order to be able to stop the boot loop and save my device?
Thanks!
Flash stock firmware
DanPLewis said:
Hello all,
Earlier today, I was browsing a website for a game on my phone when it rebooted. It continued into a reboot loop at which point no matter what I did, nothing worked. TWRP wasn't working, and I wound up flashing the phone several times with both stock Android as well as Pure Nexus. While I was able to fix TWRP, whenever I attempt to flash Beans G'Apps, the phone reboots again and stays in the reboot loop. I'm unfortunately unable to flash the image using that means. I feel like I've made progress on this issue, but everything else isn't working.
Does anyone have any suggestions on what I can do in order to be able to stop the boot loop and save my device?
Thanks!
Click to expand...
Click to collapse
Maybe start from scratch flash the factory image threw fastboot and start over.
pacods61 said:
Maybe start from scratch flash the factory image threw fastboot and start over.
Click to expand...
Click to collapse
I had tried that but to no success. I will try this again. Do you have any guides or anything for that?
Edit: I have gone through and attempted to use fastboot to flash two different images... N2G47H and N2G47W. I'm still getting the same result. Since doing this, I've also attempted going back into Recovery (non-TRWP) and doing factory reset that way. Nothing.
So apparently this has been a known issue possibly. I don't know if for a fact this is the hardware issue, or the fact I had Pure Nexus installed on it... it would also explain why Google is so readily going to give me a new phone even though my warranty is expired.
I can't post the reddit links due to new XDA account, but they are there.
DanPLewis said:
So apparently this has been a known issue possibly. I don't know if for a fact this is the hardware issue, or the fact I had Pure Nexus installed on it... it would also explain why Google is so readily going to give me a new phone even though my warranty is expired.
I can't post the reddit links due to new XDA account, but they are there.
Click to expand...
Click to collapse
How did you get Google to replace your phone? I bought mine from Swappa and warranty just expired in April
ornwilson said:
How did you get Google to replace your phone? I bought mine from Swappa and warranty just expired in April
Click to expand...
Click to collapse
This is DanPLewis under my account account (Wasn't able to remember credentials initially!). So my phone was purchased from Google for Google Fi. I reached out to their support chat. First they informed me that my phone warranty expired 3 months ago in March. I asked what options I have right now for replacement, and they voluntarily told me that they will go ahead and do a one time refurbished replacement.
The reasoning I feel as though they replaced it out of warranty was because they're aware of the issue with the phone... but they could've just been nice about it.
Punkrulz24 said:
This is DanPLewis under my account account (Wasn't able to remember credentials initially!). So my phone was purchased from Google for Google Fi. I reached out to their support chat. First they informed me that my phone warranty expired 3 months ago in March. I asked what options I have right now for replacement, and they voluntarily told me that they will go ahead and do a one time refurbished replacement.
The reasoning I feel as though they replaced it out of warranty was because they're aware of the issue with the phone... but they could've just been nice about it.
Click to expand...
Click to collapse
OK, thanks. That does seem good of them.
Folks I initially tried to root my phone *SM-G935F* using Odin and a CF hero2lte file. The flashing was all good to go with a green pass. Then upon rebooting the phone got stuck on the Samsung logo boot screen with red words at the top that said **Recovery Is Not Seandroid Enforcing**. This being the case all I was able to get into was (Download Mode). I tried to do the samething a few times and gave up after no successful attempts and the phone not being able to successfully reboot.
Fast forward to present I downloaded the phone's firmware which was a zip that contained 4 files (5 total actually because there was another CS file in the event that you wanted to preserve your data etc.). I loaded all of the files in Odin and made an attempt to flash the phone again however it got stuck on *System* and never go to Green *Pass*. So I figured I would try it a couple of more times in case Odin or something just got hung up on the first try. Any how that wasn't the case.
Now with the above being said what did change is when I would try to reboot into *Download Mode* again it said something along the lines of Emergency Smart Switch Recover. I downloaded Smart Switch onto my computer and went through the specific steps to try to Recover the phone using Smart Switch. Now after it was all done I got to the blue screen with the Android and it said *Erasing...* then the phone booted up and its now stuck at the Samsung animation screen. This being said as of current I can now access *Download Mode* and also boot into the black screen or *Recovery Mode* I think its called where I can reboot the phone through a bootloader, power off, factory data wipe / reset, etc etc.
The above being said I have tried the factory reset / wipe. The reboot in bootloader, reboot phone, all with no success.
Also would like to add that before doing all of the above I forgot to tick *USB Debugging* in Developers Mode when the phone was in its normal state. I must also mention that all of this was a first for me and I looked at doing so to try and recover lost data on my phone. Also wanna add that I am not too familiar with ADB or twrp or how to mess with any of that stuff given the limited access I have to my device because it can no longer bootup like it normally would.
I'm currently at a lost of words as to what I can do next as I am out of ideas and could really use some help. I would also be more than happy to donate a little to anyone who is able to help me boot my phone back up and get things back to normal.
Any and all help would be greatly appreciated.
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
Bro would you tell pls , what you did to restore. Thanks
shah22 said:
Bro would you tell pls , what you did to restore. Thanks
Click to expand...
Click to collapse
After me not being successful with the root or with flashing the stock OEM firmware using Odin the phone would get hung up in download mode and the only difference when it would go into download mode it would say to use SmartSwitch Emergency Recover which is what was used and that fixed the issue and the phone rebooted completely fine.
However the above being said I honestly still feel the phone has some small minor issues that I did try to resolve all with no luck. First off when loading to my home screen the icons, and clock, etc etc take about 2 or 3 seconds longer for them to appear on screen than it used like when the phone was new out of the box.
Other thing to note is for some odd reason this issue was thought to be worked out by just booting into recovery mode and doing a factory reset from there, wiping the cache, etc etc. Well this also didn't solve the issue and for some odd reason when performing this the phone didn't reboot on its own.
Basically how it should be normally is after you select that you want to do a factory reset, wipe cache, etc etc, the phone should normally reboot and go through the entire process by itself, however this was not the case. The phone instead went back to the recovery screen and I had to select reboot rather than it normally rebooting on its own.
I've honestly given up on things and given that it is in working order with just a few small minor hiccups I've decided to give the phone to a family member which they plan to use as trade-in credit towards a new Galaxy Note 8.
That being said I will always have a soft spot for the S7 Edge being it was my first smartphone after I had bought a Sony Xperia Z during the same year but returned it the day after because what was to me being poor quality of the Sony phone.
Hmm, looks strange bro , your phone didnt worked after flashing stock rom with odin , and this is the last resort , but you said it was normal before you tried to root , so i guess it was still a software issue other than some hardware problem due to software , but anyways wish you good luck in future , another thing is that my s7 edge has also a very poor build quality , has front camera issues , paint peeling around usb port , wifi issue and high battery degradation , but that happens i guess with today's phones
The version of Odin I used was v3.10.6. I had tried the most current version and a few others, and from the get go for whatever reason this was the only version that would actually pickup the phone being added. Well wait hold on a second the other version would say added when the phone was in but when hitting start nothing would happen, even after waiting an extensive amount of time, also note that the com was highlighted that blue ish color indicating the phone was being recognized by Odin but once again for some odd reason it was only version v3.10.6 that carried out the process of my root attempt and also the attempt I made flashing the original firmware on it.
As for quality the phone had no paint chip or peeling, neither the silver aluminum frame around it either. The build quality was beautiful and up to par with mine. I had a soft spot for my S7 Edge also because it was in the white color which at the time of purchasing was a bit more scarce than the other colors. I purchased the phone from an Amazon.com seller, and during that time I also purchased 2 others from other Amazon sellers but returned those because they had carrier animations for them that were Band LTE or Brand LTE, whatever its called.
This one had no carrier animation upon boot and turned out to be a UK Nougat model. Haven't really seen or came across another one since that would be from a trusted seller or source. Nowadays you never know what you're getting both on eBay and Amazon from these third party sellers.
Yeah thats really strange with odin , its good that you dont have quality issues which struck heavily on me , but yes everyone should be quite careful when ordering online and only should do with trusted resellers
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
vini3237 said:
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
Click to expand...
Click to collapse
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Hydranize said:
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Click to expand...
Click to collapse
Phone is SM-G935FD
I do not know what caused it, I already got the celuar so, in status it says Custom.
I already tried to blink for odin 3 different Stocks and the same thing continues.
When I got it it could not access the recovery mode, only the download mode was accessible, after flashing the Brazilian Stock 6.0.1 I was able to access recovery mode.
The phone turns on, and hangs at boot, Samsung logo, restarts and stays in infinite looping.
Can it be Hardware?
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Hydranize said:
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Click to expand...
Click to collapse
Ok now i think what was the problem , you didnt enabled usb debugging , and for flashing with odin its a must ! , for guys who want to flash firmware using odin .. please enable usb debugging in developer options or you will have much issues and may also brick your phone , so if you dont want to enable usb debugging or developer options , just use samsung smart switch on pc to flash your firmware.
Yeah that was my issue was I had OEM Unlock checked off and one other thing in Developer Options and forgot to enable USB Debugging leaving me stuck in the process when the phone couldn't reboot normally after the flash attempts. But yeah SmartSwitch Emergency Recovery should definitely be able to fix and resolve the issue if the phone can't reboot normally.