looking for a little help guys, not sure what has happened but i have just literally (in the last 30 minutes) installed rom manager, on running the software for the first time i got the run at your own risk message that comes up the first time and then it went to the menu...... and then the phone shut down and now wont turn on, doesnt register when i plug it in to the laptop or even when the charger is plugged in. please guys need some suggestions here as to how to make this brick work again!!!
many thanks
having tried several different ways to resolve this (pressing and holding home, vol down and pwr whilest inserting the battery being one of them), ive come to the conclusion that there is no coming back from whatever rom manager has done to my phone. thankfully the phone is still within warranty as its less than 3 months old so heres hoping that they will fix the damn thing!!!
Rom manager is a tricky app because it is known for bricking phones often.
Seems like your phone is dead.
Most user with similar prob like you had to bring the phone to the service.
http://forum.xda-developers.com/showthread.php?t=1456946
As you are on warranty bring it there and wait till it is repaired.
Good luck.
Next time better do not work with rom manager.
thanks, yeah its weird cause when i had it on my x10 mini pro i had no issues - but clearly not the case here, oh well live n learn!!!
just as a sort of fyi i took the phone to my local t-mobile store here in liverpool and the guy behind the counter couldnt have been more helpfull, took the phone and arranged for it to be sent back to samsung for repair, even tried himself to make it work but to no avail. was most impressed with his 'can do' attitude and its not often that something like that happens!!!
First, I will say that i'm not a developer. I am familiar with backups, rooting and custom roms. I'm just at a total loss with a total loss phone :/
So here's the rundown of my issue/s with my Moto Turbo (XT1254)
The phone is completely "unmolested." My phone is stuck in boot loop, currently. I did bust my screen a few weeks back but it had been working just fine. I picked up my phone to check texts, and I saw the "updating 24 of .... apps." Once finished, it's been stuck in a boot loop since. (Odd thing, my screen now shows split Moto image when trying to boot. Ex: a slot machine with only 2 roller wheels that wont match up)
I have tried to clear the cache several times with no luck of it booting up correctly. I do have files that I was trying to recover since they are not linked to a cloud account, and was trying to avoid a full on reset. I did, however, get frustrated and even tried to reset it back to full factory settings. That did not work either. So, all this being said, I'm back to trying to recover my files (my daughter's first year of life, family stuff, etc), since I cannot get it to even preform a factory reset. Does anyone have some guidance or same issue on this matter? Again, I am trying to salvage my files now while stuck in soft brick / boot loop status.
Thanks any and all who can help me with this!
******* Solved********
I have better diagnosed and fixed my own issue. I'm sorry I don't have pictures or video to better document what I did, but in short, it was as simple as replacing my damaged screen/digitizer, with a new one.
My theory was that during the update, the phone checked over it's systems and found that the digitizer was non-responsive in a few very small areas (this I already knew from using it a couple weeks with the screen damaged) and it somehow caused it to go into a boot-loop. My experience with fixing Playstations 3's, helped shed some light on this for me. I had a PS3 i thought was in good working order, updated firmware to it, and it bricked the system. Come to find out, the blu-ray laser head was no good. Upon the firmware doing system checks, it found that was bad and ended up bricked.
I did replicate the problem by switching the broken screen and new screen back and forth 2 more times after the initial fix. Upon disassembly, (youtube for teardown vidoes) you disconnect the battery from the logic board anyways, so when you boot the phone up, it does a app check and system check again. Every time the damaged screen was connected to the logic board and then powered on, it would end up in boot loop. The new, undamaged screen, would do the required checks, then boot up like normal.
I will do my best to borrow/rent a camera soon, so I can make a short video to show this works.
I'm not going to promise this will work for everyone but with replicated results, hopefully it's a fix for someone!
I hope
So I rooted my G4 a week ago. Everything was fine, was running a stock rom, no issues whatsoever. So today, I was watching a YouTube video when my phone froze. Couldn't do anything, had to pull the battery. Then it wouldn't come on after putting in the battery. I pulled it again and left it out for about 10 mins, put it in, put it on a charger and it started charging. Turned it on, the date/time was wrong, kept saying it was July 21st and 2:38 pm. Went into settings and updated the date/time; was working after that.
I left it on the charger and went on with my day. Came back and the phone was completely off, no charging LED. So it's been like this all day, it won't charge (at least the LED indicator doesn't come on), won't turn on, nothing. I figured the battery was shot. I went over to my buddy's (he has the same phone) and tried his battery in mine, nothing. I tried my battery in his and it worked, so I've established it isn't a bad battery. I've tried everything so far, keeping the battery out and holding down power so it resets it's charge, EVERYTHING, etc.
When it did come on and it was displaying the wrong date/time, that was the day I rooted it and about the time it was rooted too (2:38 pm). So, has this happened to anyone else? Am I bricked/screwed? I just don't understand why it would just die all of a sudden. It's well taken care of, no damage or anything. I really don't know what to do, I'm in a rough spot right now and not having a phone is really going to make things even worse.
Was just curious if somebody could help me with this or has any other info.
Thanks in advance!
I'm going to try the Unbrick Guide on here, hopefully that works.
So I was able to get it into download mode but then it died on me. The battery only had a 40 percent charge and now it won't do anything (again). Does the battery need to be charged at least to 50% or more in order to get in into download mode?
Though the classic bootlooping issue is just that--the phone locks up and freezes, and then on restart continuously reboots to the LG logo--the underlying problem causes a whole spectrum of conditions. For example, some affected phones will just shutdown during boot, and not continuously reboot. The stage at which the shutdown occurs is also variable--it can happen before the LG logo appears, after it appears, after the carrier logo appears, etc. The point is that the bootloop issue is not always expressed as the classic continuous rebooting to the LG logo issue. What you describe with your phone definitely falls within the spectrum of what is possible so I am going to guess that you have been hit with the bootloop issue like many others.
This just happened with my wife's VS986 after 1.75 years of flawless service. She was using it last week, then bam, it froze up, and after that it was dead. On trying to restart it immediately, it was completely dead. But by letting it sit around for a while to cool down, it could boot to the LG logo and sometimes would do this 2-3 times before shutting down again. By placing it in the freezer to really cool it down, I could boot up past the Verizon logo, but then during the Android optimizing apps screen, it would fail again. So out of the blue--after 1.75 years of perfect service--bam, it was struck with the bootloop issue.
Though I had seen mention of the bootloop issue previously, I never really investigated it till my wife's VS986 was strickened. If you do a search on it, you will see it is extraordinarily common...
Fortunately, LG is now taking responsibility for this though they were basically denying there was a problem initially. The good part is that they are repairing phones with this particular issue for free of charge even if they are out of warranty. In my case, my wife's VS986 was clearly out of warranty, but when I called up LG and explained the problem, they said they would repair it free of charge. So they steered me to the lgmobilerepair.com website to set up repair service.
They supposedly fixed my VS986, and it is now being shipped back. Curiously, they identified the problem as "Unit is not charging with cable" with the repair being "Swap Board (Main/RF) : Others". By the way, this was definitely NOT just an issue of not charging--I have an H811, and on putting my H811 battery into the VS986, the VS986 had the same problem. And on putting the VS986 battery in my H811, it worked perfectly. Whatever the case swapping the mainboard is the solution, and they did that, so they can call it whatever they want.
Anyway, do a little bit of searching on the G4 bootloop issue, try the freezer test, etc., and I am guessing you will also become convinced your G4 has been hit by the bootloop issue. If so, call up LG, explain the problem, and I bet they will offer to repair it for free. Hope this helps, and do let us know the results!
Awesome response! I'm aware of the class action against LG, but with my phone being rooted I don't think it's the best option to contact them and it's out of warranty. I do not have a bootloop issue, my issue is I cannot get the phone to go into download mode. I really hope it isn't a main board issue like you had, that means I have no way of fixing it.
I was able to get the phone into download mode, this was right after I connected it to the PC via USB and held the volume down button while connecting it, it just came on. I was able to get to the T-Mobile splash screen then it started making a weird noise (almost like PC when it locks up, a high buzzing sound). I was able to then get it into DL mode (holding volume up while connecting) but it died on me during that phase or froze. After pulling the battery then, it will now not do anything. I'm optimistic that if I can get it back into DL mode I can flash the stock KDZ and get it working again. I will let you know what happens. After spending almost all day messing around and hassling my buddy for his battery (same phone, he charged his battery to 100% and let me use his, he's using mine) I'm going to have some beers and play Titanfall 2. I'll pick it back up tomorrow. Worst case is I have to get a new phone and I just don't have the means of doing that ATM.
Regarding your phone being rooted, my wife's VS986 was rooted as well. This did not even come up in conversation with the LG. Even though her VS986 was clearly out of warranty, as soon as I started to explain the symptoms I was seeing, the LG rep (without mentioning the word "bootloop") said he recognized the problem, and that they would repair it for free. In sum, at least in my experience, having the phone rooted did not make one iota of difference. I guess the takehome message is that this issue has obviously reached levels far greater than the average 5% electronics failure rate--LG recognizes it is a hardware problem, and is prepared to deal with it (even on rooted and out of warranty devices).
You said your phone does not have the bootloop issue, but I invite you to investigate it further because the bootloop issue is not strictly confined to continuously bootlooping as I tried to explain originally. What you have described completely fits within the spectrum of observed issues related to the bootloop issue. Question for you--when you turn on your phone, is it normal that it shuts off at some (whatever!) stage of booting? You said that at point you actually got into download mode, but then it failed there--is that the normal/expected reality? No, it's not, and this behavior is definitely one type of expression of the bootloop issue... And as you reported yourself, you boot seem to fail at a range of different spots, not always consistently at the same moment. If it were a software problem, wouldn't it always happen at the same stage? That it happens at different stages of the boot process suggests an external control, i.e. a hardware issue.
You asked about the freezer trick--let me roll things back a bit, and I'll get to this in a minute. The bootloop issue is supposedly related to a failed electrical connection for a component on the phone mobo, and so how far along the boot process actually gets before failing gets is related to thermal expansion of components, at least this is my guess. As I mentioned, when my wife's phone originally locked up, on trying to restart it immediately, it was completely dead, no LG logo no anything. But after letting it sit untouched for a couple hours to cool passively, the boot process would at least advance up to the LG logo, but then fail. After this, if I tried to reboot again while the phone was still warm, again, complete failure (not even reaching the LG logo) until I let it sit and cool for a while. This is all related to the freezer trick...
I read that on freezing their phones, some people were able to boot as far as the homescreen, and have a few minutes to rescue their contacts and photos before subsequent failure. So I tried that with the VS986, and was even able to get past the Verizon logo as mentioned above. But failure occurred during the optimizing apps stage, and I could never reach the homescreen. Whatever the case, this freezer trick simply works because of thermal contraction--by cooling the phone down enough, the components contract rebridging the failed electrical connection, and if it can can stay cool enough for long enough, you might actually have a few minutes to rescue things before failure.
There are some other data rescue techniques, too, and though you do not seem to be concerned about rescuing data, I mention them because they also point to this thermal issue. In particular, besides freezing, some folks have tried exactly the opposite--intense heating--and they have been able to get a few minutes of data rescue time out of their phones. This involves heating the back of the phone with a hair dryer until it is close to burning hot, and then trying to boot. This certainly works because of thermal expansion--heating the phone up so much causes everything to expand which literally forces the components back together bridging the failed electrical connection temporarily until the component heats up internally, and overcomes this extra pressure.
Another data rescue technique involves adding a spacer above the CPU to cause more force pressing down on the component to bridge the connection failure. And some people have literally ironed their CPUs in attempts to resolder things, and have had various levels of success. But in the long run, all of these attempted repairs to phones with the bootloop issue have the common characteristic of rebridging the failed component connection temporarily, and that is key here--they are only TEMPORARY. They work for anywhere from 1.) not at all to 2.) a few minutes to 3.) a few hours to 4.) a few days, but in the long run, they are temporary, and mobo replacement is needed.
Anyway, I encourage you to investigate the G4 bootloop issue a bit more before you conclude that your phone is not affected. And furthermore, in the long run, if you do conclude that it is afflicted by the bootloop issue, contact LG about it, and they will probably repair it for free. Don't fear about being out of warranty or having rooted the device--at least in my case these things did not matter!!!
---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------
I have reread your description above, and now even more think you may have the bootloop issue! You wrote that you were able to get into download mode, but then it failed, and then it would not do anything. This is exactly my experience with the VS986--immediately after a failure when it was still hot, if I tried to restart it, bam, nothing, not even the LG logo. But if I let it sit around a while to cool, it then was willing to show some semblance of life. Let your phone sit around after the next failure to cool down a bit, and I bet that after that, again, you will start to see a few indications of life instead of it being completely dead. If so, this should convince you even more that this is a hardware-level issue, and not simply a matter of being able to get into download mode to reload the OS.
Well I let it sit without the battery for about 14 hours, tried it again today and nothing. It won't turn on, won't charge, no LED indicator, no download mode, no safe mode, nothing lol. I'm convinced it's completely dead at this point.
MTN927 said:
Well I let it sit without the battery for about 14 hours, tried it again today and nothing. It won't turn on, won't charge, no LED indicator, no download mode, no safe mode, nothing lol. I'm convinced it's completely dead at this point.
Click to expand...
Click to collapse
A suggestion--remove the back cover and battery, put the bare phone in the freezer for an hour in Ziploc bag, then pull it out, immediately put in the battery, and see if you can get some sign of life out of it. Obviously, this is not a long-term workable solution, just an experiment to see if you can get any signs of life out of it at this point. When you finally decide to let it warm up, do so while it is in the sealed Ziploc bag so it avoids direct condensation.
Whatever you conclude about your phone, the G4 is still a nice piece of equipment with a great camera even though it was released over two years ago. So repairing it is worth the effort if LG will do it for free. If you live in the US, their contact number is 800-243-0000. I'd suggest calling them up, explaining that out of the blue, the phone locked up, and since then, even though you have been able to do partial reboots a few times, it would always shut off during one of these boot attempts. Now it doesn't boot at all. There is no reason to mention that you rooted your phone a week ago (unless you want to...) because again, this is a well-known hardware problem that they know about, and that they are repairing even for phones that are out of warranty.
Admittedly, sending the phone in for repair is a bit of a hassle. In my case, I had to foot the shipping bill out to the repair facility in Ft. Worth, TX, but the turn around time was super fast. Indeed, it arrived to the facility this past Monday according to tracking, but was not actually checked in to their RMA system until Wednesday night. Notwithstanding, by Thursday evening, they had diagnosed it, replaced the mobo, and put it into Fedex shipping back to me all at no cost! I expect you would have a similar experience if you contact them to explain the problem like I have suggested.
Good luck, and let us know how the saga ends!
Your freezer trick worked! For now at least, I have the phone in DL mode but the KDZ I tried to flash gets stuck at 9% when using LGUP, I think I need to find the right KDZ to flash, looking for that currently...
UPDATE: Dead again, lasted in DL mode for maybe 10 or so mins. If that KDZ I had was right it might've worked, gonna refreeze and try again with a different KDZ...
So MTN927, I think the evidence is pointing to a hardware problem... It seems that you are thinking that this is a software-level problem, and that by reloading the correct KDZ, the phone will return to normal. Why would freezing the phone have any effect on a software-level problem? Of course, freezing the phone could clearly have an effect on a hardware-level issue.
I am not really a betting man, but at this point, I suspect that even if you find and load the correct KDZ, it will not solve your phone's problem because it appears to be a hardware-level issue. Whatever the case, give it a shot, and here's to hoping my logic above is incorrect!
Here is a possible technique that might give you a few more minutes to load a KDZ--after you freeze the phone, don't take it out, just let it sit there. And then, run a USB cable into the freezer to plug into the phone. I'm not sure it will buy you much more time, but maybe it will be just enough to get a KDZ loaded?
That's what I'm thinking, hardware and not software now, obviously.
I suggest you investigate the possibility of LG fixing it for free. Though it's a hassle to be without your phone for 1-2 weeks, at this point it's not working anyway so what do you have to lose? The G4 is still a great piece of equipment so repairing it is worth the effort.
verbage said:
I suggest you investigate the possibility of LG fixing it for free. Though it's a hassle to be without your phone for 1-2 weeks, at this point it's not working anyway so what do you have to lose? The G4 is still a great piece of equipment so repairing it is worth the effort.
Click to expand...
Click to collapse
Yea, that's gonna be the last resort. I'm checking to see if I can get a new phone right now with my carrier. Thanks for all your help though, you've been great. Honestly, if I can get it fixed for free then sure, but I'm not too confident in the phones future considering what's already happened.
MTN927 said:
...but I'm not too confident in the phones future considering what's already happened.
Click to expand...
Click to collapse
I will not be any less confident with my wife's repaired VS986, in fact, given that they replaced a known defective component, I think I will be more confident! Good luck with your replacement--here's to hoping your carrier is willing to help out given the G4's known history.
Hey guys,
I have a problem with this phone. I got my relative's note 8 for trying to fix ( i'm not android expert ).
As she says, for no reason phone freezed and shuted down. After that charging problem started, and battery doesn't show real percentage.
After that i got the phone, and tried to go factory reset in recovery menu. Now phone stucks at samsung logo. Sometimes it stucks at blue screen with "no command" text.
Phone doesn't works all the time also. For example, somehow phone charged %100, after that i tried to open it, it stucked at samsung logo. I tried hard reset, screen off and no more screen. After 4-5 hours it worked again, but stuck at samsung screen again.
I send phone to trusted local repair shop. They couldn't managed to fix also, they reported me that it should be motherboard issue and they can't do anything about it. I don't know did they tried to install stock rom again.
I see no reason for motherboard issue. No water, no big damage or something else happened to phone. There should be a way to fix this and i seek your support here.
Whaki said:
Hey guys,
I have a problem with this phone. I got my relative's note 8 for trying to fix ( i'm not android expert ).
As she says, for no reason phone freezed and shuted down. After that charging problem started, and battery doesn't show real percentage.
After that i got the phone, and tried to go factory reset in recovery menu. Now phone stucks at samsung logo. Sometimes it stucks at blue screen with "no command" text.
Phone doesn't works all the time also. For example, somehow phone charged %100, after that i tried to open it, it stucked at samsung logo. I tried hard reset, screen off and no more screen. After 4-5 hours it worked again, but stuck at samsung screen again.
I send phone to trusted local repair shop. They couldn't managed to fix also, they reported me that it should be motherboard issue and they can't do anything about it. I don't know did they tried to install stock rom again.
I see no reason for motherboard issue. No water, no big damage or something else happened to phone. There should be a way to fix this and i seek your support here.
Click to expand...
Click to collapse
I would go with what the repair shop said personally. They certainly know a lot more than I do. Unfortunately things do just break even with no error for the owner themselves.
It is definitely worth trying to flash stock rom with Odin though.
stonedpsycho said:
I would go with what the repair shop said personally. They certainly know a lot more than I do. Unfortunately things do just break even with no error for the owner themselves.
It is definitely worth trying to flash stock rom with Odin though.
Click to expand...
Click to collapse
Thanks for your thoughts, honestly i don't expect it to work again, but before throw away i want to try all chances
Hey all! New here. I just soft bricked my phone, i woke up to it not booting. I tried various fw in Odin, but no success. This is my day to day use phone, I don't have anything else, so I'd like to make it work again ASAP, hopefully without factory reset.
Hi
what manipulation did you do to get there before flashing a lot of stuff in odin?
I've been just pressing the buttons all around, then I read about Odin, so I tried it. Now my battery died, let's see if I can get to wipe the cache...
Update: no success. Is there a way to get it into recovery? the old volume up+bixby doesn't seem to work.
Sometimes its because the recovery itself is error so that button combination is not working..
Charge your battery until full, then factory reset it with odin, let see if that works
But before you do that make sure you download correct fw that match your phone model. dont try all fw available there, make sure you download fw for SM N950F..
Well it worked and it broke again... Back to square one.
Your infos are kinda vague.
Did you modify your phone and it got triggered by user-action, or did it hit the fan by itself?
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
fzoli469 said:
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
Click to expand...
Click to collapse
This was happening to me too before my phone just started bootlooping to recovery
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
fzoli469 said:
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
Click to expand...
Click to collapse
Try changing build prop, ro.config.tima to 0