Hey guys.
I have been struggling with ROM flashing lately and was wondering if anyone could help. Sorry for wall of text but going to explain as much as I can.
Short version:
• Can’t get WP7 or Android working.
• CWM gets stuck on 123456 GO GO GO.
• Can flash WP7 ROMs successfully but touch screen won’t work.
Long version:
Have had an HD2 for about two years. Have previously installed some Android NAND but have mostly been running WP7. About 6 months ago touchscreen hardware failed and it went for repair at HTC. Re-flashed WP7 when it came back. A little while ago touchscreen hardware failed again and I had it repaired again under insurance (warranty had run out). The phone was returned again with touch screen working perfectly on stock ROM. I am now really struggling to get any custom ROMS working.
I have succeeded in installing three builds of WP7 (most recent versions of Yuki’s Back to the Future, HD2O, and Ultrafruit). Yuki’s Back to the Future is what I was running before most recent repair. In all cases the touch screen is entirely unresponsive. If I flash back to stock, it works perfectly again. So I gave up on WP7 and tried Android.
I am less experienced in flashing Android NAND, so this might be a silly mistake on my part, but I have flashed Android before both on my HD2 and on my friends’. I find I can’t get into CWM Recovery from MAGLDR. It stops after 123456 GOGOGO. I have tried the 250MB recovery from here (1) and the 200MB 5.200.5 recovery from the fourth post in this thread (2).
I am on HSPL 2.0.8. I have followed the following process for both WP7 and Android using mainly ksubedi’s HD2 Android Toolkit:
• Task 29
• Radio 2.15
• MAGLDR 1.13
• Enable last 24 NAND (WP) or Install recovery (Android)
Has anyone got any ideas? I have never had any problems before. I’ve noticed that my problem seems similar to the ones here (3) and, particularly, here (4). I have tried most of what was suggested in these threads. It seems unlikely but I’m wondering if the new screen from the most recent repair is causing this problem. The OP in the second thread seems to have exactly the same situation: new screen, touch screen doesn’t work in WP7 but does in WM6.5, can’t boot recovery.
Sorry for massive post, was trying to give as much information as possible. Apologies if I have missed something really obvious.
(1) http://www.addictivetips.com/mobile...kmod-recovery-on-android-htc-hd2-with-magldr/
(2) http://forum.xda-developers.com/showthread.php?t=1507792
(3) http://forum.xda-developers.com/showthread.php?t=1472556
(4) http://forum.xda-developers.com/showthread.php?t=1603428
Edit: Messed up the links so have just put them at the bottom. Sorry!
Your guess is correct. Recently read about it, but the link to can not.
The problem is that there are several revisions touchscreen. In the new right, works only on WM6.5. So it's best to find a screen with a broken system, so to say the donor. Other options can not help you.
try the links below, you can even triple boot now
d_3ger said:
Your guess is correct. Recently read about it, but the link to can not.
The problem is that there are several revisions touchscreen. In the new right, works only on WM6.5. So it's best to find a screen with a broken system, so to say the donor. Other options can not help you.
Click to expand...
Click to collapse
Hmmm.
Damnit. If that's true then this is the worst repair ever! A repair which makes it unflashable!
Is it definitely the screen that is causing the problem and not a new mainboard (they may have replaced more than just the screen)?
Is there any way to confirm for certain that this is the problem? I saw some guys talking about something similar and suggesting editing the bootloader with JTAG. Could this work?
http://forum.xda-developers.com/showthread.php?t=881912
http://forum.xda-developers.com/showthread.php?t=887337
mengfei said:
try the links below, you can even triple boot now
Click to expand...
Click to collapse
Thanks for the link. I'll give it another go using your guides and see if I had been making a mistake somewhere.
I've now also tried booting into Recovery from cLK and booting into an Android SD build.
Both have which have also failed.
Recovery from cLK crashes at what appears to be the same point as from MAGLDR.
Android SD build stops at "Jumping to kernel (custom). I used Nexus HD2-ICS-HWA-SD_v2.7.
It really does look as though it is now unflashable, as d_3ger said.
Bah.
I am wondering if maybe they may have used parts from a TMOUS HD2 in repairing my HD2.
Is this plausible and might it have caused the problem?
Related
Hi!
The touchscreen of my phone almost doesn't work. I've read many topics about this in different forums and maybe a solution would be to reinstall all from 0 (resetting the phone with that yellow button when you revome the back doesn't work anymore).
So, I want to try to install android hoping this will solve the problem. If not, my phone will be a thin brick in a drawer.
Since the touchscreen is not working correctly, I can't go to see the details in the menu.
The phone was flashed once and currently has a rom called BSB beast 6 and when I turn it on, this red numbers appears:
2.10.50.26
15.39.50.07u
2.11.86834 8g
Current OS is Windows Mobile 6.5
I believe android will work with the current rom without the need of installing another one before, right?
Would recommend me one rom (android NAND) to put? because I saw a lot in thread here and I don't really understand what the differences would be. I just want the phone to work
I hope this is enough information
Thanks a lot!
If you want to flash Android what you need to do is...
Make sure you have 2.08.HSPL (I'm assuming you do as you have a custom ROM).
Then flash the newest radio (2.15.50.14)
Flash MAGLDR
Flash a NAND ROM of your choice.
Though I doubt that will fix the problem. Your digitizer is probably gradually dieing. You can easily get it fixed for about $80.
alc112 said:
Hi!
The touchscreen of my phone almost doesn't work. I've read many topics about this in different forums and maybe a solution would be to reinstall all from 0 (resetting the phone with that yellow button when you revome the back doesn't work anymore).
So, I want to try to install android hoping this will solve the problem. If not, my phone will be a thin brick in a drawer.
Since the touchscreen is not working correctly, I can't go to see the details in the menu.
The phone was flashed once and currently has a rom called BSB beast 6 and when I turn it on, this red numbers appears:
2.10.50.26
15.39.50.07u
2.11.86834 8g
Current OS is Windows Mobile 6.5
I believe android will work with the current rom without the need of installing another one before, right?
Would recommend me one rom (android NAND) to put? because I saw a lot in thread here and I don't really understand what the differences would be. I just want the phone to work
I hope this is enough information
Thanks a lot!
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showpost.php?p=12105680&postcount=1
Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).
Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.
Hello..a friend of mine gave me a HD2 to fix, said it can't load anything. As I own a HD2, I took it just to see what's wrong. I own an Asian HD2, and everything is fine, I tried various ROMs..both Android and WinPhone, settled at Hyperdroid. Anyway, I have no idea where the heck the other HD2 is from, neither my friend has.
So, the phone had nothing in it and was stuck at the HTC logo, so I loaded into bootloader and saw HSPL 3.03. Then I changed it to 2.08 in order to install MIUI android. Then I installed MAGLDR. The issue occured when I went to install CWM. I loaded the 150M partition at USB Flasher, it was doing all fine until it became stuck at "reset now...!". So I just took the battery off, and tried to load into AD recovery. While it loads to 1, then it shows "fatal hit" error. I tried a lot of times including task 29, but it persists. Was the phone bricked from earlier ? Something like heating issues I assume. Anyway, I tried to install my phones stock WinMo rom to it from SD but it also gives error like failed, not allow etc. The both phone looks the same, under the battery hood of my phone, it's written HTC HD2 T5858. On the other one, nothing. Rest visuals are same.
So is there any way I can bring this anonymous HD2 to life ? I think it's almost dead but still if there's any way you people can come up with. I'm using a 2GB Sandisk MicroSD and the phone's S/N is HT01CNW04979 ; if that helps to sort out the phone's identity. Your help is much appreciated. Thanks
http://forum.xda-developers.com/showthread.php?t=1520439
this is a thread I created 3 days ago....me, another user, and now you...
our hd2s are going to diee D: stop joking, I (and toher guys) think that is hardware related....like in my case....but I don't really know what's the problem, just guessing....take a look to my post
True that. Only the difference is, it's happening to me during clockwork recovery installation. And I don't know where the heck is the phone from so that I can load custom WinMo lol. My own HD2 is doing just fine by the way.
http://imageshack.us/photo/my-images/263/87604378.jpg/
http://imageshack.us/photo/my-images/412/59177201.jpg/
Hello;
It's been 5 days that i'm reading about this problem, and i didn't find any reliable solution, so i'm posting it here:
I've juste flashed my third HD2 with a new radio (2.15) an android NAND rom (the Nexus HD2 ICS), and since then i can't get into the bootloader mode, i've tried the vol -, the adb reboot bootloader, and nothing works.
i want to access the bootloader to downgrade the radio to the 2.12, and without the connection to usb via activesync, i can't do it. i just can access the MAGLDR menu when it says WPH not installed (i think it's the source of the problem) and then install roms.
So if anyone can help me changing my radio without the bootloader or how to get it back, i'd really appreciate it.
Vol down works perfet on WM6.5 and on android, and i've tested it with the key tester in Recovery mode
No answer?? no one raising the finger?? So basicly there's no solution for my problem!!!
Aaaaah did you change the boot source looks like Its trying to boot windows mobile and you have android installed btw we have no fast boot support in magldr. Change the boot source under services and technically it should work
Sent from my HTC Desire HD using XDA
I restored the boot source to Android from NAND, and it just simply avoids the "WPH not installed" message on Magldr, nothing to do with the bootloader who is still missing... anyway thanks for the tip.
Lol if your bootloader is gone your phone would be bricked!
Sent from my HTC HD2 using XDA
Big-amine said:
I restored the boot source to Android from NAND, and it just simply avoids the "WPH not installed" message on Magldr, nothing to do with the bootloader who is still missing... anyway thanks for the tip.
Click to expand...
Click to collapse
I don't think your alone because I've read a similar thread a while back but I can't seem to find it again. Basically it was reported to be an issue for many users who had used HSPL4 to flash HSPL or something like that. I did and can still access the bootloader but others have had problems. I don't think it should be something to be too concerned about unless you want to restore back to stock WinMo to send it in for repairs or something or if you want to change bootloader from MAGLDR to cLK. Flashing the radio as you wanted to do can be useful but I doubt there's a significant difference between these. And whenever anyone mentions 'do a Task29 to be safe' it's just BS. Task29ing is unnecessary in most situations but people have simply got into the habit of doing so every time they flash a ROM (which can actually be bad for the phone as it can eventually lead to bad blocks from what I've read) so whenever people ask for help their first response is Task29. Basically, I would say that you shouldn't worry about it too much
Hi all,
This week I finally replaced the screen of my old HD2, but now android won't boot anymore.
I've included the whole logcat file, but i think this are the errors that are the problem:
Code:
W/AudioFlinger( 252): Thread AudioOut_1 cannot connect to the power manager service
and/or
Code:
E/libcore ( 258): Failed to initialize the core libraries; aborting...
F/libc ( 258): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
Everything seems to work fine, it vibrates on boot, i can go to CWM, and with aroma installer I can check that the touch screen is working,
Only the volume UP button is working a bit weird, but this isn't a reason to not boot i think?
Hope some one can help me out with this.
EDIT:
Forgotten to mention, I've 2 HD2, one had a cracked screen and the other wouldn't boot, so i have take them togheter to one working HD2, so I have almost everything a spare part of.
Thanks!
Greets,
Incomer
wrong section. should be in Q & A.
Sent from space..
My fault, can anyone move it?
You can flash it again ?
It really is weird, that replacing a screen would halt android from booting. But my guess is that maybe you have replaced the screen from another manufacturer. One of them is sharp and the other i dont know. So maybe the registers have not been properly placed.
Try repeating the flashing from task29 onwards.
And the other thing is...if you had crossed over EU and TMOUS version of the hd2, there maybe problem primarily with the mobo not compatible with the WLAN/B/GPS/Camera board on the top or vice versa.
Hoping you had the same version of HD2s.
ayyu3m said:
It really is weird, that replacing a screen would halt android from booting. But my guess is that maybe you have replaced the screen from another manufacturer. One of them is sharp and the other i dont know. So maybe the registers have not been properly placed.
Try repeating the flashing from task29 onwards.
And the other thing is...if you had crossed over EU and TMOUS version of the hd2, there maybe problem primarily with the mobo not compatible with the WLAN/B/GPS/Camera board on the top or vice versa.
Hoping you had the same version of HD2s.
Click to expand...
Click to collapse
Both HD2 are EU version.
Maybe something is not completly connected, but so far as I can see everything is fine, but maybe anyone can see in the logcat from which part the error is coming .
I have already reflashed the HD2 multiple times with different rom's
have you tried using the hd2 toolkit and flashing a custom win6.5 rom and working backwards from there? it might fix it
Thread moved to proper section.