I've tried to search to see if anybody has ever encountered a problem like this, but my search was in vain.
I was trying to upgrade ROM, I successfully load SPL 3.5, before it I was running AP dual 3.0. However after the installation the device rebooted and the started auto customisation. It installed SDAautorun and then SDConfig.txt but before this one completes, the device reset itself. It restarted and do the same process again and again, just restart and restart.
I tried all types of resets and I even tried to reinstall other roms that worked with the device before but nothing is any good. This is because when the device boots it load the SPL 3.5 (Windows mobile 6.1) instead of installing the ROM I'm trying to install.
I get a chance to do so as the device can still connect to the computer and it stops when it prompts to callibrate the screen (tap four corners and center of the screen)
Please help me if there is anything I could do to start using my device again. I appriciate any support in advance. It is very possible that I've messed up something somewhere but please once again do help me, even if the by telling me that my Ameo is a brick that would help me to know what I've got to do.
NB: My device is T Mobile Ameo (Athena, Advantage X7500)
Have been running Artemis v311 NO and Android from SD card for about two weeks. All fine. Yesterday the phone started rebooting by itself when running Artemis. I've made no changes to the phone after installing Artemis two weeks ago.
Now it wont boot at all, screen shows "please wait, loading" Have tried both soft and hard reset but none of those works. (I get no response when holding down the keys)
Have tried to get an usb connetion to flash a new image but without luck.
Is it time to get a new phone or is it possible to fix this...???
Hello, I have an unrooted Hero from Orange (Spain) that enters in a boot loop. I have tryed everything to restore it but with no success. In the hboot menu it says "touch panel-fail" and even if I flash again the original rom from the hboot, it still gets in a boot loop.
First of all I will explain my case.
I had the Hero rooted, with custom roms etc, but when I bought a Nexus One, I gave my Hero to my brother. In September he told me that the official 2.1 had arrived to the Hero, so he wanted it instead of a custom rom, so I just proceeded to do so. I created a GoldCard, installed the 1.5 RUU of WWE, made the two OTAs and all OK. The last week (I think) he received a new small OTA, he updated successfully. My brother went to sleep with the Hero almost charged, but when he woke up, the Hero was off. Then, when he turned it on, and after a while (15mins or so) the Hero finally boot up, but the touchscreen wasn`t working and using it with the trackball the Hero was always prompting FC of android.process.acore (every 2 seconds more or less).
After watching that, I installed the official 1.5 of Orange hoping that it will fix it, but no way. Now it gets stuck in a loop while booting after the Orange bootscreen.
I tryed again to flash the WWE version, but with my old GoldCard doesn't seem to work (incorrect cid) and not being able to boot it up, I cannot create a new GoldCard or even root it.
I have tryed a lot of fastboot comands but I can do just little things because for the most useful things I need root.
Other thing that might be good to know is that when I plug the power to the Hero nothing happens, the led is not turning on, and I don't know how much battery I still have. Thank goodness that the battery was full before I moved the Hero to this infernal boot loop.
Please I will be so thankful if anyone can help me or just giving me any clue about how can I fix this.
I had the same problem on a refurbished hero I had. It had touchpanel fail in hboot and was in a constant loop.
I managed to get it to boot into android once by installing the ruu while in fastboot mode, however the touchscreen did not work and when I rebooted the phone it went back to the loop.
I sent the phone back for a replacement. If u check my previous threads ull see the thread icreated. In it I said that it had worked as that was when it finally booted but before I realised the sgreen didn't work
Sent from my HTC Hero using XDA App
Thank you for your reply, I will check your posts when I arrive home this evening.
hi.
I had the same problem and solve it by flashing this rom (goldcard needed)
http://shipped-roms.com/shipped/Her...io_63.18.55.06P_6.35.15.11_release_signed.exe
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App
Hi there,
A friend has T-Mobile HD2 running winmo 6.5.
He was installing an app but window stuck. He did soft reset to reboot but it started like it starts after hard reset (windows preparing for first use). During this battery ended and cell shut down. When he charged cell and turned it on, windows stuck at booting. He did hard reset and windows prepared for 1st use but when it came to network configuration its stuck at 90percent. Tried it without sim but nothing happened. Red buton also became unresponsive as well as other keys.
Now window is stuck so cant connect to pc. Its touch also has hardware issue and it stops working very often. He thought of flashing ROM via memory card but he read that HSPL can't be installed via card.
Kindly guide how to get his cell back to work.
Thanks