Related
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Creepazoid said:
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Click to expand...
Click to collapse
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Creepazoid said:
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Click to expand...
Click to collapse
I wasn't being sarcastic, however this is me now saying you're probably screwed.
Sent from my DROID BIONIC using xda premium
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Haha, alright, well thanks again for the heads up on the one-click, definitely going to come in handy in the future.
Sent from my MB860 using XDA App
beidave said:
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Click to expand...
Click to collapse
He said he's tried a few different batteries.
Sent from my DROID BIONIC using xda premium
So what was the verdict? Mine just did the same thing. However, I Have followed all of the directions everytime i've flashed and never had an issue til right now.
If you can't get the phone on at all, no fastboot or anything. No hardware buttons do anything, nothing comes up on the screen with anything you try....
That's a hard brick.
= requires a new phone
No way to fix it.
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
When I messed up my flash and my phone was stuck at the dual-core logo, I followed the steps below.
Pull your battery.
When you put it back in, hold down the power and volume down to access fastboot mode.
From there you can do a one-click restore method.
That is how I solved my problem. I hope it helps you.
Sent from my DROID BIONIC using xda premium
nickbeisher said:
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
Click to expand...
Click to collapse
have you triedf pulling the battery and putting it back in. the hold volume key down and power at the same time? if that works then just restore using fxz. if it does not work your phone is bricked
Brick!!
This is my third droid, I had The D1, the X, and now the bionic. By far I like this one much better than the the others. I have rooted all of them, and done the basic app freezing, overclocking, and other basic mods. This is my first go round with the custom rom flashing. I Flashed R3blurr3d, and every new update ( each update a new flash ). I also flashed D3blurr3d, and Liberty, just to check them out. I personally like Reblurr3d. When I flashed I always followed every direction to the letter, and if I was unclear on something rather than ask a stupid question, or ask something that had already been covered. I read and search until I find the answer I need and it is clear to me, sometimes that means searching for hours on end. I do this for the fear of ending up with a "Brick".
Now with everything I have read about any of these phones to "Brick" It is an error on the user's end while flashing or something of that sort, ( not following directions ).
So with everything operating butter smooth, and flashing dozens of times before this. What would cause a "Brick" during everyday use?
My guess is....he didn't know what he was doing. You rooted it for him and left it rooted for a user that knows nothing about root access. He probably did something using root access to fck something up.
When someone asks you to root their phone for them, the answer is always no.
Unless they know what they're doing, never give someone root access.
my first bionic did same thing. it was not rooted yet. just started rebooting it self. got more frequint then just quit the way you talked about. hardware problem.
Yes. That is what it is. It is a hardware issue, after talking to tech support it is a capacitor or something like along those lines, it stores battery power for times when more power is needed, like turning on the phone for instance. And when it randomly boots it is because it runs short on power due to the faulty hardware.
But apparently it is a known issue with Verizon, so if it happens to anyone else they should not have any trouble getting a new phone. I talked to a very nice tech support agent, and I will have a new phone by noon on Saturday.
And also I didn't have anyone root my phone, I do all of it on myself, Im no computer genius, but like I said I take my time and follow directions. And until now I have had no issues, and this had nothing to do with root access, flashing custom rims, or any other tweaking just a bad part Anthe phone. The thread was started by someone else. When I searched the threads, I found this and it was the same exact problem as I had, so that's why I asked what the end result was.
So with all that being said maybe this will be informative to someone else.
Hi everybody,
I was (am?) running CM 10.1 for a couple days just to see how it was, and it was nice. I was going to make it my daily driver until I got a call while the phone was in my pocket and suddenly, the ringing stopped. I took the phone out of my pocket and tried to unlock it. No cigar. It must have powered off. Pressed and held. Nothing. Bootloader? Nope. Try under the halogen work lamp. Nope. No charging light, no splash screen, nothing. Just a brick.
How is it possible for the phone to just brick itself like that? I remember setting the max clocking speed at 1.5ghz and the governor to "conservative" but that's really it. Plus I had rebooted a couple of times between then and now. I ddon't have many apps, let alone many that have root access. So what's up?
Please help me. I give my battery 15 maybe 24 hours before it dies and I can't boot.
Oh yeah. I don't have S-off, I got my version of CM from get.cm, no custom kernel, or any mod of any sort. The phone was not actively doing anything, except for sitting in my pocket. I held the power button and the power + volume for a good 20-30 seconds.
EDIT: Is my only option to play dumb and ask for warranty? D': I don't want to do that because the rep who traded in my GS2 noticed that it was rooted. I'll probably get denied.
Seriously, anybody? What are my options? What caused this? Is it my fault?
I wish I had some insight on why that happened to you or how to fix it. What I can say is that I was thinking about flashing my first AOSP rom in the near future but was iffy on it. Now I'm super iffy.
I suppose there is a possibility that it was not software related. Maybe the phone is just a clunker? Hopefully someone more knowledgeable than myself can comment.
try posting this in the CM 10.1 forums and you will get a result. sorry.
Sent from my SGH-I747 using xda premium
SantinoInc said:
I suppose there is a possibility that it was not software related. Maybe the phone is just a clunker?
Click to expand...
Click to collapse
That's a possibility, and what I'm thinking too. Surely someone would have noticed if their phones blew up when they received a call right? The phone wasn't doing anything I hadn't done before (i.e. receiving calls).
You think Sprint will replace it? It's pretty much mint other than the software.
And there is no HTC One Cyanogenmod forum yet.
EDIT: So is it safe for me to go to the store and tell them it crapped out on me? Will they be able to tell that I rooted it?
Have you tried using the HTC charger that came with the phone and letting it charge for for an hour? If the phone got completely discharged it may take up to 10 minutes just to lite up/
RJR
rrusek said:
Have you tried using the HTC charger that came with the phone and letting it charge for for an hour? If the phone got completely discharged it may take up to 10 minutes just to lite up/
RJR
Click to expand...
Click to collapse
First off, Lithium ion batteries do not completely discharge, ever. If they do, they are ruined. Your phone will turn off before it lets the battery drain.
Second, I had at least 80% charge left when it bricked this morning. But what the heck, might as well.
EDIT: Wow. I googled hard bricks and pretty much every case is some kind of update or flash gone wrong. Nobody was just walking around when their phone bricked. This is weird. Considering how rare hard bricks are and the fact that the only apps with root access I had were Ti, File Manager, Spirit and Nova, I'm inclined to believe this is a hardware issue. But I can't be sure.
Bumping. I only have a little while before my charge runs out.
Hmmm, do you know, or have an idea what the battery life was when the incident occurred?
==
EDIT: Oh I see...
I unplugged it about 3 maybe 4 hours before it bricked. It had maybe an hour of screen time then. I'm assuming I had around 80% when it bricked. I have no idea how much power the device is currently consuming. But if it's truly bricked, prolly not much, so it'll last for a while.
If it isn't truly bricked, then probably not that long...
Guys, I'm desperate. I'll try absolutely anything.
All right, it seems like I'm done. This device is toast. Even though it seems like I didn't make any mistakes. I know that almost for sure because my phone was ringing when it bricked at 12:36 P.M. today.
Based on what I've said, does anybody think I am COMPLETELY to blame for this? I don't want my conscience to eat me alive when I take this is for warranty and play dumb. I truly believe this has nothing to do with rooting/custom ROM. I really believe this is a defective phone. Am I wrong?
Did u try the bright light trick
Sent from my HTCONE using Tapatalk 4 Beta
Try the bright light trick...
You can't even get into the boatloader? Or does anything show up when you plug it into the computer?
Sent from my HTCONE using xda app-developers app
sauprankul said:
Hi everybody,
I was (am?) running CM 10.1 for a couple days just to see how it was, and it was nice. I was going to make it my daily driver until I got a call while the phone was in my pocket and suddenly, the ringing stopped. I took the phone out of my pocket and tried to unlock it. No cigar. It must have powered off. Pressed and held. Nothing. Bootloader? Nope. Try under the halogen work lamp. Nope. No charging light, no splash screen, nothing. Just a brick.
How is it possible for the phone to just brick itself like that? I remember setting the max clocking speed at 1.5ghz and the governor to "conservative" but that's really it. Plus I had rebooted a couple of times between then and now. I ddon't have many apps, let alone many that have root access. So what's up?
Please help me. I give my battery 15 maybe 24 hours before it dies and I can't boot.
Click to expand...
Click to collapse
i knew there was something going on here, between cm10.1 and the sprint htc one ? sure makes me wonder, i've been on my replacement for nearly 2 weeks now running stock rooted with s-off. http://forum.xda-developers.com/showthread.php?t=2310750
Ok I just read your thread and was wondering. did you get your 150 back?
Either you and I are incredibly unlucky or the m7spr cm 10.1 is suicidal.
Just a question. in general, what setting were you using? Anything similar to mine? I had also set notification light to "long". how about you?
sauprankul said:
Ok I just read your thread and was wondering. did you get your 150 back?
Either you and I are incredibly unlucky or the m7spr cm 10.1 is suicidal.
Just a question. in general, what setting were you using? Anything similar to mine? I had also set notification light to "long". how about you?
Click to expand...
Click to collapse
I was told I would be refunded on my next bill so i'm waiting it out to see before I send back the bricked one. no i was stock-cm and what I mean by that is i installed cm10.1 added my apps, set up my home screens and used it like that until it died. i changed nor tweaked any of the settings from cm defaults
The same thing happened to my room mates HTC One yesteray. I first installed CM, and it was getting extremely hot, so I decided to try rootbox, similar issue, and the device was discharging far too fast. He turned the phone off to wait for me to get home so I could try to fix it. I got home, and there was no sign of life, it was charged fully before he turned it off. It wouldn't turn on at all. I had him take it to sprint and do warranty, they said they needed to open it(LAWL). He went back an hour later, they couldn't open it of course. They handed him a new phone.
Have you tried plugging it into a pc to see if it recognizes anything in device manager? Checked adb devices and fastboot devices?
I have. And nothing. No charge no power no recognizing
Sent from my HTCONE using Tapatalk 4 Beta
The screen acts as if someone is pressing random buttons and swiping etc. It does it for seemingly no reason at random times and sometimes only lasts a few seconds and other times lasts for 10 minutes or so. It is very annoying and makes using the phone impossible whilst it is happening.
I am rooted, S-OFF and running a 4.4 GPE Rom.
My actual carrier is EE so it wasn't originally a GPE if that makes a difference!
Thanks,
Joe
It could be a small pieces of dust under the glass. Probably factory defect.
NeoCreator said:
It could be a small pieces of dust under the glass. Probably factory defect.
Click to expand...
Click to collapse
It's only a recent thing. I have had the phone for about 8 months now and it's only recently started happening in the last 2 months or so which makes me think it isn't a factory defect.
smartiejoe said:
It's only a recent thing. I have had the phone for about 8 months now and it's only recently started happening in the last 2 months or so.
Click to expand...
Click to collapse
i had the same problem and i only had the phone for 7 months
fuzziion said:
i had the same problem and i only had the phone for 7 months
Click to expand...
Click to collapse
What did you do about it? I was hoping it was something to do with ROM and I could just restore it.
smartiejoe said:
What did you do about it? I was hoping it was something to do with ROM and I could just restore it.
Click to expand...
Click to collapse
i had a warranty so they give me a new one
smartiejoe said:
The screen acts as if someone is pressing random buttons and swiping etc. It does it for seemingly no reason at random times and sometimes only lasts a few seconds and other times lasts for 10 minutes or so. It is very annoying and makes using the phone impossible whilst it is happening.
I am rooted, S-OFF and running a 4.4 GPE Rom.
My actual carrier is EE so it wasn't originally a GPE if that makes a difference!
Thanks,
Joe
Click to expand...
Click to collapse
Its hardware issue, i'hv had this issue before you have to send in for warrenty, the more you leave it alone the worst it gets.
i used to have the same problem on My Desire X, nothing on Htc One but as soon as i deleted the Super User app & Unrooted it, it started working fine....
My little Fire's been working great for a couple of weeks with CM installed then today it just refuses to switch on.... I've tried charging it but there is just no signs of life not even a dead battery indication, no Amazon logo or anything...
I'll take it back for a replacement tomorrow, still only 3 weeks old, hoping the replacement is still on 5.0.1
Anyone else has any similar problems?
Did you just return it?
Can you go to recovery?
FredBloggs13 said:
My little Fire's been working great for a couple of weeks with CM installed then today it just refuses to switch on.... I've tried charging it but there is just no signs of life not even a dead battery indication, no Amazon logo or anything...
I'll take it back for a replacement tomorrow, still only 3 weeks old, hoping the replacement is still on 5.0.1
Anyone else has any similar problems?
Click to expand...
Click to collapse
my replacement came with 5.0.1. saved me from the locked 5.1.1 i was on.
Welcome to the dead Fire club. CM12-1 is something you want to try - I moved my wipe to the front of flashfire, like was suggested. It wiped & then never finished the load. Probably some quirk in ff that doesn't like CM12-1 so much - who knows. Waste of $50, so I'll order another one after I try the support folks.
So after doing a factory reset it now refuses to even turn on. I factory reset last night (But I was on 5.3.2.1 so I was able to disable ota.) This morning it was off when it shouldn't have been. Plugged it in and the low battery indicator came up. Weird because there was 50% last night. (I also noticed it was getting much hotter than it should be.) Now it won't even show that if I plug it in. I could hold the power button for 7 minutes straight. Nothing, zilch, nada.
Jake1702_ said:
So after doing a factory reset it now refuses to even turn on. I factory reset last night (But I was on 5.3.2.1 so I was able to disable ota.) This morning it was off when it shouldn't have been. Plugged it in and the low battery indicator came up. Weird because there was 50% last night. (I also noticed it was getting much hotter than it should be.) Now it won't even show that if I plug it in. I could hold the power button for 7 minutes straight. Nothing, zilch, nada.
Click to expand...
Click to collapse
How did you disable OTA updates on 5.3.2.1 given that build is not rootable? As for the non-responsive device, symptoms suggest a hardware failure or attempt to down level to an invalid FireOS build.
Davey126 said:
How did you disable OTA updates on 5.3.2.1 given that build is not rootable? As for the non-responsive device, symptoms suggest a hardware failure or attempt to down level to an invalid FireOS build.
Click to expand...
Click to collapse
Remember that those under 5.4.4.0 or something I can't really remember can be "debloated" and it works to disable OTA updates. I had mine on 5.3.2.1 for months thanks to that. I forgot to mention. It did work today, but I left it charging and when I came back it wouldn't turn on. I think it's something to do with hardware, what a coincidence it happened right after I factory reset.
Well, I guess I might have to get a new device.
Jake1702_ said:
Remember that those under 5.4.4.0 or something I can't really remember can be "debloated" and it works to disable OTA updates. I had mine on 5.3.2.1 for months thanks to that. I forgot to mention. It did work today, but I left it charging and when I came back it wouldn't turn on. I think it's something to do with hardware, what a coincidence it happened right after I factory reset.
Well, I guess I might have to get a new device.
Click to expand...
Click to collapse
Thanks - forgot about the alternative OTA block which isn't 100% reliable but works for most. It's possible some previous debloating invalided the factory reset function. Pure speculation, but not out of the realm of possibility given the irresponsible actions taken by some the the debloat scripts. Lots of cow boys/girls whipping these things up.
Davey126 said:
Thanks - forgot about the alternative OTA block which isn't 100% reliable but works for most. It's possible some previous debloating invalided the factory reset function. Pure speculation, but not out of the realm of possibility given the irresponsible actions taken by some the the debloat scripts. Lots of cow boys/girls whipping these things up.
Click to expand...
Click to collapse
To be honest, because of my issue with the battery and the overheating issue, I think it's a hardware problem and it's just a coincidence that I reset it the night before. Lucky I did - resetting means I backed up stuff I needed. My screen was badly cracked anyway. It might be best to get a new tablet. Are there any non-Amazon ones that are of a cheap price and at least similar specs to this one? If I'm getting a new one I want one I can root and possibly install a custom ROM on. Being locked down isn't my style,
Jake1702_ said:
To be honest, because of my issue with the battery and the overheating issue, I think it's a hardware problem and it's just a coincidence that I reset it the night before. Lucky I did - resetting means I backed up stuff I needed. My screen was badly cracked anyway. It might be best to get a new tablet. Are there any non-Amazon ones that are of a cheap price and at least similar specs to this one? If I'm getting a new one I want one I can root and possibly install a custom ROM on. Being locked down isn't my style,
Click to expand...
Click to collapse
If you want root at a comparable price point look into a 3rd (not 4th) generation HDX 7 or 8.9. These devices will run circles around any Fire 7 or HD 8 and will give a HD 10 a run for the money. Fully rootable & bootloader unlockable with a nice selection of custom ROMs.
Davey126 said:
If you want root at a comparable price point look into a 3rd (not 4th) generation HDX 7 or 8.9. These devices will run circles around any Fire 7 or HD 8 and will give a HD 10 a run for the money. Fully rootable & bootloader unlockable with a nice selection of custom ROMs.
Click to expand...
Click to collapse
I don't think any device that can't have expandable storage is very practical though.
Jake1702_ said:
I don't think any device that can't have expandable storage is very practical though.
Click to expand...
Click to collapse
Depends on use case. 16GB HDX (11GB available) with a suite of powerful apps is my daily driver. Not even using 50% of available space.
Davey126 said:
Depends on use case. 16GB HDX (11GB available) with a suite of powerful apps is my daily driver. Not even using 50% of available space.
Click to expand...
Click to collapse
I barely used mine since the screen got cracked and I completely filled internal storage and only had 2GB out of my 16GB card remaining. So for my case, that won't be a suitable option.
Jake1702_ said:
I barely used mine since the screen got cracked and I completely filled internal storage and only had 2GB out of my 16GB card remaining. So for my case, that won't be a suitable option.
Click to expand...
Click to collapse
Not trying to change your mind but in my line of business what, why and where (among other curiosities) are paramount. Amazing what gets retained locally. I also understand the virtual appeal of a bottomless shoebox. Good luck in your search.
Davey126 said:
Not trying to change your mind but in my line of business what, why and where (among other curiosities) are paramount. Amazing what gets retained locally. I also understand the virtual appeal of a bottomless shoebox. Good luck in your search.
Click to expand...
Click to collapse
So due to financial issues, my brother might be buying me a new Fire. I'm 99.9% sure it's going to be a 7th gen (As that's most likely). What is the oldest firmware available for it? From what I've seen it seems to be 5.4.0.0? That version can be debloated right?
Jake1702_ said:
So due to financial issues, my brother might be buying me a new Fire. I'm 99.9% sure it's going to be a 7th gen (As that's most likely). What is the oldest firmware available for it? From what I've seen it seems to be 5.4.0.0? That version can be debloated right?
Click to expand...
Click to collapse
Correct on both.
Davey126 said:
Correct on both.
Click to expand...
Click to collapse
We're also looking at getting a 5th gen that has CM installed on it from Ebay. Looks like a couple other people are watching it also though, and I can't find any others that are rooted/have a custom ROM flashed.