Related
Every time I reset or turn on my fone after shutting down, it will stuck at the logo boot up. It wasn't like that when I first bought the fone. Now it's getting worse and worse since the issue happens so frequently.
I have to take out the battery and put it back, then wait for about 3 to 5 mn before I turn the phone on.Then it would boot up as usual.
Is there anyone facing the same issue as I am? Any suggestion guys?
Are you experiencing excessive heat when this occurs? Also, can you give more info such as: does this happen only after recent charging or does it ever happen when the phone has been turned off for a long time? Was there any recent apps you installed or ROM changes when this started happening? Was there any potential damage done to the phone -dropped it, got it wet, or microwaved
When you say frequently, does that mean every time you restart? every other time? every five times?
Lastly, do you have any other issues/symptoms other than freezing at startup? Does the phone ever freeze during normal use?
i'd suggest you do a hard reset of your phone (hold down both vol up and vol down keys while powering on/resetting). that should fix the problem. if the problem still persists, it's probably some hardware faults.
Me too
My HD2 just started doing this too. It was fine for 7 weeks I have owned it. However, as described in this by OP, when doing soft reset would it would also get stuck on bootup logo. I'd have to remove the battery for a few minutes before it would bootup.
However, my HD2 also crashes and upon reboot then get stuck on bootup logo. It appears to crashes randomly eg not with any particular program or action.
I figured it was software issue so did hard reset. This worked fine. After hard reset the only software I loaded were Total Commander and Cookie Editor.
After Cookie Editor install I did soft reset and it got stuck on bootup logo. : (
So I did another hard reset but it hung up again upon reboot on bootup logo.
This appears to be a hardware issue. But has anyone else had same issue?
T-Mobile HD2
Stock ROM
Purchased July 6 2010 from Expansys
yes i am experiencing the same problem and i have uploded a video on youtube showing this! Yes my phone heats up when this happens..
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Stormrider75 said:
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Click to expand...
Click to collapse
It will retain whatever rom you are using
Htc Hd2 vodafone UK
HD2 issue
After some more searching it appears this is not uncommon for HD2. Its not clear to me if it is specific to T-Mobile HD2 or HD2 in general.
It appears to be a hardware issue. Although that is not 100% clear either. I find it hard to distinguish what some people report as 'freezing' which i believe is different to the issue described in this post which is 'hanging up' or 'getting stuck' on boot up screen - in my case it is the T-Mobile 'stick together' pink and white screen/logo.
(The 'freezing' issue that i believe is different to this 'getting stuck on bootup logo' issue appeared to have been resolved iwth new T-Mobile ROM - and I never experienced it on my HD2).
The resolution for getting stuck on bootup screen issue described here appears to have been to exchange HD2 (although some people exchanged up to 6 times and keep getting same issue!)
I think it is important to note that my HD2 performed fine for 7 weeks with lots of soft resets, hard resets, and lots of software installs (though no ROM reflashing) but within last week or so, start crashing randomly, then upon reboot get stuck on bootup screen/logo. This also became more frequent as time progressed. After doing hard reboot, the issue is now acute, eg it gets stuck on every reboot, and crashes more often.
This leads me to think some hardware has failed or degraded and is getting worse, maybe a connection/soldering etc?
However, is there any possibility that a ROM could 'degrade'? Can a ROM have a setting that is modifiable? (I know it is 'read only memory' but is it really?)
Anyways, love to hear from others on this issue.
Same problem here. Bought my HD2 in june. Cooked my own rom with Chucky's kitchen. Flashed different radios, hard resets, task 29 etc. Absolutely no problem. Worked fine for several weeks. But sometime it begun to freeze, auto resets, stuck at boot logo. It was getting worse. Even flashing stock rom it hungs at boot logo.
Now my HD2 is out for repair. Now waiting for returning. Hope they will change the motherboard.
several people have had their motherboards replaced and that has seemed to fix it for them. You'll probably have to fight with htc or your carrier, but should be able to get it replaced.
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
HD2 is an odd one
Thanks for replies. I really don't want to send it in .. but it will probably be the only way to resolve the issue. It will cost me courier there and back, and $20 'triage' fee .. total cost to me will be ~$100 just to have them look at it. Price of doing business I guess.
Anyways, I realized that one of my issues was that it was crashing when syncing. A little digging reveals that HTC Sense does something to all contacts when syncing first time putting a bit of html in contact notes field (weird but it is true .. its their way of reminding you bought an HTC phone?) So once I got it up and running, I disabled Sense and syncing went fine, no crashing.
(Btw, Sense also appears to do something with SMS msgs too so if you have lots it crashes on due to this reason too).
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Still, important point is that it was ok for 7 weeks, and then started crashing, more and more, even after hard reset, though some of issues may have been due to Sense (which is reported by many users).
It is still not a 'normal' thing for a $700 consumer device to have such erratic behaviour. So, given others have exchanged crashing handsets for new handset that has no issues points to underlying hardware issues as suggested above eg motherboard.
As comparison I also have HTC Diamond 2 which has been rock solid for 2 years of continuous use even with lots of software install, tweaking, reg hacks, etc.
Stormrider75 said:
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
Click to expand...
Click to collapse
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
genoki said:
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
Click to expand...
Click to collapse
Thanks. Btw I read before we can actually 'disable' Sense.
How do we do that?
Sense - go to Today
Go to Start - Settings
- iI you see the black HTC Settings (has 'Personalize' on top of items) then go to Menu and select 'All Settings' (this will show Windows Mobile's Settings. HTC Sense 'Settings' doesn't everything Windows Mobile Settings has or shows it differently)
- Select 'Today'
- Select the 'Items' tab in Today
- Check 'Windows Default' and click OK in top right.
This will 'swap' out HTC Sense 'today' with Windows Mobile standard Today screen and voila you will have 'disabled' HTC Sense and you are back to using Microsoft's Windows Mobile 6.5 version of Sense (not anywhere near as useful or neat-o to look at but hey they are pretty happy with it )
genoki said:
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Click to expand...
Click to collapse
Just by disabling Sense is not going to make it work. I had this problem with my HD2 also and without using Sense it seemed to be working (there were fewer crashes), but only for few days. My HD2 was getting worse day by day - it was not crashing only if it was not touched (it was crashing just cycling between Sense tabs or by initiating a call).
At repair center they told me (after three weeks of waiting) that the motherboard must to be changed.
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
I have my HD2 back. Took me 2 weeks, the repair center changed the motherboard and got an new IMEI.
Now all is working, no more stuck at bootlogo.
But i'm on stock rom (1.66) with 2.07 radio. No way to run Android with this radio. Hmm...
axman79 said:
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
Click to expand...
Click to collapse
I'm afraid as well to flash any custom rom now. For Android i need to HSPL and flash a 2.08 radio or greater to use it. But i'm stick on stock rom for sure.
I want to know as well if it possible to damage it by flashing customs roms ?
As i stated earlier, i flashed plenty of roms, doing task 29 etc., in the end stuck on bootlogo.
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Yah, disabling Sense hasn't stopped my HD2 from crashing eith. Without using Sense it crashed several times while using Opera and more than a few times while syncing over the past three days. Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
genoki said:
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Click to expand...
Click to collapse
Was flashing stock rom with stock SPL, was at the shop where i bought it and they send it. I told them it stucks at bootlogo. Repair center changed motherboard without any question. Cost me nothing.
genoki said:
Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
Click to expand...
Click to collapse
Ja ja, same here.
genoki said:
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Click to expand...
Click to collapse
Yes you will, but dont forget to flash back stock rom regarding SPL !
genoki said:
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
Click to expand...
Click to collapse
I want to know as well !
hey guys. I am so glad I found this post! I have exact same issues ith my HD2, it's driving me nuts.
I kept sort of log and described my problems in this post: http://forum.xda-developers.com/showthread.php?t=712729
I think I have to send my HD2 for replacement or repair.
Can you please tell me how can I get my phone fixed/replaced?
I got the US T-Mobile version, but I don't have account in T-Mobile. Can I deal directly with HTC? Where do I have to call to get RMA number etc.
I would greatly appreciate your help!
KML
Hi all,
My Galaxy S II keeps crashing. The phone will just power off and the battery will drain right out and the only way to turn it back on is take the battery out then charge it again. Sometimes if I am quick and realised it has crashed I can take the battery out and turn it back on and the battery will have drained 30% in an hour.
Does anybody know why the phone might do this or is there a way I can track whether something in particular is crashing the phone via a log or something like that?
Thanks
Yes there are apps that can do that.
So whats the score.......are you on latest o2 or latest unbranded.
Post the about phone details lol.
Hi,
It is on the latest H3G UK firmware and is unlocked via the Galaxy S Unlock app by Helroz (so via nv_data.bin)
4.0.4
I91000NELP4
Build: IMM76D.XWLPY
Any ideas and what is the app called?
Thanks
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
zetsuboumeow said:
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Glad to know it is not just me. I'm hoping I can get an app that will log what is going on right up until crash time!
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
Click to expand...
Click to collapse
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Rackers said:
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Click to expand...
Click to collapse
Me too facing above all,unfortunately riding in same boat.
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
BladedYouth said:
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
Click to expand...
Click to collapse
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Tonyco1 said:
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Click to expand...
Click to collapse
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
BladedYouth said:
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
Click to expand...
Click to collapse
Yes just browse this forum but only section about Windows Phone 7 Development and Hacking. You will find DFT exclamation of how to install HSPL. In mine it was very easy because I not receive Country ID fail my phone was buy in Europe. If you receive Country ID error you need to proceed with goldcard it is explained there but first proceed without goldcard if it work it is very easy. Also when you proceed SPL2.05 it is not clear in the topic but you need to be in bootloader so you should start your phone with VolUp and VolDn keys pushed this is not explained in the topic and I waist a lot of time till figured out. After that just download one of the 7.8 ROMs here in Radar section and write it down. Also download new radio and use some RUU to put it on the phone before the ROM other wise the phone can not boot. Try and after that if you have problems write down here.
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
BladedYouth said:
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
Click to expand...
Click to collapse
OK but you need to but some custom ROM my phone turn back on when I put custom ROM a lot of features and works really good.
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.