I wanted to try NFSFAN's custom 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
esskay said:
I wanted to try NFSFAN's custom 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
OK, relax - its not bricked
the D 3NFS is just NFSFAN's signature on his ROM's nothing to worry about there
First try pulling the battery for a couple minutes and then putting it back in and trying to start, if that still fails, have you tried to hard-reset the phone? red+green+stylus in hole at bottom and hold until the gray screen appears warning you your about to reset the device (your lose you data but it will reload the last ROM you flash
try those if that still doesnt do it, rename the RUU_signed.nbh file to VOGUIMG.nbh and copy it to your SD card then put the SD card back into the phone and press and hold the power+camera+stylus and it will reflash from the SD card (referred to as bootloader mode)
hope that helps
Detroit Doug
I'm up and running again!
I can't thank you enough Detroit Doug, I don't know what I would've done without your help.
Same problem.. put NFSROM's 6.5 rom on my vogue and it worked fine at first, but froze while i was changing the Today theme, and when i soft-reset, it hard-reset itself instead. Never heard of that happening.
After the hard reset it restarted itself as usual, but never recovered after that, just gets stuck at Bell loading screen eternally.
I think it might be because I let customization run the first time, forgetting that I was supposed to reset before customizations run. Possible?
Anyways, I'm trying your last suggestion Detroit_Doug, I put the RUU_signed.nbh on my microsd and renamed it to VOGUIMG.nbh (no other files), popped it in and put it in bootloader... now it's at the gray screen saying it's updating, but the progress bar isn't going anywhere.
Any other solution to recover?
...
Fixed it. I gotta look around more for solutions! I downloaded the official Bell ROM from the HTC website and that ran flawlessly.
Now to do it all over again!
blackrook said:
Same problem.. put NFSROM's 6.5 rom on my vogue and it worked fine at first, but froze while i was changing the Today theme, and when i soft-reset, it hard-reset itself instead. Never heard of that happening.
After the hard reset it restarted itself as usual, but never recovered after that, just gets stuck at Bell loading screen eternally.
I think it might be because I let customization run the first time, forgetting that I was supposed to reset before customizations run. Possible?
Anyways, I'm trying your last suggestion Detroit_Doug, I put the RUU_signed.nbh on my microsd and renamed it to VOGUIMG.nbh (no other files), popped it in and put it in bootloader... now it's at the gray screen saying it's updating, but the progress bar isn't going anywhere.
Any other solution to recover?
...
Fixed it. I gotta look around more for solutions! I downloaded the official Bell ROM from the HTC website and that ran flawlessly.
Now to do it all over again!
Click to expand...
Click to collapse
No problem - the SEARCH feature can be your friend LOL
As for the initial issue - it came with the today theme - you state you flashed to 6.5 ROM which will NOT use today themes (not sure if it was a misused term on your part or if you were actually trying to use a today theme on a 6.5 UI (Titanium or CHome as it is referred to)
Even then, if you are flashing to the 6.5 ROM and wanting themes, they really are not needed - change the overall color via then included color themes and/or install the Color Bar cabs which can be found around the forum and then just browse to a picture it will work great doing something simple rather than complex on a pre-release OS
There are some "themes" available, but be careful and read the threads regarding them before installing and try to keep to the ROM thread itself when applying themes as other users will report pros and cons of such action and can keep you from having to hard reset or completely re-flash your phone for some colors and graphics
Detroit Doug
Related
Hi All,
A couple of days ago, my HD was slow to respond so I did a soft reset. However, it got stuck on the 'smart mobility' startup message and wouldnt go any further.
As a test, I reflashed a radio via the SD card but this had no effect either. So I bit the bullet and reflashed another ROM from the SD card. This seemed to work and the new ROM loaded as normal but after a couple of soft resets the same thing happened (wouldnt go past 'smart mobility' on boot).
Today I flashed HardSPL again via SD but that didnt seem to work. Now my device goes straight into bootloader mode and says 'Upgrade ROM code error Please try again'.
Ive started to pull my hair out on this one, so any advice is much appreciated at this point!!
What next steps can I take?
remove the battery for 30 minutes or so then try flashing a stock ROM from SD, if you haven't yet. Also you can try flashing via RUU, just remove the SD from the slot.
If that doesn't help, perform a hard reset...
I managed to get it going by reflashing hardspl and putting on a new rom. However after a few reboots, the phone just keeps getting stuck at 'smart mobility'.
I cant keep doing hard resets as this happens everytime after soft restarting.
If the problem persists with a stock ROM and original SPL, take it back to you vendor for repair/replacement.
Ive managed to get it going with stock SPL and panosha rom.
Is it possible a corrupt memory card is causing this as now its removed, the issues no longer happen (or is it just coincidence)?
slud said:
Ive managed to get it going with stock SPL and panosha rom.
Is it possible a corrupt memory card is causing this as now its removed, the issues no longer happen (or is it just coincidence)?
Click to expand...
Click to collapse
Could be a coincidence. If you revert back to the ROM that kept failing, what happens now?
Thats actually the ROM ive been having issues with (sticking with it as I know something else is at fault here, not the ROM).
I havent tested very much yet, just using another phone for now until I get more time.
first things first: the hd2 is my very first windows mobile device. i've already read the wiki and searched the forum/the internet for help, but i didn't find a solution for my problem. i'm also not a newcomer when it comes to flashing (i've gained some experience from my psp/wii/nokia n82/creative zen).
so i got my htc hd2 a few days ago and one of the first things i tried was flashing a rom (i didn't like the t-mobile branding).
i had absolutely no problems installing hspl (this forum was very informative) and flashing the artemis rom (i strictly followed the instructions), which i found in the rom developement sub forum. since everything seemed to work fine, i started adding my contacts and some applications, still no problems.
but after a while one of the apps seemed to have crashed and the phone became unresponsive.
i removed the battery and turned my phone back on, but it was stuck in the boot screen (the very first screen on which it says "r g d" in red at the bottom). since i didn't know what to do, i simply flashed the artemis rom another time and so the story repeats: at first everything worked fine and after a while the phone got stuck again.
after 4 tries i decided to switch to the shock star r9 rom (also found on xda), which also seemed to work fine at first, but it didn't take long for the phone to freeze again. i took out the battery again and turned the phone back on. this time (to my surprise) it didn't get stuck on bootup, but instead it (automatically) performed a hard reset. the phone now does a hardreset everytime i turn it back on, which makes it pretty much unusable...
since i'm getting REALLY tired of adding my email accounts/favorites/application shortcuts (by now i'm just installing them on the sd card, so i don't have to reinstall them)/facebook associations for my contacts/etc and i thought i'd better ask for help.
does anyone know what causes this issue and/or how i can solve this problem? help would be appreciated!
and since i'm here, what should i use to backup my phone (once it's running perfectly)? i already tried pim backup (sadly it doesn't create a backup of everything) and spb backup (freezes on registry recovery). would it be possible to create a rom that contains ALL of my information (settings/contacts/favorites/applications/registry tweaks/...)?
tl;dr:
my hd2 automatically performs a hardreset on bootup, how do i fix it?
please ignore any grammar errors, i'm tired and not a native english speaker
I have the same problem exactly regarding self-hard-reset. I still did not find any reasonable cause for this problem which is starting really to push on my nerves
This sounds to me like a corrupt file system, which can happen after ROM flashes. I would try this:
http://forum.xda-developers.com/showthread.php?t=644781
@Moandal: thanks for the answer. i just flashed the shock star rom again and the phone boots up normally again. but i really doubt that it will stay like this, unless i know what caused the problem. next time it happens, i'll try the program from your link.
but if i'm not mistaken, that program also hardresets the phone (correct me, if i'm wrong), so i could just flash a rom instead and that's what i'm trying to prevent (as i said, i don't want to have to enter my personal stuff again and again and again...).
what exactly could cause a corrupt file system? could it be a problem with the rom(s) or am i just doing something completely wrong?
A "simple" custom ROM flash only overwrites the ROM's contents without prior erasing, which on the HD2 has been found to sometimes cause trouble like the continuous hard resets you've suffered.
The solution is a full erase of the ROM before flashing the new ROM, which this mtty command does. So, you obviously can't do it without hard resetting/reflashing.
@kilrah: ok, that made things much clearer. i'm going to use the program posted above and flash the rom again, i hope that will fix future issues.
thanks for the fast help, guys
I had the same issues, at first I thought it was the artiums rom but having done MTTY walkthrough I'm 1 week into the Miri rom without much issues (apart from the odd program crash)
since it started pretty much straight away on the first rom, id be a little concerned that it might be an issue with the phone.
if it continues after you mtty/task 29 then id flash back to stock, including spl, and monitor that for a few days.
Code:
@samsamuel: since my last post the phone crashed only once (i was using opera 9.7 when it became unresponsive again), but this time it didn't perform a hard reset!
the main issue seems to be solved and that's good enough, for the time being.
if the problem occurs again, i'll follow your advice.
opera 9.7 - have you moved the cache to the memory card? I've had a lot of freezes the last few days with opera 9 7, turns out it was cos the cache was on the sd card (default 2 gig that came with it).
moved the cache to the phone yesterday, not a crash in 30 hours.
no, but i was actually going to. won't do it now, obviously
please help cause it went crash and hardreset by itself over again..... how can I fix this??
Hello,
I have an XV6700 that for almost 5 months now was running WM 6.5 flawlessly. I worked for a company that forces a passcode on the device. Now I never had an issue with the passcode until yesterday. Even though I kept entering it it assumed that I wasnt and after 5 attempts it hard wiped the phone. Which that doesn't bother me. But I have noticed since the wipe I cannot enable the phone radio any more and when it boots where it says R= theres nothing there. So basically I have a big ugly PDA right now. I have tried to flash to a different WM6.5 rom and the same thing happens. I tried to flash to the 1.43 radio but with the RUU that came with it, it did not want to flash and when I tried the RUU from the 6.5 rom I had it just errored out when I tried to update. Any help making my phone a phone again would be greatly appreciated!
Trying to get some help regarding my HTC HD2 Leo for Tmobile. For some reason any windows rom i flash, it will always crash. It will either crash on its own during boot up,after boot up, while im doing something on it, or while i have it locked in my pocket. My phone worked fine before i tried to flash a new windows rom and install a new Android. I went over the steps i did before my phone started being jacked up, i cant seem to figure out what i did wrong.
What i did before the problem:
-Clear storage under windows
- Task 29, held the volume button down once it hit 100%, this put it into boot loader again.
- I flashed the windows rom that was used by dark-stone on his site. ( which i cant post since im new or something) <<< i was trying to use same windows build as him and update my android that he put out on Oct 17th.
- Once my windows rom flashed and it booted up is when it started screwing up, freezing, shutting off by its self after boot, not booting up once i would restart it and also if i left the phone on the tmobile screen it would vibrate like 5-6 times then stop
What i have tried since my issues:
- I tried to flash my old windows roms, with many others that i had before that worked fine. All of these i tried gave me same problems
- i tried to update to the new T-Mobile update that posted on October 20th, and i also tried old version of tmobiles stock roms. Same issues again
- I tried re doing task29, tried new radios, resets of all sorts
I do have HSPL on my phone, always have since i first started flashing roms.
At this point i have a windows rom that can last me couple hours without crashing, so i can text and call. However its really annoying since the phone seems to be fine i doubt i bricked it since it lets me flash new roms and radios. Should i just take off HSPL and reset everything and get this HD2 exchanged, or does anyone by any chance have a way of helping my figure this out, or have any suggestions i could try.
Its keeping me from using windows and even better android
Thank you
So I tried to install Mskip AL v6 and AmericanDroid for a dual boot system.
The installation seemed to go fine (my radio was fine, and was going from the stock tmob ROM), I launched the HATRED and CLRAD within WM, I selected the options I wanted for the loader, it performed the restart and the screen went to black with the green HTC logo.
It never went any further than that.
I left it for an hour, still no change. I pulled the battery, and restarted the phone.
I got bunch of errors about tray.app not being able to start, and then some about trusted certificates.
SO I try to install again, and can't install anything, because I get the trusted cerificates/or one of the components missing etc.
Can anyone help?!?!
I've tried the security disable cabs on here, but they can't be installed due to the above problem.
Does the phone need to be unlocked first? Do I need to install something else first like HSPL?
And before anyone suggests it, no I don't want to go full NAND yet as I want to be able to check out Android on the hd2 before making the full jump.
Thanks!
Mskip loader has nothing to do with your problem, it just simplifies running clrcad and haret from android folder (which you can do by yourself from file manager),
the black screen with htc logo means the AmericanDroid loading started, then something stops (don't know what) - I'd suggest checking this thread for possible clues,