My Omnia 7 is stuck in loop boot :|
I have tried everything from hard resetting phone, to flashing custom/earlier roms, but whatever I do, I always get stuck at "Samsung Omnia 7" splash screen.
Does anyone know what else could I try?
PS: I do not have official Samsung support in my country.
Same happened to me when i flashed mi7rom v2 .
Stuck :/ Would appreciate any help
Edit: Fixed after I took out the battery a few times xD
andreit0 said:
Same happened to me when i flashed mi7rom v2 .
Stuck :/ Would appreciate any help
Edit: Fixed after I took out the battery a few times xD
Click to expand...
Click to collapse
Trust me... I tried more than few times
I have exactly the same problem, but the phone recovers after a while and Windows Phone loads properly, just to crash and boot loop again after using it for browsing or gaming for 10 to 15 minutes.
It is very annoying and I don't believe it is a software related problem to be honest.
Since I've 8 months of warranty left on the phone, it's been sent to the official Samsung Repair Center for the Benelux region: Dynafix.
That name alone made me shiver... And rightly so.
The first time it was sent to them, they flashed it with 7.0.7392.0 and returned it to me. Yes... It didn't get stuck in the boot loop.
I setup the phone again and hook it to Microsoft Zune for restoring pictures, music etc.
Of course Zune pushes the updates to the device as well: they crash one after the other on "Step X of Y: Restarting your phone..."
The phone enters a boot loop for several minutes and then recovers, installs the update (download mode of the phone) and loads WP after again... a few minutes of crash boot looping.
In the end, I manage to get the latest version on it, but it went from looping to freezing for 1h17m before I removed the battery and unplugged the USB cable as the phone and battery become warm, if not hot.
In the end, the phone remains only usable for about 15 minutes and then crashes. Playing Infinte Flight makes the bottom back side of the board where the battery is located burning hot. My brother, who has the same phone and plays the same game doesn't have this issue of warm device at all. It gets a little warmer, but far below what mine produces as heat.
So I sent it a second time to Dynafix, asking for a proper examination of the phone, especially the hardware. They simply flash it again and returned it. Of course the same story repeats.
I went back for a 3rd time. They don't accept it anymore. They flashed, and I quote: "the latest stable release for your device" and I should NOT update it with UNOFFICIAL Zune updates. It's my fault that the phone fails.
I strongly disagreed and stated that some of the apps I bought in the Market need these updates. They bluntly say and I quote "should not have installed unsupported 3rd party software" from the Market. Even Microsoft Photosynth, Microsoft SkyDrive are thus unsupported application...
I am outraged by the so called "service" and "repair" that I'm really considering sending a letter to Samsung's HQ packed in a box together with my phone requiring a proper repair or a replacement!
Related
Here is the story,
I flashed Marshmallow on my note 4 n910w8 via odin (I had 5.1.1). After it was done I noticed that the phone got laggy and warm. It would sometimes not boot/restart or it would shut down after it freezes for sometime. I would get the download page with mmc_read failure in red, I would pull out the battery and try again.
What I did:
*Unrooted the phone through SuperSu and flashed Twrp throughout (because it gave other errors and I had to do it again and again after each attempt)
*I tried flashing through twrp but I got the "no md5" error
*Flashed the stock ROM 6.0.1 with PIT since it gave the PIT error on odin
*Wiped cache/data/factory reset multiple times.
*I used both Kies and Smartswitch and was not successful (either read or write failure)
*Flashed the stock 4.4.1 (the original, It could not boot up once) so I returned to the stock 6.0.1
*The phone boots up 3 out 5 times and I was able to watch a full movie on Netflix and browse the web and google maps. But as soon as I locked it, It shut off and did not power up (until i took out the battery and let it cool down).
Where I went:
*A Samsung repair agent here in Montreal said that most of the time it is the Mob and that it would cost 300-400$ CAD to replace
*I went to other repair shops, a few hinted that it might just a matter of reprogramming the Mob and that it involved a risk of bricking the phone for good.
N.B: It is not under warranty and I'm not on contract, It is my own phone.
My question(s): Is there something else I could try? Is there someone who fixed the issued (Assuming it is not hardware) maybe and unbrick fix or something? And also, it there anyway to thoroughly wipe out the old installations so I could start anew?
Also I consider myself pretty knowledgeable. Or I at least learn quick. Do not hesitate to suggest something coarse for me to try. Worse comes to worse, Ill sell it on eBay for part, since it it in mint condition.
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
The Sponge said:
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
Click to expand...
Click to collapse
Thank you very much for your reply, I take it you have the same problem? I will try Wake Lock. And also I'm way ahead of you in the freezing game. Leave for 10mins in the freezer and you can basically flash anything. Also, do you a custom ROM would help?
I bought a droid turbo 2 about a year ago, and after a few months of use it was dropped into a sink causing minor water damage. Other than minor screen bleed everything seemed to have been in working order after a few days of drying.
About a week and a half after it finished drying and was in use, the phone shut down and went into a boot loop. It will boot to the motorola M but after 30 seconds it shuts down and restarts.
I have tried doing a verizon update from my computer but after the program says "updated" my phone is unable to restart dissallowing the update. I do have the ability to boot the phone in "fast boot" or "recovery mode", But if i go into recovery mode and do a factory reset the problem persists through it.
I figured the best way to try and fix my phone would be to flash a factory android version onto the phone, but that is where i am running into issues. Maybe it is my lack of understanding of ADB and flashing, but i dont understand how i am supposed to allow debugging on my phone if it is already stuck in a boot loop? I also am running into the issue of my phone not being recognized by the ADB daemon. even though the verizon updater recognizes it and allows for an update. Please any help from somebody with experience with these sorts of things would be extremely appreciated.
Bootloop after disconnecting charger, tried everything
I am having same problem after disconnecting charger from phone, went into bootloop. Did you ever fix yours?
Same problem, different reason.
Goes to Motorola logo and restarts until battery dead. I have flashed up-to-date stock ROM both with "Verizon Software upgrade" program with windows 10(once) and 7(several times), and have flashed with old "RSD lite" in win 7. Both flashing methods worked flawlessly and says "successful". but still looping. Have tried draining battery to totally dead and full recharge, no joy. Can boot into recovery fine. Did full factory resets, etc. Thought battery may be problem, but battery lasted full day or more before needing recharge before problem, and drains normally now with constant restarts, but gets hot. (plugging in to check % charge after restarts says still in 90+% range after many restarts).
I know this is an old thread, but any suggestions are appreciated. Cant understand if flashes good, why cant restart.
Old thread, old problem -- my problem, as well. (In my case it's a hand-me-down phone for experimentation; all my own androids are rooted starting with my first.)
This 'Droid Turb'o 2' worked fine until left alone a while, after which time its battery then seemed to lose its "elasticity" as it were, resulting in poor charging/capacity characteristics, and then shortly thereafter, this annoying and horrid bootloop. (It's also a Verizon phone, they like to "tighten-up" the phones they sell to one, or so I have read.)
All I have to offer really, are my observations, and possibly some insight. My suspicions of something to do with the current flow/battery-drain are also pure conjecture, and perhaps an educated guess at best. I, too, continue to solve this mystery because it's somewhat atypical of my own android experiences, and this is the sort of knowledge that broadens the spectra of engineering as a whole (and the suspense sometimes can give one a hell of a headache).
For now, my conclusion is that this appears to be a problem specific to a particular model that is no longer made, and perhaps for good reason. I still hope to find this mystery solved some day.
73 DE N6BHU
Hello, so i've had this Note 4 for about 2 years, i had no problems with it thus far until recently ( 3 hours ago actually) i was just texting and browsing Instagram and out of no where the screen froze, it became unresponsive and the screen went black and started constantly vibrating so i quickly pulled the battery out and put it back in again, tried to start it again and it got stuck on the Samsung logo, i went for recovery mode and tried to look up latest cashe log and it froze right there too and restarted, pulled battery out and in again, tried to get into Recovery mode for a second time and a dm-verity verification failed error on the lower left corner popped up, i selected "Restart phone" and it got stuck on the Samsung logo again, battery in-out, tried to get into Recovery mode for a third time to do a factory reset but this time it got stuck whilst trying to boot onto recovery, and i had to out-in battery again, tried several times to get into recovery and it didn't work, i just gave up and started searching, then after 14 minutes i decide to give it another try and it normally booted up! i inserted in my PIN and browsed the apps for about 2mins but it froze, again, and the whole cycle kept repeating i let it cool down for 15mins and it boots up normally but freezes again after a few minutes of usage, i noticed that it insanely overheats before freezing (especially right above the SIM card area) and the four CPU cores are showing 2469MHz and on 100% (But that's also the case when the phone just boots up right?), Now i basically can't access recovery mode and i'm stuck with a Freeze-Reboot looped and i'm left with no other option but a full Stock ROM flash, the thing is i can't even get into recovery to do a full wipe before flashing in the ROM, can i just flash in again a TWRP recovery? and is there any way to fix this without having to do a full Stock ROM flash (i Tried the wake lock app it didn't work) and i'm on Android 5.0.1, this has JUST happened today and never before. i'm hoping this isn't a hardware issue.
UPDATE: i have just noticed something rather interesting, the phone immediately freezes and goes nuts with the reboots and failed recovery modes instantly after i connect it to a wifi network, and exactly when it's attempting to "send report", a sending report sign shows up in the notification bar and it immediately screws up the phone until i do another Factory reset, i just did another one without connecting to a wifi network and i've already gone 40mins with it without any issues but perhaps it's just because it's not on heavy usage?
Sounds like you have the eMMC issue.
You can try and reflash with Odin. Get the right version from Sammobile.
Do yu get to download mode in any of the scenarios you describe?
Try WakeLock again and select the level to 4
Having the same issue
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Cybrid013 said:
I'm having the same issue and don't have any idea how to help, just hoping someone out there knows...:crying:
Click to expand...
Click to collapse
If you have the Snapdragon version - it's highly possible to have the emmc problem. Which is a bummer and the phone is like dead.
Unless you can buy another 910C motherboard and swap it.
Sorry.
What is short name for emmc?
jjoeshua said:
What is short name for emmc?
Click to expand...
Click to collapse
embedded multimedia controller
Just been having a very similar problem. I posted this elsewhere, but it may be helpful:
"My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilĂ ! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1."
Also now downloaded a eMMC bug check that says my eMMC chip is 'sane'. Guess we'll see
Hi everybody,
So I have a S7 Edge that I buyed in Spain in December 2016, so it has a year and a half by now.
The phone have the Gorilla Glass a bit broken but the display is perfect aswell as the touch, the back is also broken, main issue there was a corner fall but, this either started nor agraviated the issue in hand, it was no difference between before and after that situation.
The phone was submerged in water, less than a meter for less than 5 minutes, again I dont remember that this issue started nor agraviated the issue.
Now the issue I'm not sure when it started but it was this year for sure, maybe 2 to 3 months ago.
As far as I remember the issue started after a Samsung update, a large update like 1 Gb, the phone restarted to install the Update and during the Update it froze while installing the update in the boot and started heating up I wasnt able to do a thing I wasnt able to either restart it nor shutdown it, so I just waited until the batery run out wich it wasnt much time since it was heating up a lot.
After it shutdown I charged it and then started, it was able to update but from that point I didnt want to either shutdown nor update the phone again being afraid of the phone dying, so some day the phone forced another update, and I encountered the same issue, after that once in a while the phone restarted.
From that point I dont actually remember how it happens if I had some issues but one day the phone restarted and entered a boot loop restarting the phone after a second or two of the Samsung ROM splash, so I tried to shut it down and wasnt able to do so, at some point it "shutdown" but with a red led on and I wasnt able to start it, after 3 to 4 days the light went off (batery run out) and then I charged the phone again but wasnt able to boot up, after a few restart it boot up but then restarted and loop again.
After a few tries I was able to Factory Reset the phone and the phone started functioning kinda alright, I installed an app and while using it the phone restarted so I uninstalled the app, after that the phone didnt shutdown, so I used the phone for some days and never shut it down nor let the batery run out, till one day I updated the apps from the Play Store while updating the apps the phone shutdown again, boot loop and subsecuently shutdown with a blue led this time and not being able to start the phone again, so I waited like before, but for some reason the blue light stayed for like 2 weeks, I guess the phone has a lot of charge and the only thing using the batery was the led I dont know.
After all this I decided that the problem was a Software problem since all the main issues apeared while updating apps, updating the system, using apps, etc, so because I didnt have guaranty I decided to install TWRP and then some custom ROM, so I do it so, I installed TWRP, booted into TWRP, backup EFS, wipe dalvik, cache, data and system, in this process the phone rebooted, boot loop and then again blue led and not being able to start the phone, so I was tired by now and I opened the backpanel breaking quite a bit one side didnt care if I fix this I will change the back and front glass, I detached the batery and the phone shutdown then I was able to start it, boot into recovery TWRP and installed HavocOS this time (I will try with another one just in case), I installed it run it and it appears to be working fine... it rebooted one time and after that nothing I installed Whatsapp a 2.3 gb backup started to download alongside 34 apps from the PlayStore I guess the apps that I had in the previous installation.
While downloading the 34 apps the phone restarted I guess while installing Facebook, after that it shutdowns again after apparently working just fine for an hour or so.
So I decided to install again HavocOS but dont instal any APP but Whatsapp, maps and some other things I need (Keepass, Bank stuff, etc) but from here on the phone started to reboot even in TWRP, while installing the ROM sometimes it freezes sometimes it shutdown sometimes it rebooted and antered boot loop but at least it didnt get stuck anymore I was always able to shutdown and start the phone but with boot loops and shutdowns and totally impossible to use.
So now I'm almost totally sure that it is not a Software (free fix) problem, and now I'm thinking in replacing the batery, the batery is not very expensive (compared to a now phone ofc) but it is a bit expensive for my economy and I'm not totally sure that the batery is the problem, can somebody, with all the information given here tell me something like "I'm at least 90% sure that the problem is the batery"?, cause, I'm a PC Technician that didnt know much about phone but they are practically the same as a PC but less modular and sincerilly I think that it might be the Processor or the Internal Storage, both non-easy-removable and change and both more expensive than a batery and both things that I have to buy outside of my country that may or may not come in 1 to 3 months so, is it really worth buying a batery or this issues point to a direction that the phone is almost imposible to fix with the money I have so its better to save money and buy a new one... thing is in this effing country a new S9 for example cost 1000 u$s and my salary is 600 u$s so its a bit anoying to save for something like that, even a new S7 Edge is worth 600 u$s here, and thats what I paid in Spain one and a half year ago when it was the latest Samsung phone available.
Sorry for the long post I wanted to explain everything throughly and I hope my english is ok.
Best regards.
This may seem like a noob thread (which it probs is) but my issue is probably rare in htc 10 phones. You see.. my htc 10 just randomly decides to reboot from time to time. I've noticed some pattern to it but it still does not help. The reboots occur randomly. Some days, no reboot at all. Other days, it reboots so many times. Reboots more noticeably while watching videos (I got the phone knowing this problem). So, a logical person might say, "Hey, why don't you reset to factory settings/why don't you flash stock ruu/use htc repair tool or sync manager." To which, I reply, "I have done literally everything I can except getting it s-off and flashing custom rom on it. And the best part? when I select repair on htc sync manager, it says, "No software available for your device""
It may be a hardware issue. Most people say that it could be related to battery. If it were related to battery, the phone would just completely shut down and restart. However, in my case, the phone hangs or freezes for about 10 seconds and is unresponsive till it finally shuts down and reboots. I've put in safe mode as well but still no luck.
I've completely gone into zen mode now. I don't watch videos anymore xD
Help would be GREATLY appreciated. Thanks.