Hy everyone;
Because i am not allowed to post in the development forum i had to post my problem here...
I had the "HD2O© v1.14 WP7 BUILD 7.0.7392.0 NODO" ROM and now want to flash "blackSideSeven v2.05.7592".
I execute the "Task29" Utility. And made a HardReset.
Then i installed the Mango ROM like i did it by HD2O before in the MAGLDR.
But now the problem is that only the HTC Screen appears and nothing else.
I also installed it a second time, same problem...
What can i do?
EDIT: Now i flashed HD2O again and it works perfect.
So, only blacksideseven not works...
_______________________
i know...bad english^^
I had the same problem with the latest XBmod ROM. After installation it just stops in the HTC screen.
I also didnt get help so far...
Did you try another Mango ROM?
Maybe you take out your SDCard, format it with some proper format tool to make it clean.
then you reformat the fone with task29.
then you try again.
its also 2.06 out now. try that.
I can just say for myself that I only tried the XBmod ROM. I did Task29 etc... SDFormatter... nothing!
I dont have a SD Card in my HD2
I do find it kind of odd that I'm unable to flash mango again. It all started when I decided to flash blacksideseven 2.06 rom from elfinlazz mango, which has been working. I've always been able to flash WP7 without ever having to do task29. Well, in the process of flashing blacksideseven I had a problem as it was throwing an error everytime it reached part.004. I tried it two more times with the same result. Then I moved to a different port and successful on the second attempt. It never worked as either it was caught in a boot cycle or it was just freeze at the HTC screen. I decided to do task29 and reflash magldr and the rom again but still can not get in. I tried elfinlazz rom again and then Yuki's but still no luck. Changed SD cards and nada! So as of right now I'm currently starting everything back from scratch by doing task29 and then magldr and stock 6.5 and then back to mango to see what happens.
P.S. As I'm writing 6.5 started up with no problems! Need to charge the phone because I've been at this since last night. I hate this!
Edit: It worked. But, you know what? I think I'm staying with 6.5 now. I mean WP7 was fun for me for 6 months that it was on my phone from dft original all the way up to mango beta 1. I found myself using my android side more often than WP7 every since Mango because I needed something reliable as WP7 mango had issues due to its beta stage. Not even 20 minutes passed before my WP7 got a no sim error! I thought I needed to restart it anyways and on the subsequent boot up it rebooted 5 times before it got stuck on the htc screen for 35 minutes. Another manual reboot worked but 20 minutes later it just went to no sim error again, so I decided i'm not gonna take this headache anymore! Elfinlazz rom previous was good but there were certain things I needed like data that didn't work 100% of the time. Again, it was fun. I believe I may go back some day. Hopefully somebody will work out the SD card issue because I believe this is the main problem I have with WP7. Maybe some workaround in the future. Good luck guys!
Now i have installed http://forum.xda-developers.com/showthread.php?t=1157535 and it works without problems...
Thats the ROM I had before trying to flash Blacksideseven. It was fine for a few days and then after that the data stopped working regularly. Then about a few days ago data disappeared entirely! That is what prompted me to try a different ROM. Now I'm stuck back with 6.5. Eww! Now it reminds me of how clunky this OS is. Been on it for few hours and I'm missing my WP7 already! Thank god I still have my android.
Related
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
I would relock and the re-unlock your hspl and see what happens. That is indeed a weird problem (that you can't send your phone in for).
Good luck
TheWizzard2203 said:
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
Click to expand...
Click to collapse
sounds like a defective phone!!!!
Yeah, that was my idea too. I tried relocking and reunlocking it with HSPL, but that doesn't matter.
But the problem is, how do I explain this to HTC if I want to send the phone to them for repair? I can't tell them that the problem only occurs when I install a custom made rom.
Pfff okay, I found the solution. It wasn't a hardwareproblem after all. I went through a terribly long trial and error procedure but finally pinned the problem down to only one cabfile, named HD2MemTweak found in the registry tips and tricks section of the general forum of the HD2.
I'd installed the lastest official 3.14 rom and installed all the cabs I was used to. But noticed, after several reinstalls, that when I installed that specific cab and rebooted the phone, everything went wrong. So I installed it without that cabfile and allw as working fine again. Then reinstalled HSPLv3 and installed the latest NRG Cookie Classic rom, which works fine again.
So that was the problem indeed. But one thing is strange of course, is that the mentioned cabfile used to work and suddenly stopped working. Could this maybe have something to do with the fact that the latest roms were build on the new 3.14 official rom? Who knows.....
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Guys,
I'm kindly asking to share your thoughs on any of the questions. It is very important for me since I don't know whether it is my fault or the phone was already damaged.
The rom I tried to flash was a stock rom and the flashing process hasn't been interrupted.
Thank you!
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
az_registration said:
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Click to expand...
Click to collapse
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Thank you for your replies!
T-Macgnolia said:
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Click to expand...
Click to collapse
Yes, that's a useful tool, but I'm afraid that I might damage the existing rom and will not be able to flash it agian. Also it requires to flash HSPL before which also potentially might brick the device ( I mean the flashing process).
sike222 said:
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
Click to expand...
Click to collapse
So it was a factory defect, wasn't it?
If I did something wrong during the stock rom flashing process, could be the reason of the problem?
Thank you.
After reading forums it seems to me that the issue appears mostly for T-Mobile US version..
If it is a hardware problem, does anybody know what part of hardware is damaged?
Thanks!
I installed MCCM GB V2.0 Gingerbread HoneyComb Sense theme [kernel tytung_r5] and for the beginning everything worked fine. But after installing some apps and rebooting, the phone app gave robotic sound and asked for force closure. I tried to reinstall, reboot several times but same problem exists. I formatted sd card with SDFormatter 2.0 completely. Still prb exists. What am I doing wrong or is this a general problem everyone having? HD2 details as follows: WM 6.5 Build 1.66, Radio 2.10.8, HSPL 2.08. I would very grateful if someone could help me out with this prb.
How did u flash your ROM ?
Did u use CWM or DFT method ?
muzap2000 said:
I installed MCCM GB V2.0 Gingerbread HoneyComb Sense theme [kernel tytung_r5] and for the beginning everything worked fine. But after installing some apps and rebooting, the phone app gave robotic sound and asked for force closure. I tried to reinstall, reboot several times but same problem exists. I formatted sd card with SDFormatter 2.0 completely. Still prb exists. What am I doing wrong or is this a general problem everyone having? HD2 details as follows: WM 6.5 Build 1.66, Radio 2.10.8, HSPL 2.08. I would very grateful if someone could help me out with this prb.
Click to expand...
Click to collapse
No, I just flashed it to sd. and another problem with my phone is I cannot flash anything radio, wm custom, etc. when i start to flash anything via active sync, RUUCustom starts bootloader on the phone, shows the progress bar (bar stays at 0% always) and it stays for approx. 2-3 minutes and gives an error "connection error" and goes to recovery stage. I remeber last time I just falshed HSPL. That's it. Since that time I can't flash anything like radio, magldr etc. That's why I flashed android to sd by just copying android folder to sd and running clrcad.exe and haret.exe. I'm a novice and don't understand much. But I have general idea. If anyone can help me to sort out above problems, I would be very grateful.
Got the same problem with that build. I heard that it's caused by some sort of memory problems, Anyway I didn't found the solution.
Could be left over data from previous build, delete data of the apps that keep crashing.(Dialer, Dialer storage), reboot, try again.
Ok first and foremost...I have tried searching
I have been a lurker most of the time here on xda seeing as if I just search and read I'll get most of my answers, but not this time.
Ok some background info first:
TMOUS US HD2 1024Leo
Radio: I'm not 100% sure but I did a task29 that supposedly flashed 2.15.50.14
HSPL: 2.08
MAGLDR 1.13
I bought this phone about a year ago, flashed tytung's Nexus HD2 Gingerbread rom which worked flawlessly for about 10 months or so. One day the phone froze up, pulled battery then inserted and the rom reset to the point where it was like new. Around that time tytung's ICS AOSP thread came alive and I followed it closely watching the updates and what not.
I never installed it until Beta 10. Followed his instructions, set up the partition to 200MBs with a cache of 45MB...45MB for cache because I suspect I may have some bad NAND blocks. Anyways install went flawlessly, everything that was supposed to work, worked...ect ect
Used it for about 24hrs then all of a sudden it froze, when I rebooted I started getting all these random apps crashing(gapps[google apps?], Email, Google Login Services ect), needless to say I task29'd the HD2 and reinstalled everything, worked fine for a day then everything started crashing again.
So after all that info I'm just wondering if someone is experiencing the same problems and/or can maybe lead me in the right direction to figure out this problem.
I know its only a beta but I havent read many posts containing my problems. So Im just left wondering if my NAND is going bad completely and I need a new phone or if theres just something I'm doing wrong.
Before i begin - I have no experience with that Rom, these are just common general ideas.
1) as the rom starts well and then only after a day it breaks, maybe it is because of something (update) getting installed on your device. Have you tried fixing permissions after you encounter the problem?
Or try figuring out which update of which app does it.
2)It also might be the problem of the nand bad blocks, if you suspect it, but if thats the case, there is not really a lot you can do...
No offense, but that's the reason its beta. It doesn't have all the bugs worked out yet.
If you're looking for a daily driver, you should try something more stable.
Hi,
Not sure if you still have this problem..
Have you tried re-installing the ROM again or a different ROM to confirm if the issue is with your phone (hardware) or with the ROM (beta version)?
Hello,
I've experienced the following problem:
I have installed WP7 from XBmod-Yuki's thread. Everything was great, until the moment in which i decided to update my system with Zune. I connected the phone and a long process begun. After the update everything seemed to be working, but when i locked the screen and waited a couple of minutes i wasn't able to unlock the screen - pressing all the hard buttons just didn't work, also the phone restarted by itself.
Can anyone tell me why, please?
dont know whats wrong but much safer is update with CAB files.. i very suspicious to MS updates.... you never know what MS pushing....
I believe there is some kind of a bug, since it did it with the downloaded rom too.
Don't panic, it's just a known bug with update of Yuki's ROM via Zune. Best solution is just to flash with the last Pdaimatejam ROM