Related
Bad Kernel? Bad Radio? What?
I've used quite a few different ROMs. (Enom, Kang [CM], MIUI, and most recently, Rodriguezstyle's miui.)
But, the problem keeps happening, despite wiping between each ROM.
is it the radio? or the kernel? I think it might be, but I'm fairly certain I have the right kernel...and I upgraded my radio when I went to Froyo...
Gah.
I dunno about the kernel, but from what I've heard, if you have the wrong radio your n1 will be bricked. So I guess it's not the radio.
It's not a problem, I've been living with it. It's just rather annoying...
Maybe it's an app I have installed? Or things aren't...done right? Augh idk.
Change the Kernel and that will fix it, pershoot's worked the best for me.
Do you have to pull the battery when it reboots?
cmarti said:
Change the Kernel and that will fix it, pershoot's worked the best for me.
Click to expand...
Click to collapse
I've changed it to many kernels. Right now i'm using this one:
2.6.35.4-950mV-BFS-SVS-AIX-720p-Monks-082710
rickytenzer said:
Do you have to pull the battery when it reboots?
Click to expand...
Click to collapse
No. I will be chilling on the phone, and then I will randomly see the boot image.
if your nexus is still less than a year old, get a new replacement device
watch the logcat output (adb logcat), and also kernel messages http://bootloader.wikidot.com/linux:android:kmsg
khanh1289 said:
if your nexus is still less than a year old, get a new replacement device
Click to expand...
Click to collapse
I don't have insurance, I don't think...idk. I bought it outright from the google store...what would I have to do? Also, its unlocked, obviously...
hollywooder said:
I don't have insurance, I don't think...idk. I bought it outright from the google store...what would I have to do? Also, its unlocked, obviously...
Click to expand...
Click to collapse
Are you overclocked?
SiNJiN76 said:
Are you overclocked?
Click to expand...
Click to collapse
Not that I'm aware of. I don't even have setcpu installed anymore.
So unless the roms themselves overclock, then no. I upgraded my
kernel, but it has done a random shut off once since then. But it's
not that often. Not as often as it was at least.
Do you have more than one battery to try? My phone locked up or randomly rebooted several times a day when I was using Cyanogen 6rc1, but it only did it with one battery and ran fine with the other. The problem went away after I updated CM though.
My theory is that my "bad" battery is damaged slightly enough that it conflicted with something particular in that rom (also happened with 3-4 different kernels). I don't know anything about batteries, but if that's accurate, I don't see why a battery couldn't be damaged enough to conflict with all roms.
It doesn't sound like your problem exactly, but might be one of the simpler things to try, especially if you have a spare or could borrow one or something.
Try to extract the SD-card and Power ON the phone without it. If the phone works
well in that condition, problem solved.
Something like this happens to me one time, all I do was to format the entire SD-card
in my iMac with the Disk Utility, filling all the space with zeros (0) for be sure all the
data was erased correctly. Then I make the partitions again, flash a ROM and all
is fine now.
Good luck!
I had the same problem. Phone would reboot during many tasks. This would happen with any ROM even stock. I sent the phone to htc and they changed the motherboard under warranty. I noticed it first started to happen with robo defense and then other apps such as YouTube or browsing the net. I wasn't able to use the phone while it was charging or it would reboot.
wsrider said:
I had the same problem. Phone would reboot during many tasks. This would happen with any ROM even stock. I sent the phone to htc and they changed the motherboard under warranty. I noticed it first started to happen with robo defense and then other apps such as YouTube or browsing the net. I wasn't able to use the phone while it was charging or it would reboot.
Click to expand...
Click to collapse
My phone isn't that bad, and no luck with the sd card thing.
hollywooder said:
My phone isn't that bad, and no luck with the sd card thing.
Click to expand...
Click to collapse
I bought my nexus one in may. It got worse over time and i had it repaired in september
If you buy it off from google store, it comes with a 1 year manufacture warranty, call HTC and get a replacement device
khanh1289 said:
If you buy it off from google store, it comes with a 1 year manufacture warranty, call HTC and get a replacement device
Click to expand...
Click to collapse
I don't believe I ever filled out the warranty, can I still get it replaced?
Sorry for the double post, but I'm really curious...about the warranty thing.
sergioalvarezmac said:
Try to extract the SD-card and Power ON the phone without it. If the phone works
well in that condition, problem solved.
Something like this happens to me one time, all I do was to format the entire SD-card
in my iMac with the Disk Utility, filling all the space with zeros (0) for be sure all the
data was erased correctly. Then I make the partitions again, flash a ROM and all
is fine now.
Good luck!
Click to expand...
Click to collapse
This is my suggestion as well. A friend of mine had this problem. There was a corrupt video on his sd card that caused the entire issue.
ok so these days... i been using RA. alot probably flashing 30 times a day
because of the wifi problem.
the trackball decided to stop working
when i scroll it up it wont work.
scrolling down , left, right works.
(my phone is unlocked) <- i know it avoids the warranty.
so..i decided to take chance and call HTC about warranty
this is what im gonna tell them
that my wifi isnt working
and i didnt find it out till now cause i never used wifi, and used 3G. and recently i canceled my plan and i dont have data plan anymore
so when i tried to use wifi it didntt work , and tell them i already did hard reset and soft reset and even called my router's company and changed the setting of the router and they told me that it has to be the hardware problem of my phone
So, this is my plan
1, call HTC
2, tell them wifi isnt working and its a hardware problem
i have that strange screen touch issuse too when i hold the phone tightly and try to touch the screen it doenst work, and it thinks im touching the bottom of the screen so it goes into menu and dialer when im clicking the middle of the screen, or vibrate cause it thinks im clicking the capacitive button.
3. i'll demand a replacement, and when i send my phone back hopefully it will cover by warranty( i know unlocking the phone avoids the warranty but i know many people have succeded getting replacement eventhough their phone was unlocked)
4. when they receive mine and it turns out its not covered by warranty are they going to charge my 500 dollar.
or find out that my trackball is broke.
what things do that ask? when i call them ? did anyone go through the process? do they require credit card number and all?
bought my phone through craigs about 3 weeks ago i think
lost the number of the seller..( that son of [email protected]#@# told me everything was working when i got it the wifi wasnt working)
EDIT: should i just complain about the screen?
i doubt they're gonna test the wifi and all.
does anyone knows how they inspect their device?
in what awy do i have higher chance getting replacement without issue.
Complain about the screen not working properly which is hardware issue
complain about the wifi <--- could b cause of rooting and messing up idk..
well..i already googled it and trackball isnt covered by warranty..
i have AMOLED screen but..dont really care about if i get SLCD or not..
so just your trackball doesnt work?
just flash everything back to stock recovery partition and all, then call them and say your trackball stopped working
disgustip8ted said:
so just your trackball doesnt work?
just flash everything back to stock recovery partition and all, then call them and say your trackball stopped working
Click to expand...
Click to collapse
i already did but i heard that trackball are not covered by warranty.
It wont be a problem. I had trackball problems too and got a replacement by the end of the week. They don't care about your bootloader. Try it. It's as painless as possible. Stop worrying.
pwig said:
It wont be a problem. I had trackball problems too and got a replacement by the end of the week. They don't care about your bootloader. Try it. It's as painless as possible. Stop worrying.
Click to expand...
Click to collapse
Thank you i am going to call HTC
I'll keep you guys updated.
Update:1 nov-26-2010 , wow less than 10 min i went through the swap process, and got an email for credit card process. ..Now let's just hope they dont charge me $200 cause i rooted the phone!
eunkipark92 said:
Thank you i am going to call HTC
I'll keep you guys updated.
Update:1 nov-26-2010 , wow less than 10 min i went through the swap process, and got an email for credit card process. ..Now let's just hope they dont charge me $200 cause i rooted the phone!
Click to expand...
Click to collapse
you need to go back to stock rom. unlocked bootloader is fine, i suggest NOT sending it back without stock rom
andy2na said:
you need to go back to stock rom. unlocked bootloader is fine, i suggest NOT sending it back without stock rom
Click to expand...
Click to collapse
yup already put everything back to stock. FRG83D
update #2 nov-30 2010
got my replacement from HTC it looks like they sent me a brand new spanking phone
no dusts under the screen, no scratches what so ever, everything works perfectly
, and it looks have it has new parts(which means SLCD)
my old nexus one had dark grey-ish trackball and this one have white-ish light trackball. it looks like the notification light is brighter.
is going to send my old nexus one tomorrow or the day after tomorrow
hopefully they wont charge me.
will update soon
So they send you the replacement first? When u send ur old one do they fix it or do u keep the replacement. The vibrate on mine is screwed up so im thinking of sending it also
Sent from my Nexus One using XDA App
mac208x said:
So they send you the replacement first? When u send ur old one do they fix it or do u keep the replacement. The vibrate on mine is screwed up so im thinking of sending it also
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
When u call them, you have 2 choices, you can either do swap or do repair
in my case i did swap. they will require your credit card number
and you will have $530, pending on your credit card, you have to send it back your old n1 if you want the charge to be dropped
or you can just send your n1,which will take longer..
Rather than creating another thread for a similar issue...I am having issues with my power button. Sometimes it takes about 5 tries to get the screen to come on.
My question is, are they swapping with N1's or does the AT&T version get something else? I have heard about someone receiving a Captivate instead and I do not want a branded / locked phone.
eunkipark92 said:
update #2 nov-30 2010
got my replacement from HTC it looks like they sent me a brand new spanking phone
no dusts under the screen, no scratches what so ever, everything works perfectly
, and it looks have it has new parts(which means SLCD)
my old nexus one had dark grey-ish trackball and this one have white-ish light trackball. it looks like the notification light is brighter.
is going to send my old nexus one tomorrow or the day after tomorrow
hopefully they wont charge me.
will update soon
Click to expand...
Click to collapse
just a question, why do people dislike the SLCD version vs the AMOLED? Isnt SLCD better with battery life and easier to see in sunlight?
andy2na said:
just a question, why do people dislike the SLCD version vs the AMOLED? Isnt SLCD better with battery life and easier to see in sunlight?
Click to expand...
Click to collapse
AMOLED produces more vibrant and richer colors and SLCD creates a sharper picture and a warmer tone,
as far as i know amoled is a little bit better in sunlight, not by much. Its not the screen but its how htc makes thier glass.its like glossy and stuff)
and no amoled have better battery life
eunkipark92 said:
AMOLED produces more vibrant and richer colors and SLCD creates a sharper picture and a warmer tone,
as far as i know amoled is a little bit better in sunlight, not by much. Its not the screen but its how htc makes thier glass.its like glossy and stuff)
and no amoled have better battery life
Click to expand...
Click to collapse
yea, I JUST read the article on engadget comparing the Desire's Amoled vs SLCD:
http://www.engadget.com/2010/09/13/spot-the-difference-htc-desires-slcd-versus-amoled/
I hope I dont have to send mine in now :/
andy2na said:
yea, I JUST read the article on engadget comparing the Desire's Amoled vs SLCD:
http://www.engadget.com/2010/09/13/spot-the-difference-htc-desires-slcd-versus-amoled/
I hope I dont have to send mine in now :/
Click to expand...
Click to collapse
its ok most people cant tell the difference unless its side by side
i cant tell the difference..
update #3: dec-02-2010
i have sent out my old nexus one to HTC
and i just got a mail from them saying they have received my n1 and is in process of inspecting
we'll see how it goes, hopefully they wont charge me
update #4
service is complete. they didnt charge me
update #5 dev-04-2010
sold my nexus one now have mytouch 4g. bye guys
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 story is I was having a lot of general problems with my Sprint HTC One. I was using it with CyanogenMod 10.1 and I noticed it was getting VERY warm. I then noticed that the battery was at 21%, I had hardly used it all day. It would normally have been around 94% percent. So I was shocked. Then I noticed that is would make weird clicking and "eek" noises when I would browse the Operating system. It would make an especially annoying noise when I would turn on the LED Camera light. I also noticed that the battery would drop about 1 percent ever 30 seconds.
I immediately shut it off and plugged it into my charger (AC). I opened up ClockworkMod and wiped my cache and dalvik cache and then did a factory reset from ClockworkMod. The problems still occured. I then tried flashing an Earlier version of CyanogenMod 10.1. The problem still occured. So I let my battery charge up to 50% (it took a especially long to charge, it would actually lose a charge while charging at times) and then used RUU tool to flash it to Complete Stock. That got rid of the weird noises caused during the operating system use. But the battery continued to run hot and take especially long to charge (somtimes the battery level actually was dropping). I then installed an app to control the frequency of the CPU. It was set to always run at 1.7GHz. So I fixed that and made the minimum Frequency the lowest option and the Max Frequency 1.7GHz. That solved the charging problem.
I left it to charge over night and by the morning it was at 100%, so I unplugged it and turned it off. I thought I had solved everything. I left the phone alone for about 4 hours and when I checked on it, it would not boot whatsoever. I could not not even get into the Bootloader! Then I plugged it back into the charger to find out that the Orange charging indicator LED would NOT light up! So for now, it is just sitting in the charger without the charging indicator light lit up.
I would also like to mention that I am not the original owner. I bought this phone used. It does not have the normal Sticker on the back of the phone to indicate the Serial Number etc. And since I am not the original owner, I do not believe I qualify for a replacement warranty. Any help at all would be greatly appreciated. Thank you for your time.
this has been happening to alot of people
which of the nightlies did you flash?
flex360 said:
this has been happening to alot of people
which of the nightlies did you flash?
Click to expand...
Click to collapse
It was either the cm-10.1-20130731-NIGHTLY-m7spr (2013-07-31) build or the cm-10.1-20130730-NIGHTLY-m7spr (2013-07-30) build
Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta
krazyflipj said:
Might need to go to sprint for a replacement
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Am I able to get a replacement even though I'm not the original owner?
ammuica said:
Am I able to get a replacement even though I'm not the original owner?
Click to expand...
Click to collapse
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta
krazyflipj said:
If you are under service they should. Phone is still under manufacturer warranty. If you don't have insurance, worst case scenario you pay $50 for a refurb/new phone. Of course that's if they can't repair
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
It is not under service. I Bought it with the plan of not using it on a contract because I cannot afford a data plan, but I would still like to use an android smartphone.
Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta
Alex1123 said:
Yeah just got and get a replacement for 50$ I was not the orginal owner and they got the serial number off they're system I got a refurbished one I think but it was in like brand new condition but now it seems the brick problem is still around
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
But will they still replace it if I'm not using it with a plan? I bought it from someone else and I never re-activated it.
I've called sprint and since I don't have the phone under my account and since it is not activated, they will not repair it. So a replacement/repair is out of the question. So is there anyway I can fix this myself? I'm familiar with flashing and all that stuff, so any of that stuff is just fine.
There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.
sauprankul said:
There is no way you can repair this yourself.
And eek! This problem's back? What? You were using the latest nightly too?
And since you have no warranty (pretty sure its non transferable), you should look up JTAG services. $60. It may not be as clean as you'd like, though. Besides, HTC repair service wouldn't fix your device for free because, even though the device is bricked, they can see your tampered boot loader. They charged me $200. I probably won't root again.
This has happened to at least a dozen people, but all if them were before July 3rd. This is kind of disturbing.
Click to expand...
Click to collapse
Hey, it's always worth a try. I always used the latest nightly. I updated whenever they pushed a new update. I had it running CyanogenMod 10.1 Nightly for over a month without a single problem. I've been using it on my Galaxy Nexus for over a year. This is the first time it's ever given me a problem.
I'll look into the JTAG, but if anyone else has any ideas I'm up to try anything. The bright light while holding Volume Down + Power didn't work for me.
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
I did know what I was doing. I was running a stock build flashed by RUU. So I assumed that it would have a decent frequency management (that should be a safe assumption). I know what I'm doing when it comes to android's. I'm not stupid enough to have the CPU running at the full 1.7 GHz. Immediately after it started getting warm again that was the first thing I checked. Normally I underclock my devices. I usually have my Galaxy Nexus run at 700 MHz. I've also been using Nightly builds for my Nexus for over a year and I've found it to be stable enough to decide to flash it on my HTC One. And until 2 nights ago, It was perfectly stable.
I've done no fault on my own. I personally blaim HTC for pumping out a ROM that let it run at 1.7GHz 24/7, even unrooted.
Also to include, while I was running CM 10.1 I had my CPU set to a minimum of ~300MHz (forget exact frequency) and a maximum of 1.7GHz. I'm not stupid enough to set it to run at 1.7GHz 24/7 for any reason whatsoever. I was shocked when I saw that it had been running at 1.7GHz 24/7 (had only been running for an hour in sleep mode at that point before I fixed it).
Admiral Sir Manley Power said:
OP.... wow. Just wow.
So you have the device's processor spinning at 1.7 GHz constantly, and you are wondering why it is warm? You are also running a custom OS with a myriad of bugs and issues, and you are wondering why now your device isn't working properly.
Unbelievable. You shouldn't be playing around with its powerful hardware if you have absolutely no clue what you are doing, don't you think?
Sent from my SM-N900T
Click to expand...
Click to collapse
?
10.1 is very close to stable...
Except, you know, the bricking issue.
Where does it say the device was maxed out on purpose? Stock CM is supposed be pretty good at CPU management.
So now we know what is causing the bricks. The CPU is literally self destructing. We should have deck look into it.
I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.
ammuica said:
I'm considering selling it to technollo.com . With a promo code, they will pay $70. I only payed $230, so I might as well just cut my losses.
Click to expand...
Click to collapse
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?
sauprankul said:
Really sucks man.
Again, just goes to show. If you can't afford to lose/fix your device, then you shouldn't be rooting it and stuff. HTC makes no guarantees that the phone will be able to run AOSP ROMs. The devs just do their best. Phones are getting more and more complicated, and it gonna get harder and harder to make stable ROMs for them.
Looks like this is your only option... maybe you can go and get yourslef an N5 when it comes out as a replacement?
Click to expand...
Click to collapse
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.
ammuica said:
Well I think it's worth the risk. Usually I can fix nearly any software issue possible. However, this is a hardware issue. I love modifying my devices and I won't stop anytime soon. My Personal computer currently has full liquid loop (GPU + CPU) that I setup and maintain that I am proud of. Sometimes things just go wrong. That's no reason to give up. For now I'll just continue to use my Galaxy Nexus until I find it necessary to upgrade.
However if anyone would be interested in purchasing this HTC One from me, just message me and we could try to work something out.
Click to expand...
Click to collapse
I never asked you to stop rooting. It was just a PSA saying one should only root if one can afford to lose or fix one's device.
English is stupid.
Hello,
the problem I've with this phone is that the wi-fi wont turn on, either the bluetooth.
So I tried different roms, stock 2.3.5, and then cm10.1.2 stable, and the same issue.
The last thing I tried was a simple one-click odin installation consisting in a super wipe plus the installation of a stock 2.3.5 firmware.
And here I am, facing the same problem. Actually when I go to "about phone", status, then I see:
Wi-Fi MAC Address: Unavailable
Bluetooth Address: Unavailable
At this point it seems like this is a hardware problem, and for that reason is more than welcome an oppinion in the opposite way
dionieins said:
Hello,
the problem I've with this phone is that the wi-fi wont turn on, either the bluetooth.
So I tried different roms, stock 2.3.5, and then cm10.1.2 stable, and the same issue.
The last thing I tried was a simple one-click odin installation consisting in a super wipe plus the installation of a stock 2.3.5 firmware.
And here I am, facing the same problem. Actually when I go to "about phone", status, then I see:
Wi-Fi MAC Address: Unavailable
Bluetooth Address: Unavailable
At this point it seems like this is a hardware problem, and for that reason is more than welcome an oppinion in the opposite way
Click to expand...
Click to collapse
EDIT: nvm just saw your other post.
Sent from my SGH-I747 using xda app-developers app
Yeah... they nor bluetooth nor wi-fi can't be turned on, actually the wi-fi in menu in settings looks "bold", like you can't move the switch, you know what I mean?
what if my captivate was shipped with a generic non-original battery cover and that's the thing provoking this issue? I'm saying this because battery covers shoud have some little metallic things on the back that improves the wifi, gps and bluetooth, am I right?
dionieins said:
Yeah... they nor bluetooth nor wi-fi can't be turned on, actually the wi-fi in menu in settings looks "bold", like you can't move the switch, you know what I mean?
what if my captivate was shipped with a generic non-original battery cover and that's the thing provoking this issue? I'm saying this because battery covers shoud have some little metallic things on the back that improves the wifi, gps and bluetooth, am I right?
Click to expand...
Click to collapse
Actually, they should work whether you have the back on or off. I never saw that problem before you and the guy mentioned it in the 4 years I've had this phone. It's quite odd.
BWolf56 said:
Actually, they should work whether you have the back on or off. I never saw that problem before you and the guy mentioned it in the 4 years I've had this phone. It's quite odd.
Click to expand...
Click to collapse
Also I found this:
near to the screw that is close to the sd card slot, there should be a copper pin coming out from a tiny hole. Every Captivate has that tiny pin of copper, that should match with a white spot in the back of the battery cover.
Mine doesn't have that tiny pin; there is nothing but a tiny hole in that spot.
So this is what happen when youg get a refurbished Captivate on eBay these days...
dionieins said:
Also I found this:
near to the screw that is close to the sd card slot, there should be a copper pin coming out from a tiny hole. Every Captivate has that tiny pin of copper, that should match with a white spot in the back of the battery cover.
Mine doesn't have that tiny pin; there is nothing but a tiny hole in that spot.
So this is what happen when youg get a refurbished Captivate on eBay these days...
Click to expand...
Click to collapse
Perhaps that's your problem. There might be a way to replace it.
You can try contacting Josh @ mobiletechvideos.com on that if you can't find the necessary info.
BWolf56 said:
Perhaps that's your problem.
Click to expand...
Click to collapse
I don't think this pin is the problem. Unable to turn on <something> usually means the system did not recognize the module during boot process. As it was mentioned already, Wifi/Blutooth on Captivate works fine with back door removed. Missing part indicates the phone was disassembled and someone attempted to repair something.
Val D. said:
I don't think this pin is the problem. Unable to turn on usually means the system did not recognize the module during boot process. As it was mentioned already, Wifi/Blutooth on Captivate works fine with back door removed. Missing part indicates the phone was disassembled and someone attempted to repair something.
Click to expand...
Click to collapse
I remember reading a thread a year or so ago about a guy who replaced that pin after having problem with his cappy. He had done it by himself though.
I might be wrong but what you suggest would come from the modem and/or kernel which seems to work fine on every other phone that runs CM.
It's a shot in the dark but it's what we got for now if you check what the other guy has tried so far (in the other thread with the same problem). Could be a good idea to ask that other guy if his phone still has the metal golden pin.
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
I might be wrong but what you suggest would come from the modem and/or kernel which seems to work fine on every other phone that runs CM.
Click to expand...
Click to collapse
I'm not sure either, not very familiar with phone software specifics. I'm a computer guy and in computers missing software controls means device not initialized. Kernel/modem software is fine, but there is something wrong with the hardware. I personally don't believe restoring the pin will fix the issue. On a good Captivate, even with this connection open (back cover removed), wifi/bluetooth works fine. A good repair guy have to take a look here and check all currents/voltages from SoC through amplifiers to antenna. Shooting in the dark is asking for more trouble. On the other hand there is no point to pay for shipping/repairs on a $90 device.
Val D. said:
I'm not sure either, not very familiar with phone software specifics. I'm a computer guy and in computers missing software controls means device not initialized. Kernel/modem software is fine, but there is something wrong with the hardware. I personally don't believe restoring the pin will fix the issue. On a good Captivate, even with this connection open (back cover removed), wifi/bluetooth works fine. A good repair guy have to take a look here and check all currents/voltages from SoC through amplifiers to antenna. Shooting in the dark is asking for more trouble. On the other hand there is no point to pay for shipping/repairs on a $90 device.
Click to expand...
Click to collapse
Good call.
OP, I believe your best chance is to try with mobiletechvideos or a electronic shop in your area.
If you ever find the problem/solution, please let us know so we can help others.
Sent from my SGH-I747 using xda app-developers app
Yes, I will! actually this thread had pointed out some interest, I'm saying this due to the over 200 visits it had in just a few days lol
Back to the topic, this phone definitely was disassembled because it was a refurbished unit bought from a big store on eBay.
This piece of.. hardware, cost me $89 by the way, and the only solution I got from the seller -as I'm overseas now and I can't ship it back without expending lots of money- was to get a refund for the half of the price...
So basically I got this $45 Captivate that only works for:
calls, sms, music, storage & camera
Still, I don't think that $45 is a good price of this piece of... hardware.
And yeah, now I'm convinced that the missing pin of copper it's not related to the wi-fi issue, actually that pins only exist to improve call reception as I was told by the seller.
Therefore, and after flashing many stock and non-stock roms through Odin & cwm respectively, I must conclude that this is a hardware issue.
So I'd like to know if any of you guys would drop me a link of a DIY for disassembling and replacing wi-fi hardware on a captivate, because I've another Captivate with a different issue: usb port broken, so I can take the good parts of both and create a fully working Captivate
let me know
peace
BWolf56 said:
Good call.
OP, I believe your best chance is to try with mobiletechvideos or a electronic shop in your area.
If you ever find the problem/solution, please let us know so we can help others.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
BT/WIFI main logic in inside SoC, can't replace it. There are few external components you may check, but you need oscilloscope, good voltmeter, some special tools and advanced electronics repair knowledge. DIY repair in home conditions is not possible. I can send you the repair manual, if you want. One thing you can do is to repair the USB port on the other Captivate. It is doable, but you still need some equipment like vacuum pump, precise soldering gun, solder wick, good flux, etc.
install this app (Blade Wifi Fix)