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!
Related
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
Hey guys, I am kind of a noob but have successfully been hacking with my Touch for a while now...or so I thought. I flashed to the 3.37.78 radio a while back and have been keeping up with NSFAN's ROM's for over a year now with no problems....until a few months ago. My phone locked up and I had to soft-reset but to no avail. It got stuck on the startup screen and would not do anything so I did a hard reset and all was good. Then it happened again weeks later. Now it has been happening a lot more recently. I will be texting or on the internet with it and then all of a sudden it will lock up, I do a soft reset and it will hang up either on the startup screen or seem to boot up but then contacts will be missing and there will be no signal. Sometimes the today screen will show but I cannot do anything on it.....all of this requires a hard reset to fix. This happened after I flashed NSFAN's latest ROM so I flashed back to some of his older ROM's that I had no problem with in the past and still the same problem. It has been happening every week or 2 now to the point that I can't even bother setting up the phone the way I want because I know it will happen again. Can any of you guys tell me what the problem is? I really need to get this resolved because I am losing information everytime. Please help!!!
Im a GSM Phone user... and as a general rule, if things start to go wrong.... Flash the OEM rom. That would be the stock ROM. And then flash back to your "custom" rom... Ive had to do that with my phone(s) as well.... It basicly puts things back to 'ground zero'. BUT. Use the phone with the stock rom for a day and see if you still have the same problems... it may be a problem in the phone. In which case you may need to replace and/or send the phone back for replacement to your carrier.
Hope this helps....
Thanks for the reply.....What I ended up doing is reflashing my radio to the 3.42.50 version and then reflashing my ROM to NSFFAN's again. So far so good. I am really hard on my phones and the fact that I drop my phone on a regular basis can't help either....I just need it to last me a few more weeks until I get a new one. Thanks again...
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
Hi, I was running Android on my HD2 for almost 9 months, currently HyperDroid5.5.2. Till now, without any problem whatsoever. Suddenly, when I checked my phone this morning it didn't respond. So I waited a while, then tried pulling the battery. Booting got stuck at Android logo. No problem I thought, I periodically do nandroid backups just in case. Tried to restore it - stuck at restoring data. Then I tried advanced restore, only boot and system... either of them didn't work. After this, I decided to reinstall from scratch - task29, radio, magldr, cwm. The ROM installation got stuck again. So I tried flashing stock SPL and stock ROM from HTC site. SPL okay, ROM not. Got error 262 from the RUU. Tried searching the forum but there is so much stuff that it's impossible to get through. So please don't bash me from beeing a noob. Can anyone please help?
Edit: After the phone finally accepted WM back, I want to put Android back on it... ROM installation gets stuck at restoring Batterystats.bin... any ideas?
Hello everyone.
Two days ago a friend of me asked if I could install Android on his "new" HTC HD2.
As I installed Android on serval HD2's I said yes, no problem at all.
But once he came to my house and I started working on it only trouble is what came to me.
The HD2 was stock so Windows Mobile was running on it.
I install HSPL4 , no problem.
Flashed the radio, no problem.
Installed cLK, no problem.
Installed recovery : PROBLEM.
The trouble started from there.
The phone did not reboot, even tough it said "rebooting phone"
So what I did is unplug the phone, Task29'd it and did everything over again.
Than, I got an error on the radio installation.
The phone rebooted and when I got to the tri colour screen I was shocked.
It said some kind of "error rom update failed"
After this nothing worked, installing a Radio failed, installing the stock firmware downloaded from HTC failed etc.
Only flashing HSPL4 and Task29 worked, so I tought I was screwed.
I readed many many threads and somewere I got to the "Chill in fridge trick"
So I putted the phone in the freezer for 10minutes, copied the nbh file from the stock Windows Mobile rom to the SD Card and TADAAA! It worked!
So, here I was, back on Windows Mobile, trying again! to install Android.
As long as I kept the phone cold everything worked, also installing cLK and Clockworkmod.
But now here the thing is: Installing and running Cyanogemod is no problem at all, Cyanogenmod boots and run fine.
But when I want to install a sense rom, it works as long as the phone is cold.
When the phone gets to normal temps it stops responding and tries to reboot.
It stays stuck on the boot, and I have to put it in the freezer again to make it work.
This problem only occures with a sense rom!!
Windows Mobile rom doe snot have any problems, also Cyanogenmod does not have any problems.
The phone does still have warranty, but as the phone does not have problem with Windows Mobile I don't think I can send it to HTC for repair, as I think this is a hardware problem.
Does any of you know what I could do in this kind of situation?
Thanks in advance!!!
Oops, Admins, this one is duplicate, I refreshed the page and accidently clicked post thead twice, can you delete this one please? Thanks!
Did you flash magldr?
Sent from my HTC HD2 using Tapatalk
AFAIK HSPL4 is not for Android but only for Windows Mobile.