Related
Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
I am not sure if this has to do with using Android or not, but sometimes my HD2 decides to reboot itself unexpectedly, on WM as well as on Android and I can't really find what's causing it.
But what happens is, after switching itself off, it switches itself on again and hangs on the HTC logo, sometimes with or without the following info:
R 2.10.50.28_2
G 15.40.50.07U
D 1.66.76641
I am using stock ROM that came with it, i assumed it will be stable by itself but it reboots itself randomly sometimes just like on Android.
Does it have to do with the Radio version (i changed it from 2.07.xx). I tried 2.12.xx before and had same problems.
I should note that the only way for it to run again is to remove the battery for a while and then put it back. If i remove it and put it back briefly it will still hang.
Anyone is familiar with this strange behavior?
Thanks
ME too
I have the EXACT same problem. It only started for me after using android. now whenever i run Android it will unexpectedly reboot and sometimes hang like yours. It also does it in WM though not as often. I was able to notice it might have something to do with data connections bc if i run android but only use wifi it seems to be fine. I tried changing Radios WM ROMs and Android builds i even hardspled my phone again but nothing solved it. The problem needs to be talked about more. it got so bad for me I bought a Desire and gave up on my HD2 for the moment. Keep this thread up.
sounds like i have to follow
I hope not!
I notice if i do heavy download on wm or android i get it. But it could be that the phone is too hot? But it's not alarmingly hot tbh.
I hope more people can shed light on this.
Thanks for your input.
Yeah this is what seems to happen to me too, i start a downlogsd it gets a bit warm then freezes or reboots and gets stuck. However it doesnt even have to be a large download for me, a simple cab file or youtube video sometimes. And as far as heat, this never used to be a problem and i know for a fact my phone used to heat up way more before without a problem.
Maybe the qualcomm chipset go in "safe mode"..i remember that for first start tickle the orange led and after the device freeze or restart..maybe your device overheat. Try to touch cover's device or install a battery status monitor software. If you have changed radio, return on the original status. In case the restart happen always, make a backup using Pimbackup, and do an Hard Reset. For first try to use the telephone without the memory card and test the stabilty. If is all ok, you have to provide to format your SD card in Fat32. Try also to change the HSPL with the original SPL.
What happened to this thread? Suddenly 3 recent posts have disappeared?
relic said:
What happened to this thread? Suddenly 3 recent posts have disappeared?
Click to expand...
Click to collapse
Forums Restored from Backups - LOST DATA - PLEASE READ
As many of you may have heard, we underwent routine maintenance on our Database Server. Upon rebooting the Database Server, it refused to boot and all indications are that the RAID 10 (what is RAID? http://en.wikipedia.org/wiki/RAID) array failed.
We have restored the Forums from a 24 hour old backup. We know this is not ideal, but at this point, the chances of recovering the failed array are slim.
We sincerely apologize for this. In fact, this maintenance was intended to boost the redundancy of our database setup and lightening strike.
http://forum.xda-developers.com/showthread.php?t=792013
__________________
svetius
-----
User Experience Admin
xda-developers
http://forum.xda-developers.com/announcement.php?f=743
Thabks. Back to the subject, today i tried downloading on wifi a 150mb file on android and it rebooted byitself.
Then i tried to play a wmv video file on WM stock ROM and after 6 min it rebooted.
So its starting to look more and more like cpu/heat problem, anyone having these issues?
So does anyone think this might have something to do with all the overclocking in those android builds we've been using?
After 45 mins of install HD2 still hanging?
Hi, I just installed FroyoSense by darkstone
Release date: 07.AUG.2010
I don't know if this is the latest (probably not) but after 45 minutes of install the screen has in the top left hand corner tiny small text (excuse my lack of knowledge here) but no scrolling text as I expected, its now like 50 minutes, how long should it take?
Any help please would be appreciated, thanks
John
New to the HD2
So, I just bought a used HD2 a week ago. It was having similar problems in WM. I took it to a local store, and they said that is just how WM phones are. I've flashed HSPL and different radios and ROMs, installed Android, but still have trouble with freezing and rebooting on it's own no matter what I do. IT happens the same in WM or Android. Is there any way to find out if these might be due to hardware problems caused by the previous owner?
I got the same problem, when I do a lot of things on the same time on the HD2 it hangs or reboot. During de restart of the phone it hangs on the White screen with HTC on it. I have te take the battery out of it en than reboot again.
When I listen music and Internet the same time it almost always happends.
It happends on WM but also on Android, I tryed different ROM's and Radio Version's but nothing worked. Also tryed to work without SD-card, but still the same problem.
So I have no idea how to solve the problem...
I hope someone now's how to solve it...
Sorry for my bad English but I hope it's clear
FroyoStone with HTC Sense V2
Polar bear said:
Hi, I just installed FroyoSense by darkstone
Release date: 07.AUG.2010
I don't know if this is the latest (probably not) but after 45 minutes of install the screen has in the top left hand corner tiny small text (excuse my lack of knowledge here) but no scrolling text as I expected, its now like 50 minutes, how long should it take?
Any help please would be appreciated, thanks
John
Click to expand...
Click to collapse
Ok having waited for 2 hrs, I shutdown and installed FroyoStone v2, this time the tiny text appeared and faded after about 5 -10 seconds and the screen has gone blank, is this normal? No scrolling text, nothing, I going tpo re-boot and will keep you updated. Thx
If you read the previous posts you would know this thread has nothing to do with the problem youre describing. I understand the confusion of the title but pls read the thread first.
Polar bear said:
Ok having waited for 2 hrs, I shutdown and installed FroyoStone v2, this time the tiny text appeared and faded after about 5 -10 seconds and the screen has gone blank, is this normal? No scrolling text, nothing, I going tpo re-boot and will keep you updated. Thx
Click to expand...
Click to collapse
Your problem is unrelated to this thread.
So far we have more and more people having the related issue on WM and Android. We need some expert to help us pinpoint the problem.
jasperbleumink said:
I got the same problem, when I do a lot of things on the same time on the HD2 it hangs or reboot. During de restart of the phone it hangs on the White screen with HTC on it. I have te take the battery out of it en than reboot again.
When I listen music and Internet the same time it almost always happends.
It happends on WM but also on Android, I tryed different ROM's and Radio Version's but nothing worked. Also tryed to work without SD-card, but still the same problem.
So I have no idea how to solve the problem...
I hope someone now's how to solve it...
Sorry for my bad English but I hope it's clear
Click to expand...
Click to collapse
i have the same issues.
I can add also playing videos for longerthan 5-10min would make the phone reboot too weither its WM or android.
Today I was in the Store where I bought mine HTC HD2, because I was sick off it. They told me that is was a familiar problem with the HTC HD2. They also would repair it free for me. I didn't do it yet because first I have to delete my HSPL etc.
I asked them also what the would repair to solve te problem, he told me: the will do a complete bodyswap. So everything will be renewed, exept the tochscreen and front.
So I guess it is a real and serious hardware problem....
Why we dont hear people conplaining about it if its comon?
I find that very odd.
Someone could try PMing one of the devs in the forum and linking them to this thread to see if they could shed some insight or at least bring more attention to the issue.
Well I live in the Netherlands and on the Dutch HTC HD2 forum, I heard some people complaining about it. But the salesman of the store said that it is a familiar problem, so that sounds to me like a regular problem. But indeed it's weird we doesn't hear more people complaining.
Maybe the most of the people think is normal with WM, but I am really sick of it...
Hey guys,
So I loaded RubiX a while back and after getting everything all fancied up the way I wanted it my phone decided that it doesn't like when I touch it (touch-screen stopped responding, the hard keys still worked fine, but I have to serious hold screen-keys down to make anything happen).
I thought this problem was just something in the ROM that my phone didn't like, or a bad setting I changed, so I tried out Liberty ROM (which, by the way, is AWESOME). After getting everything completely made for the Liberty ROM, the exact same thing happened.
In a fit of frustration I decided to start from scratch, root and deodex, then load all my fun settings (like the de-throttle and imoseyon's memory changes) and it all started doing it again. Is there something I don't know about the way the screen works?
Another interesting fact: While I was trying to figure this problem out with my phone (stock with root/deodex and imoseyon's changes) I unplugged it from charging on my comp and now it's running pretty smoothly again... I've been having this problem all day, restarting and clearing cache / loading different ROMs and running restores didn't do anything... this is really strange!
Any idea what this is / has anyone experienced it before. I was just about to call Verizon and reset my phone to stock to get an exchange.
Try running a ROM stock and see what happens. Could be an app...
zehk,
I've tried every combination, including running to stock...
What I know now is that it only happens when phone is charging from a computer... The touchscreen goes completely brain-dead...
Any ideas?
I've had a problem when charging my phone from USB before. Someone said it was the drivers on my PC... might try a newer or older version depending on what you have.
That's an odd problem. Seeing how you have tried to troubleshoot your issue, trying the PC Drivers might indeed help as suggested by zehkaiser.
I would recommend downloading Motorola'as MotoConnect. It's the only driver I use for any Motorola device I hookup to my computer. You can download it here. Hope that helps and if not, sounds like you will have to do a .340 SBF with RSD Lite or the maderstcok zip 340 and return your phone for a new one.
nope
It's not the drivers either, I've now realized that it's happening when I plug into the wall too. I thought that might be due to using an old palm charger, since it's slighty higher amperage, but it turns out the standard moto charger still causes this problem...
My DX does exactly the same thing after unplugging. Any ideas?
This problem remains forever, doesn't matter what custom rom you're using, it'll be still there.... I've tried a lot of thing to fix it, some doesn't work like this or that thread, however, this worked for me (not completely, I'll explain why...)
Well, the last one didn't work for me because after every new update/build, the fix is cleaned and you need to flash it again every new build/update. How to deal with it?
I need go give my phone to one of my parents and they don't know how to flash. I was happy because, at least, LineageOS updates itself automatically (except by the fix which need to be done manually). Unfortunately I don't know any other custom rom that has OTA updates working (and of course, updates itself automatically) and the audio is working normally.
I don't use the stock due to sluggishness, errors, being outdated since 2017. So, I need to flash a proper rom but it seems to be hardcore issue.
I need some help.
Get a pin and shove it in the mic hole
Get all the rubbish out & you might have to pierce the filter that's on the other side too like I did
After doing that I had no mic issues
Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.