Related
Background: Very familiar with the Eris, rooted it, flash ROMs frequently, never had an issue.
So I bought the phone on eBay, only issue was the phone was a bit beat up and the screen had been replaced. No big deal. Turned it on everything was fine, worked for about a day, then I decided to flash another ROM. Flashed the ROM and the phone would reboot every time I got to the lock screen UNLESS I had signal, then it would work. This issue happens to EVERY ROM I flash. I wiped cache,dvlik-orwhatever, full wipe, everything each time I would flash a ROM, and none of them have been stable. After flashing the first ROM I also ran into the turn off and vibrate 5 times with a flashing green light problem. I have gotten out of this twice with the USB pull method. I have researched these issues, I have tried flashing quite a few ROMs, and nothing seems to work flawlessly. Is the DI just a terrible phone or do I just have a bad unit? The main issue seems to be with signal, such as if I go from airplane mode on to off it will reboot and then get stuck in a boot cycle and the issue with flashing the phone and having to have signal before I can unlock the phone.
I am currently about to flash the PB31IMG to see if it will resolve the issues and then attempt to re-root. Any advice would be greatly appreciated as nothing has seemed to work so far. I would key you into what I have tried but I don't remember. Basically all the things to fix the 5 vibrate issue and general flashing woes.
Update:
Still no good. Flashed the PB31IMG via vol. down and power and it still did a reboot. Unlocked, got to the white HTC screen, and restarted. Booted the second time, got to the lockscreen, and rebooted before I could even slide down the unlock. Third reboot, got to activation this time, then it rebooted. Fourth reboot, go to activation, then rebooted. Fifth reboot, got to lockscreen, then rebooted before I could slide down.
So yeah. basically you can see what I am dealing with. And it is not fun. I have tried SD card in, SD card out. Just did its 6th reboot, didnt even get to the unlock screen before rebooting.
UPDATE 5/3:
Link to the video of whats happening. Nothing special and I recorded it with my Eris, but you'll at least see the timing of the reboots and what not. And ignore the breathing. lol. Just turn off the sound. Right after the video ended it did a 5 vibe. Pulled the battery and now it's just doing bootloops.
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
As for the flashing green light and 5 vibrates, I have so insight on this. It can happen if you press power and Vol+. I think it puts it in a safety mode and the only way to get out of it is a battery pull. So if you ever get stuck in a situation like this wait 10 minutes and try to turn it back on normally. If this doesn't work try booting into hboot (power + vol down) if this doesn't work power + vol up has worked for some people too.
There are cases however, where battery pulls don't help either. And no matter what the person tries the phone won't turn back on. This is a hardware problem and the only way to fix this is getting a new phone.
Dhessler5 said:
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
snipped.
Click to expand...
Click to collapse
Would flashing the PB13IMG in Hboot unroot it or would I need to follow the guide? Just curious as I have never unrooted before, but I do know there is a guide for it.
The 5 vibrate thing is under control, it just has happened so I wanted to make it known.
And thanks for the info.
I would follow the guide for it, it would be the easiest and safest way and if you run into any problems they would be able to help you out and know exactly what to tell you. I have yet to unroot too so I don't want to tell you something without being 100% sure so I recommend the guide.
Alright, so it turns out flashing the image I flashed via Hboot is a way to unroot. :/ And that is when I got all the reboots in the beginning (the ones specifically posted, its not the first time). I am going to flash again once more to see if I can get a flawless start.
Still no good, flashed it again via Hboot and it restarted again. This timeat the white HTC screen after unlocking but before activation. :? Hm. Better than nothing, after the first reboot it fully loaded and everything is fine so far. Lets just home it doesn't slowly begin to degrade like last time.
A while ago while running the peanut stock ROM, every time my phone would reboot some apps would loose information (such as log in) and I was eventually unable to access the EPST settings.
If you rerooted your phone you could try to go into hboot and then recovery and "fix permissions." I am not sure if this will do any good but it couldn't hurt.
Also if it is unrooted you could try to bring it in to Verizon and see if they will give you a new phone or a restored one.
Make sure you have the stock Rom if you bring it back to Verizon also
sent from my dinc
sorry to hear this happened on an ebay phone... I've had it happen to 3 of mine... warranty took care of it since I'm still within my date. but after one year what do I do? luckily I bought my bros early upgrade meaning the Inc2 will suffice until april 2012
ohh yea my point sorry: I had an Eris before the Inc. //////had many problems after 5 they gave me the Inc if I agreed to drop my current one year contract and get a new two year paying the two year price PLUS got credited $199 for the Eris, and got to keep it, so I thought I made out until I realized this phone isn't gunna last two years. ANYWAY. I bought the Eris off Ebay, they gave me warranty after warranty no problem, best of luck
I have had my Inc for a year and have not had any issues. I would say you bought a bad model from someone on eBay. The 5vibration green light is indicative of a hardware failure and I have not seen anyone have a fix for it.
Sorry to say but I have seen no one, NO ONE recovery from the 5 vibs of death. From what I have gathered it is some sort of qualcomm download mode and I know of no way out. I have a feeling it is caused by pressing the vol + and vol - and power while trying to get into hboot.
This is just an uneducated guess. If your willing to part with the device I would love to get my hands on a 5 vibs phone.
Since it happens when the phone loses the signal, I'm wondering if it might be a radio issue. Which radio version is installed? It could be incompatible for your area/ROM/whatever.
Another thought: you said the screen was changed out. It is very possible that the kernal installed won't work for an lcd screen.
Anyway, more things to check and to test. Good luck!
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
ACD168 said:
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
Click to expand...
Click to collapse
That should be 3 vibs, not the 5.
they both won't work after wards thought as far as my testing.. had to get warranty replacements
I remember reading Chingy fixed 5 vib. It's not the end. I've seen other people fix it with ruu.
I couldnt fix mine when I got the 5 vibrations and I tried everything. My theory is that it has something to do with a messed up kernel flash since the baseband and kernel are apparently linked and I saw somewhere that flashing the same baseband 2x will cause this. It happened to me when I tried to flash a kernel twice (the first time it failed), some people could be getting this when flashing roms since they install new kernels also.
You can flash radios and kernals twice. There was one leaked radio in the past that caused problems from being flashed twice, but it isn't typical
Edit: I think chingy said something about trying a hundred different things, but eventually he got it to work by connecting to PC with battery removed. I could be wrong though because I read that post months ago. I know he got it working again by wiping system and starting fresh
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Trifurcated said:
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think the 3, vibrate and 5 vibrate are connected because both times I had the 3 vib I had the same problems, would turn on when connected to usb then 3 vib and green flashing light... weird.
Hello dear friends!
HTC let me down Kind of stupid phones indeed at least desire...
I have my phone for quite a time now, it is rooted with unrewoked, clockwork recovery and s-on. I flashed many different roms in the past and everything was brilliant. In a pas half-a-year or so I stayed with only one ROM - MIUI-Au. I kept updating it to the newer versions and so on and on. Never had any random reboot or something. At least maybe it was because of some strange app or something else. But now it started to reboot randomly and constantly!
Phone gets hot abit and it just reboots, and never comes to android homescreen again, until I put out the battery, hold it for few minutes, pop it back and then it boots. But as soon as start to play music, or run a game the phone gets hot abit and reboots again. and so on and on. I thought maybe it was a miui issue. So I tried to flash different roms, but guess what? None of the even boot! The main screen shows and with the same second it bootloops again and forever!... (
Even from recovery it sometimes reboots randomly. So i managed somehow to flash my miui back and it at least boots. But it is very unstable now, I barely can use my phone now
PLEASE WHO CAN HELP ME????
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?
What have you set the CPU max to?
Sent from my HTC Desire using xda premium
Thank you for response! Appreciate, really!! I didn't set it, I left everything by default I think! Because as i said, i even tried flashing different roms, not only miui.
What else could be? By the way, with stock froyo rom If I remember correctly, sometimes it became extremely hot, but I didnt get any reboots from that. But now, it gets just a little bit hot and it seems that this causes the reboot...
Now what I just noticed, I get reboots even when the phone is idle. And it is not even warm!
If its not getting hot then I'm confused lol. It sounds like a actual hardware fault. Sorry I can't help with this one
Sent from my HTC Desire using xda premium
cluendo said:
My warranty probably out of date, and my phone is rooted, I dont think HTC would accept it...
any thoughts? friends?
Click to expand...
Click to collapse
try and get it taken back to stock if you dare.
The phone hasn't been out 2 years yet, which is how long the warranty is.
Thank you! But is there any possibility to fix it without HTC involvement? Maybe it is not hardware issue ? Can it be because phone is rooted and I flashed many roms to it ? I didnt try AOSP roms since reboots started, I will try to pop in Cyanogenmod or other and see if I will get reboots.
Would rerooting my phone and updating my recovery fix the problem?
and Note: yesterday I tried to S-OFF my phone, but I can't even do that with my unstable MIUI. It rebooted in the middle of the process..
I had a similar problem, apparently it's not uncommon on the early revisions. I sent mine to HTC and they replaced the mainboard.
Thank you for answer! But what if my phone is bought through a contractor?
Can just call HTC and ask the for repair? Or should I contact my contractor first ?
Just give them a call and they will try to help you out. I had a very good customer service experience with them when my desire had some issues.
They will require a proof of purchase though. If you managed to get the receipt from your "contractor" (I am unsure what you mean by a contractor), then there should be no problem.
Sorry for misleading word, I meant T-Mobile. I bought my phone under contract. I think I have a receipt. I even have whole box and stuff of the phone somewhere in my drawer.(just sayin ). So how is customer service of HTC? Poor, good ? I heard you need to tell them that you did a factory reset and that didn't help. Is that true. Also if I will unroot my phone, will they know it was rooted anyhow?
Ahhh....this overheating issue seems common. How they can release faulty phones?? No clue.
thanks for answers mates!
In Singapore, HTC service is really good. Phone was still under warranty.
It took me just one (real) call to confirm a repair order. The first call I was just checking to see what options were available to me.
The second call was an actual repair request. And the third call was me pestering them for a pickup date. heehee
In Singapore, repairs were done via courier. They picked it up and 1 working day later, they sent it back.
Naturally, you will probably need to impress upon them that you tried everything to fix your phone (which I hope you did which includes proving to yourself that it's not the ROMs fault).
You will definitely need to reset everything back to zero. In my case, I downloaded an RUU to totally reset everything back to STOCK, which included removing clockworkmod recovery. You WILL need to create a goldcard for this though so bear in mind that it's not exactly a case of a simple flashing procedure. At least not if you don't already have a goldcard.
Sorry if I overread it at some point, but you speculated at the beginning there could be some faulty app causing this, but you never meantioned performing a full wipe. Have you full wiped yet? Just to make sure it is indeed no software problem.
greets
Thank you for your answers. At the moment I have SuperNova classic ROM. ( 2.3.3 + Sense 2.1) But my phone crashes again and again, it is so annoying and causes me so much trouble.
I never tried a reset or unroot and return to original rom. Im just wondering now, would this help to remove or at least remove those reboots?
Today I was in my work and i was keeping my phone in my jeans pocket. it got hot as u would expect when keeping in pocket and suddenly it rebooten, then it went into a bootloop and started to bootloop 7 times in a row quickly. then again and again. It became very hot at that time.
For the interest, what exact hardware faults causes these reboots and why phone gets even hotter if you keep it on boot loop. If I keep phone cold, the rom usualy stays normal, without reboots. but as soon as I start using my phone, texting or calling for at least 5minutes of using it just reboots.
as I said- really annoying thing :S
I remember my happy times with miui, apps and no reboots Was fun!
cheers for helping!
I would give full wipe / factory reset a chance, and maybe RUU.
At least try it before sending phone to htc.
It is hardware problem, search forum. Fresh ROM without SD card, enabled WIFI and GPS, running G navigation, back of the phone is warm - restart after few minutes.
Maybe someone know how to read info form the phone right before reset? We could understand why the phone is reseting and hopefully add some patch.
Reboot-loop experience
Hey,
i had the same problem over the last few months: In the beginning my phone restarted only when it got hot, but it got worse over the last few weeks, in the end i was not able to use two apps at the same time (music and mytracks) or even to surf the internet longer than a few minutes. The problem did noticeably decrease when the phone was cool - tested by putting it on a fan or in the fridge. Yet, Skype was regularly killing it. As i really love my phone (and especially the AMOLED-Screen!) i did not want to resign. The battery cover contains some metal which is supposed to enhance heat dissipation - so i attached a little thermal pad to the hotter bottom of the phone to improve contact with the head spreader. Unfortunately it did not entirely fix the problem. Yes, it improved the situation a little, but it got even worse after a week or two - in the end i had to turn it in.
So i decided to take it to the Telekom-Shop. They were very kind and told me they would call the other day to confirm that the replacement would have been shipped. It took a few days longer, but i got a phone with the AMOLED-Screen! The employee said it was a used mainboard in a new case, completely refurbished. They only replaced the main unit, i kept the battery, sd-card, charger and so on. Now i have a working Desire again!
Terminator
Similar?
Hi i on the other hand have similar problem, qiute anoying one, my desire, cm7 hboot, s-off, insert coin cm7 rom, have phone freezing in diferent situations, sometimes its working sometimes just freezez and i need to get battery out and turn it one and sometimes several times in row to get it working again???? RUU and go to give phone in service? plaese advice?
@cp6ija Sandisk SD card? If yes, smash it.
nvm
cant delete post so just posting gibberish
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
aaronpaws said:
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
Click to expand...
Click to collapse
Would it be possible that you tried so many combinations that the phone's battery has died? Have you tried plugging it in and seeing what happens?
charged for four hours and nothing.
Took it to a tmobile store and they're doing a warranty exchange since they couldn't get it to do anything either, even with a different battery.
Kind of curious as to what'll happen when I send it back since it has cyanogen mod 7 on it and its rooted. Then again, the phone won't boot, go into download mode, or recovery.
edit: I'm thinking the phone won't charge because of the custom kernel in cm7. Don't know how I would flash a kernel if I couldn't get it to boot though.
Dam,, too late
But for reference try!
Take the battery out and let it sit for a few min the put it back in and see if it boots.
If it still will not boot
Take the battery back out
Plug in the USB cable connected to the computer
Hold down the volume up and down then
Put the battery back in.
You should get the option: Volume UP / Volume Down for Reboot
Hit Volume UP and go get some Odin love!
I still have the phone, I'm gonna try this now. Will update with results.
aaronpaws said:
I still have the phone, I'm gonna try this now. Will update with results.
Click to expand...
Click to collapse
Cool man, keep us updated.
Well, I tried both suggestions to no avail. Anyone else have any ideas?
aaronpaws said:
Well, I tried both suggestions to no avail. Anyone else have any ideas?
Click to expand...
Click to collapse
I did not see you mention it, but did you try the "10 second" power button hold? You know it works when the phone vibrates 3 times. Simply hold the power button until it vibrates. It takes about 7-10 seconds (although when you think your phone is bricked, it feels like it is taking 5 minutes). If it vibrates, you are in the clear. You can usually get to recovery or odin from there. Try doing this on battery only first.
no cigar with the hold for ten seconds method on the power button.
aaronpaws said:
no cigar with the hold for ten seconds method on the power button.
Click to expand...
Click to collapse
It is really, REALLY difficult to brick a phone unless you are changing the radio (for example, flashing a wrong or corrupted radio). A kernel can hose your phone, but not brick it as you don't need a kernel to access recovery. A bad recovery could also brick your phone, but then you have download mode (Odin) to access that bypasses recovery. In other words, there are layers of protection or access points. We have not flashed any new radios for our phones yet, so you know that is not the problem. Having said all that, that does not mean you are not bricked.
To be clear on your position, you are getting no power response at all? Again, try this:
Unplug your phone;
take battery out (wait about a minute before replacing battery);
replace battery;
"10 second" hold until phone vibrates 3 times (or vibrates at all for that matter);
If you see no sign of life, then try the above process with phone plugged in (try plugged into computer and wall socket separately). Odin recognizes when you are plugged into computer and the boot process goes differently.
As for Odin bootup:
Load Odin;
Plug in your USB to computer;
try the volume/power boot up;
if that fails, try the "10 second" hold boot up with Odin running on your system and phone plugged in.
Outside of that, I can not think of any other way to get you to recovery or Odin.
I have flashed my android phones probably 150+ times in the last 2 and a half years and never made a brick. I thought I had, but was always able to get to recovery or bootloader (think Odin for HTC), and recover the phone. The only times I ever saw anyone truly brick the phone was when flashing the wrong or bad radio for their phone (radio is your 4G / cell receiver). So, walk through your processes to recover your phone in a methodical way and if that all fails, then return it. If you can't get it to go trying all these techniques, then T-mobile probably won't be able to as well and see that you rooted it.
Hope this helps.
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
What happens when you pull your battery, put it back in and attempt to turn your phone on?
Sent from my SGH-T989 using Tapatalk
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Are you seeing anything on the screen?
Sent from my SGH-T989 using XDA App
aaronpaws said:
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Click to expand...
Click to collapse
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Typically with Samsung phones, if you can get ANYTHING at all to show on the screen it is not bricked.
Do you have a G+ account? If I can see what is going on while I walk you through it it would be easier. Could possibly hold an open hangout so others can join in and help or just for informational purposes.
I have had soft bricks on my behold 2, vibrant and SGS2, over 100 times all together. Sometimes it takes a little fiddling, my SGS2 seemed a little more difficult only because of the relative simplicity of it compared to the others.
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
mikeyinid said:
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well i think he said it did boot initially, so I doubt that is the problem.
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
btyork said:
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
Click to expand...
Click to collapse
That depends if they can tell or not.
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
aaronpaws said:
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
Click to expand...
Click to collapse
Let me know, G+ is easy. Im out of class at 2est.
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
more like it wasn't plugged in properly to begin with
because that happened to me, even though it said "charging"... it was stuck at 43% for like 4+ hours, so i figured something must be wrong
and indeed it was, so i unplugged it, and plugged it back in, then voila! now it starts to charge as it was supposed to.
the phone is not picky by any means, i've used my old BB charges with it, the other HTC charger, the other samsung USB, the generic cheap chargers i get from Deal Extreme, etc
they all charges the phone just fine and fast
you do have to be careful when you plug it in, and make sure it's really charging
sn0warmy said:
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
Click to expand...
Click to collapse
Okay I recently wrote a thread about the random restrarts on my g3 that happened 10 times a day, but the things have gone too far. As i was having random restarts when I monstly use the camera but not only for about 5 days and some of those restarts were also shutdowns now the problem is more serious. Today i was intending to take a picture of something and as usual the phone restarted but STUCK on the startup boot "picture" that says that lifes good and then goes black screen and startup picture and black screen and so on. I wasn't able to use the phone. I pulled out the battery and tried again but it didn't worked. So as I went home i plugged the phone ot the charger and when i powered it on it started normally and tried to take pictures and there weren't any problems. So I think that this is the battery that is making this **** to happen. I highly doubt that this is software problem but from my quick examination i think that the problem is from the battery . What do You think. Tommorow i will go to my carrier and "ll try to explain them about this. But they are usually jerks who don't know anything about phones. They only know how to get your money.Anyways. Yes.
discoverymen1999 said:
Okay I recently wrote a thread about the random restrarts on my g3 that happened 10 times a day, but the things have gone too far. As i was having random restarts when I monstly use the camera but not only for about 5 days and some of those restarts were also shutdowns now the problem is more serious. Today i was intending to take a picture of something and as usual the phone restarted but STUCK on the startup boot "picture" that says that lifes good and then goes black screen and startup picture and black screen and so on. I wasn't able to use the phone. I pulled out the battery and tried again but it didn't worked. So as I went home i plugged the phone ot the charger and when i powered it on it started normally and tried to take pictures and there weren't any problems. So I think that this is the battery that is making this **** to happen. I highly doubt that this is software problem but from my quick examination i think that the problem is from the battery . What do You think. Tommorow i will go to my carrier and "ll try to explain them about this. But they are usually jerks who don't know anything about phones. They only know how to get your money.Anyways. Yes.
Click to expand...
Click to collapse
here is a gif showing what exactly is happening
discoverymen1999 said:
here is a gif showing what exactly is happening
Click to expand...
Click to collapse
Are you rooted? Did you flash anything? Did you edit any system files? Looks exactly like when I bricked my phone. There is a fix. Check out this thread and the links in it. http://forum.xda-developers.com/lg-g3/help/lg-g3-unbricking-steps-clarification-t3119844
Also can you access download mode or recovery. You might want to try them first.
No I havent rooted it or made any system modifications. This problem occurs only when my phone isnt charging. When iits charging even at 100% there isnt any problem
I've gone to my stupid carriers office and explained everything but they do not want to give me a new battery unless they bring the phone to the other end of the country for repair. This is extremely stupid. Now I can't use my phone because its totally "bricked". I xan only use it with my original dc charger if i unplug it the phone shuts off. Yesterday Ive decided to make a factory reset, but i wanted to copy my internal storage to my pc, but the phone won't turn on when its plugged to the pc. I don't know what the **** is happening with this 500 piece of pancake.
well i have finally decided to do a factory reset but after the anticipation and thinking it is a software problem it isn't apparently. Maybe i will just send it to repair and hope that i wait less than 20 days for it to come back. And i hope that they don't figure out the problem and send a new phone but i think it is the battery that is the problem. Anyways the modern technologys are the most incredible thing and the most getting you pissed of one. You pay 500 dollars+ and expect something good and there you go .
So did you do factory reset or not?
Btw, getting phone to repair center is a good decision, they'll see what's wrong.
I have been happy with my G3, only "minor" thing I don't like is the horrible backspeaker (coming from HTC One m7)
Well, I'm at wit's end. I'm usually pretty decent at borking and consequently unborking a phone. But I think I'm stumped this time; and am hoping that the community here can help me out. Though, to be fair, I suspect that rolling back to my old phone and eventually buying a new one is my only recourse.
So I imported an H815 Open EU from Handtec UK. No real issues on that front. I eventually unlocked the bootloader, flashed TWRP, and used the KDZ method to (clean) flash my way up to Europe OPEN H81510D initially, and then around two months ago, to Europe OPEN H81510E. I've been running that software without issue since that clean flash. And all this time I've been rooted through the TWRP method.
While this is (was?) my first LG phone, it isn't my first Android experience. So I've been using TiBu to back up my apps nightly, was running Kickoff's lovely hybrid theme, and had a few Xposed modules activated to tweak my experience a bit from stock behavior. I was curious about Marshmallow, but autoprime's warning that it could be non-final test software and the fact that Xposed doesn't work on it kept me from indulging that curiosity.
Everything has been going swimmingly until today. No major issues that I couldn't solve on my own. Certainly nothing that booting into recovery and clearing caches didn't fix. I was out and about engaging in a chat via Hangouts with a friend when my phone suddenly crashed and black-screened. I wasn't plugged into the wall or my PC, and I hadn't performed any kind of major update since the 10E flash a month or two ago. I had not installed any new Xposed modules or any rogue Google Play store apps. I was just using my phone normally and it crashed.
I popped out the battery and played around with it, trying to get it to boot up. I couldn't access recovery or even get beyond the LG logo. It would just hang there and after a few seconds, black-screen. Only popping the battery out and reinserting it would allow me to try again. I eventually left it alone until I got home, at which point I figured I'd try for download mode and reinstall the 10E KDZ via a CSE flash. It's always been a last resort, but a reliable one. I successfully performed the CSE flash of the 10E KDZ.
I thought it did the trick, as I got past the static LG logo for the first time and saw the LG boot animation, but it hung towards the end of the animation and black-screened again. Tried a few more reboots. Recovery mode still not accessible. Download mode was only accessible every third or fourth attempt. Finally got back into download mode and figured I'd try to roll back to 10D (I still had the KDZ I had previously used saved, just in case). Everything seemed to start going fine. Download mode's circle arrow animation on the phone was doing its thing, and then I hear the USB connection drop out. The arrow animation hangs, and the phone black screens. LG Tool 2014 spits out an error I can't read (the software is all question marks for me at this stage). Before it black-screened, it appeared that download mode hadn't progressed beyond 0%.
Now the phone is completely unresponsive. Popping out the battery and reinserting shows no signs of life. No USB sounds from my PC. No static LG logo. No recovery mode or download mode. Not even the lonely flash of an LED.
I've never had a phone hard brick, but I imagine this is what it tastes like.
So I'm probably out of luck, right?
I apologize for the long story. Thanks in advance for sticking around.
Maybe a stupid question but still deserves to be asked, what does pluging the phone in a wall socket gives you?
Sent from my HUAWEI MT7-L09 using Tapatalk
that is strange to happen randomly. The same thing happened to one of my old devices, a 1st gen moto atrix after I dropped it. I can get it to boot up but eventually it acts like the battery is pulled and just reboots. I'm convinced some wires or chip has been damaged inside even though it was only a 2 foot drop on thick carpet... not a whole lot you can do off warranty. Good luck.
Yeah, I figured the phone was toast. Of course the only time I hard brick a phone, it'd be the one time I import one from another country. Alas.
I think I'll return to my Galaxy S4 for now and pick up a Moto X Pure in a week or two, if no other ideas or opportunities present themselves.
As for having the phone plugged in, I just mentioned it in passing in order to rule out a power surge or short or whatever. Just to be completely clear about what I was doing with my phone.
There are already a few other threads on this man. Try to read first and post. Probably it's a motherboard problem. See the date of manufacturing of your device.
I read completely through the first 5 or 6 threads I saw on bricks and was overwhelmed by Marshmallow woes. Mobo, huh? That's a damn shame. Thank you.