[Q] What ROM? - Omnia 7 General

I've been trying to get a Chevron unlock on 7004 for quite a while now, and so far null success Closing Skype, etc. didn't work, and I do have the registry value added. Flight Mode didn't work either, and I'm on older Zune software.
Now, I read that Chevron only works on certain ROMs with Omnia 7 but I'm not sure what I should flash exactly. So, what exactly should I flash to get that Chevron unlock going?
P.S: I'm on Windows XP, maybe that's part of the problem?

KidKlimax said:
I've been trying to get a Chevron unlock on 7004 for quite a while now, and so far null success Closing Skype, etc. didn't work, and I do have the registry value added. Flight Mode didn't work either, and I'm on older Zune software.
Now, I read that Chevron only works on certain ROMs with Omnia 7 but I'm not sure what I should flash exactly. So, what exactly should I flash to get that Chevron unlock going?
P.S: I'm on Windows XP, maybe that's part of the problem?
Click to expand...
Click to collapse
i flash this unbranded omnia 7 ROM (tnx Casey_boy) unlock it with chevron method. have you load the ChevronWP7.cer over email? you have install the wp7 developers tools?...

Yeah, that ROM seems to have worked, thanks!
Sent from my OMNIA7 using Board Express

Related

[Q] Is there a way to update WP7 on HD2

I cant seem to find a ROM that updates.
Every ROM proceeds till the backup needs to be created and then it stays stuck at 0% and then the update process gives me an error.
I thought it must be because of cutom ROMs with Chevron hack built in but it happens with the original Cotulla release too.
Any ideas?
the 7008 update is useless at the moment.. wait for nodo builds..
but what causes the error would be good to know.
tis not ment for your phone, and since EVERY rom out there for WP7 on the HD2 is actually the same ROM they all share the same issues.
Wait my friend, likely you'll need to wait for nodo that will also not work in our device so a further wait until someone gets that bodged in to a ROM will be needed
yeah you are right actually.
All custom ROMs must spring from the Cotulla release and since that one gives an error every one of the other must as well
inasar said:
yeah you are right actually.
All custom ROMs must spring from the Cotulla release and since that one gives an error every one of the other must as well
Click to expand...
Click to collapse
correct my friend!
And, zune gives a registry error, obiously because the registry was tweaked to make it think it's an HD7. As much as they are alike and have the same specs, the hardware is completely different, so, you could do as much as brick your phone if you force an update. Although I'm not sure it would be bricked with the magldr in place........
peter768 said:
And, zune gives a registry error, obiously because the registry was tweaked to make it think it's an HD7. As much as they are alike and have the same specs, the hardware is completely different, so, you could do as much as brick your phone if you force an update. Although I'm not sure it would be bricked with the magldr in place........
Click to expand...
Click to collapse
amen to that
Actually there is no more a registry error. Currently the 7008 update gives a timeout error. On anther note: During the update my PC installed drivers for a new device called LEO I guess this is where the problem really is
TheOnly1 said:
Actually there is no more a registry error. Currently the 7008 update gives a timeout error. On anther note: During the update my PC installed drivers for a new device called LEO I guess this is where the problem really is
Click to expand...
Click to collapse
i noticed that as well so obviously our device still contains something that links it to a leo...i wonder what happens if you stop that device from installing?
I been searching through the registery on my PC and its full of Leo traces from before....cant remove them as they are all protected, will need to do a safe mode and get rid of it that way
dazza9075 said:
i noticed that as well so obviously our device still contains something that links it to a leo...i wonder what happens if you stop that device from installing?
I been searching through the registery on my PC and its full of Leo traces from before....cant remove them as they are all protected, will need to do a safe mode and get rid of it that way
Click to expand...
Click to collapse
Ok nothing like this happens in my case. However, i havent checked the registry recently so i dont know if there are orphan (or not) LEO traces there.
My phone is recognzed as an HD7, which is what the ROM chef intented i guess.
We al have to:
Work with the update files and cook them in a rom.
Wait a lot until someone release a rom with the update.
abq1230 said:
We al have to:
Work with the update files and cook them in a rom.
Wait a lot until someone release a rom with the update.
Click to expand...
Click to collapse
oh indeed, this is a much more sensable solution but it is curious that when trying to update Zune detects the phone as a HD2 and installes a LEO device driver for it, even though the phone is still listed and displayed as connected as an windows phone 7 deviec
very curious indeed
did someone thought in the bootloader ?!?!if it's behind the Leo issue after the restart...
jianototi said:
did someone thought in the bootloader ?!?!if it's behind the Leo issue after the restart...
Click to expand...
Click to collapse
I am guessing that the bootloader is not the one at fault here. I think it could be the USB driver. We are using legacy USB drivers in the ROM that have been ported from windows mobile 6.5
That could be the reason the computer installs the device as a LEO

Reset my phone

heelo i put win7 on my hd2 it kept locking when connecting with zune now chevron wont work tryed everything if i reset phone will i still have my live services or will i need to put activation code back in and certificates for live services thx
stesteste said:
heelo i put win7 on my hd2 it kept locking when connecting with zune now chevron wont work tryed everything if i reset phone will i still have my live services or will i need to put activation code back in and certificates for live services thx
Click to expand...
Click to collapse
you have to set everything back up from scratch....the reset wipes out all your settings back to factory defaults.
i suggest following the LEO link (select the correct one based on if you are in the US) and use task29 to do a clean wipe of your phone. then proceed to re-flashing wp7 per wp7 flashing procedures.
try a rom that already has the chevron hack built in so the only thing you would have to do is put the activation key
hakuchi18v said:
try a rom that already has the chevron hack built in so the only thing you would have to do is put the activation key
Click to expand...
Click to collapse
try frantic's 7008 ROM
hakuchi18v said:
try a rom that already has the chevron hack built in so the only thing you would have to do is put the activation key
Click to expand...
Click to collapse
thanks do you reccomend a windows 7 rom

HTC Surround OEM cabs

Hey I just wanted to share the (2) OEM updates for the Surround.
1st was included with the 7392 update:
http://download.windowsupdate.com/m..._e9a01966f3fe897b61f9f0712b2746adb067bfd1.cab
Brings the following up to:
Firmware revision # 2250.21.15204.502
Radio software version 5.66.09.09_22.46.50.21H
Bootloader version 1.5.2.2250.4
2nd was included with the 7720 update:
http://download.windowsupdate.com/m..._9dc85b25de5f2e11d7649ce4fbc0a30a6918fab9.cab
Brings the following up to:
Firmware revision # 2250.21.40300.502
Radio software version 5.69.09.05a_22.50.50.21H
Bootloader version 4.3.2.2250.0
I traced these earlier using wireshark, enjoy!
donjulio0088 said:
Hey I just wanted to share the (2) OEM updates for the Surround.
1st was included with the 7392 update:
http://download.windowsupdate.com/m..._e9a01966f3fe897b61f9f0712b2746adb067bfd1.cab
Brings the following up to:
Firmware revision # 2250.21.15204.502
Radio software version 5.66.09.09_22.46.50.21H
Bootloader version 1.5.2.2250.4
2nd was included with the 7720 update:
http://download.windowsupdate.com/m..._9dc85b25de5f2e11d7649ce4fbc0a30a6918fab9.cab
Brings the following up to:
Firmware revision # 2250.21.40300.502
Radio software version 5.69.09.05a_22.50.50.21H
Bootloader version 4.3.2.2250.0
I traced these earlier using wireshark, enjoy!
Click to expand...
Click to collapse
Hmm, my Surround is running different Firmware and Bootloader versions:
Firmware: 2250.21.40500.502
Bootloader: 4.5.2250.0(129685)
Running Mango OS: 7.10.7720.68 - No forced updates.
I am not sure why yours are different, I flashed a pre-NODO AT&T ROM to the device and I let Zune take it from there all the way to 7720. This is what was downloaded and installed to my Surround. I already downloaded those cabs manually and applied them to my wife's phone with no issues via cab sender. She missed the OEM updates alnog the way somehow.
Dunno. Purchased on launch day, and stock all the way. I did have the Beta 1&2 versions of Mango on my device (Developer Unlocked), but did a hard reset just before updating to the official Mango. No updates since then, although I did get three updates that day; pre-Mango cleanup, Mango and HTC firmware.
jimski said:
Dunno. Purchased on launch day, and stock all the way. I did have the Beta 1&2 versions of Mango on my device (Developer Unlocked), but did a hard reset just before updating to the official Mango. No updates since then, although I did get three updates that day; pre-Mango cleanup, Mango and HTC firmware.
Click to expand...
Click to collapse
jimski, I think you just explained why yours are different. You applied the beta versions of Mango to your phone which altered the "stock" ROM you had on your device. I had the same versions as your phone before I reflashed to stock and allowed Zune to do all the work this time. Even though you had a pre mango cleanup your ROM wasn't noticed as stock anymore. Anyone that has never applied the beta mango on their AT&T device and is up to todays specs please post what versions you have compared to those listed above. Thanks!
donjulio0088 said:
jimski, I think you just explained why yours are different. You applied the beta versions of Mango to your phone which altered the "stock" ROM you had on your device. I had the same versions as your phone before I reflashed to stock and allowed Zune to do all the work this time. Even though you had a pre mango cleanup your ROM wasn't noticed as stock anymore. Anyone that has never applied the beta mango on their AT&T device and is up to todays specs please post what versions you have compared to those listed above. Thanks!
Click to expand...
Click to collapse
Actually, his firmware and bootloader version are the same as mine, and I haven't tampered with my phone at all. Our firmware and bootloader versions are newer than yours. There's something wrong. By the way, do you by any chance use a Zune subscription?? The HTC Surround has been locking up while playing songs on battery power ever since the Mango Update.
israel.lopez217 said:
Actually, his firmware and bootloader version are the same as mine, and I haven't tampered with my phone at all. Our firmware and bootloader versions are newer than yours. There's something wrong. By the way, do you by any chance use a Zune subscription?? The HTC Surround has been locking up while playing songs on battery power ever since the Mango Update.
Click to expand...
Click to collapse
I dont subscribe to the Zune service. However I did state that I had the same versions as you before I recently reflashed the stock AT&T ROM and let Zune do all the updating. Now I wonder why the current updates dont match the older updates. P.S. My phone performs much better with these lower versions that I now have compared to the versions that I had before(which you currently have). No lockups, no hesitations, no restarts. Everything has been flawless since reflashing and reupdating.
I did experience lockups (alarm bug), restarts, and quirky volume changes when plugging anything into the 3.5m jack literally from the day I got my Surround (on launch day), and through the NoDo update. After NoDo, without any noticable bug improvements, I did my first hard reset (last March) and all the issues dissapeared. I wrote it off as something getting screwed up during manufacture, although the underlying ROM seemed to be fine. You might be experiencing the same thing with your recent stock ATT ROM flash. Did you try a hard reset prior to flashing?
BTW, for israel.lopez217, I do have Zune Pass, but don't stream music very often. Been playing streamed tracks for the past 20 minutes though (5 or 6 so far) and no lockups. On battery, and the screen is sleeping.
How to install the CABs
Please, can you tell me how to install the CABs, I tried copying the cabs on the "WP7 Update Cab Sender" folder and then launch the bat file, but the tools states: Error: No update files.
Thanks.
dach said:
Please, can you tell me how to install the CABs, I tried copying the cabs on the "WP7 Update Cab Sender" folder and then launch the bat file, but the tools states: Error: No update files.
Thanks.
Click to expand...
Click to collapse
Please read this thread, it explains everything.
http://forum.xda-developers.com/showthread.php?t=1306415
SOLVED Error: No updates files
dach said:
Please, can you tell me how to install the CABs, I tried copying the cabs on the "WP7 Update Cab Sender" folder and then launch the bat file, but the tools states: Error: No update files.
Thanks.
Click to expand...
Click to collapse
The problem was that I was right clicking the BAT file then Run as Admin, for it to work I had to open an elevated command prompt (run as admin) and then launch the BAT file from the cmd.
Hope this helps someone.
I'm not able to use the second cab to update the bootloader to version 4.3.2.2250.0 with the NT cab provided by Ansar for HTC Surround. It goes through the entire procedure and then gives an error msg at the end, saying that the update was unsuccessful.
mangojain said:
I'm not able to use the second cab to update the bootloader to version 4.3.2.2250.0 with the NT cab provided by Ansar for HTC Surround. It goes through the entire procedure and then gives an error msg at the end, saying that the update was unsuccessful.
Click to expand...
Click to collapse
I think you misunderstood what OEM meant. You need to check with Ansar about updating his ROM.
I am not allowed to post on the development forum yet, else i would ask Ansar there. Hope he reads these posts too. Updating the bootloader is hardly important, but i wish he would provide a solution for Internet Sharing not working on his NT rom.
donjulio0088 - the 2nd cab updated my stock rom yesterday. any idea where i can lay my hands on a cab for the latest firmware (2250.21.40500.502 at least) . . . Zune is not showing any updates available . . . am really desperate for ICS, my broadband connection often goes down and with my Windows 6.5 device i used to have a fallback option.
mangojain said:
donjulio0088 - the 2nd cab updated my stock rom yesterday. any idea where i can lay my hands on a cab for the latest firmware (2250.21.40500.502 at least) . . . Zune is not showing any updates available . . . am really desperate for ICS, my broadband connection often goes down and with my Windows 6.5 device i used to have a fallback option.
Click to expand...
Click to collapse
Unfortunately I didn't get that one to my phone. I haven't seen anyone else post any other cabs for the Surround either. If you manage to locate please post your findings.
It is here somewhere in the forum, as I downloaded it. I will try to find it and post it.
donjulio0088 said:
Unfortunately I didn't get that one to my phone. I haven't seen anyone else post any other cabs for the Surround either. If you manage to locate please post your findings.
Click to expand...
Click to collapse
Yeah, I'm on 2250.21.40200.661 and would like to update it, too.
Sent from my A100 using Tapatalk
i m on 7713.wm7_main(DFT) rom when i connect to zune it says update is available from htc but m not able to update since in DFT zune update doesnt work....so can someone plz help how to update my phone via zune? or else how do i revert to stock rom so tht i can update my phone via zune.... plz helpme.

[Q] Not suer where to start

I bought this phone three months ago knowing WP8 was coming out soon. :crying:
I see the XevRev for Spark_W stuff, radio collecctions, tons of custom rom stuff, and etc, but I'm at the point where I'm utterly confused at what it what.
I guess I'm asking where I should start?
Here is what I think might be relevant:
OS Ver: 7.10.8773.98
FW Ver: 2305.13.30202.605
HW Rev: 0003
Radio SW Ver: 1.43.00.06.14_23.17w.05.13U
Radio HW Ver: 3.2.3.D4
Bootloader Ver:3.2.230513.2
Changed DUN NAI from dun.vzw3g.com to vzw3g.com
Just got my dev unlock through dreamspark.
thals1992 said:
I bought this phone three months ago knowing WP8 was coming out soon. :crying:
I see the XevRev for Spark_W stuff, radio collecctions, tons of custom rom stuff, and etc, but I'm at the point where I'm utterly confused at what it what.
I guess I'm asking where I should start?
Here is what I think might be relevant:
OS Ver: 7.10.8773.98
FW Ver: 2305.13.30202.605
HW Rev: 0003
Radio SW Ver: 1.43.00.06.14_23.17w.05.13U
Radio HW Ver: 3.2.3.D4
Bootloader Ver:3.2.230513.2
Changed DUN NAI from dun.vzw3g.com to vzw3g.com
Just got my dev unlock through dreamspark.
Click to expand...
Click to collapse
Well, dev unlock is really unnecessary if you plan on installing an HSPL and flashing a custom rom. Then again, your OS version of 8773.98 suggest that you are running DFT or ansar's rom, but didn't install HSPL (only RSPL to flash the rom). Even with the official rom, your OS level should be 8779.8 after updating via Zune.
First, if you REALLY want to unlock the power of this phone, install HSPL using my HSPL guide for SparkW. It explains every step in detail so you can be ready to flash a custom rom.
Second, give my SparkW rom XevRev a shot for a great Tango experience. Just flash the rom, then update via Zune after setting up the phone to get the newest radio installed. It has FullUnlock and Root Tools, and is the only rom currently around that allows for the phone to be fully programmed using *228 (older roms have an older Xap Deployer package that didn't allow the programing tools to be installed).
You can ignore the radio thread and the "stock like" threads because the contents of those are now outdated with my rom being out.
Get 10+ post under your belt and you can reply to dev forum topics. I'm working on a 7.8 rom, but I won't be able to test it until my third Spark_W comes tomorrow and I transplant a digitizer into it. Maybe since I'm taking it apart I'll also upgrade the SD Card on that one too? (I don't want to flash my primary phone since it's too much of a pain to get reinstalled when I need it for an alarm clock.
Before you flash another rom though, I want to ask you a few things. Do you have Unlimited data via Verizon, and if not, what plan do you have? Also, is tethering working for you NOW before flashing my rom simply by doing the dun nai change? The dun nai change should only be necessary for Unlimited data users.
I'm using factory updates. All I know is that I have my phone updated as far as I can through Zune.
We just switched from AT&T to Verizon, due to the lack of any signal across the entire house. When we went into the store they had to have their manager bring the phone all the way from Kentucky. Anyways, they had just started to push the share everything plan, but the reps acted like they weren't comfortable with those plans yet. I have a 2gb a month, but I called verizon and they disabled the DUN for my phone (as I didn't want charged one of the wifi access fees) When I enabled the wifi after I called them I got a webpage showing I could re-enable it for the $30.
I tried to do the Interop_Unlock but that seemed to not work. But I might as well wait for your 7.8 then.
thals1992 said:
I'm using factory updates. All I know is that I have my phone updated as far as I can through Zune.
We just switched from AT&T to Verizon, due to the lack of any signal across the entire house. When we went into the store they had to have their manager bring the phone all the way from Kentucky. Anyways, they had just started to push the share everything plan, but the reps acted like they weren't comfortable with those plans yet. I have a 2gb a month, but I called verizon and they disabled the DUN for my phone (as I didn't want charged one of the wifi access fees) When I enabled the wifi after I called them I got a webpage showing I could re-enable it for the $30.
I tried to do the Interop_Unlock but that seemed to not work. But I might as well wait for your 7.8 then.
Click to expand...
Click to collapse
Yeah, Interop is a pain to do unless you are running Mango v1. You could factory downgrade to do it.. but its really a big pain.
I'm aiming to have 7.8 and international language roms out by Sunday, work is guna make it difficult. Are you able to use tethering with the dun nai changed though? I'm curious because other users with metered data plans were still having issues.
If you can't use tethering even with the dun nai changed, try deploying JerryJiang's Tethering unlocker for Verizon Trophy. If you still can't tether, I think I know a final adjustment that may need to be made, and you could be a helpful test subject since JerryJiang sent me his apps source code. After I get the details sorted, I can apply the fix directly into my rom without a need for an app (and create a rom package for others to cook into their roms).
TheXev said:
Yeah, Interop is a pain to do unless you are running Mango v1. You could factory downgrade to do it.. but its really a big pain.
I'm aiming to have 7.8 and international language roms out by Sunday, work is guna make it difficult. Are you able to use tethering with the dun nai changed though? I'm curious because other users with metered data plans were still having issues.
If you can't use tethering even with the dun nai changed, try deploying JerryJiang's Tethering unlocker for Verizon Trophy. If you still can't tether, I think I know a final adjustment that may need to be made, and you could be a helpful test subject since JerryJiang sent me his apps source code. After I get the details sorted, I can apply the fix directly into my rom without a need for an app (and create a rom package for others to cook into their roms).
Click to expand...
Click to collapse
Tethering works with the internet sharing in settings. I have no issues what so ever.
I'll beta test if needed. (If it says anything im running win8x86 rtm kinda as my main os)
EDIT
Just saw how big RUU_Spark_W_S_VERIZON_WWE_2.04.605.02_Radio_NV_021 5_NV58008_RELEASE is. I have hughesnet and a 500mb daily cap. I'll have to wait till I'm at my grandparents(I'm 19) where dsl is king tomorrow. lol
thals1992 said:
Tethering works with the internet sharing in settings. I have no issues what so ever.
I'll beta test if needed. (If it says anything im running win8x86 rtm kinda as my main os)
EDIT
Just saw how big RUU_Spark_W_S_VERIZON_WWE_2.04.605.02_Radio_NV_021 5_NV58008_RELEASE is. I have hughesnet and a 500mb daily cap. I'll have to wait till I'm at my grandparents(I'm 19) where dsl is king tomorrow. lol
Click to expand...
Click to collapse
That is the rom for flashing back to stock. You'll need the older rom in the HSPL thread to downgrade the bootloader. Get both roms and back them up if bandwidth is a problem.
So, I finally got to download the RUU_Spark_W_VERIZON_WWE_1.03.605.22_RS0512_2K_4K_hybrid_new_partition_RELEASE and I got it to flash the phone, but now when I try to flash using [ROM_SPARKW][TheXev]XevRev_Beta1a_8835 the phone gets stuck at 0%. I can follow the instructions shown on the program, but it seems to get stuck at the same place.
I can just unplug the phone and turn it back on and i can get calls in the meantime, but it seems I can't proceed.
I tried the dft rom aswell, but it shows the following:
Code:
[Error Description]:
Invalid ModelID. This means that your phone not supported.
This installer supports only limited number of the phones.
SPARK, MOZART, MONDRIAN, GOLD, SCHUBERT.
If you have phone from this list, but still have this error, please contact with DFT team.
[Info]: USBWorkRSPL.cpp (235)
[Error Description]:
ModelID is 'PC402000'. Please report this info to DFT.
[Info]: USBWorkRSPL.cpp (234)
thals1992 said:
So, I finally got to download the RUU_Spark_W_VERIZON_WWE_1.03.605.22_RS0512_2K_4K_hybrid_new_partition_RELEASE and I got it to flash the phone, but now when I try to flash using [ROM_SPARKW][TheXev]XevRev_Beta1a_8835 the phone gets stuck at 0%. I can follow the instructions shown on the program, but it seems to get stuck at the same place.
I can just unplug the phone and turn it back on and i can get calls in the meantime, but it seems I can't proceed.
I tried the dft rom aswell, but it shows the following:
Code:
[Error Description]:
Invalid ModelID. This means that your phone not supported.
This installer supports only limited number of the phones.
SPARK, MOZART, MONDRIAN, GOLD, SCHUBERT.
If you have phone from this list, but still have this error, please contact with DFT team.
[Info]: USBWorkRSPL.cpp (235)
[Error Description]:
ModelID is 'PC402000'. Please report this info to DFT.
[Info]: USBWorkRSPL.cpp (234)
Click to expand...
Click to collapse
You need to install HSPL before you can flash a custom rom. After downgrading the bootloader to 1.3, you can then install HSPL. Follow my guide here for complete instructions, step by step.
GOT IT!
TheXev said:
You need to install HSPL before you can flash a custom rom. After downgrading the bootloader to 1.3, you can then install HSPL. Follow my guide here for complete instructions, step by step.
Click to expand...
Click to collapse
I finally got it to work! Thanks for the help. I had to find the DFT_XSPL_WP7FG3 that I had downloaded a month ago. The DFT HSPL thread didn't seem to have the file anymore.... When I found that rar, it worked perfectly; I'm now running your 7.8 rom!
I'm still unsure how the WM Device Center actually works, but I'll have to take that up with ultrashot. It seems to work intermittently, I can browse all the files on the phone with the pc that I first set it up with, but all it seems to do on my other pc is just show "error" instead of "not connected."
Its probably because I was trying to do all this on Win8x86.
thals1992 said:
I finally got it to work! Thanks for the help. I had to find the DFT_XSPL_WP7FG3 that I had downloaded a month ago. The DFT HSPL thread didn't seem to have the file anymore.... When I found that rar, it worked perfectly; I'm now running your 7.8 rom!
I'm still unsure how the WM Device Center actually works, but I'll have to take that up with ultrashot. It seems to work intermittently, I can browse all the files on the phone with the pc that I first set it up with, but all it seems to do on my other pc is just show "error" instead of "not connected."
Its probably because I was trying to do all this on Win8x86.
Click to expand...
Click to collapse
First start Zune, then WMDC will start working!
TheXev said:
First start Zune, then WMDC will start working!
Click to expand...
Click to collapse
That did the trick. Been using it for a while now. THe only issues I've had has been with GPSKit Tether. MS Streets and Trips doesn't think that the data is NMEA 2.0 compatable, I can open terminal on the port being used, and it shows data. The only thing I would like to see in your build is the updated start icons. Also I can't seem to get the Nokia Counters installed. I got the files to copy from my ringtones to \Windows, but can't seem to get the provxml file to execute.

what does it take to unlock/root/rom my VZW trophy

im on mango with bootloader 3.2.230 im trying to downgrade via RUU but the RUU wont see the device the drivers are installed cause zune sees it without issue my end goal with this is to get it on wp7.8 and unlocked to T-Mobile im a big android modder with an HTC One V so i know howw RUU's work seeing ive used them before its just this one is a little funky
what do i do?
cammykool said:
im on mango with bootloader 3.2.230 im trying to downgrade via RUU but the RUU wont see the device the drivers are installed cause zune sees it without issue my end goal with this is to get it on wp7.8 and unlocked to T-Mobile im a big android modder with an HTC One V so i know howw RUU's work seeing ive used them before its just this one is a little funky
what do i do?
Click to expand...
Click to collapse
The Zune driver is different from the HTC Diagnostic driver that is required to flash roms. If you read my guide stickied to this sub-forum, "[HOWTO] Use DFT HSPL with Verizon Trophy (SparkW only!)" that will show you EVERY step you need to get HSPL installed onto your phone to flash custom roms. This includes explaining what you need to do to install the diagnostic drivers. After HSPL is installed, you can flash any custom rom you want (for SparkW, do not attempt to flash Spark GSM roms to your phone!).
Fortunately, you indeed can downgrade the bootloader via RUU with SparkW... Spark users are not so lucky (they need GoldCard).
As far as unlocking the phone for T-Mobile, you'll be in for a huge disappointment as some have said that the phone will not post HSPA+ speeds on T-Mobile (as the radio and hardware don't support the bands). You'll need to pay an unlock service to security unlock the sim-card slot, but before starting in on all of this, you may want to ask yourself if its worth the effort for a phone that may get stuck in 2G.
Here is an older thread that I replied too on the issue. Here is another thread on unlocking the Verizon Trophy SIM Card slot.
Here is yet another thread on someone who tired to use the phone on StraightTalk and couldn't get above Edge speeds.
Will the diag drivers from my one v work? (Had attempted a PRL change ended miserablely)
Sent from my HTC One V using Tapatalk 2
cammykool said:
Will the diag drivers from my one v work? (Had attempted a PRL change ended miserablely)
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
From my guide:
TheXev said:
IF THE DRIVERS FAIL TO INSTALL automatically, try this first: Click Start=>Printers and Devices=>Right Click on the big computer and select "Device installation settings"=> Select "Yes, do this automatically."=>Save changes.
Click to expand...
Click to collapse
Drivers shouldn't matter. As long as you follow this step to enable Windows to download drivers from Windows Update, you shouldn't need to worry at all as the OS will download them. It's much easier then manually tracking them down, and most Windows 7 installations have the feature disabled by default for some reason. If you do use this method, Windows will ask to install Windows Mobile Device Center.. which is fine since most roms (mine included) have software installed to allow WMDC to be used on WP7.

Categories

Resources