HTC Surround OEM cabs - Surround General

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.

Related

[HOWTO]Vodafone Froyo for DEbrandend Legends

1. DOWNGRADE to 1.31 using this tutorial.
You do this by copying the RUU on your Goldcard and executing it.
2. Keep your Goldcard in, install this RUU.
Maybe other RUU files work too, I tried this one only. After successful install, check for updates on your phone, upgrade to 2.1-update1 and then again to FroYo!
It didnt work for me without step #1.
Edit: Instead of the RUU mentioned above under #2, you may install other Vodafone RUUs adapted to your country. Haven't tried them out though, but the UK Vodafone RUU seemed to work according to macnpaul.
this will give you vodaphone firmware with branded apps/etc? does the vodaphone froyo not have the CID check?
this gave me froyo with a boot screen from A1 and as far as I can tell no vodafone apps.
did you use the RUU_Legend_Vodafone_AT_GER_Mobilkom_1.31.177.3.. instead of the RUU mentioned in the tutorial or after downgrading to 1.31. as explained in the tutorial?
does this involve rooting ?
cos that tutorial seems to be for rooting :\
no, I don´t think this involves routing,
I think this changes the version number for you get no error 140 when loading an older RUU
This method does NOT involve rooting.
Do one step after the other. First you install the first ROM (non-Vodafone), then you install the second ROM and then the upgrade path to froyo is available to you. This avoids the [140] error.
did you use the RUU_Legend_Vodafone_AT_GER_Mobilkom_1.31.177.3.. instead of the RUU mentioned in the tutorial or after downgrading to 1.31. as explained in the tutorial?
Click to expand...
Click to collapse
After downgrading as explained in the tutorial.
RunSeven said:
This method does NOT involve rooting.
Do one step after the other. First you install the first ROM (non-Vodafone), then you install the second ROM and then the upgrade path to froyo is available to you. This avoids the [140] error.
After downgrading as explained in the tutorial.
Click to expand...
Click to collapse
HELP!!
I did exactly as described in the tutorial, i.e. downgraded my debranded Voadafone Legend from 2.05 to 1.31 and then installed the German 1.31 rom. No problems. I then used the phone to upgrade OTA to german vodafone 2.05, again no problem. Finally I then used OTA to get Froyo. The update downloaded OK and seemed to install OK. However, when the phone rebooted the touchscreen doesn't work and I can't unlock the phone to use it. I've tried rebooting several times by removing the battery and also clearing the cache and doing a factory reset - all to no avail. The phone works as a can call it but I can't answer it as tghe screen doesn't work.
As I can't get into the phone at all I can't even set debugging mode to downgrade back to something that works.
Can anybody help me?
Thanks in anicipation.
RunSeven said:
This method does NOT involve rooting.
Do one step after the other. First you install the first ROM (non-Vodafone), then you install the second ROM and then the upgrade path to froyo is available to you. This avoids the [140] error.
After downgrading as explained in the tutorial.
Click to expand...
Click to collapse
HELP!!
I did exactly as described in the tutorial, i.e. downgraded my debranded Voadafone Legend from 2.05 to 1.31 and then installed the German 1.31 rom. No problems. I then used the phone to upgrade OTA to german vodafone 2.05, again no problem. Finally I then used OTA to get Froyo. The update downloaded OK and seemed to install OK. However, when the phone rebooted the touchscreen doesn't work and I can't unlock the phone to use it. I've tried rebooting several times by removing the battery and also clearing the cache and doing a factory reset - all to no avail. The phone works as a can call it but I can't answer it as tghe screen doesn't work.
As I can't get into the phone at all I can't even set debugging mode to downgrade back to something that works.
Can anybody help me?
Thanks in anicipation.
Look here, this might help... others have experienced it too, it does not seem to relate to the update method.
RunSeven said:
Look here, this might help... others have experienced it too, it does not seem to relate to the update method.
Click to expand...
Click to collapse
Yeh, I had a look at that earlier. He managed to get into the phone though so he could make changes. Mine is just stuck solid on the lock screen. I did just notice that when it is starting up the language on the lock screen goes from german to english and then back to german. Weird.
Any other suggestions would be greatly appreciated
you can´t get into bootloader?
nikst4 said:
you can´t get into bootloader?
Click to expand...
Click to collapse
Yes I can. Will that help?
Another thing I tried that didn't help was renaming the German Froyo update file as update.zip and then installing from the SD though recovery. The full intallation seemed to happen but the screen still stays locked.
I also tried extracting firmware.zip from the update, renaming it to legeimg.zip and then puting it on the SD card. With a standard SD card fastboot says incorrect CID or something similar. With a goldcard it says no image or wrong image.
If it's of any use to anybody the Hboot version is on the phone 0.43.0001.
Probably a stupid question, I got a debranded vodafone legend with all the latests updates (apart from 2.2 obviously) and my hboot is 0.43.0001. But where can I check my rom version? Or is it 2.1 as shown under settings - software?
its something like 2.05.405.2 a little bit further down the menu.
Thanks that is what I ment. So I do need to downgrade first. Does anybody happen to have a mirror for the ruu file? Because shipped roms doesn't seem to work atm. All downloads get cut off.
Massive thanks to RunSeven
I followed the link to downgrade but used a vodafone UK rom (instead of the one mentioned) to put my Legend back to how it was before I debranded it. That allowed me to upgrade to FroYo using the OTA updates.
Obviously I now have the branding back, but I can live with that.
Worked for me!!
thanks !
Basically i'm after any advce please.
I debranded my Legend a few weeks ago (was UK Voda) its now on 2.03.405.3
I have an option ota to go to 2.05 then pressumably to froyo.
Do i give it a go, has anybody been able to get debranded to froyo via ota.
Or do i re-create a goldcard and go back to Voda 1.32 which i have downloaded ready.
If i stick with debranded and try froyo will it be any harder to go back to branded Vodafone after?
Or option 3 should i stick where i am and wait for a 2.2 RUU?
mancrunch said:
If i stick with debranded and try froyo will it be any harder to go back to branded Vodafone after?
Click to expand...
Click to collapse
No, it won't be harder, I think. Probably the update to Froyo will fail with debranded rom, that is all.
mancrunch said:
Or option 3 should i stick where i am and wait for a 2.2 RUU?
Click to expand...
Click to collapse
Don't know if that will ever arrive.

[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

Downgrade to No-Do problem

Hi,
I try to downgrade from Mango to Nodo but I have a problem:
When running restore.bat the batch file keeps saying that I dont have zune 4.8 installed ... but I did .... I de-installed and re-installed again ... but no luck ...
Suggestions ?
btw I used:
http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
I think I have the same problem. I have a US Verizon HTC Trophy updated now to Mango 7720 and I'm looking to restore it back to NoDo.
I used the method posted on windowsphonehacker (How to get Mango Beta 2 for non-developers) to update my phone 7712.
It made a backup for me which is in my C drive folder.
Then I recently updated my phone from 7712 to 7720 with the Mango RTM flash that was just released.
So I wanted to see if I could restore back to Nodo and I'm running into problems.
With Zune 4.8 installed, I ran the restore.bat file from the windowsphonehacker post and it said that the version of the windows phone update tool did not match Zune. So I unintalled Zune 4.8, re installed the original Zune 4.7 and ran the restore.bat again. This time, it runs but says "No restore point found."
Anyone have any ideas? If not, is there a stable Verizon US Nodo ROM I can flash to my phone?
Thanks.
Step away from the phone...
I have a similar problem. I successfully updated my Trophy to the first Mango beta, but I'm having a slew of issues getting it up to the latest (final?) Mango release. I can't seem to restore back to anything below 7401... and I'm afraid I won't get the official release in September. I'm generally down a rabbit hole and would just prefer to flash and get back to 7932 as if none of this ever happened.
Any advice for a noob would be appreciated.
thx
Hi, must turn off ur phone n switch to 3 colour page
downgrade problem
Yeah, I did that. It wouldn't flash the phone correctly.... maybe I had the wrong ROM. If anyone can point me to the Verizon Trophy 7392 US ROM I would appreciate it.
666todd666 said:
Yeah, I did that. It wouldn't flash the phone correctly.... maybe I had the wrong ROM. If anyone can point me to the Verizon Trophy 7392 US ROM I would appreciate it.
Click to expand...
Click to collapse
My understanding is that you will not be able to accomplish your task. The multi-color screen on the Verizon Trophy does not allow loading of ROMs since it cannot be unlock. Unless I am misunderstanding this. Shouldn't you be able to restore to a previous point in the Zune software?

[Q] Updating HD2 to WP7 Mango (Yuki XBmod Back to the Future Rom)

Sorry for posting this here, but it wont let me post a reply in the developer thread because i am that much of a noob. But while trying to update this ROM to 7392 from 7008, the Zune software just claims that i have the most up to date version. I have looked through all of the other threads and i can't find anyone with the same problem as me. I've done everything in the right order
>(I already had HSPL
>Revert to WM6.5 Stock Rom
>Install 2.15 radio
>Install MAGDLR 3.13
>Uselast24nand and ClearSD MBR
>USB Flasher install HD2_Updatable_XBmod_Yuki_v2_native.zip (7004)
>Ive set the time and date perfectly
>Launch Zune update to 7008
>Restarts but doesnt find any further updates
>Everything hurts. My body cant take it.
try this http://forum.xda-developers.com/showthread.php?t=1012189
Get well soon
Edit; welcome to the forum
I can offer you a few suggestions
Reset the phone from about and leave it on "Welcome Page" see if zune detects update..failing that
Force the update
http://www.wpcentral.com/force-mango-update-early-through-zune-software
If that doesnt work
Try sending the devicepro.cab via cab sender(this is knowN to work from 7392 onwards but give it a shot) Tip..when you send via cabsender use B rather then S this will back up your phone if it fails
If you cant update via zune - try the cab method install
Dont abandon hope we all got there in the end let us know how you get on
I had the same problem after flashing the second time.
The cab-solution made it work for me. After that just try and try and try for the 7720 update - sometime it will work!
You guys are AWESOME. It worked and is now in the process of updating to 7720.
Thank you. My body is now ready.

[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.

Categories

Resources