Is anyone else having this problem..? Like this is my first time booting it up and it's been about 1 hour and still my phone is trying to boot up android. Anyone know why it's slowing up.
I have a same problem, when I boot Android with HTC sense form HTC desire form SD card, everything goes good for a while, and then all diplay fade out and goes to black.
I wait some time but I give up. and return to winmo with a simple reset...
Now I searching a solution...
If anyone have a similar problem let us know.
ive never managed to get it to boot. (tho to be fair i only tried five or six times, all different builds tho, not just teh same one over and over)
I suspect its my sd card.
Try to copy android files directly on root of sd card not in the android folder...
here are some observations:
Every so often the hardware keys stop working. (soft keys seem fine) Quick fix is put unit into standby then unlock and keys work again.
Lookout Mobile: while doing a backup the system shuts down for some reason.
I just upgraded my wife's g-tab yesterday to G-Harmony. She hasn't had any of the issues that you mentioned.
From what I can tell from the main thread, you need to completely wipe the gtab before flashing the rom. Here's (Basically) what I did.
Formatted each and every mount point
Cleared each and every cache
Connected to my computer via USB
Flashed the Rom in.
Booted and let it sit about 20 minutes before I did anything.
Downloaded a Term emulator and ran V6.
Everything pretty much seems to be ok. Every once and a while she experiences an issue with an app or two after it sits running for a long period of time but a reboot seems to fix it.
Hope this helps.
Other issue observations...
After loading G-Harmony on my wife's tablet this weekend, I've noticed a few things (complaints from her).
* After running for about 1 1/2 - 2 hours, system will get very slow and eventually just locks.
* Browser simply goes to a white screen
* Audio stops running (I found a thread that said to turn off GPS and reboot. I've tried that, but I don't know if it has made a difference yet.).
That's all for now. Is anyone else seeing anything like this?
There is a new ics rom by jamcar. Try it out. I did and it runs very good.
Thanks.
I'll take a look at it. Not sure if my wife will give up her tablet or high scores (again) but I'll see how she reacts. ;o)
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.
I have been having issues where my phone have been freezing up at seemingly random times and then getting into a bootloop until i do a hard power off and turn it back on. I've attempted a clean reinstall of the ROM but no luck.
I was going to flash RUU but my USB port doesn't work for data anymore so fastboot is out. (I tried to use fastboot on 2 computers running Win 7/ 8.1 with a couple different USB cables)
Can anyone recommend any sort of troubleshooting solutions to get this ROM (or possibly a different 4.4 AOSP ROM) to run a bit more stable?
admiral licorice chaps said:
I have been having issues where my phone have been freezing up at seemingly random times and then getting into a bootloop until i do a hard power off and turn it back on. I've attempted a clean reinstall of the ROM but no luck.
I was going to flash RUU but my USB port doesn't work for data anymore so fastboot is out. (I tried to use fastboot on 2 computers running Win 7/ 8.1 with a couple different USB cables)
Can anyone recommend any sort of troubleshooting solutions to get this ROM (or possibly a different 4.4 AOSP ROM) to run a bit more stable?
Click to expand...
Click to collapse
Hi, sorry, I don't have an answer necessarily, but I was having the same issue with OmniRom before I moved over to the new partition layout. One thing you might try, though, is going back to stock (or at least some Sense based Rom) and see if you can get ADB/Fastboot working on it then. I noticed that I wasn't able to get it working on AOSP Rom (I think it was PAC-Rom specifically) but when I restored back to my Initial Stock nandroid, I was able to do it (Run the RUU for new partitions). So give that a try before giving up.
But I also had the random freeze, and boot which could only be stopped by the simulated battery pull like you described, and then it would work. A couple times, I would just be using it and it would freeze. A couple other times I would pull it out of my pocked and it was sitting there with the little android dude sitting there in the circle, staring at me. One time I just left it there for a while, and noticed that it actually was booting (kind of) but super slowly. It would sit there for like a minute, and then the antennae would twitch a little, wait 3 seconds, twitch again, wait 3 seconds twitch again. It was like it was running on extreme slow motion on the boot animation. I don't know if it ever would have finished, given enough time, because I never gave it enough time.
Anyway, if anybody has ideas on why AOSP roms seem to do that, I'd appreciate it. Had a similar experience with PAC-Rom, on the old partitions, with random freezes that couldn't be recovered from.
bpaulien said:
Hi, sorry, I don't have an answer necessarily, but I was having the same issue with OmniRom before I moved over to the new partition layout. One thing you might try, though, is going back to stock (or at least some Sense based Rom) and see if you can get ADB/Fastboot working on it then. I noticed that I wasn't able to get it working on AOSP Rom (I think it was PAC-Rom specifically) but when I restored back to my Initial Stock nandroid, I was able to do it (Run the RUU for new partitions). So give that a try before giving up.
But I also had the random freeze, and boot which could only be stopped by the simulated battery pull like you described, and then it would work. A couple times, I would just be using it and it would freeze. A couple other times I would pull it out of my pocked and it was sitting there with the little android dude sitting there in the circle, staring at me. One time I just left it there for a while, and noticed that it actually was booting (kind of) but super slowly. It would sit there for like a minute, and then the antennae would twitch a little, wait 3 seconds, twitch again, wait 3 seconds twitch again. It was like it was running on extreme slow motion on the boot animation. I don't know if it ever would have finished, given enough time, because I never gave it enough time.
Anyway, if anybody has ideas on why AOSP roms seem to do that, I'd appreciate it. Had a similar experience with PAC-Rom, on the old partitions, with random freezes that couldn't be recovered from.
Click to expand...
Click to collapse
Nah, installing a Sense ROM didn't work out for recognizing data over USB. I'm hesitant to flash RUU over wifi ADB (if thats even possible) because I wouldn't be able to use fastboot if something goes wrong.
admiral licorice chaps said:
Nah, installing a Sense ROM didn't work out for recognizing data over USB. I'm hesitant to flash RUU over wifi ADB (if thats even possible) because I wouldn't be able to use fastboot if something goes wrong.
Click to expand...
Click to collapse
That's good you didn't try it over wireless, because as part of the RUU process, it reboots to fastboot, and if all you had was a wireless connection at that point, the process would fail.
bpaulien said:
That's good you didn't try it over wireless, because as part of the RUU process, it reboots to fastboot, and if all you had was a wireless connection at that point, the process would fail.
Click to expand...
Click to collapse
Hmmm.... I may be out of luck then. I'll just deal with the issues until a new Nexus phone is released (if one ever is).
Thanks for the suggestions though.
Hello
I have just recently obtained an HTC Desire HD from my brother, to start off with the hardware has been well taken care of, he is always careful, it was always in an otter case, and ran perfectly scratch free when I got it, so I already know there is nothing wrong with the hardware.
I was trying to root the device, I was using these instructions;
"how to permanently root Telus HTC Desire HD" (was going to be link but I can't yet)
The problem being that he had kept it well updated so I had to change the method a bit. I had to use the tacoroot method, it worked well, I was able to obtain "#" in the ADB, and modify my Misc_version. I then had trouble getting a hold of the PD98IMG.zip, I finally found one in the DHD_Downgrade_package.zip from "Downgrading and Rooting Your HTC Desire HD" (again would have been link) .
I then went to flash it, I had trouble because I didn't know you had to make a new goldcard every 2 uses or so, so that took a while, but when I realized that this morning I got to it, I flashed it, it let me and then that's where it all went down hill, or rather stopped.
It was flashing fine, as far as I saw it only needed to flash the radio. I was in the middle of making my lunch for work so I wasn't watching in intently.
When I looked back at it after a minute or so (and I had checked it in between, it was going fine) it was suddenly a blank screen, and I knew it was supposed to ask if I want to restart, I left it for a minute to nothing. then I decided to try force it to reboot, nothing.
Where I'm at now is that I've realized if I leave it with the battery in it for about five minutes or so it does turn on, only gets as far as the htc logo, and vibrates for probably 60 seconds. If its plugged into my computer, when its done vibrating my computer recognizes it (it dings and if I go under manage for my computer, its under devices) but that's it. Cant get into hboot as far as I've been able to try, though I haven't held the buttons for the entire five minutes, and ADB doesn't recognize it.
Please someone help, I am fairly newbish with android, I do have a tablet with android, but its from china so it barley counts lol.
Thanks a lot
-DonutFUN