So My phone is most certainly bricked this morning. I saw a few posts on the topic, as well as one that was locked. Seems that there a re more than 5 of us, can a mod by chance merge the posts, so we can start troubleshooting the issue, and keep it from happening in the future. I will describe what I have done, and maybe it will help someone come up with an idea of what binds us all to our bricks.
Once upon a time in a galaxy far far away I was a flashoholic:
So I get my black one in the mail, and start playing in the forums, seeing what's what, and I go about trying to moonshine, firmware doesn't match so it doesn't work, get her rooted, s-off with revone, and flash a few sense based roms. No problems. Try the cm rom listed in the first post of the 10.1 link, no gps, weak signal, back to sense. Finally get a few of the threads completely read, and find rc2 of 10.1 flash(using twrp 2.6.1.0, and I do all the wipes and format data, and factory reset before sideloading my roms) get it up and running, gps works, find the build.prop line to edit to get it to stick to sprint to work, and away we go, rom is good, problems are small, phone working exactly llike it's supposed to. I did play with trickster mod here and there, but didn't much care for the program. So was playing in original development, and saw that the twrp forum had new input, so I go into it, and see a new twrp available (2.6.3.0) dl, flash the .img, reboot recovery, wipe everything, sideload 10.1 rc2 again and gapps. Almost immediately noticed the temp on the phone was very warm, almost hot, and that was without being on the charger. It was bedtime, so plugged phone in, go to bed, get up look at phone, and its at 50 percent on the dot, and no red light. Houston we have a problem. So I start researching how to ruu back to stock, and just to see if it was the recovery, I flashed cwm, didn't like it, and then reflashed the older twrp, problem persists, well I really didn't want my phone to reach 0 percent battery, so the race was on, set phone on ac vent and charge it, take it off charger, it would drop 20 to 30 percent in five to ten minutes. Get ruu downloaded, can't get it to run, troubleshooting that, my battery plugged in is down to 6 percent and the speakers are hissing at me, when I see the problem, plug it in to the laptop, run ruu, watching phone, watching progress, complete!!! yes reboot phone, log in to gmail, get message about phone using more power than it's receiving (plugged in to wall again) and boom shutdown. So now I'm thinking to myself hrmm good or bad, red light says charging, go smoke a few cigs comeback in phone boots, and is charging, no errors, everything is running like it is supposed to, everything works. It's still very warm though for not running much of nothing, leave it in the cold air, and she charges up to 100% (albeit slowly took most of the day) unplug her, go to sleep, and about 3 hours later I heard the low battery warning, and woke up to my nice black brick. No red light, no pressing buttons for x amount of time, she is most certainly dead.
Hopefully this can help us figure out what is causing the bricks.
And only 3 more hours to the sprint store opens :victory: that's bound to be fun
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
phatmanxxl said:
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
Click to expand...
Click to collapse
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
I don't know, I love Slim ROMs but if it happens again Sprint will start asking questions and might investigate the phone, plus I got the last red phone in stock
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
How many brick threads have you seen in here on Sense roms?
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
Including folks that flashed gsm roms? Zero
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
i wont even flash an aosp rom on this phone i have seen a few people brick while on aosp.. and the dude i got my one from he bricked his first one running an aosp rom.. he said he rooted it flash an aosp rom.. was fine for a week or so the while listing to music on the phone it died brick.. im not saying its deff aosp roms but i have seen and heard enough where im not going to try it... lol im good with my sense:good:
I wonder what's the difference between GE ones and Sense ones.
raptoro07 said:
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
Click to expand...
Click to collapse
I guess you could summarize it like that, but I thought that I stated I knew it was going to die, shortly after I upgraded my recovery. All flashing after that was an attempt to troubleshoot/save the beast if at all possible.
Well I know what's causing the bricks.
So i figured out in part at least what is indeed causing the bricks. It was my first guess, but I messaged a couple of kernel devs, and the information they gave me led me to believe my first assumption was wrong. Apparently it was not. i am not sure if it's an aosp thing, a twrp (was using 2.6.1.0) when I found out, or just a really nice user error experienced by a handful of people. But regardless, either the kernel, and or some of it's settings are not being wiped in twrp to include an advanced wipe of all check boxes besides usbotg, a format data, and then a factory reset wipe. So when kernel or settings interact with new kernel/rom that you install and they don't play nice together, you get your nice little brick. Oh but how do I come across such preposterous conclusions you ask yourself? So I payed my 50 bucks, got my new phone, put my go to rom on it, and play away; lo and behold a stable 10.1 cm comes out. Can't resist, must flash, disapointing to see in the stable release the first thing I have to do is edit build prop to get sprint signal(it is a sprint rom yes?) Still liking the rom for what it is, probably my favorite, except Trebuchet is laggy as S**t(ping pongs kernels alleviate this, but his kernels are for 10.2). So in an attempt to fig the lag, i play with different settings and whatnot that I found laying around xda here and there. nothing is helping with the stutter I see on the home screen. So I go to the main One thread, and look around for kernels, I find one, don't figure it will work, but figure I'll just wipe if it does bad things to my phone; and it did. 8 boot loops later what do I do? Wipe everything as mentioned above, and sideload 10.1 stable, guess what happens on reboot? That's right bootloops. So some how the kernel or some of it or its settings at least are not going away as they should on a clean install, and that I'm sure is what is causing the bricks.
Ty,
I'll be here all night
You sure do keep a really good attitude through it all though. We've all been there but you are purposely putting yourself and wallet through it over and over to find the culprit. I for one appreciate it.
D
Related
I was wondering if I was missing a post. I still get random Cyanogen Shut downs. I am using 4.2.13 after a wipe and still experience random shutdowns.
The phone just goes dark and I have to power it up again.
I have read some people attribute it to locked home screen and some people while using locale.
It is quite frustrating and I was wanting to know... if there isn't a fix, what Rom should I port back to. I need to clear this up because it gets aggravating missing calls.
Give superD 1.2 a try or even dwangs ROM they both are very speedy and well stable
Try re-flashing the rom, or you can try another rom as you said...i recommend Super D or WG Build....i myself use WG Build
You might be running out of system space.
Go to console:
$ su
# df
Check the Available next to /system. 28mb should be normal, but you could always apply the 10mb ramhack. Go with CFS for stability.
Can you recreate the scenario by which the phone will reboot on it's own and get a logcat?
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Brutal-Force said:
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Click to expand...
Click to collapse
Try Enoms rom if you tried Super D and WG-Build Y-2.6 with no success.
The problem you have is definitely weird.
I also suggest updating your Radio, Spl and RA Dream to the latest versions.
If possible try another microSD card preferably Class 6 to see if that fixes your problem.
I've been experiencing this same thing with random shut downs. I am running 4.2.13 also.
I have tried a wipe and re-install but the problem still exists.
There doesn't seem to be any rhyme or reason to it. The only thing I can say is that it always happens after the phone has been idle and when I go to pick it up it's powered down and I then need to power it back up.
It is very frustrating becuase you're never fully aware that the phone is off until you go to use it. I don't know if it's the ROM or some program that I've installed. I've been uninstalling all recent programs but so far the problem still exists. Perhaps I'll try one of the other recommended roms.
I have tried the stock rom and Dwangs rom, so I doubt its the ROM. Also I installed minimal applications and it still happens.
Its a toss-up between battery and phone. Although my battery is an extended battery, it can happen even when the battery is at 80%+ charge.
I called T-mo and they are going to swap out my phone. When I get it I will run the stock rom for a couple days with my Extended Battery. If it continues, I will put the stock battery back in it. Then I will go back and root it. If the problem comes back, then it has to be the rom.
Brutal-Force,
I'll eagerly wait your results. Unfortunately I purchased my G1 off of ebay a year ago so if it is the phone I'm out of luck.
Out of curiosity do you use Nitrodesk Touch down for Exchange? I've had some reboots right in the middle of synchronizing my email with this program.
Thanks
No I do not. As a matter of fact, I had uninstalled almost everything in an attempt to track down the culprit.
I really do think its gonna end up being the battery. Since the phone is not an option for you, I would recommend trying out a cheap 10 dollar battery off the internet. While I can't imagine why a charged battery would do this, I have noticed by looking at a friends G1 that the phone interprets batteries in different ways. In his phone his battery never showed below 90% even though after 10 hours it would run out of battery. As soon as he put in on the charger it showed 90%.
I to had purchased one of the extended batteries shortly after purchasing the phone. It has worked fine for just about a year but perhaps it is beginning to have problems. I'll dig out the original stock battery later today and try that for a day or so and see what happens.
Thanks
I have the same problem. My phone randomly restarts. It's more of an annoyance rather than a big problem, especially since it's almost always a restart and not a shutdown. If you guys do indeed find out it's the battery do post your findings here!
Thanks
I have exactly the same symptoms. Though before I saw this post I was attributing it to the fact that I have recently dropped my phone.
I also have a spare battery (I'm using Andida instead of original now), so I'll test to see if that happens with the original too.
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
rckeystone said:
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
Click to expand...
Click to collapse
Its good that you guys are investigating the cause of this issue. I too admitingly started using CM when I first rooted my phone. I too had issues and FCs so changing the Rom was the first thing that came to my mind.
You never know maybe its the battery (see the 1700 battery thread on the many problems Andidas has had with their G1 extended batteries)
In the end I am hopeful that you find a solution and have found out sometimes its as easy as changing Roms to fix many complaints/issues you might have.
This is what I've experienced so far.
I did a full wipe of my phone yesterday and installed the AOSP ROM (went away from cyanogen) and I have installed most of my programs. So far all is great. I've had no reboots or any other issues. Since yesterday I have been using my extended battery so I know the battery is OK.
I can't say for sure what was causing my issue. I had been using cyanogen's ROM for quite some time so I don't have a reason to think it was the ROM unless it was one of the current updates.
Perhaps I just had a collection of issues that came to a head and it was time to clean the phone and start over.
Same Problem
Hi, First post here. Great site by the way.
I am having the same problem as you are. Cyanogen, manup's 2.1 (1.5) and the "official tmobile 1.6" rom would frequently reboot or shut off on me. I tried three different sd cards and completely wiped my phone everytime i went between these roms. After much frustration I unrooted my phone last week and went to stock 1.6. It was working perfectly fine but the terrible battery life convinced me to try rooting my g1 again. After going through all the steps the same symptoms came back. So in order to be able to use my phone I went back to the stock unrooted rom. I also would like to mention that before these symptoms came up I had my phone rooted since may 2009. I also tried various SPL's and recoverys while trying to resolve my problem. Thanks
Random reboots are the reason why I don't run CM roms for any length of time anymore. I do load them from time to time to check it out and what not, but more often than not, I always find myself back on a Dwang rom.
My new G1 should be arriving tomorrow, but it has been 2-3 days now with the original battery. No shut downs. While it will be nice to have a new phone (although my phone is unblemished) it will suck to have to re-root it. I am pretty certain its the battery.
I will recheck when I get my new phone set up, I will put the extended battery back in it. I am still pretty certain it is the battery though.
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One
Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.
I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue
Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman
The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE
Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman
I used to be a Droid 1 user and I played with a lot of custom ROMs. Got the Droid 4 on release day and I'm thinking of playing around with custom ROMs.
If I install the recovery and a custom ROM, isn't the factory restore option always on the phone so anytime I want, I can restore the phone to the day I got it?
Are there any downsides to installing custom ROMs as of now (such as battery, glitches, etc)
I rooted my phone and I've seen a decline in battery life. There is another thread about it but I wanted to ask here, anybody else have this issue?
Lastly, is it worth installing custom ROMs now or just waiting for the official ICS update? I basically just want a working phone with the best battery possible. The only reason I rooted was to uninstall the bloatware on the phone however wifi tether and screenshot are nice to have.
Thanks!
Installing any custom ROM right now is going to be a little risky simply because there are no fastboot files to restore your phone with. Now, SafeStrap does a pretty good job of minimizing that risk by creating what is essentially a dualboot environment allowing you to run a secondary ROM on your phone while leaving the stock ROM intact.
I am running the ICS Beta ROM by Hashcode and it is running really well for me. Battery life has been fine, pretty much on par with stock. Being a beta there are things that are not perfect but I am using it as a daily driver with no issues. You can find a list of known bugs in the ROM OP. Although it seems to be hit a miss with some of them. I have had no issues with wifi or mobile data connections at all.
I ran stock rooted for about 1 1/2 weeks and didn't notice any decline in battery life personally. Not I froze apps rather than uninstalling anything so I could get them back if I needed to. And I really didn't freeze much unless it was something I saw running in the background that I knew I wouldn't need/use.
Really, if you are just looking for a phone that works with the best battery life, you are probably better off staying with stock. In my experience with the Droid 2, no ROM I ran could touch stock for battery life. And really, I think the stock experience on the D4 is fine. The bloatware wasn't overly bad IMO, smart actions is pretty neat, and the UI was plenty snappy. I'm just a flashaholic.
I am quite happy with stock after debloating it.
Sent from my DROID4 using XDA
Thanks for explaining safestrap. Does it actually set up a dual-boot environment, or does it swap out /system, /data, etc. I've tried reading hashcode's blog, but the instructions are a little fuzzy on what exactly is going on. I don't have my D4 yet, and I'd like to get a handle on what exactly safestrap is doing before I take the plunge.
Currently I have a D1 and I'll fully admit I'm spoiled that it is essentially unbrickable. Once, I screwed it up so bad that it wouldn't even boot up into recovery. I have no idea how I managed that, but a quick session with RSDlite fixed everything...
Of course, I know a lot more now than I did back then, but here is hoping we get hold of some fastboot images for the D4 soon...
I finally took the plunge and installed Safestrap. Once your phone is rooted, you just run an APK installed on your phone. The process feels incredibly clean, and I was completely comfortable that as long as I was careful, nothing bad would happen. This proved to be true.
It really does set up a dual-boot. I spent several hours today playing with CM9, and when I was done, I simply disabled the safe system, and the phone booted right back up into my rooted and debloated stock. The most dangerous part is making sure that you do NOT try to flash over the non-safe system, and, in fact, Safestrap generally won't even let you do that.
Not only did I find that Safestrap worked great, but CM9 works better on the Droid 4 than almost any other device I have played with it on. If they can make sure that the data connection is reliable and get the font camera working, it is practically ready for prime time. Everything else works great. I am now confident that we will see CM9 for the Droid 4 as soon as CM itself is complete and stable, since drivers do not seem to be a problem on this phone. I also suspect we will see some CM7-based roms quite quickly as well.
I am also very glad of the option to always easily revert back to the stock system without losing anything, it will make going to the Verizon store very easy if I ever need to.
I also came from a D1, installing ROMs was so easy, I'm a little hesitant on this one especially since a genuine ICS update is on the way. I might wait for that before I try custom ROMs. I use a front camera a lot so CM9 is unfortunately out of question. My battery issue was solved with a calibrate (deleting batterystats) even though it's not supposed to work, I can confirm that it definitely worked for me.
Once you toggle on the safe system, installing ROMS is just as easy as it was on the D1. What is nice, though, is you can keep your stock system fully in tact. I actually keep my phone on a simple rooted stock, but when a friend asks about Android ICS, I just toggle on the safe system, and boot it up. When I'm done, I toggle off the safe system, and back to stock. Safestrap is awesome.
core2kid... this is moto, the official update is gonna take 3-6 months so i would not suggest waiting it out.
i came from a D1 as well and safestrap bugged me out for a while... but once i installed and started using it i really like it. think of it as a dual-boot.
1 is your stock system that you do not f** with... you just leave it so that you have a backup should you f** up your...
2nd system is the one you flash all your ROMs on... no matter what you do to it, the first system is not touched, so you have to try REALLY hard to brick it.
Thanks. I'll give it a go. Last question, if I have hardware issues with the phone, is there a way to restore it to factory so I can warranty it? My main concern is my battery dying. I don't want to be stuck with a useless phone because the battery is in built.
i cant say with 100% certainty, but theres got to be a way.
as for the battery... it will probably die the day after your warranty is up, and by then there will be DIY replacement kits.
greekchampion04 said:
as for the battery... it will probably die the day after your warranty is up, and by then there will be DIY replacement kits.
Click to expand...
Click to collapse
With my luck, I can see that happening :/
I just got my One a week ago today, and rooted it the first day as well. From last Wednesday to earlier today, I've had no issues at all with it; suddenly, audio is not working at all, either through the headphone jack or speakers. I thought it might be a ROM issue, so I reflashed the ROM clean (PACMan 4.2.2), and it still didn't work. I flashed 2 other ROMs, SlimBean and a Sense 4.2.2 based one, and the audio still doesn't work at all. I've done nothing that could've damaged it; I don't overclock, it's never gotten wet, nothing. Has anyone else had this issue, and know a fix, or do I have to return it to stock and turn it back into Sprint?
Also, another note- earlier today it was getting really hot for no reason- I wasn't running anything that would do that, no OC like I said. I Googled, and many people said it was a common occurrence due to the aluminum body dispelling heat from the internals. It went away after 20 minutes or so, so I figured it wasn't an issue. Could that have done some damage? Thank you for any help in this, I'm really worried since I just got the phone and it's already having issues. I've loved it otherwise so far, and owned 3 other HTC phones, and nothing like this has happened before, so I hope it's just a one time thing.
I don't have the audio issue with any rom I flashed, maybe your device is damaged. You can return it for a new one.
I also have the heat problem...
sent from my m7spr using tapatalk 4
I've been backing up my stuff to get it ready to take back. I hear the blue model's coming to Sprint on the 10th, maybe I can hold out a few more days and pick up one of those
Update- I've been trying all morning to restore to stock, and I'm getting worried now.
I went by this thread http://forum.xda-developers.com/showthread.php?t=2250904 to use that RUU to return to stock. I am trying to relock my bootloader in fastboot, and I get the error "[Err] Command Error!" each time I try. To use the RUU, I need to have a locked bootloader, but I can't get a locked bootloader because of that error. What might be wrong here? I am using the stock USB cable with a USB 2.0 port, Windows 7 32 bit.
Alright, it turns out that was due to a stupid error on my part. I have got my bootloader relocked, but now when I try to flash the RUU, I get the 171 USB Connection error. It'll get stuck on the black HTC screen at that point. What could possibly be wrong now?!?! If anyone has any tips, I can provide as much further information as you may need.
Alright, I have an issue that's been getting ridiclious the past few months. Ironically it all started when trump took office, but that's another subject....
On any rom besides a sense based rom, and i've tried alot, AICP, CM, Lineage, candy, etc etc. I'll have random reboots when getting text messages, or random reboots when trying to send a text message. I've tried all these roms wiped, with and without gapps, and i end up with the exact same result. Straight up random reboots.
The moment i wipe and restore the stock sense i imaged immeditately unlocking, no issues. I flash badboyz, no issues. I've been experimenting the past few months, and i can honestly say it only happens on non-sense roms. I thought it was because of gapps. So i ran CM11, which has been flawless since 2014, and without gapps, after a fresh flash and boot, the 1st text message i receive, instant hard reset.
The phone was s-on when i bought it, i took the latest OTA to grab carrier and OEM software and radios, then i did only the bootloader unlock, flashed TWRP, imaged my system. that was back in 2014 when the phone was first released. Since unlocking i've been running cm11 flawlessly for several months, at times a week or so of uptime, and i use my phone heavily.
Now it's to the point, when i flash a clean CM11, no gapps, just sitting on the table with the tethering on, either USB or wifi, it'll reboot. Sometimes itll get into a reboot loop and it'll take up to 10x of hard resets until it gets android fully loaded (mind you no gapps, no 3rd party, just the rom itself) before it's usable, that's if it doesn't run itself dead with the bootloops.
What's blowing my mind, if it's hardware, then why no issues on sense? Why only issues on non sense, and why now and not before? and the differences are all i can think of is software from: htc, sprint, google
When those 3 are removed, stability issues. but why now and all of a sudden?
anyone want me to supply something from adb? this has truly got me interested. I'm willing to copy and paste and upload some info. I'm really wondering what this issue is.
Thanks!
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
swerff said:
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Here's what I would say:
Because non-Sense ROMs don't have the same drivers, HTC developers, etc, they tend to be less stable as a group. The developers work hard to mitigate that, but the random reboots are the hardest for them to figure out. If you go through non-Sense ROM threads for years, you'll see that common complaint.
Now, as for CM11 being solid and now it's not, my guess is that updated firmware, radios, etc caused it. CM11 is quite a few years old and was written under older radios.
When the m7 was my daily driver, I had good luck on these three ROMs. They had the occasional reboot, but it was about once a week at most and rebooted right back in.
Resurrection Remix
PAC ROM
NusenSeven (Sense based from the m9)
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
swerff said:
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Misread and thought you updated radios recently. Not sure how replacing the battery would help, but you never know.
I had been running the three ROMs mentioned above with minimal issues when I used the m7 as my daily driver. I had run the latest RUU (see development section) to update to the latest radios, firmware, etc first. As I recall, all three were good. NusenSeven being stock based was most stable, but the others were good too.
swerff said:
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Worth a shot, but your instability seems relatively reproducible. Personally never done it. So I'm not sure that would help, but like I said before, you never know.
Well, tonight I'm going to replace the battery.
If that diesnt help, going to relock and ruu just to make sure, unlock and flash the same zip I've been using for years.
If there's still issues, something is going down regarding big brother not enjoying his stuff on my phone.
That's my take and opinion.
Sent from my One using Tapatalk
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
swerff said:
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Great! I'm glad it worked. It is odd, but what you say makes sense. Maybe the Sense ROM had something optimized in the kernel or ROM that the non-Sense ones don't. That's why I love this site; I learn something new everyday. Thanks for putting the results of your work in the thread for future members who may have the same problem.:highfive:
Well, update
It eventually got back into its old habits of randomly rebooting after ending phone calls or sending /receiving messages.
Soon after that it had issues if not coming out of airplane mode, which would require a hard restart, soft restarts were unsuccessful.
About week ago my son wanted to play on it, so i enabled airplane mode so he wouldn't accidentally call anyone.
Enabled airplane mode.
Handed phone to him.
Within 30 seconds I took it back, and in this time frame all he was doing was holding it/touching screen.
The phone now endlessly reboots to the initial HTC logo for maybe 5 seconds, goes black, and repeats. It will do this until the battery is dead.
Plugging in charger results in no battery charge state, screen or LED. After several moments of being plugged in with no signs of life, it'll light up to HTC screen, only 5 seconds later to go black and repeat, endlessly.
Holding power + volume down I can access the bootloader, which before it resets again I can pick recovery option.
It'll then reboot into HTC screen, saying entering recovery up at the top, but never doing so, and continue with boot loops.
The power button is not stuck, as holding only volume down will not encourage bootloader initialization.
Ideas?
swerff said:
Ideas?
Click to expand...
Click to collapse
It seems to have gone beyond the Sense working but non-Sense not working issues it started with. At this point, I'd probably try to RUU the thing back to stock and see if that fixes it. If not, I'd venture something hardware related. I wrote a guide on how to do this mainly because I kept forgetting all the steps. Hope it helps.
https://forum.xda-developers.com/sp...de-reset-phone-using-ruu-htcfastboot-t2876110
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
swerff said:
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
That's too bad. I don't know what to tell you my friend. I saw you could access the bootloader and select recovery, but if it's not stable enough to stay in fastboot, then that's beyond my knowledge capability. At this point, if it were me, I'd buy a new device or take it to a repair shop.
I'm investigating surface mount memory readers and the like.
I'm hoping to solder up something to pull the memory in binary.
The phone wasn't encrypted. There's a handful of photos I'd love to recover. Not having an external sdcard is stupid.
Sent from my One using Tapatalk