Please Help... - Mogul, XV6800 ROM Development

I posted this in the Titan forum by mistake. Sorry for the duplication
I need some help...I'm freaking out...
I cooked a ROM with dcd's version 1.6.9 for BELL a few days ago and it was wonderful and worked great.
Today, I tried to upgrade to version 1.6.10 and I f___ed something up.
It starts the htc boot up screen as usual, then the Bell screen comes up as usual, then a Sprint screen comes up briefly and then the Windows Mobile screen comes on and HANGS........
I have tried cold reboots, and nothing. I cant connect to it with USB.
I can kick myself for making an error because I was rushing......
Can anyone please help............................
Edit/Delete Message

koilmaker said:
I posted this in the Titan forum by mistake. Sorry for the duplication
I need some help...I'm freaking out...
I cooked a ROM with dcd's version 1.6.9 for BELL a few days ago and it was wonderful and worked great.
Today, I tried to upgrade to version 1.6.10 and I f___ed something up.
It starts the htc boot up screen as usual, then the Bell screen comes up as usual, then a Sprint screen comes up briefly and then the Windows Mobile screen comes on and HANGS........
I have tried cold reboots, and nothing. I cant connect to it with USB.
I can kick myself for making an error because I was rushing......
Can anyone please help............................
Edit/Delete Message
Click to expand...
Click to collapse
Try the hard reset.
If that doesn't work then try the bootloader mode and reflash it.

Hard reset
Hard reset did not help, it hangs on windows mobile screen.
Can u give me a bit more detail on how to get into the bootloader mode?

I figured it out. You have to but it into bootloader mode by pressing the POWER and CAMERA buttons at the same time and then reboot.
Then load ROM as usual'
Thankyou

You are the fing master. OMG mine was in the EXACT situation and i was freaking out. its currently reloading the ROM back on. Thank you soooooo much.

it probably happenned because modules overlapped, run g'reloc before building to avoid this.

Related

Stuck on splashscreen

So I followed the simple steps of unlocking my phone then installing VetVito's Aero Windows Mobile (6.1.1) OS but did not install the radio 3.27 and now am stuck on the HTC splash screen. I've tried soft and hard resets with nothing to come out of it and at this point I cannot get into the OS to install a new OS, install the radio or do anything by this point. What are my options or at this point is the phone bricked? Thanks in advance.
Jim
hold cam+power and hit the reset button to enter your bootloader. Flash the 3.27 rom and thank me later
bimmerd00d said:
hold cam+power and hit the reset button to enter your bootloader. Flash the 3.27 rom and thank me later
Click to expand...
Click to collapse
I thank you very much good sir, I was about to crap myself but NOW the phone keeps turning on then immediately keeps restarting. I read that it might be a problem with the SD card so I took that out with no resolution as soon as it turns on it pretty much immediately restarts, any idea's? BTW i have tried once again hard and soft resets with no help to come out of it. Thanks again Bimmerdood.
yah, I'm stuck with you in the same spot. I somehow screwed up installing 3.27 radio. It got stuck at the splash screen. So I did a format, and found a 3.16 .nbh file. Since everyone releases the installs as complete executables, grabbing a .nbh file is a pain.
Found one, got it to load past the splash screen but the thing resets immediately. I get about 1 to 20 seconds before the reset occurs. Annoying the crap out of me. Looking for another nbh file to try and hope it works.
docgiggs said:
yah, I'm stuck with you in the same spot. I somehow screwed up installing 3.27 radio. It got stuck at the splash screen. So I did a format, and found a 3.16 .nbh file. Since everyone releases the installs as complete executables, grabbing a .nbh file is a pain.
Found one, got it to load past the splash screen but the thing resets immediately. I get about 1 to 20 seconds before the reset occurs. Annoying the crap out of me. Looking for another nbh file to try and hope it works.
Click to expand...
Click to collapse
hold cam+power and hit the reset button it will get u to bootloader...load 3.27 radio put your phone in bootloader again and load new rom! Good luck
I thank you to my good man. =D

Rom flash problem

Can someone please help me? I tried flashing a new rom to my phone and now nothing works. I installed the hard spl to unlock the phone. I then installed a rom update utility. When I flashed to the new rom I screwed up and did it while the phone was on the today screen. Now the phone just vibrates and says TOUCH pro then shuts off. It keeps repeating this. Now the active sink says it cannot connect with the phone. I don't know what I can do now, or if a completely screwed up my phone. It is brand new and never even been activated. please email me at [email protected] if you can help me.
Thank you,
Mike
sounds like you need to do some reading... flashing from the today screen isn't a problem, just gotta have an activesync connection.
put your phone into bootloader mode, and then flash a stock/shipped ROM that is meant for phone. since you've got a cdma pro i would suggest making sure you're flashing a cdma touchpro ROM.
ppcgeeks is a little more geared toward CDMA phones than here on xda

ROM error message

Through a comical accident, my FUZE was trhown agaisnt a wall and landed on a computer keyboard, which then Bluescreened. Why ..I don't know. But the phone came apart. When I put it back together, it started with a error message....
It boots into the Tri colored screen and says ROM loading error, please try again.
I originally had OlipPro spl on the device. After reading for about an hour, I tried to reinstall the hard spl. that didn't work. I found a stock spl from the forum here and tried raphimg.nbh. That boots but goes into a Loading... screen with no other action.
I can't imagine what caused this...I was in the dentist office when the accident occured. I would expect this to occur if I was flashing or something.....
Any one have any thoughts...or is this bricked
alodar1 said:
Through a comical accident, my FUZE was trhown agaisnt a wall and landed on a computer keyboard, which then Bluescreened. Why ..I don't know. But the phone came apart. When I put it back together, it started with a error message....
It boots into the Tri colored screen and says ROM loading error, please try again.
I originally had OlipPro spl on the device. After reading for about an hour, I tried to reinstall the hard spl. that didn't work. I found a stock spl from the forum here and tried raphimg.nbh. That boots but goes into a Loading... screen with no other action.
I can't imagine what caused this...I was in the dentist office when the accident occured. I would expect this to occur if I was flashing or something.....
Any one have any thoughts...or is this bricked
Click to expand...
Click to collapse
A brick it is not. After reading the notes in the Disaster Recovery thread, I found a stock ROM in the WIKI and tried to flash it. Because I could get a USB connection, the ROM loaded. And, after a couple of hard resets, I now have my FUZE functional again. Thanks for the WIKI and all the experts here that contribute.
alodar1 said:
I can't imagine what caused this...
Click to expand...
Click to collapse
Something to do with the wall?
I expected this to be something like "What does error 206 meanzorz111!!1?"
Quite refreshed to see that that was not the case. I am glad you fixed your error. I have had issues like that with my kaiser before, and since I got windows 7, the comp recognizes the device even from bootloader. Congrats on solving your issue, best of luck in the future, and dentists are bad
I've never had a cavity, ever. Brush once a day and haven't seen a dentist in 3 or so years $$

[Q] Htc hd2 won't boot windows mobile

Hello!
I use android with the htc hd2 for about 1 year ago, and the i want to back to windows mobile. I came from android, and when i finished the rom install the phone is stop when the windows mobile (orange color installer,please wait while your device is starting for the first time...) installer is finished it's always power off or just do nothing. I try to install a custom too. Neither the original and neither the custom din't work. The android work great, but i want the windows mobile 6.5.
If you have an idea please tell me.
Sorry for the bad english.
First of all, congratulations to your first post.
How have you tried to install WM?
Have you removed HSPL?
Have you changed RADIO?
Maybe you will have a look on this thread: http://forum.xda-developers.com/showthread.php?t=1421179
uli71 said:
First of all, congratulations to your first post.
How have you tried to install WM?
Have you removed HSPL?
Have you changed RADIO?
Maybe you will have a look on this thread: http://forum.xda-developers.com/showthread.php?t=1421179
Click to expand...
Click to collapse
I find my problem:
MicropERROR:
Microp Version Mismatch
0x0
Please update lateset Microp
firmware
What can i do?
somebody have the same problem?
The touchscreen isn't work in windows mobile, but if i install android or windows phone 7 the touchscreen is working
Mene44 said:
I find my problem:
MicropERROR:
Microp Version Mismatch
0x0
Please update lateset Microp
firmware
What can i do?
somebody have the same problem?
The touchscreen isn't work in windows mobile, but if i install android or windows phone 7 the touchscreen is working
Click to expand...
Click to collapse
I changed the radio the spl,hspl, rom(custom,orginal)... but nothing
bear with me here, guys, as i am new to not only this site, but to the world of htc and smartphones all together...i apologize in advance!
so my friend had this htc lying around and said i could have it since my previous phone took a crap. it's on tmobile so i was going to have it flashed over to at&t.
however, the phone seems to be a brick....it will not boot past the initial "stick together" screen.
yes, i tried the hard reboot...pressing and holding volume up+volume down+power button. it takes me to the screen asking if i want to reset the device..i hit volume up to confirm. it goes through the reset. i hit volume up to boot the device. it gets to the "stick together" screen, vibrates 7 times, and freezes.
well, it was doing that anyway...but only when plugged in. the little orange light used to turn on when i connected the charger--now nothing.
and now it won't let me into the hard boot screen again. just...black. removing the battery and replacing it does not work.
i had taken it to the gentleman to flash it to at&t, not knowing this problem existed. he called me (because i left the phone there, since he had a line of people) to tell me the phone was freezing on that screen. i gave him the ok to do what he called a "hard wipe". i went back for the phone this morning and he said he did the hard wipe, and it was still freezing--told me the phone was only good for parts at this point.
so i took it home. i plugged it in, and i did what i described above.
what the heck do i do?! i would love to be able to rescue this phone! like i said, i'm totally new to all of this so if you're going to throw terms at me like RUU (which i saw all over this site), i have no idea what you mean so please post a link to another thread or something that can explain these things to me, if you do not want to do so yourself.
oh, my friend also said she had put an at&t sim card into the phone (unflashed, still on tmobile) before and tried to turn it on...but nothing happened. could that be what caused the problems?
UPDATE: took the battery out for approximately 10 minutes. put it back in, and the phone turns on again...one short vibration while the screen is still black, then the "stick together" screen pops up and the phone vibrates 7 more times....annnnnd freezes again. its also starting to get very hot on the bottom, backside...

[Q] Help needed to unbrick HD2 - After restoring WinMo rom

Hi guys,
I successfully flashed Android to my HD2 a few months back. I used what I believe is Cotulla's rom(?). However the other day my phone sorta died and whenever I plugged it into the charger it would vibrate go through the boot screen and reset at the "1234 go go go" stage. I read some reading on the forum and flashed it back to "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship" from the HTC website, using the SD card. Windows mobile restored the phone and I started using it again.
I tried to put android back on it and I think I unsuccessfully tried to update the radio after which the phone sorta died again. So I thought ok, no problem, lets get back to windows again. So I installed the HTC rom again through the SD card, which the screen told me was successful. But now I can't get the phone to boot or go into bootloader or anything. When I plug the charger in, I get a vibrate and HTC bootscreen, with the red writing at the bottom left and then dead to only do this again and again. If i pull out the charger, the phone just dies. Battery charge was about 50% when it died.
Any ideas or help on how to resurrect my beloved HD2 would be greatly appreciated!
*quick update*
I stuck the phone in the fridge for a while and managed to get it into the bootloader just once and flashed the official winmo rom again, which was successful but still dead phone!
What made you decide to stick the phone in the fridge??
What is your SPL version??
mentalityx said:
What made you decide to stick the phone in the fridge??
Click to expand...
Click to collapse
Probably the dozens of threads that talk about successfully flashing only when the phone has been cooled.
@op it doesn't look good. Usually the fridge trick working implies hardware overheating issues.
Just confirm please, its not a tmous right?
Samsamuel is right, i just read about it and thought hey, why not! plus it got a priceless look from the mrs! lol
It's definitely not TMOUS, its UK Virgin and the SPL was 3.03.0000 if I recall correctly.
When I cool it, I can get it into bootloader, but only once.
well, i still suspect its hardware and unfixable, but there have been cases where for whatever reason a rom suddenly seems to fix it. Try all the versions of the correct stock Rom.
Try the 1.43 the 1,66 and again the 3.14, wwe ones, chilling the phone well before each flash, a good 20 mins.

Categories

Resources