Hi,
I've recently rooted my phone and moved from WM to Myn's Donut NAND build. I like it a like except for a couple things. The most annoying is that my phone reboots every time it enters sleep mode, either from timing out or from me sending it into sleep manually.
I've reflashed the ROM a number of times with different builds, and even some of the other ROMs. Same problem.
I tried flashing back to one of the custom WM builds and that was even worse, it rebooted soon after coming up to the WM desktop. I never had problems prior to unlocking and doing the initial ROM flash.
It seems odd that I would have picked up a hardware problem right as I did the unlock and first ROM flash. Does anyone have any ideas?
Thanks
what unlocker did you use?
I have the 2.31 CoKE HardSPL unlocker that is referenced in the how-to guides such as the paragraph below. Think something is wrong with the install?
First and foremost, make sure you have unlocked your phone with the "2.31 CoKe" HardSPL. If you have ever flashed a custom Windows ROM from this site or ppcgeeks.com, to your device, then you most likely have already done this. If not, perform the steps HERE first, before continuing.
Click to expand...
Click to collapse
tsrich said:
I have the 2.31 CoKE HardSPL unlocker that is referenced in the how-to guides such as the paragraph below. Think something is wrong with the install?
Click to expand...
Click to collapse
I know that there are vogues that are different than others. That may be the case with yours. Some don't work right with android, some do. I'm not sure if it's something with the unlockr or slightly different hardware. For example, my wifes vogue is a funny one;
I can't flash a new nbh from the SDcard. I have to use the htc flash app, also for a long time she couldn't update her build because the kernel was incompatible. However now, the most recent kernels are fine.
Since unlocking some of the 6.5 builds won't work, they would randomly hard reset. but the 6.1 builds were perfectly fine..
mssmison said:
I know that there are vogues that are different than others. That may be the case with yours. Some don't work right with android, some do. I'm not sure if it's something with the unlockr or slightly different hardware. For example, my wifes vogue is a funny one;
I can't flash a new nbh from the SDcard. I have to use the htc flash app, also for a long time she couldn't update her build because the kernel was incompatible. However now, the most recent kernels are fine.
Since unlocking some of the 6.5 builds won't work, they would randomly hard reset. but the 6.1 builds were perfectly fine..
Click to expand...
Click to collapse
I had that problem where it would reboot on sleep, even in windows mobile, i figured out that it was the unlocker, so i relocked it, then unlocked it again with .31 and that fixed it.
mrono said:
I had that problem where it would reboot on sleep, even in windows mobile, i figured out that it was the unlocker, so i relocked it, then unlocked it again with .31 and that fixed it.
Click to expand...
Click to collapse
I've already unlocked my Sprint Vogue.
Can you please provide URL for "relocking"?
Will need it in the event that it needs servicing.
Thank you...
JM-PDA said:
I've already unlocked my Sprint Vogue.
Can you please provide URL for "relocking"?
Will need it in the event that it needs servicing.
Thank you...
Click to expand...
Click to collapse
just use the unlocker v.40 then flash stock rom, then unlock again with the .31
as for the url, just google vogue unlocker .40
How did you install the .40 unlocker? It uses activesync to connect to the Vogue. Did you have a WM ROM installed first?
tsrich said:
How did you install the .40 unlocker? It uses activesync to connect to the Vogue. Did you have a WM ROM installed first?
Click to expand...
Click to collapse
flash it via sdcard or through bootloader
cp0020 said:
flash it via sdcard or through bootloader
Click to expand...
Click to collapse
Maybe I'm doing it wrong then.
I opened up the vogue_unlocker.exe and extracted all the files to a dir. I changed into that dir and copied the VOGUIMG.NBH file to RUU_signed.nbh. I've had to do that for other ROMs, so I did it just to be safe. I then put the phone in bootloader mode, and connected it via USB. Then I ran the ROMUpdateUtility.exe from that dir.
It wanted to update from image ver ' <blanks>' to image ver ' 1.00.000.0'
It runs through the install, but doesn't seem to update the ROM. The bootloader still shows SPL-0.41.CoKE
I ended up flashing to a custom WM ROM, which let me establish an Activesync connection, so then I could run the full .40 install from windows, which worked.
Related
Has anyone found a way to upgrade to any WM6 ROMs on Windows Vista? I'm sorta at my wits end here!
In the Wizard Upgrading forum there is a thread "Upgrading your phone on Windows Vista". The driver instructions (which are really well written) work perfectly, but the RUU version fails with an "out of date" error.
There have been a number of other RUU versions suggested, but they all crash on Vista.
Shelltool works on Vista only about 25% of the time. Usually it just starts the flash process and hangs indefinitely. I was able to successfully flash XM6r4, but since then nothing else I've tried has worked. I did go back to the latest AT&T ROM afterwards, but haven't been able to get back to WM6 since. One of the things I tried was extracting the RUU from Cingular's update, but that one didn't work either, which confuses me even more!
All of the RUU Wrapper versions I've used to flash my Hermes work great on Vista, yet none of the RUU versions seem to be able to do so on my G4 Wizard (Cingular 8125).
Please, if anyone has any suggestions, I'd really appreciate them! I've searched and searched through the forums for different methods and versions, but have come up empty handed.
FWIW, I don't have access to an XP machine, and dual booting is not an option for me.
Thanks!
Dual Boot!
I just ended up dual booting XP, I noticed you said it was not an option, but did you know you can do it without reformatting through computer management in Vista?
Vista RUU
dktech said:
I just ended up dual booting XP, I noticed you said it was not an option, but did you know you can do it without reformatting through computer management in Vista?
Click to expand...
Click to collapse
Yep! Unfortunately that's not an option either. It's a matter of resources. I'm stuck with Vista, on which, I should point out, I can upgrade my Hermes successfully 100% of the time!
The RUU versions used to flash .nbh format ROMs to my Hermes all work, yet the older versions which take the .nbf format ROMs used by the Wizard don't!
There's got to be some solution. Using Shelltool usually works, but that only flashes the OS, not the ExtROM, splash screen, etc, so it's really only part of the solution.
Hmm i myself had some problems with flashing using Windows Vista. here are some observations i had
1) i first flashed using the origional tmobile rom (3.08 spl/ipl with 2.69 radio) i flashed it without doing anything special besides putting it in bootloader mode
2) next when i tried flashing it with a cooked rom it wouldnt work ( again i just tried to flash from bootloader mode without following any of the instructions givin in the Upgrading with Windows Vista thread)i found the RUUupdater version to be 2.0?? ( im sorry i forget the exact version numbers)
3) On checking the RUUupdater of the Tmobile that worked i found it to be 2.5???( again i forget teh exact version but suffice it to say it was newer)
4) i copyed the cooked rom nbk files to the Tmobile origional rom folder ( the one that worked on updating) but unfortunatly it wouldnt work
5) i then went to the thread and downloaded the drivers and installed them as the instructions said i should
6) i then downloaded the VistaRUU file they had there and then copyed the nbk files to that folder and VIOLA i flashed it and it worked like a charm ( again i flashed in bootloader mode)
This was just my experiance hopefully someone can figure out what i did right and why it worked for me and hopefully make it work for everyone else having problems
I thought there was a thread somewhere here about how to use Vista...if I remember, it may have even been stickied.
There was a stiki but it seems to have been unstikied and has since gone outta sight
Was this the thread??
It is still stickied if it is the thread.
I don't use Vista, so I haven't really read through it.
http://forum.xda-developers.com/showthread.php?t=338473
docnas said:
Hmm i myself had some problems with flashing using Windows Vista. here are some observations i had
1) i first flashed using the origional tmobile rom (3.08 spl/ipl with 2.69 radio) i flashed it without doing anything special besides putting it in bootloader mode
2) next when i tried flashing it with a cooked rom it wouldnt work ( again i just tried to flash from bootloader mode without following any of the instructions givin in the Upgrading with Windows Vista thread)i found the RUUupdater version to be 2.0?? ( im sorry i forget the exact version numbers)
3) On checking the RUUupdater of the Tmobile that worked i found it to be 2.5???( again i forget teh exact version but suffice it to say it was newer)
4) i copyed the cooked rom nbk files to the Tmobile origional rom folder ( the one that worked on updating) but unfortunatly it wouldnt work
5) i then went to the thread and downloaded the drivers and installed them as the instructions said i should
6) i then downloaded the VistaRUU file they had there and then copyed the nbk files to that folder and VIOLA i flashed it and it worked like a charm ( again i flashed in bootloader mode)
This was just my experiance hopefully someone can figure out what i did right and why it worked for me and hopefully make it work for everyone else having problems
Click to expand...
Click to collapse
What do you mean by putting the phone in bootloader mode first? In my experience, the phone has to be booted fully in order for the RUUs to work. Is there a way to get it to recognize the phone if it's already in bootloader mode?
If I put the phone in bootloader mode and then run RUU, the RUU just comes back and says it can't talk to the phone.
FWIW, I did the same as you, as far as flashing the original (Cingular) ROM and trying to use the RUU that came with that update. It seems that those RUUs won't work with any other ROMs.
Thanks for any help!
akashastrega said:
Was this the thread??
It is still stickied if it is the thread.
I don't use Vista, so I haven't really read through it.
http://forum.xda-developers.com/showthread.php?t=338473
Click to expand...
Click to collapse
Yep, that's the one! Been through it. As I mentioned above, the driver instructions in that thread are required when using Vista, but the RUU doesn't work.
Other than docnas here, everyone else has had the same problem as me. The Vista RUU comes back and complains that it's out of date.
I'd like to figure out what docnas did differently to get it to work. BTW, what version of Vista were you using? 32 or 64 bit? Mine is 64.
I'd also like to find out how it worked with the phone already in bootloader mode, since everyone says (and my experience has shown) that the phone needs to be booted and synced before the RUU will talk to the phone.
This may all be too late for me anyway. I'm giving my old Cingular 8125 to a friend, which is why I've been updating it. Unfortunately (or fortunately? ), once she has it, I'll only be working with my ATT 8525, which I can update and work with without any of the problems I've had with the Wizard.
I have been trying different roms to try to upgrade my phone to WM6.5 and so far the roms I've tried won't even load onto my phone. The download status bar will come up but it goes nowhere then it says update error. The phone will turn back on and work with the stock WM6.1
I'm just looking for a very clean OEM style WM6.5 ROM. Any recommendations?
ryche316 said:
I have been trying different roms to try to upgrade my phone to WM6.5 and so far the roms I've tried won't even load onto my phone. The download status bar will come up but it goes nowhere then it says update error. The phone will turn back on and work with the stock WM6.1
I'm just looking for a very clean OEM style WM6.5 ROM. Any recommendations?
Click to expand...
Click to collapse
Have you read the Dummies Guide? If not, you should do this. Just try some roms to see what fits better to your needs.
Assuming you hardspl or setup for USPL prior to flashing any ROM's. I have the 8285 and run the following ROM's: NRG LEO, PDAVIET LEO, and MIRI's LEO based ROM's. I personally keep going back to NRG as I have followed him from other devices and like his work. All the cooks are great. I also flash from SD card vs. using Activesync, find it faster and more reliable.
NRG is clean and mostly bug free ? yea from what you're saying maybe I did do something wrong. I'm not too advanced on this, I downloaded the energy rom and tried to update it. I've done nothing previous
ryche316 said:
NRG is clean and mostly bug free ? yea from what you're saying maybe I did do something wrong. I'm not too advanced on this, I downloaded the energy rom and tried to update it. I've done nothing previous
Click to expand...
Click to collapse
well then that's why you're having problems for sure. as others have mentioned follow the Dummies Flashing Guide. if you're using HardSPL, make sure the top (RED) section of your bootloader looks like this Pic of Bootloader with HardSPL. when it looks like this, you're ready to flash a ROM!!
OK I found the 156OliNex.zip file. I put the phone into bootloader mode, when I tried to launch the file it would not execute. It flashes up on the screen for a second and that's it. I made sure that the windows firewall is turned off
Best, the least error, safest flashing tool USPL
i highly recommend you use USPL : I still yet have to see someone who had a problem after using USPL. This is even endorsed by Dutty Throy (you can see that he even states that this is the SAFEST METHOD) - Moderator ROM Cooker par excellence!
look here
http://forum.xda-developers.com/showthread.php?t=505377
and here
http://forum.xda-developers.com/showthread.php?t=462347
format your sd card using fat32 (full format) (if you are a frequent flasher I suggest you get a small capacity sd card – 1Gb - and devote this only for flashing)
rename the RUU_signed.nbh to BLACIMG.nbh and pair this with ROMUpdateUtility -(application file). copy this two files in you formatted sd card.
then using Digital Outcast's USPL GUI: look here
http://forum.xda-developers.com/showthread.php?t=508361
if you're using Vista see this to update your sync driver
http://www.modaco.com/content/windo...u-on-vista-it-can-be-done-the-ultimate-guide/
flash the ROM.
please let me know once you've done this succesfully, i wish you the best of luck!
ryche316 said:
I have been trying different roms to try to upgrade my phone to WM6.5 and so far the roms I've tried won't even load onto my phone. The download status bar will come up but it goes nowhere then it says update error. The phone will turn back on and work with the stock WM6.1
I'm just looking for a very clean OEM style WM6.5 ROM. Any recommendations?
Click to expand...
Click to collapse
You need to start posting in the Dummies Flashing Guide as posted above as this thread will be closed as soon as a mod comes across it. You'll find all your answers and help there
ryche316 said:
OK I found the 156OliNex.zip file. I put the phone into bootloader mode, when I tried to launch the file it would not execute. It flashes up on the screen for a second and that's it. I made sure that the windows firewall is turned off
Click to expand...
Click to collapse
do you have .Net installed on your PC? if not, you need to install first. if you have .Net installed, retrace your steps to make sure you've got everything setup properly, e.g., installing the driver supplied in the thread. also, if you have problems please post your questions in the Dummies thread...the moderators will close threads like this one because "all" the info you need to flash can be accessed from the Dummies thread.
yes I have NET installed on my computer. I tried using the files in the dummies guide and had issues
OK. so I finally got the NRG energy rom installed and it shows up distorted on the screen.
ryche316 said:
OK. so I finally got the NRG energy rom installed and it shows up distorted on the screen.
Click to expand...
Click to collapse
if you're using a WM 6.5 ROM then you do not have the right SPL installed.... look at Post #5 and make sure your bootloader looks like the one in my picture; if it doesn't then you haven't installed SPL 1.56 Olinex. again, please post your questions in the Dummies thread, you'll get appropriate help there... thanks!
I want to thank everyone for their input. I finally got a rom installed and working properly
I just wanted to thank everyone for their ideas and input. I finally got a rom installed and working on my phone
glad to know you were successful! we've all been there before and i know it can be frustrating. patience, diligence and patience (lol) will get you there!
Solution found, thread closed
Hello,
I know you guys got some excellent walkthroughs, roms, programs and threads where you've helped a lot of people out but I could really use some personal feedback. I had hoped to fix my phone using one of the excisting threads but unfortunalty I can't get it to work with those.
My problem is one I've seen more of in here, I used the SE updater and it froze at 53%, I did what the program said, reconnected and it froze again at 12%, and again, again, etc. So I disconnected thinking it might be a bad USB port. But then the updater didn't recognise my phone at all. So I used the mtty program suggested in some of the threads and I got past the red/green/blue screen but now it's stuck at the Sony Ericson logo, as if WM6.1 is gone.
This is what the red/green/blue screen currently states:
KOV110
SPL-0.78.0000
MicroP1-787
MicroP2-707
From what I gather this means I can't flash roms, right? I tried making it a hard-spl but when I use the tool it says it can't connect.
So is there anyway to get a rom on it and bring it back to life?
Thanks inadvance!
Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards
meska said:
Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards
Click to expand...
Click to collapse
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.
Ronnet said:
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.
Click to expand...
Click to collapse
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
original roms will still work with original spl... but nevermind =P
laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
My phone can still power on in the sense that it shows the Sony Ericson logo or that I can access the three collor screen. But it won't launch WM6.1. I also have a problem with updating to hard DSL. It does recognise my phone because without it connected the program finds nothing and with the phone connected it wants to start updating. It says ''updating from image version: (emply) to image version: 1.00.X1 Ipress next and it opens a progress bar on both my X1 and the PC. But it never goes beyond 0% and then gives me an connection error. I think it has something to do with not being able to get passed the Sony Ericson logo. I mean the hard-DSL program does recognise my mobile but activeSync is never active because my PC doesn't recognise a WinMobile phone (since it wont go past the Sony Ericson screen)
meska said:
original roms will still work with original spl... but nevermind =P
Click to expand...
Click to collapse
Really? That might fix my device then. Could you suggest a rom from the long list? Perhaps one that works on all versions? Because I'm dutch but my mobile has always been in english so I'm not sure what rom version I had. Except that it was identified as an R2 Rom by the Sony updater before it killed my X1...
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
I'm now downloading the initial dutch R1 firmwire, could that one work?
Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
Alright so I got an R1 original rom (I now realize that the R3's were originals aswell) and it worked! I'm not sure if it was the different rom or the formatting with FAT32 that did but it works again. So I'd like to thank everyone who was kind enough to reply.
The device is incredibly slow now but now I can use the hard-DSL installer, right? DOes anyone have a suggestion for a good rom to use?
laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
DON'T hard-spl if you're going to flash a stock ROM. And especially if you're going to use SEUS.
Try flashing the R3A first. The R1s are way slow, as you've seen.
Hi,
My experience today is the motive of me writing this guide to help most of you out of this problem and eliminate the Fear that you will have of you blackstone might gone bad (hardware fault).
ok,
here is what happend to me today.
I had XannyTech Rom flashed on my phone and i really felt i found something interesting about another ROM so i decided to flash that one.
after a smooth flashing, the phone booted and i started syncing using myphone.
left the phone on the desk for a while, came back and found that the device is not responding to the power button, poked that red button and the phone get's stuck at the "smart mobility" screen!!
Hard resetted the phone and started over, again the phone hanged.
i thought that it's maybe a bad flash! so i downloaded the file again and flashed again.
still the same!!!!
decided to go to the old ROM ,
still after a while i get the same result!
notice that i hard resetted after each and every flash!
so what did i do?
[Guide]
Hard Reset the phone, check if it's a software you installed or if it happens even on a pure ROM.
If the problem still exist, Confirm it's not a bad flash! flash again the same ROM.
If you still have the same symtoms, go to HTC website and download the latest OFFICIAL ROM from there.
Run the RUU from your pc (Don't worry about HSPL, it's protected so you will NOT have to HSPL your device again, Thanks olinex)
Test your phone with the new official ROM (in my case -blackstone- it's a 6.1 rom ). Mostly everything will be back to normal.
flash the rom of your choice.
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Hope you find this usefull.
Regards,
Adel
I will remember this if it happens to me!
Thank you!
For me, with the HSPL, when I went back to original rom, I had a big problem with color. I flashed to old SPL too, and so, color where good after
Wiki
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
edit : oops, the link is accessable from the wiki
re the topic:
Looks like Viagra cant fix this issue then
anaadoul said:
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
Click to expand...
Click to collapse
Hi
You should fix your link and put wiki instead if forum
Jal84 said:
Hi
You should fix your link and put wiki instead if forum
Click to expand...
Click to collapse
it is good to see that you have followed the link
anaadoul said:
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Click to expand...
Click to collapse
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol
Ehol said:
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol
Click to expand...
Click to collapse
Good explaination!
also while i was extracting a shiped ROM i got an unknown nb file which might be responsible for this?
what you have said means that as long as you are flashing a larger sized ROM you should have no problem, but once the new ROM have a smaller size then you will face some issues?!
oh, one more thing.
after formating the phone with the stock ROM, i noticed that it runs much faster (around 15% performance increase) can anyone try flashing shipped ROM then the same one he was using and confirm this?
I've searched everywhere and I can't find an answer.
I purchased an HTC Touch for Sprint today, booted it up/unlocked it, and flashed Android. I realized that I never setup Power Vision in WinMo prior to unlocking/installing Android. I've tried to reinstall the Windows Mobile 6.1 stock rom that came with the phone so that I can get to the EPST menu and update my PV info, but the rom freezes at 29% when I try to flash it.
I'm not vary experienced, so please pardon me if there is a stupidly easy answer. I've flashed a 6.5 rom, but I couldn't figure out how to get to the EPST menu on it to auto-configure my data settings.
If anyone can help me out, it would be greatly appreciated. Thanks!
i also had a lock-up when flashing the official sprint ROM once, and i created a new windows account, re-downloaded the rom, and it worked. no idea why
Hey, what do you mean by a new windows account? Thanks!
new user/login
GeJohnO said:
I've searched everywhere and I can't find an answer.
I purchased an HTC Touch for Sprint today, booted it up/unlocked it, and flashed Android. I realized that I never setup Power Vision in WinMo prior to unlocking/installing Android. I've tried to reinstall the Windows Mobile 6.1 stock rom that came with the phone so that I can get to the EPST menu and update my PV info, but the rom freezes at 29% when I try to flash it.
I'm not vary experienced, so please pardon me if there is a stupidly easy answer. I've flashed a 6.5 rom, but I couldn't figure out how to get to the EPST menu on it to auto-configure my data settings.
If anyone can help me out, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If your using the unlocker .40 then that's why, use unlocker .34, only use unlocker .40 if your relocking your phone and flashing back to stock to send in for warranty repair, some phones don't like to flash from usb when relocking.
you might be able to get it to flash from the memory card if you put the nbh from the exe onto the mem card, etc.. or just try to flash a 6.5 rom.
if it just so happens that you can't flash anything and you can't go anywhere past the bootloader, take it into the store, tell them you turned it on and it wouldn't boot and they will take it into the back and reflash it, then start again from the beginning, but remember to provision your phone first.
mrono said:
If your using the unlocker .40 then that's why, use unlocker .34, only use unlocker .40 if your relocking your phone and flashing back to stock to send in for warranty repair, some phones don't like to flash from usb when relocking.
you might be able to get it to flash from the memory card if you put the nbh from the exe onto the mem card, etc.. or just try to flash a 6.5 rom.
if it just so happens that you can't flash anything and you can't go anywhere past the bootloader, take it into the store, tell them you turned it on and it wouldn't boot and they will take it into the back and reflash it, then start again from the beginning, but remember to provision your phone first.
Click to expand...
Click to collapse
How can I flash 2.31 when I cant bring up activesync? (I dont have 6.1 installed)
mrono said:
if it just so happens that you can't flash anything and you can't go anywhere past the bootloader, take it into the store, tell them you turned it on and it wouldn't boot and they will take it into the back and reflash it, then start again from the beginning, but remember to provision your phone first.
Click to expand...
Click to collapse
Then take it to the store and have them reflash it for you
put your phone in bootloader mode (tricolored screen, hold camera and power, then press and release soft reset). connect to your computer. download andn run the official sprint gps rom (not the stock rom; can use with unlocked phone, won't mess with the unlocker, here, under shipped gps rom newer version in post 1), and allow it to flash your phone. get 3g working however you can - even call sprint if you have to. then flash back to android.
tatnai said:
put your phone in bootloader mode (tricolored screen, hold camera and power, then press and release soft reset). connect to your computer. download andn run the official sprint gps rom (not the stock rom; can use with unlocked phone, won't mess with the unlocker, here, under shipped gps rom newer version in post 1), and allow it to flash your phone. get 3g working however you can - even call sprint if you have to. then flash back to android.
Click to expand...
Click to collapse
It's possible that he won't be able to flash at all, when mine screwed up and wouldn't let me flash none of the roms worked, even offical ones
Fixed it. Flashed a custom 6.5 rom, ran activesync and flashed a .31 rom, installed stock rom, provisioned. Thanks for the help! I would have never figured out I had the wrong unlocker, haha.
GeJohnO said:
Fixed it. Flashed a custom 6.5 rom, ran activesync and flashed a .31 rom, installed stock rom, provisioned. Thanks for the help! I would have never figured out I had the wrong unlocker, haha.
Click to expand...
Click to collapse
Cool, glad to see you got it all figured out!